[BT] Added BT for Speech2Text model

What does this PR do?

Fixes #488 (issue)
Before submitting

[x] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[x] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

Description
@younesbelkada
I've followed your suggestion from the documentation here and your suggestion here for the Tapas model. I see that the speech2text encoder layer module was copied from MBart. I'm opening a draft PR as I'm not sure if I missed anything completely and also wasn't sure about the testing for this model.
Please let me know if any fixes are needed, thank you!

Hi @younesbelkada , I just opened this PR from a draft PR. Could you take a look when you have the time, please? I left some comments on the description above for reference. Thank you!

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Removed IExportFactory.

@davkean enlightened me that ExportFactory doesn't need to be mocked, as it has a constructor that takes a parameter. This removes the useless abstraction.
@dotnet/project-system @davkean for review.

👍 Apart from the file name.

@davkean filename fixed.


Issues with new GoogleMutant plugin

Thanks for providing this leaflet plugin which is a really great improvement! Anyway we discovered some issues with the new Google leaflet plugin GoogleMutant
(https://gitlab.com/IvanSanchez/Leaflet.GridLayer.GoogleMutant/) - tiles are missing on basemap change (eg from OSM to Google Roadmap) if the option edgeBufferTiles is not explicitly set to 0 for GoogleMutant basemaps. Perhaps this could be added to the readme so that other users do not run into the same issue (which took us quite a while to figure out ;-)
Anyway as the edgeBuffer does not work for GoogleMutant in the first run (due to the way tiles are loaded via GoogleMutant), it would be great in the long run if EdgeBuffer support could also be added for GoogleMutant basemaps. We tried to figure out how to best achieve this, but did not succeed here yet - so any help would be much appreciated!

@TolonUK FYI - please see the comment from Ivan on how to add EdgeBuffer support to GoogleMutant at https://gitlab.com/IvanSanchez/Leaflet.GridLayer.GoogleMutant/issues/27#note_23940563 - this does not work yet though - we tried as you can see in the following comment, it only worked if edgeBufferTiles was set to 1. Any help here would be appreciated!

@robertharm Thanks for bringing this to my attention, I'll make the documentation update as you suggest.
I've got a fix for the missing tiles problem, as per https://gitlab.com/IvanSanchez/Leaflet.GridLayer.GoogleMutant/issues/27#note_24035411, but that still doesn't make the edgebuffer functionality work as it should. I'll investigate this further based on the suggestion from @IvanSanchez.

@TolonUK you´re welcome. we did some further tests and it seems GoogleMutant is not working with EdgeBuffer even if we follow the approach from Ivan in # 27 - so therefore we decided to disable EdgeBuffer for GoogleMutant basemaps for now...


Creating new environments info is incorrect.

The Learn about Power Automate environments article incorrectly states "To create environments, you must be a Power Automate administrator". This is not accurate. Any appropriately licensed user can create a production environment in the Power Platform Admin Center unless the default "Who can create production environments" setting has been changed from "Everyone" to "Only specific admins". There are settings for control of trial environment creation as well.

@AaronAdmin Thanks for letting us know about this issue. We are updating the document and the updates will be live later today.


[Nextcloud] [feature] add support for Nextcloud tasks app

Extension
https://www.raycast.com/uetchy/nextcloud
Description
Currently supports: Favorites, Search Files, Show Activity, Deck, Notes.
Would be great if support for Tasks could be added to that list.
Who will benefit from this feature?
Nextcloud users using the Tasks app would be grateful.
Anything else?
Tasks source and issues are here https://github.com/nextcloud/tasks, repo has ~450 stars.
It is a featured Nextcloud app with a 4,5/5 star rating. (https://apps.nextcloud.com/apps/tasks)

Dear bot, why would this be stale?!


Thermostat

Any plans to add?

Not likely. I already have smart thermostats from another manufacturer. It's almost impossible to develop the software without having the device local for testing.


Update Pokémon Service to use Smithy IDL v2

Smithy IDL v2 has long been released and there's good support for it in the server generator. Our example Pokémon Service should reflect standard best practices; we should give a good example and use the latest IDL.

We should also add some complexity to the service to demonstrate some more features.

@timClicks What things did you have in mind? We showcase pretty much everything we support: TLS, Lambda integration, data and event streaming, usual request-reply operations, sensitive data...


rel is a space-separated list

In HTML, rel is a space-separated list of values (like class). This patch implements logic for detecting monetization in such a list. This matches e.g. <link rel="author monetization" href="https://person.example.com">.

@da2x
Thanks, will check this out

closed and noted issue in #833


WIP: Scorecard pull policy

Description of the change:
Motivation for the change:
Checklist
If the pull request includes user-facing changes, extra documentation is required:

[ ] Add a new changelog fragment in changelog/fragments (see changelog/fragments/00-template.yaml)
[ ] Add or update relevant sections of the docs website in website/content/en/docs

Closing as this was purely to debug PR #5054 The problem is that since it is doing an image pull policy of Always it is trying to pull an image from quay that does not exist.


Redis Integration

Redis Integration with Apache Storm Updating Topology status to fast memcache

Key : node-roadMapID+mapID

Separate handling bolts about StatusSpout and TriggerSpout to SchedulingBolt and StatusBolt


Initial changes to remove keyvault and use AAD instead for Computer Vision

Purpose
I've discovered from the computer vision team that we can use Bearer header with Azure credential token provider. I'm testing this change more thoroughly but initial experiments look good.
Does this introduce a breaking change?

[ ] Yes
[X] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[X] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

Testing azd up with GPT-4-V, both locally and deployed should work

Update: I need to update prepdocs as well.

This is blocked on the Azure credential bearer token not working in App Service. Works fine locally.

Code to try it in SSH (failing now)
>>> import aiohttp
>>> from azure.identity import DefaultAzureCredential, get_bearer_token_provider
>>> azure_credential = DefaultAzureCredential(exclude_shared_token_cache_credential=True)
>>> token_provider = get_bearer_token_provider(azure_credential, "https://cognitiveservices.azure.com/.default")
>>> url = 'https://cog-cv-qn2a735t7pshk.cognitiveservices.azure.com/computervision/retrieval:vectorizeText?api-version=2023-02-01-preview&modelVersion=latest'
>>> headers = {"Content-Type": "application/json"}
>>> params = {"api-version": "2023-02-01-preview", "modelVersion": "latest"}
>>> data = {"text": 'puppy'}
>>> headers["Authorization"] = "Bearer " + token_provider()
>>> import requests
>>> response = requests.post(url, json=data, headers=headers, params=params)

I realized I was missing a role, this now works for me locally and in production. @mattgotteiner Please try it out if you have the time.


Make azure sdk as optional dependency in spring-integration-azure

Codecov Report

Merging #77 into master will decrease coverage by 0.08%.
The diff coverage is 42.85%.

@@             Coverage Diff              @@
##             master      #77      +/-   ##
============================================
- Coverage     40.51%   40.43%   -0.09%
- Complexity      139      140       +1
============================================
  Files            57       57
  Lines           770      774       +4
  Branches         45       45
============================================
+ Hits            312      313       +1
- Misses          428      431       +3
  Partials         30       30

Impacted Files
Coverage Δ
Complexity Δ

...loud/autoconfigure/telemetry/TelemetryTracker.java
53.12% <0%> (ø)
6 <0> (ø)
:arrow_down:

...nfigure/context/AzureContextAutoConfiguration.java
50% <50%> (-12.5%)
3 <2> (+1)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fc29508...bf263b7. Read the comment docs.


Android performance regression: view flattening is broken (0.71)

Description
After updating from React Native 0.67 to 0.71 (still using the old architecture), we noticed our view hierarchy has grown significantly.
While debugging the issue, we noticed there now seems to be a 1:1 relations ship between React components and actual views on the screen.
The issue started happening after the introduction of accessibilityValue (https://github.com/facebook/react-native/commit/e8739e962de3398bc7e42675b1d87ab35993f705) and accessibilityState (https://github.com/facebook/react-native/commit/98d84e571df64b00e1ed3484923a1d8169dcfda1).
Both objects (even if empty) are passed into all components, and, as a result, seem to be skipped while flattening the hierarchy.
On the positive side, this issue seems to be (accidentally?) fixed in 0.72 already: https://github.com/facebook/react-native/commit/3681df287835f5467a2ad5afe950eae16b95fd8b. Instead of always passing the accessibility value object, it's now only passed in if one of the values is actually present.
For the time being, we managed to restore view flattening by applying the following patch:
diff --git a/node_modules/react-native/Libraries/Components/View/View.js b/node_modules/react-native/Libraries/Components/View/View.js
index 8ef1f81..c0deb96 100644
--- a/node_modules/react-native/Libraries/Components/View/View.js
+++ b/node_modules/react-native/Libraries/Components/View/View.js

@@ -66,20 +66,39 @@ const View: React.AbstractComponent<
     const _accessibilityLabelledBy =
       ariaLabelledBy?.split(/\s*,\s*/g) ?? accessibilityLabelledBy;

-    const _accessibilityState = {
-      busy: ariaBusy ?? accessibilityState?.busy,
-      checked: ariaChecked ?? accessibilityState?.checked,
-      disabled: ariaDisabled ?? accessibilityState?.disabled,
-      expanded: ariaExpanded ?? accessibilityState?.expanded,
-      selected: ariaSelected ?? accessibilityState?.selected,
-    };
+    let _accessibilityState;
+    if (
+      accessibilityState != null ||
+      ariaBusy != null ||
+      ariaChecked != null ||
+      ariaDisabled != null ||
+      ariaExpanded != null ||
+      ariaSelected != null
+    ) {
+      _accessibilityState = {
+        busy: ariaBusy ?? accessibilityState?.busy,
+        checked: ariaChecked ?? accessibilityState?.checked,
+        disabled: ariaDisabled ?? accessibilityState?.disabled,
+        expanded: ariaExpanded ?? accessibilityState?.expanded,
+        selected: ariaSelected ?? accessibilityState?.selected,
+      };
+    }

-    const _accessibilityValue = {
-      max: ariaValueMax ?? accessibilityValue?.max,
-      min: ariaValueMin ?? accessibilityValue?.min,
-      now: ariaValueNow ?? accessibilityValue?.now,
-      text: ariaValueText ?? accessibilityValue?.text,
-    };
+    let _accessibilityValue;
+    if (
+      accessibilityValue != null ||
+      ariaValueMax != null ||
+      ariaValueMin != null ||
+      ariaValueNow != null ||
+      ariaValueText != null
+    ) {
+      _accessibilityValue = {
+        max: ariaValueMax ?? accessibilityValue?.max,
+        min: ariaValueMin ?? accessibilityValue?.min,
+        now: ariaValueNow ?? accessibilityValue?.now,
+        text: ariaValueText ?? accessibilityValue?.text,
+      };
+    }

React Native Version
0.71.10
Output of npx react-native info
System:
    OS: macOS 13.0
    CPU: (10) arm64 Apple M1 Pro
    Memory: 139.69 MB / 32.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.14.0 - ~/.nvm/versions/node/v16.14.0/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 8.3.1 - ~/.nvm/versions/node/v16.14.0/bin/npm
    Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
  Managers:
    CocoaPods: 1.12.0 - /Users/lucastwisk/.rbenv/shims/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 22.1, iOS 16.1, macOS 13.0, tvOS 16.1, watchOS 9.1
    Android SDK: Not Found
  IDEs:
    Android Studio: 2022.2 AI-222.4459.24.2221.9971841
    Xcode: 14.1/14B47b - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.14 - /Users/lucastwisk/.jenv/shims/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 18.2.0 => 18.2.0
    react-native: 0.71.8 => 0.71.8
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Steps to reproduce
Here's a Snack containing a reproduction project: https://snack.expo.dev/@lctwisk/flattening-repro-project
In this project, we've added an example component, taken from the view flattening docs.
We've used the Android layout inspector to retrieve the view hierarchy.
First without the fix:
view_hierarchy_without_fix.txt
And after, with the fix applied:
view_hierarchy_with_fix.txt
Even for a tiny component, there's a clear difference in the size of the view hierarchy.
Snack, code example, screenshot, or link to a repository
https://snack.expo.dev/@lctwisk/flattening-repro-project

Added a request to back port the fix to 0.71 https://github.com/reactwg/react-native-releases/discussions/70#discussioncomment-6162288.

For those of you that came across this thread like I did, this issue also applies if React Native was being too aggressive with the view flattening on Android .
Updating to RN 0.71.12 fix the issue for me 😄

For those of you that came across this thread like I did, this issue also applies if React Native was being too aggressive with the view flattening on Android .
Updating to RN 0.71.12 fix the issue for me 😄


python311Packages.pysigma-backend-elasticsearch: 1.0.7 -> 1.0.8

Diff: https://github.com/SigmaHQ/pySigma-backend-elasticsearch/compare/refs/tags/v1.0.7...v1.0.8
Changelog: https://github.com/SigmaHQ/pySigma-backend-elasticsearch/releases/tag/v1.0.8
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 259920 run on x86_64-linux 1

6 packages failed to build:

python310Packages.pysigma-backend-opensearch
python310Packages.pysigma-backend-opensearch.dist
python311Packages.pysigma-backend-opensearch
python311Packages.pysigma-backend-opensearch.dist
sigma-cli
sigma-cli.dist

4 packages built:

python310Packages.pysigma-backend-elasticsearch
python310Packages.pysigma-backend-elasticsearch.dist
python311Packages.pysigma-backend-elasticsearch
python311Packages.pysigma-backend-elasticsearch.dist


fix: update governance types for relevant TimeLock events

:tada: This PR is included in version 1.21.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.21.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Api differences with Commercial org?

Seems odd that a cloud api would behave differently, I am on firmware <IP_ADDRESS>CFFD14. Any ideas?

Suggest including handling for this in the check api response:
{"errors": [{"status": "404","title": "NotFoundError"}]}

Thanks for the report, I'd very much like to ensure that the python lib and the HA integration work for commercial orgs too.
Would you be able to share a bit more detail - which schema did you need to alter? I did find issues with get override if the charge point was offline, I have hopefully protected against that with the latest version.

Looks like slug should be used based on the evnex web app:
path={/v2/apps/organisations/${orgSlug}/charge-points}


[Refactor] Shift the audio playing logic for the Effects to the useAudioPlayer custom hook

Currently, the audio-playing logic for the Tracks is consolidated within the useAudioPlayer custom hook. However, the same logic for Effects is not centralized and is present individually within the Effect.jsx file. To maintain a consistent and centralized source of truth, it's advisable to include the audio playing logic for Effects within the useAudioPlayer custom hook.
The task involves:

Modifying the useAudioPlayer custom hook to incorporate the audio playing logic for Effects.
Adjusting the Effects.jsx and EffectCard.jsx components to accommodate this change, ensuring there's no loss of functionality.

@ArvindParekh
Do you mean EffectCard.jsx should also use the useAudioPlayer hook just like Tracks file does?

Yes, precisely. However, the useAudioPlayer hook currently doesn't support the kind of logic that's required for playing "Effect" audios, the logic is still present natively in EffectCard.jsx. It'd be better if there's one single custom hook that takes care of the entire audio logic for both Effects and Tracks.

@ArvindParekh ,
Is this issue still open for contribution?
If yes, maybe I can try it out and see if it can be made as a custom hook.

Hey @sahild91, yes the issue's still open, feel free to work on it if you'd like. We already have a custom hook in place, we'd just like to incorporate the logic of Effects into it.
(You can get the issue assigned to you, and here are the contributing guidelines if you'd like to take a look 👍🏻 )

/assign

Hey @sahild91, just wondering how far you got on this issue, I was thinking of taking a peak at it see what I can do.

/assign


dropbox: 73.4.118 -> 81.4.195

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @

There is no point updating this unless the earlier version can no longer be found as dropbox will update itself after installation.
You can also have a look at maestral as an open-source alternative to the dropbox client.

Weird but dropbox start -i didn't want to upgrade until I made this change
And there is point in upgrading because following your logic there is less probability that newer version will be deleted and no longer found

And there is point in upgrading because following your logic there is less
probability that newer version will be deleted and no longer found

If you've already verified that it works, we might as well merge it. It just doesn't make sense to change this just for the sake of "upgrading" unless the old link stops working.

If you've already verified that it works, we might as well merge it

Yes, let's merge it, I don't want to verify is it really that client was updated because nixpkg was up updated or it was just a fluke, let's merge it just in case

[detached HEAD 564a4c6512a] dropbox: 73.4.118 -> 81.4.195
Author: Serhii Khoma<EMAIL_ADDRESS>Date: Thu Sep 19 20:26:50 2019 +0300
1 file changed, 1 insertion(+), 1 deletion(-)

[detached HEAD 55724cea1de] dropbox: 63.4.107 -> 73.4.118
Author: Langston Barrett<EMAIL_ADDRESS>Date: Sun May 26 10:34:09 2019 -0700
1 file changed, 1 insertion(+), 1 deletion(-)
[detached HEAD 73aec98c72e] dropbox: 73.4.118 -> 81.4.195
Author: Serhii Khoma<EMAIL_ADDRESS>Date: Thu Sep 19 20:26:50 2019 +0300
1 file changed, 1 insertion(+), 1 deletion(-)


EU Exit Data Export

This adds a new Rake task which exports data from the publishing-api as requested by the EU exit team. The task takes a few hours to run.
It's an export of content items from Whitehall for each organisation, with information about what taxons that content is tagged to, a CSV file with these headings title,url,last updated,document type,the taxons it is tagged to,"Is this Brexit-related?".
I've intentionally not added tests to this class because I don't think they would add any value for something we will run once, but happy to include some if people think it is worth it.
Paired with @binaryberry and @jonodrew.
This is the first part of Trello Card.

Replaced by https://github.com/alphagov/publishing-api/pull/1253


add FindTagsAppend()

I suggest a FindTags() version that can minimize memory allocations, which is implemented in this PR.
The PR introduces FindTagsAppend(), which uses a destination slice instead of allocating it inside the function. The slice can be pre-allocated by the caller, and re-used between successive calls.

Thanks @pforemski. Good idea, I'll take a look. Sorry for the delay - I need to update my GitHub notifications :)

Thanks @pforemski. Good idea, I'll take a look. Sorry for the delay - I need to update my GitHub notifications :)

Any chance to merge this anytime soon? I'd love to go back using the mainstream repo ;)

@pforemski This is really great stuff - thank you so much. I took your idea and ran with it.
I'm not maintaining backwards compatibility. It'll require minor changes to update, but everyone's performance will improve because of it. I just converted the FindTags to your FindTagsAppend, updated FindDeepestTags and FindTagsWithFilter in the same vein, and added a buffer parameter to the Delete method.
While I was at it, I got rid of the unused error return values - as you noticed, they're all returning nil anyway.
Check this out - old code vs new on Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz in a VM:
BenchmarkFindTags-5                     	 3721257	       294.3 ns/op	     160 B/op	       6 allocs/op
BenchmarkFindTags-5                     	41273214	        28.12 ns/op	       0 B/op	       0 allocs/op

PR accepted with additions in this one https://github.com/kentik/patricia/pull/14
Thanks for the submission!


Fireflies removing with Impulse Noise Reduction

I found that all denoisers are bad at dealing with fireflies, sometimes they make black holes around, which make them look even worse.
RawTherapee is a great, open-source image editor which has a nice tool to remove fireflies called Impulse Noise Reduction.
So i'm curious what if integrate this algorithm into denoiser pipeline, maybe it would give a more neat result?
Example 1:

Example 2:

Example 3:

Example 4:

Isn't that the same as clamping?
What is the difference between the Raw Therapy algo and clamping at render time?

Clamping at render time should work a lot better because it is done sample by sample while Raw Therapy can works only on the end result (the sum of all samples).

Isn't that the same as clamping?

It was my first thought too
But if clamp affect big bright areas, impulse denoise handle only pixels, both bright and dark.
Fireflies remain on the clamped image even after denoise.
Clamp with impulse denoise:


XGrabPointer makes mouse_button_callback stop triggering

So using XGrabPointer to lock mouse pointer inside window makes mouse_button_callback stop procing. Calling XUngrabPointer makes it start working again.
In my particular use case I need to both render the cursor AND constrain it inside the window. Currently the RAW cursor mode of glfw does not allow this, it hides the pointer.

This seems silly on my part, the 3rd param should be True and it receives events again.


Filepulse connector using on AWS MSK

Hi
I am using Filepulse 2.9.0 version on MSK to connect to s3 to read json files and push to topic.
Connector created successfully. But connector not listing files.
Starting to list object files using:
AmazonS3FileSystemListing (io.streamthoughts.kafka.connect.filepulse.fs.DefaultFileSystemMonitor:283)
Completed object files listing. '0' object files found in 72ms
I have json files in s3 path. I don't see any error in log as well.
Here is the connect config used.
connector.class=io.streamthoughts.kafka.connect.filepulse.source.FilePulseSourceConnector
filters=ParseJSON, ExcludeFieldMessage
filters.ParseJSON.type=io.streamthoughts.kafka.connect.filepulse.filter.JSONFilter
filters.ParseJSON.source=message
filters.ParseJSON.merge=true
filters.ExcludeFieldMessage.type=io.streamthoughts.kafka.connect.filepulse.filter.ExcludeFilter
filters.ExcludeFieldMessage.fields=message
fs.cleanup.policy.class=io.streamthoughts.kafka.connect.filepulse.fs.clean.LogCleanupPolicy
fs.cleanup.policy.triggered.on=COMMITTED
fs.listing.class=io.streamthoughts.kafka.connect.filepulse.fs.AmazonS3FileSystemListing
fs.listing.filters=io.streamthoughts.kafka.connect.filepulse.fs.filter.RegexFileListFilter
fs.listing.interval.ms=10000
file.filter.regex.pattern=.\.json$
offset.policy.class=io.streamthoughts.kafka.connect.filepulse.offset.DefaultSourceOffsetPolicy
offset.attributes.string=name
skip.headers=1
topic=connect-file-s3-test-json
tasks.reader.class=io.streamthoughts.kafka.connect.filepulse.fs.reader.AmazonS3BytesArrayInputReader
tasks.file.status.storage.class=io.streamthoughts.kafka.connect.filepulse.state.KafkaFileObjectStateBackingStore
tasks.file.status.storage.bootstrap.serversbroker=********
tasks.file.status.storage.topic.partitions=10
tasks.file.status.storage.topic.replication.factor=1
tasks.max=1
aws.access.key.id=*********
aws.secret.access.key=********
aws.s3.region=******
aws.s3.bucket.name=******
aws.s3.bucket.prefix=*****/****

Hi @iamsamba, it seems the connector does not see any S3 object due to the log Completed object files listing. '0' object files found. Maybe you should double-check the aws.s3.bucket.prefix property. In addition, make sure the configured prefix is not ending with /. In addition, make sure you have granted access to your S3 folders.

Hi @iamsamba, it seems the connector does not see any S3 object due to the log Completed object files listing. '0' object files found. Maybe you should double-check the aws.s3.bucket.prefix property. In addition, make sure the configured prefix is not ending with /. In addition, make sure you have granted access to your S3 folders.

Thanks @fhussonnois, it helps. Able to list files now.


ops.linspace broken in Tensorflow when num is a tf.Tensor

When using ops.linspace with Tensorflow backend, if the num argument is a tf.Tensor the code will break here:
https://github.com/keras-team/keras/blob/a243d91e43b4c43fe8d184b541b608b6ddd80f71/keras/src/backend/tensorflow/numpy.py#L1332
Because start and stop are required to be floats, num is required to be int and TF won't auto cast a tf.Tensor, computing the step like this will cause the issue.
To test you can run this:
ops.linspace(0.0, 1.0, ops.conver_to_tensor(10))
And a mere cast should do for the fix.

Hi @gustavoeb ,
Thanks for the report. I have reproduced the issue and attached gist here. The Op linspace is breaking when the value of num is int or float

Hi @gustavoeb - thank you for reporting this. Would you be interested in contributing the fix?
I believe it should just be adding num = convert_to_tensor(num, dtype=tf.int64) under https://github.com/keras-team/keras/blob/a243d91e43b4c43fe8d184b541b608b6ddd80f71/keras/src/backend/tensorflow/numpy.py#L1323 but you would have to confirm execution works.

@grasskin seems like it is already close now, maybe next time :)


How to switch language to display?

I looked at the documentation and I couldn't find a way to change the user language, any help?

I hasn't found it too, but you can change the language on this way:
Source in vb.net:
WPFLocalizeExtension.Engine.LocalizeDictionary.Instance.Culture = System.Globalization.CultureInfo.CreateSpecificCulture("de")

or for C#
look at this Example Code:
https://github.com/SeriousM/WPFLocalizationExtension/blob/master/Tests/LocalizationTest/App.xaml.cs
You can find example sources (C#, VB, SL, Phone, etc.) in Tests - folder:
https://github.com/SeriousM/WPFLocalizationExtension/tree/master/Tests

Thanks a lot, I didn't know about the examples in the Tests directory.
I will try what you suggested, thanks.
On Wed, Jul 22, 2015 at 4:51 PM Ueli Hilfiker<EMAIL_ADDRESS>wrote:

or for C#
look at this Example Code:
https://github.com/SeriousM/WPFLocalizationExtension/blob/master/Tests/LocalizationTest/App.xaml.cs
You can find example sources (C#, VB, SL, Phone, etc.) in Tests - folder:
https://github.com/SeriousM/WPFLocalizationExtension/tree/master/Tests
—
Reply to this email directly or view it on GitHub
https://github.com/SeriousM/WPFLocalizationExtension/issues/66#issuecomment-123747908
.

Your first example worked perfectly, thanks a lot!


[3270] [3265] [3260] General content tweaks

Context
https://trello.com/c/HPMGB4uA/3270-snag-you-cannot-withdraw-this-trainee-page-content-update
https://trello.com/c/QvDbu51Q/3265-snag-deleting-a-trainee-you-cannot-delete-this-record-content-update
https://trello.com/c/NN1wWZs1/3260-snag-record-action-bar-trainee-status-content-update
Changes proposed in this pull request
Updates content to match prototype on following pages:

trainees/{slug}/withdrawal-forbidden
trainees/{slug}/delete-forbidden
On trainees/{slug} record status bar for trainees who are pending TRN and deferred (record -> trainee)

Guidance to review

Check the content against the prototype.

 [SNAG] "You cannot withdraw this trainee" page - content update

 [SNAG] Deleting a trainee - "You cannot delete this record" content update

 [SNAG] Record action bar - trainee status content update

The heading size for this question is "govuk-fieldset__legend--m" it should be an "l" to be consistent with the rest of the question pages.


FindNexMerkleRootAfterReset

an RPC that given an Reset seqno and the prev merkle signed into the reset record, find the next merkle root that contains the reset

There's a test included, and tested manually on the CLI via:
 ~/src/go/bin/keybase --run-mode=prod --home=/tmp/x --standalone fnmr -r 3 cafe40a5e60f33d87ca3501c60602900
{"res":{"seqno":2966733,"hashMeta":"860a9e8ed8c9fb4d125e5ae0948673b2348a85c2d9cf02574b44f58208454dc3"}}

cc: @strib


[#207] Improve error message for incorrect date

Fixes #207
Improved the message constraint when a user enters a ContactedDate in the wrong format.

Codecov Report

Merging #237 (5916643) into master (511b42f) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #237   +/-   ##
=========================================
  Coverage     70.59%   70.59%
  Complexity      621      621
=========================================
  Files            96       96
  Lines          2034     2034
  Branches        223      223
=========================================
  Hits           1436     1436
  Misses          515      515
  Partials         83       83

Impacted Files
Coverage Δ

...java/seedu/address/model/person/ContactedDate.java
95.83% <ø> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 511b42f...5916643. Read the comment docs.


conditional wgan

Could you release your source code of conditional WGAN-GP for cifar 10 (as shown in Figure 5 in your updated v2 manuscript)? Thanks.

Just curious if you are planning to release it or not. Thanks!

Sorry for the delay. We are planning on releasing code for that model soon.

From: tenoyart<EMAIL_ADDRESS>Sent: Monday, June 12, 2017 11:21:15 AM
To: igul222/improved_wgan_training
Cc: Subscribed
Subject: Re: [igul222/improved_wgan_training] conditional wgan (#29)
Just curious if you are planning to release it or not. Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/igul222/improved_wgan_training/issues/29#issuecomment-307840691, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABBP7o69QcAZi7jP3ryjl1pTUTpcQUkiks5sDWV7gaJpZM4N1kAY.

Great, thanks! Looking forward to that.


💡[Feature]: Face Mask Detection

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
Face mask detection using machine learning has several important applications-
Public Health and Safety, Automated Monitoring, Access Control.
The model uses Convolutional Neural Network.
Use Case

Benefits

Add ScreenShots

Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@sanjay-kv can you please assign me this issue


Fix: HTML string inputs should not have a size attribute valorized with 0

Related to https://github.com/rails/rails/pull/14579

Thanks :ok_hand: :

Thanks to you @mshibuya :smile:


[UI] usability nit-pick

Rancher Version: 1.0.0
There is no visual cue as to which submenu is open... which can cause some minor confusion.
This example shot suggests that we're looking at the submenu for applications.. alas, we're not (for newcomers, it's the catalog submenu)

As the headline says, this is rather minor, but would be nice to have addressed. ;)

D'oh, there's supposed to be an off-white caret there to match the background but it's only shown on hover of the top-nav:

Version - master 4/1
Verified fixed


Implement Heap_Array_Nth

Unlike the array index operator, this would allow the client to pull multiple instances of the same linear value out of a Heap_Array of linear values. This is pretty much necessary for any unsafe code using generic heap arrays.

Closed because Heap_Array has been merged into Pointer. Superseded by  #110


Fix escaping of the escape quotes in Strings

@NikCharlebois
This PR fixes the escaping of escape quotes in Strings. Example:
"<table border=0 cellspacing=0 cellpadding=0 align=left width=`"100%`">" would be escaped to "
", which is invalid because the escape quotes for the " double quotes are not escaped themselves, leading to a parse error within PowerShell.
The implemented solution is to first escape the escape quotes within the strings and then escape the standard double quotes. New result: "<table border=0 cellspacing=0 cellpadding=0 align=left width=```"100%```">", which is valid PowerShell.

Fixes https://github.com/microsoft/Microsoft365DSC/issues/5135

This change is

Thanks for taking a look at this issue.
Just out of curiosity what would happen if we remove any invalid escaping? In your example, there is already a double escape instead of a single escape. This does not look good to me.
If there is no other option left, go for it. 😉

@andikrueger I just had to update my first example, GitHub broke the design of it 😆 To answer your question: I'd say it's not up to us to decide if we should remove the escaping quotes inside of a string. Our job is to escape these escape quotes and make sure they work inside of what we want to achieve with them. Removing the escape quotes in a string (before being processed by us) would result in a different configuration exported than what was inputted by the user in e.g. EXO (the transport rule for our example with some HTML things).

Very true. Our job is to maintain the original structure and if this means even more escaping: yes.


Add filesystem api

This PR adds the following improvements
1.. Introduces a basic FileSystem API.
2. Implements LocalFileSystem
3. Adds an explicit FileSystem registry.

Perhaps, upgrade the PR from draft status.

@mbasmanova this change will likely require the invocation of registerLocalFileSystem() on the Prestissimo side. Would you prefer if I added a PR there for that?


How to pass empty password

await MySQLConnection.createConnection( host: '<IP_ADDRESS>', port: 3306, userName: 'root', password: 'root', databaseName: 'coba_dart_mysql', secure: false, );
hi, thank you for making this excellent package,
i just wanna ask, for connection sometime our local mysqldb not require the password,
how to handle this case? thx

This flow is not implemented... I don't think it's hard to implement, but currently I have lack of time, maybe next week I will check it out. You can provide some password as a workaround before it's implemented

okay i see, thankyou for your response, appreciate


Add geo location bypass option

youtube-dl tool has some options to bypass geo location by faking X-Forward-For http headers, for example:
    --geo-verification-proxy URL         Use this proxy to verify the IP address for some geo-restricted sites. The default proxy specified by --proxy (or none, if the option is not present) is used for the actual downloading.
    --geo-bypass                         Bypass geographic restriction via faking X-Forwarded-For HTTP header
    --no-geo-bypass                      Do not bypass geographic restriction via faking X-Forwarded-For HTTP header
    --geo-bypass-country CODE            Force bypass geographic restriction with explicitly provided two-letter ISO 3166-2 country code
    --geo-bypass-ip-block IP_BLOCK       Force bypass geographic restriction with explicitly provided IP block in CIDR notation

So maybe we can have something like that for the youtube-search-python as well?

Sorry, but I have no interest in reverse-engineering youtube-dl just for this header. I know, there exists an MDN page about this HTTP header, but I just don't have the interest needed. In the end, I'd be happy to accept pull requests. Marking this as good first issue and help wanted.


Automatically fallback to default CPU execution if a parfor cannot be offloaded to a SYCL GPU device

Currently for any NumPy operation or parfor that is not offloadable to a SYCL GPU we throw an exception. A more optimal behavior from a user experience will be to fallback to the default Numba behavior and run the code on the CPU.
Closed when PR #8 gets merged.

PR https://github.com/IntelPython/numba/pull/8 got merged. Closing this issue.


Add shell script to generate certificates + update README.md to use openssl CLI

Modifications added :

Rename app name to ssl-2way to prevent misunderstanding with the official openssl CLI.
Add shell script to generate certificates & private keys.
Update README.md so official openssl CLI can be used as the server or the client to validate the example.

Thank you very much for the PR!


Scrolling

Top & bottom 10% for fast scroll (stop when you leave this zone)

Send up/down key event at height 'y'


Improve the orbit eye  origin

One aspect that I consistently found to behave is surprising way is the orbit origin of the 3D view eye, and I have reasons to believe that I'm not alone.
After spending some time in OnShape, I noticed that it uses the bbox center of the geometry visible on screen as default orbit point. Also, if an hovered object is (right-)clicked, then it is used as orbit point instead. We should consider implementing something similar.
https://github.com/rerun-io/rerun/assets/49431240/45d5b463-4f7e-4030-9753-4dd31f85b664
https://github.com/rerun-io/rerun/assets/49431240/c6d50db4-72d8-4224-a40a-821640c83ed4

Using the centre of bounding box of all displayed objects (on screen or otherwise) would already be an improvement IMO.

Dual cube OnShape playground: https://cad.onshape.com/documents/6183b6e53b67ad1a89aa7abb/w/cbc3cec32eb338f09732aa38/e/702de136749c7ed77764f756?renderMode=0&uiState=65eebcf38b06243496523313

I noticed that it uses the bbox center of the geometry visible on screen as default orbit point.

doesn't seem to be the case, once two boxes are on screen it doesn't orbit around the center of those two, only if there's a single one on screen. I'm a bit unclear what it orbits around actually.
Taking our orbit camera model as-is today and change the orbit center also means changing the camera's position, thus completely changing the screen's content. This clearly doesn't happen in onshape, they decouple this somehow further.
What might be related is that the pan operation changes the camera's center point on the image plane, not the camera position. Something we don't support at all.

someone in this thread called this style of orbiting "mcad style", maybe that gives us some pointers to look deeper into this later :)


[Unity/Android]Build apk Error

Hello,
I use [Particle Unity SDK 1.3.4]  project. export apk error.
Please help to check.
Configuration:
Unity 2022.3.17f1

Configure project :
Build was configured to prefer settings repositories over project repositories but repository 'Google' was added by build file 'build.gradle'
Build was configured to prefer settings repositories over project repositories but repository 'MavenRepo' was added by build file 'build.gradle'
Build was configured to prefer settings repositories over project repositories but repository 'maven' was added by build file 'build.gradle'
Build was configured to prefer settings repositories over project repositories but repository 'maven2' was added by build file 'build.gradle'
Build was configured to prefer settings repositories over project repositories but repository 'maven3' was added by build file 'build.gradle'
Build was configured to prefer settings repositories over project repositories but repository 'maven4' was added by build file 'build.gradle'
Build was configured to prefer settings repositories over project repositories but repository 'flatDir' was added by build file 'build.gradle'

Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8
FAILURE: Build failed with an exception.

Where:
Build file 'D:\Unity\particle-unity-release-1.3.4\Library\Bee\Android\Prj\Mono2x\Gradle\launcher\build.gradle' line: 1

What went wrong:
A problem occurred evaluating project ':launcher'.

Failed to apply plugin 'com.android.internal.version-check'.
Cannot parse project property android.enableR8='' of type 'class java.lang.String' as boolean. Expected 'true' or 'false'.

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 640ms

Put all error messages from Android Studio into a txt file


web doc needs to be fixed after vue3 compatibility

@change => @update:modelValue
value => modelValue
For search, radio and maybe others.

:tada: This issue has been resolved in version 1.4.0-rc.14 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 2.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


chore: bump @okp4/ui to 1.11.0

This PR bumps @okp4/ui from 1.10.0 to 1.11.0 that embeds the SVG sprites fix for Safari.
👉 closes https://github.com/okp4/faucet-web/issues/59

:tada: This PR is included in version 1.0.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Enable property checking customization in test file

This PR provides supports for customization of property checking in test file. We provide the features of

Excluding the resource reference property checking automatically.
Supporting property_check_includes field to specify the properties users want to include from all the properties listed in property filed.
Supporting property_check_excludes field to specify the properties users want to exclude.
When both are specified, we use property_check_includes rather than property_check_excludes.

The customization rules in the basic.yaml or complete.yaml are

The two filed are designed to be array of strings.
Using the terraform state representation to specify the property.
Using prop* to represent all the sub-properties inside the prop.

Here is an example.  And this results in checking only all the representations with prefix custom_rules.1 in test file.
--- !ruby/object:Provider::Azure::Example
resource: azurerm_web_application_firewall_policy
prerequisites:
 - !ruby/object:Provider::Azure::ExampleReference
   product: resourcegroup
   example: basic
properties:
 name: "<%= get_resource_name('ApplicationGatewayWebApplicationFirewallPolicies', 'wafpolicy') -%>"
 resource_group_name: ${azurerm_resource_group.<%= resource_id_hint -%>.name}
 location: ${azurerm_resource_group.<%= resource_id_hint -%>.location}
 custom_rules:
   - name: Rule1
     priority: 1
     rule_type: MatchRule
     match_conditions:
       - match_variables:
           - variable_name: RemoteAddr
         operator: IPMatch
         negation_conditon: false
         match_values: [<IP_ADDRESS>/24, <IP_ADDRESS>/24]
     action: Block
   - name: Rule2
     priority: 2
     rule_type: MatchRule
     match_conditions:
       - match_variables:
           - variable_name: RemoteAddr
         operator: IPMatch
         negation_conditon: false
         match_values: [<IP_ADDRESS>/24]
       - match_variables:
           - variable_name: RequestHeaders
             selector: UserAgent
         operator: Contains
         negation_conditon: false
         match_values: [Windows]
     action: Block
property_check_excludes:
 - custom_rules.#
 - custom_rules.0.*

This PR solves the issue #25.


Roll engine 876c4c339064..7d3caf895255 (3 commits)

https://github.com/flutter/engine/compare/876c4c339064...7d3caf895255
git log 876c4c339064ed321f37fba61422194d84cbfdb7..7d3caf895255f9f7d9f553563c6e888147d1a428 --no-merges --oneline
7d3caf895 Avoid leaking the VM in runtime_unittests and update failing tests. (flutter/engine#8626)
91b71070f Revert "Add a unit test for PhysicalShapeLayer (#8616)" (flutter/engine#8627)
8b667b017 Add a unit test for PhysicalShapeLayer (flutter/engine#8616)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff (cbracken@google.com), and stop
the roller if necessary.

Trybots failed. These were the failed builds: https://cirrus-ci.com/task/6684120221483008

Commit queue failed; closing this roll.


🚀 Feature: Remove the ComponentType type where possible

🔖 Feature description
Remove the ComponentType type where possible.
🎤 Context
According to ADR006 backstage wants to avoid use of the types FC and SFC; however, ComponentType is a superset of the two types. Therefore, all references to the ComponentType type should be removed where possible.
✌ Possible Implementation
Backstage should switch to the (props: ...) => JSX.Element type because it is what most codebases use with the additional benefit of better intellisense and stricter types. This will also help with the React 18 migration.
👀 Have you spent some time to check if this feature request has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
Yes I am willing to submit a PR!

ComponentType is a superset of the two types. Therefore, all references to the ComponentType type should be removed where possible

I don't think we should do that at this point. React 18 addressed the children issue, and I think that going forward we may want to keep using that type where it makes sense, especially as an input type.

Hello @freben
There are two primary rationales for discontinuing the use of the React.ComponentType type within our codebase. Firstly, this decision aligns with our architectural choice to remove React.FunctionalComponent from our codebase, as using React.ComponentType is just a superset of React.FunctionalComponent:
type ComponentType<P = {}> = ComponentClass<P> | FunctionComponent<P>;

Secondly, it's recommended to type functional components by annotating the return type with JSX.Element. With the latest React 18 types and TypeScript 5.1, opting for React.FunctionalComponent is mostly a matter of style, while the use of React.FunctionalComponent is discouraged.
For more information please read.

Right, so it agrees that it's mostly a stylistic choice for recent TS+React.
For me personally, I'm happy to CREATE components with implicit types. But does it get a bit more nuanced for INPUT types? As in, places that accept a component as input. What should the standard signature be there?

The explicit vs implicit return type debate is not really a debate when it comes down to providing a library for users for the following reasons.
Pros of explicit return types

Understanding the intent of a function.
Easier to catch yourself doing something strange.
It helps you reason early about your types and make more safe typeguards.
Faster transpile time.

How using explicit return types compounds in a library

Contributors can understand the codebase better.
Contributors can contribute to the codebase without fear of accidently returning the wrong type.
Contributors are less likely to accidently change the return type for downstream users.
Faster transpile time.

Here is a good video going more in depth on why everyone should always use explicit return types.
The input type for a React component are a separate discussion. You should always use the type ReactNode here. There are better ways to handle the typing of a React component than ComponentType. I would be happy to discuss this further if you would like. Ideally through a call or something since it's a rather long discussion. Using ComponentType also adds unnecessary properties such as defaultProps and displayName.

@freben I would suggest reading these two articles on React prop types, they are very insightful.
React.ReactNode vs JSX.Element vs React.ReactElement
How to Pass a Component as a Prop in React

The first one says

I'd also suggest not annotating the return types of your components to avoid confusion - but if you're using TypeScript 5.1, go ahead

and also

In TypeScript versions before 5.1, you can't use React.ReactNode in one specific case - typing the return type of a component.

So does that mean that we need to hold off on that?

@freben

The first one says

I'd also suggest not annotating the return types of your components to avoid confusion - but if you're using TypeScript 5.1, go ahead

Everything should have explicit returns in a library that is meant to be consumed from what I have read. Please read my explanation on "How using explicit return types compounds in a library." I am a bit baffled why there is so much hesitancy in explicit return types. Explicitly declaring return types generally takes only a few seconds anyways. Further, TypeScript is meant to be a type safe language, lets use that power to our advantage.

and also

In TypeScript versions before 5.1, you can't use React.ReactNode in one specific case - typing the return type of a component.

So does that mean that we need to hold off on that? Especially for external-facing interfaces since we don't force anybody to pick a particularly recent TS version as consumers of our libraries.

Yes, at least until TypeScript 5.4 is released because of the TypeScript Releases Policy. In the meantime we can either use JSX.Element or React.ReactElement. I decided to stick with JSX.Element since the codebase is already using it. Ideally, I think if we want to change the return type we should do that in another PR.

Everything should have explicit returns in a library that is meant to be consumed from what I have read. Please read my explanation on "How using explicit return types compounds in a library." I am a bit baffled why there is so much hesitancy in explicit return types. Explicitly declaring return types generally takes only a few seconds anyways. Further, TypeScript is meant to be a type safe language, lets use that power to our advantage.

Oh there really isn't any hesitancy per se. Everyone is perfectly free to add explicit return types to make things better. This is just me pondering how prescriptive or forcing we should be, on the sliding scale between "do as you prefer" all the way over to "we have an ADR, we lint for it, and reject PRs that don't follow convention".
Adding return types in a lot of places as a public service quality improvement - that I really don't have anything against.
One very minor niggle, part of what led me to ask in the first place about these things, is e.g. whether we should do JSX.Element | null as the return type, or just let things go back and forth between | null or not based on circumstances changing over time. Also, which JSX? The global one or React.JSX? I assume the latter.
I'm not saying no, I'm just gathering information and trying to find the best implementation to land on.

In TypeScript versions before 5.1, you can't use React.ReactNode in one specific case - typing the return type of a component.

So does that mean that we need to hold off on that? Especially for external-facing interfaces since we don't force anybody to pick a particularly recent TS version as consumers of our libraries.

Yes, at least until TypeScript 5.4 is released because of the TypeScript Releases Policy. In the meantime we can either use JSX.Element or React.ReactElement. I decided to stick with JSX.Element since the codebase is already using it. Ideally, I think if we want to change the return type we should do that in another PR.

Alright, see above.

@freben

Oh there really isn't any hesitancy per se. Everyone is perfectly free to add explicit return types to make things better. This is just me pondering how prescriptive or forcing we should be, on the sliding scale between "do as you prefer" all the way over to "we have an ADR, we lint for it, and reject PRs that don't follow convention".

Adding return types in a lot of places as a public service quality improvement - that I really don't have anything against.

As you can probably tell, I am in favor of an ADR advocating for explicit return types on the upstream. However, downstream users should be able to decide whether or not to use them. I think this policy would enable the upstream while allowing downstream users to be flexible.

One very minor niggle, part of what led me to ask in the first place about these things, is e.g. whether we should do JSX.Element | null as the return type, or just let things go back and forth between | null or not based on circumstances changing over time. Also, which JSX? The global one or React.JSX? I assume the latter.

I'm not saying no, I'm just gathering information and trying to find the best implementation to land on.

Yeah you are right. I guess I should have looked it up beforehand because I have always thought | null seems weird. Here is a good article on what we should use instead. Apparently returning null will disconnect a child from the DOM tree whereas false will keep child in the DOM tree. Also by returning false we will not need to add | null to the return type since JSX.Element is a superset of boolean.
Correct, React.JSX.

@freben

Am I misreading it entirely, or is this one saying the exact opposite in the null/false debate? Haha :) I'm confused.

React themselves explicitly call out the usage of null, nothing about booleans except as a side effect.

I guess we should read the official React documentation instead of articles haha.

Well that would anyway mean that the return type would have to be React.JSX.Element | boolean, possibly adding | null as well for completeness ... Getting a bit wordy.

I'm slightly in the camp of "is this all really worth it" as you can tell, but I'm keeping an open mind.

I think the return type, when a component potentially returns nothing, should be React.JSX.Element | null  because users can easily infer that a component returns null using intellisense. Whereas, returning false is not mentioned in the official documentation and false is not as clear as null which literally means 0 value. If a component cannot return nothing, the return type should be React.JSX.Element.

I'm gonna bring this back to the original issue. I'm all up for a debate return types but that's not really what this particular issue is about 😅

According to ADR006 backstage wants to avoid use of the types FC and SFC; however, ComponentType is a superset of the two types. Therefore, all references to the ComponentType type should be removed where possible.

Sorry I'm not following this. Just because a type is expressed in terms of a type that we discourage doesn't mean that the reason for the discouragement applies to the former type? Should we also remove all usages of React.lazy because it is expressed in terms of ComponentType as well? We need to weight the benefits and drawbacks of using ComponentType alone, it doesn't matter how it happens to be defined.
In my view ComponentType is the best choice for input types in public API, simply based on its name and it's semantic meaning. It also allows for both class and functional components, which can come in handy if you want error boundaries, but isn't really a big deal nowadays. Now unfortunately ComponentType had this side effect of forcing an optional children prop and so we haven't used it everywhere. With the React 18 fix I do see any other reasons not to use it at this point.
For output types there's perhaps a bit more debate to be had due to the additional static properties that ComponentType has, and it's always nice to keep output types slim. I still feel that it's worth the tradeoff though, as it communicates very clearly what type of value you are receiving. I could imagine a developer of the more junior kind to get confused about () => JSX.Element and call it directly as a function, which of course works! ... maybe ... and then might blow up in the future.

Just because a type is expressed in terms of a type that we discourage doesn't mean that the reason for the discouragement applies to the former type?

If you discourage the usage of said type, should you not also discourage the usage of a superset of said type? When using ComponentType it will always be inferred as the FunctionComponent type because the majority, if not all, the components are functional components. If that is the case, why aren't we using FunctionalComponent? Both of these types have the implicit children problem in React 17. Further, is it not best to narrow the type of a variable to the true "type"? If so, this would mean that you cannot get any closer to the true "type" than (props: Props) => React.JSX.Element.

Should we also remove all usages of React.lazy because it is expressed in terms of ComponentType as well? We need to weight the benefits and drawbacks of using ComponentType alone, it doesn't matter how it happens to be defined.

This is a different discussion because we are consuming those types and have the choice of whether or not we want to emit those types downstream.

In my view ComponentType is the best choice for input types in public API, simply based on its name and it's semantic meaning.

In the future, it may be best to remove passing components as props and adopt the Radix/Headless UI component architecture model. This is beyond the scope of the PR though.

It also allows for both class and functional components, which can come in handy if you want error boundaries, but isn't really a big deal nowadays.

In the future, this will be a non issue because the React Core team are developing an error boundary hook.

For output types there's perhaps a bit more debate to be had due to the additional static properties that ComponentType has, and it's always nice to keep output types slim. I still feel that it's worth the tradeoff though, as it communicates very clearly what type of value you are receiving. I could imagine a developer of the more junior kind to get confused about () => JSX.Element and call it directly as a function, which of course works! ... maybe ... and then might blow up in the future.

I think it is important for React developers to understand the differences between a component and an element at the core level.

When it is a function, it is a component.
When it is JSX, it is an element.

When you add the ComponentType type it hides the fact that a component is a function at its core. React developers need to understand this construct to build proper composable components.
These changes would also help the React 18 migration go smoother.

Yep I think those are some reasonable arguments for the case. Curious if anyone else in the community has any other compelling arguments or preferences, let us know.

Can you ping me when we can move forward with this issue?

not stale

not stale

Hey, we talked among ourselves and went through the arguments put forward, and decided that usage of this type is not something that we see any significant benefit in discouraging. The react 18 migration is also complete at this point without incident. As such, we'll choose to chose this issue. Thanks for sticking with us through the discussion though!


Add let expression parsing

Purpose

Add let expression support

Fixes #23056
Approach

N/A

Samples

N/A

Remarks

N/A

Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[x] Added necessary tests

[x] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

I will fix the falling after updating from upstream.


Added constant and citation for converting cubic meter to gallons.

Added constant and citation for converting cubic meter to gallons.

Thanks!


Bloom Issue

Something obscure is going on when Bloom is first loaded.  In some cases, the node types aren't populated.  This seems to occur intermittently.  Need to figure out what exactly is going on.

Related to perspective in DB.
Per Jeff --- WHERE NOT n:BLOOM_PERSPECTIVE AND NOT n:BLOOM_SCENE

I haven't been able to recreate this.  I think it may have gone away with the introduction of Workbench.  Closing.


Informers cache: don't send updates for non-meaningful Pod/Service updates

The informer clients get often updates about Pods that are not really meaningful to us (they don't affect to the pod information we really want). This PR avoids sending messages after this kind of update.

@marctc having issues with the downgrade :( go mod tidy always updates it to the latest version.
For the moment, I'll update to the very latest version of all the dependencies, even indirect, and see if it is fixed. If not, we'll spend some extra time digging into the dependency map to see which library has a dependency to the kube library v0.31.0.


cli: Add flag to list legacy service BPF maps

This PR:

Adds the --legacy flag which can be passed to the cilium bpf lb list command in order to dump the legacy service BPF maps (addresses https://github.com/cilium/cilium/pull/7639#discussion_r274989402).
Extends the LB runtime tests to check whether the svc legacy and v2 BPF maps are in sync.

This change is

Adding the label wip as some test failures are expected.

test-me-please

test-me-please

test-me-please

Coverage decreased (-0.005%) to 41.89% when pulling fea293e6e415c8c3afb187f22a05591963e3ce84 on pr/brb/bpf-lb-list-legacy into d8474e499ad1fb779827e506890fa327194e56e7 on master.

PTAL - all tests have passed.


Move final message of eligibility questionnaire to income question page

The current eligibility questionnaire flow includes a final page to explain the filter did and what to expect (see #691). In the interest of minimizing the number of pages, it would be great to move the content from this final page to the Income question page (the last page of the questionnaire).
The content currently reads:
"Thank you for checking how you qualify for affordable housing. Because affordable housing can be reserved for certain age groups or income levels, we have filtered our property listings based on your household characteristics. We hope you find housing that meets your needs. It's important to note that a good portion of affordable housing has a waitlist, but calling properties you're interested in is a good way to get on waitlists or learn of immediate openings."
The new content should read:
"Thank you for answering these questions. When you click or tap "See Results Now", you'll see rentals that might fit your needs based on your answers. Multiple factors might can effect eligibility for specific rentals, so if you see a rental you're interested in, contact the Property Agent on the listing. They can help determine if you're eligibility for that rental."
Design is viewable in Figma (03.5).

It looks like this has been fixed.


[WIP]fix(region): struct input for detach server network

这个 PR 实现什么功能/修复什么问题:

[ ] 功能、bugfix描述
[ ] 冒烟测试
[ ] 单元测试编写

是否需要 backport 到之前的 release 分支:

release/3.7

/area region
/cc @zexi

Codecov Report

Merging #10162 (3ff4787) into master (c98df7d) will increase coverage by 5.85%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master   #10162       +/-   ##
===========================================
+ Coverage    5.94%   11.79%    +5.85%
===========================================
  Files         860      234      -626
  Lines      133615    26262   -107353
===========================================
- Hits         7937     3097     -4840
+ Misses     124973    22854   -102119
+ Partials      705      311      -394

Flag
Coverage Δ

aFlag
11.79% <ø> (+5.85%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/cloudcommon/db/lockman/fifo.go
76.92% <0.00%> (-7.70%)
:arrow_down:

pkg/hostman/system_service/sdnagent.go

pkg/multicloud/aws/loadbalancerlistener.go

pkg/util/fileutils2/blkid.go

pkg/cloudcommon/db/apply_manager_method.go

pkg/compute/regiondrivers/ucloud.go

pkg/util/stringutils2/namepattern.go

pkg/cloudcommon/db/external.go

pkg/multicloud/aws/monitor.go

pkg/util/qemuimg/consts.go

... and 616 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c98df7d...3ff4787. Read the comment docs.

感觉不需要批量卸载网卡，一块一块地卸载比较安全。输入参数结构化是应该做的。


[2pt] Set up login and registration page with devise

Should be built with Devise.

@zakiyousufi kindly can you please checkout this pull request
https://github.com/Zuhaib042/Food-Fusion/pull/14


Pretty much everything is exceeding Vercel Edge function Size limits

Deployed project as directed with vercel and received errors of the form:
Error: The Edge Function "[page].rsc" size is 2.04 MB and your plan size limit is 2 MB. Learn More: https://vercel.link/edge-function-size
These are not isolated to one function as one would expect, initially it was an index function, then it was the opengraph-image function which I fixed by commenting out font importation as follows:
...     {       width: 1200,       height: 630       /* fonts: [         {           name: 'Inter',           data: await fetch(new URL('../fonts/Inter-Bold.ttf', import.meta.url)).then((res) =>             res.arrayBuffer()           ),           style: 'normal',           weight: 700         }       ]*/     }   ); }
I see that similar issues were fixed back in July 2023 among hobby users with a limit of 1MB, yet they seem to persist while I am using a PRO plan with edge function limit of 2MB.

We'll soon be moving to Partial Prerendering which runs on Node.js https://github.com/vercel/commerce/pull/1236


Dark mode

Do you consider adding dark mode? Would be cool.

Hmmmmmm, I've been thinking about it for a long long time. But I'm not an expert on UI design and I tried to make it but the colour scheme is just not right and natural.

maybe you can give us the colorcodes that you use right now and we can help out with it

maybe you can give us the colorcodes that you use right now and we can help out with it

Hi, I don't have the color scheme anymore, I was just editing it in chrome. If you have a good design for the dark mode, feel free to make a PR for it ;)

Coming up with a nice color scheme isn't all that hard. The attached screenshot is a proof of concept of how it could look like.
I'd love to work on developing and creating a PR for something like this, however, as of right now, the development workflow of that is horrible due to bootstrap being minimized. It'd be much easier if bootstrap was installed as a NPM package with its source so we could use SCSS to create a custom bootstrap theme.

Coming up with a nice color scheme isn't all that hard. The attached screenshot is a proof of concept of how it could look like.
I'd love to work on developing and creating a PR for something like this, however, as of right now, the development workflow of that is horrible due to bootstrap being minimized. It'd be much easier if bootstrap was installed as a NPM package with its source so we could use SCSS to create a custom bootstrap theme.

Wondering how would you achieve that if we have the scss?

The easiest way to do it would be to have a CSS file that just overrides the colors of the bootstrap CSS.

The easiest way to do it would be to have a CSS file that just overrides the colors of the bootstrap CSS.

Yeah i was thinking that. Can you create a PR of your theme?

Yeah i was thinking that. Can you create a PR of your theme?

I will later this week due to some components not really looking right at the moment and therefore need tweaking.

Yeah i was thinking that. Can you create a PR of your theme?

I will later this week due to some components not really looking right at the moment and therefore need tweaking.

Thank you!

@LeoEricson I've pushed a CSS file to the v3.1-dev branch, under the src/static/css/theme, is a dark mode css i've worked on a long time before but just did not apply to it. You can disable/enable in the header.html under src/template:
https://github.com/donaldzou/WGDashboard/blob/2b90a2eed28af374fb7c8fd980e497aaa102cdef/src/templates/header.html#L17-L19

@LeoEricson I've pushed a CSS file to the v3.1-dev branch, under the src/static/css/theme, is a dark mode css i've worked on a long time before but just did not apply to it. You can disable/enable in the header.html under src/template:
https://github.com/donaldzou/WGDashboard/blob/2b90a2eed28af374fb7c8fd980e497aaa102cdef/src/templates/header.html#L17-L19

Okay, I'll look through that.

@donaldzou Close this issue?


Optimize trace generation

Currently, trace generation, both main and auxiliary, takes roughly about 10% of the total proving time. We benchmark and profile this step in order to get an idea of bottlenecks.
Witness generation is an inherently sequential process but there are still strategies that one could explore in order to improve things. One such approach is multi-stage building of the main trace through several passes, where for example the first pass could fill the minimal amount of trace values needed in order to be able to fill the hasher chiplet in parallel.

Additional context: https://github.com/0xPolygonMiden/miden-vm/pull/1533#issuecomment-2449052138

I think a good target here would be to get main trace generation to run at at least 50 MHz on something like an M1. And a stretch goal could be 100 MHz. I think it should be double but would require quite a bit of investigation and potential refactoring.


Update YAML

Add BC Government tag to the Environmental Reporting BC here:
https://bcdevexchange.org/programs

Done.


Dockerise demo AI component

We need to publish a Docker image for the AI component developed by #4.

[ ] Develop docker file
[ ] Upload image to DockerHub

Rather than DockerHub use RAMP's own registry at: https://docker.ramp.eu

done during the Nov 2021 demo sprint.


instance security-groups attribute lists vpc id and not security group

This is also present in otc-tool and likely an OTC API bug. If you list a specific instance (describe_instances with OtcConfig.INSTANCE_ID set) the ['server']['security_groups'] attribute contains the vpc id and nothing else.

Issue is still valid, but it's not on CLI side, but API.

Hi György,
The issue has been fixed on the API side with the Mitaka update - old VMs do not benefit from it, only new ones though.
HTH,
Kurt Garloff<EMAIL_ADDRESS>(Sent from Mobile with K9. Please excuse brevity & typos.)
Am 5. März 2017 01:30:10 MEZ schrieb hodigy<EMAIL_ADDRESS>
Issue is still valid, but it's not on CLI side, but API.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/OpenTelekomCloud/python-otcclient/issues/29#issuecomment-284195487

Issue could be closed as it's corrected with Mitaka update.

Based on prev comments CLOSED.


Unable to connect to the server if the nickname is Cyrillic

Spark link
https://spark.lucko.me/648VGmvU8s
Expected behavior
I change the value of username-valid-characters to add the required range of letters, but it does nothing. Also, if you leave the field empty, then I can still log in with a nickname of Latin letters and numbers
Observed/Actual behavior
^[a-zA-Z0-9_.]$ - Default
->
^[a-zA-Zа-яА-Я0-9_.]$ - Nothing changes
->
empty - Nothing changes
Steps/models to reproduce
...
Purpur version
1.19.3 (1933)
Agreements

[X] I am running the latest version of Purpur available from https://purpurmc.org/downloads.
[X] I have searched for and ensured there isn't already an open issue regarding this.
[X] I ticked all the boxes without actually reading them
[X] My version of Minecraft is supported by Purpur.

Other
[22:40:39] [Server thread/INFO]: /<IP_ADDRESS>:63690 lost connection: Internal Exception: java.lang.IllegalStateException: Invalid characters in username

The game has character limitations for many things. The option for usernames we added is for things like geyser where some server owners use a different prefix [...]. It doesn't mean you can use literally anything you want there. You have to stay within the limits of the game itself

- BillyGalbreath, the Discord server


[stable/postgresql] securityContext is not set to initContainer

**BUG REPORT
Version of Helm and Kubernetes:
Kubernetes 1.12.3
helm 2.10.0
Which chart:
stable/postgresql
What happened:
Unable to run chart with a PodSecurityPolicy witch has RunAsNonRoot even with the securityContext set.
(by default RunAsUser: 1001)
create Pod postgresql-postgresql-0 in StatefulSet postgresql-postgresql failed error: pods "postgresql-postgresql-0" is forbidden: unable to validate against any pod security policy: [spec.initContainers[0].securityContext.runAsUser: Invalid value: 0: running with the root UID is forbidden]
postgres is not able to launch
What you expected to happen:
postrgres server run
How to reproduce it (as minimally and precisely as possible):
set a PodSecurityPolicy with RunAsNonRoot
helm install stable/postgresql -n postgresql --debug --namespace postgresql
Anything else we need to know:
I add some new message as comment to give more information
@prydonius
@tompizmor
@sameersbn
@carrodher
@juan131
@desaintmartin

I have this problem. the "nami" daemon will run postgres with 1001:1001 anyway.

Have you an idea of how to do to to deploy it on a K8S with RunAsNonRoot pod security policy?

Hi @obeyler @desaintmartin
The initContainer was added to avoid issues on some K8s distributions were SecurityContext wasn't respected. Therefore, we needed a way to ensure the volumes had the proper permissions.
What do you think about adding a parameter such as initContainer.enabled that can be se to true/false so you can decide whether to install the chart with it or not? cc/ @tompizmor

Agree. We should have enough flexibility to enable/disable both the securityContext and the initContainer.


PyIterReturn for StopIteration

Same as ArithmaticValue for NotImplemented
close #3124
I worked only for iternext slots and kept the generator internal as TODO

Oh, it needs more works but resolving #3124 itself. Thank you


Missed golden cookies

Hi, nice add-on. I only miss one feature: too see how many golden cookies I have missed. You can see it by typing "Game.missedGoldenClicks" (without quotes) in the console. Other add-ons have it so I am sure you could add it too.

Ah, so you do already know about that stat command.  I guess I can add it but maybe I'll have it as a setting or hidden as I know my OCD would not be happy with how many I've missed, lol.

Finally added thanks to @Alhifar.  Will be released in Version 2.3


CI: K8sPolicyTest Multi-node policy test with L7 policy using connectivity-check to check datapath: connectivity-check pods are not ready after timeout

CI failure
/home/jenkins/workspace/Cilium-PR-K8s-1.20-kernel-4.9/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:518
connectivity-check pods are not ready after timeout
Expected
    <*errors.errorString | 0xc000d89050>: {
        s: "timed out waiting for pods with filter  to be ready: 4m0s timeout expired",
    }
to be nil
/home/jenkins/workspace/Cilium-PR-K8s-1.20-kernel-4.9/src/github.com/cilium/cilium/test/k8sT/Policies.go:1698

https://jenkins.cilium.io/job/Cilium-PR-K8s-1.20-kernel-4.9/1088/testReport/junit/Suite-k8s-1/20/K8sPolicyTest_Multi_node_policy_test_with_L7_policy_using_connectivity_check_to_check_datapath/
35de3e43_K8sPolicyTest_Multi-node_policy_test_with_L7_policy_using_connectivity-check_to_check_datapath.zip

Seen in https://github.com/cilium/cilium/pull/15384

This test failed because one endpoint is in CrashLoopBackOff. It tries to listen on port 41001 of the hostns, but fails. ss--t--p--a--i--s.md tells us that the cilium-agent is already listening on that port:
    LISTEN    0      128                         *:41001                          *:*                                                                                users:(("cilium-agent",pid=1,fd=24))
    	 cubic rto:1000 mss:536 cwnd:10 lastsnd:3124844 lastrcv:3124844 lastack:3124844

Not sure why the cilium-agent would listen on that port :thinking: I don't see any reference to that port in the source code...

Oh that's interesting @pchaigno, good find. I think 41001 might be the Cilium  proxy port in this case. This theory aligns with the fact that this test failure is from the L7 suite.
The port is not going to be in the source code because we don't usually care what the port is. We simply ask the OS to give us a free port.

I think 41001 might be the Cilium proxy port in this case.

Yup, @christarazi beat me to it. :)
We should see check the log "DNS Proxy bound to address".

Good find, filed https://github.com/cilium/cilium/issues/15986 for it

One mystery remained---fear not, this comment will solve quickly that---why are the flakes happening almost always with this echo-c-host-container container when we have several other pods running in host-network namespace, in the connectivity checks and in other tests?
Following the kernel sources, we can see that the bind(2) syscall ends up calling sk->sk_prot->get_port, which in the case of TCP I believe is inet_csk_get_port. That last function as an interesting comment:
/* Obtain a reference to a local port for the given sock,
 * if snum is zero it means select any available local port.
 * We try to allocate an odd port (and leave even ports for connect())
 *

Let's see what ports we use apart from 41001 in connectivity checks:
$ git grep -A1 "name: PORT" | grep -oP "(?<=value: \")\d+" | sort | uniq
41000
41001
8080

echo-c-host-container is the only hostns container using port 41001 and others use odd-numbered ports.
I'll send a PR to use 41002 instead and we'll see if that does the trick.

Nice find! Although, in the case of DNS proxy, it's a UDP port. I don't see a similar comment for UDP (regular UDP doesn't have a connect call anyway).

Although, in the case of DNS proxy, it's a UDP port. I don't see a similar comment for UDP (regular UDP doesn't have a connect call anyway).

It's both TCP and UDP actually: https://github.com/cilium/cilium/blob/4f27865e975cc095891b68df5f4a7bc0e26ecca5/pkg/fqdn/dnsproxy/proxy.go#L420-L424
The echo-c-host-container container is also only listening on TCP so the conflict is definitely on a TCP port.

Yes, that's right. DNS proxy also supports TCP requests.


Update readme of demo project

Hi @rtkhanas,
How can I run this demo? please elaborate it. I did not get it "The demo is not possible, because of cors. But it works on a server.". please help me out.

Hi @deepakkumarrai ,
Set your login and password here: https://github.com/rtkhanas/icloud-session/blob/master/demo-nodejs/login.js and run this file node login.js. You will authorize and also session file will be created. Then you can do node load .js and you will get list of contacts.
Hope it helps.

@rtkhanas ,
Thanks it is very helpful for me

@rtkhanas ,
Hey man, can I create new contacts or contact groups back to my Icloud account?

@deepakkumarrai I guess yes, it is more about iCloud API. This lob is just an auth library so you can build spmething on top of it as I did with https://github.com/rtkhanas/icloud-contacts for getting a list of contacts.


[bug] Importing stories from separate packages in a monorepo no longer works with v0.14 - testMatch returns 0 matches

Describe the bug
https://github.com/storybookjs/test-runner/pull/339 added capability to import stories in a monorepo with a regex, but this is broken for me now in v0.14.
I worked upwards from v0.13 and identified that the breakage occurs from 0.14.0-next.3 - so it must have been introduced with the code in https://github.com/storybookjs/test-runner/pull/376.
To Reproduce
I can work on a reproduction repo for this but it might take a bit 😬 If there's a CodeSandbox template available to give me a head start that would be great 🙇
I've redacted some info from the output below, you can see we're using Nx to run the task from within a storybook package. This is working fine to display the stories on Storybook and the interaction addon works fine in the browser too.
aislinn.hayes@XXXXXXXXXXXX my-repo % yarn nx run storybook:test-storybook
yarn run v1.22.19
$ /Users/aislinn.hayes/code/my-repo/node_modules/.bin/nx run storybook:test-storybook

> nx run storybook:test-storybook

$ test-storybook
No tests found, exiting with code 1
Run with `--passWithNoTests` to exit with code 0
In /Users/aislinn.hayes/code/my-repo
  5 files checked.
  testMatch: /Users/aislinn.hayes/code/my-repo/packages/**/*.stories.@(js|jsx|ts|tsx|mdx) - 0 matches
  testPathIgnorePatterns: /node_modules/ - 5 matches
  testRegex:  - 0 matches
Pattern:  - 0 matches
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

 ————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————

 >  NX   Ran target test-storybook for project storybook (3s)

    ✖    1/1 failed
    ✔    0/1 succeeded [0 read from cache]

error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Expected behavior
Test runner should have found a few tests!
Screenshots
N/A
System
Storybook Environment Info:

  System:
    OS: macOS 13.6
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 16.18.1 - ~/.nvm/versions/node/v16.18.1/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v16.18.1/bin/yarn <----- active
    npm: 8.19.2 - ~/.nvm/versions/node/v16.18.1/bin/npm
    pnpm: 8.6.7 - ~/.nvm/versions/node/v16.18.1/bin/pnpm
  Browsers:
    Chrome: 119.0.6045.105
    Safari: 17.0
  npmPackages:
    @storybook/addon-a11y: 7.5.3 => 7.5.3
    @storybook/addon-essentials: 7.5.3 => 7.5.3
    @storybook/addon-interactions: 7.5.3 => 7.5.3
    @storybook/jest: 0.2.3 => 0.2.3
    @storybook/react: 7.5.3 => 7.5.3
    @storybook/react-vite: 7.5.3 => 7.5.3
    @storybook/storybook-deployer: 2.8.16 => 2.8.16
    @storybook/test-runner: 0.14.0-next.3 => 0.14.0-next.3
    @storybook/testing-library: 0.2.2 => 0.2.2
    eslint-plugin-storybook: 0.6.13 => 0.6.13
    msw-storybook-addon: 1.9.0 => 1.9.0
    storybook: 7.5.3 => 7.5.3

Additional context
Versions below 0.14.0-next.3 work fine.

Opened this under a test Github user I had, my bad! Just to let you folks know I'm not a bot 😂

Hey @ahayes91 and 🤖, thank you for reporting the issue!
The only actual change from that PR is this:
https://github.com/storybookjs/test-runner/pull/376/files#diff-192b7f2e275030badbef39a08e82d3b8836a81600ea3fae116511507c676da77R80
could you please try to undo that change, in your local node_modules, and see if the issue is fixed?

Hey there @ahayes91 I tried to make a reproduction but couldn't get it to fail. In fact, I noticed you're using NX so I set a workspace up here:
https://github.com/yannbf/nx-test-runner-repro
yarn nx run org:storybook to run Storybook
yarn nx run org:test-storybook to test it
And that works correctly:

I renamed the story files so that:

both files are .stories.*
both files are .story.*
one file is .story.* and the other .stories.*

and every scenario worked correctly.

Hey @ahayes91 and 🤖, thank you for reporting the issue!
The only actual change from that PR is this: https://github.com/storybookjs/test-runner/pull/376/files#diff-192b7f2e275030badbef39a08e82d3b8836a81600ea3fae116511507c676da77R80
could you please try to undo that change, in your local node_modules, and see if the issue is fixed?

No joy when I made the changes in node_modules, still failing:

Anything else you could think of that I can fiddle with to try and debug this a bit? (Maybe point me towards the file internally that finds the Storybook files?)
I really appreciate this definitely needs a proper reproduction, so I'll work on that now - we're using package-based Nx (a very annoying restriction on us right now due to other internal blockers) and have Storybook in its own package (so that I can put some task management around the storybook commands), so it wasn't generated in using @nx/storybook.

@ahayes91 you can reach me out on discord at @yannbf, happy to assist!

In the meantime, can you remove this line of code as well? It must be the culprit

In the meantime, can you remove this line of code as well? It must be the culprit

Yes this fixes it! 💪

Hey @ahayes91!
Your use case is valid, and I've seen other people do it, mostly because they do not want dependencies from Storybook to somehow get in the way from their application's dependencies. We do not recommend this as de-facto Storybook configuration because we don't use it ourselves, we don't support it as greatly (as you can see) as with basic configurations, and because there could be hoisting and other issues caused by tools like Yarn PnP and pnpm PnP. You are free to use it as you see fit, of course.
Regardless, you have detected a bug from a change I did in a previous PR, so I reverted it on #387 and it's now released as a patch in 0.14.1. Please upgrade and it should all be good now, with no need to eject the test-runner config.
Also, I greatly appreciate the effort you put into getting this fixed! Thank you so much and have a great week!


WebService Consumption

Hello, I am a beginner in NativeScript and I have a project in development where I need to consume webservice, for information manipulation (input and output), but I'm kind of lost because I'm a beginner, I do not know where to start or how.
So I wanted the help of someone who can tell me the best way to make this connection and how to do it, or if possible indicating any articles that will contribute.
Thank you !

Hi @joaovictorpsantos,
Thank you for your interest in NativeScript.
In your case, I would suggest reviewing our getting started tutorial , where are described all the best practices while developing a NativeScirpt Angular application.
Please for any further questions use our NativeScript forum  or StackOverflow.

Thank you very much !


Getting version numbers set by the build farm

Summary of the Pull Request
As outlined in https://github.com/microsoft/PowerToys/wiki/Versioning, we are moving the versioning e2e on the build farm.  From now on there is a single spot that will set the version number and all local dev builds will be 0.0.1
This also sets up the start of having application titles / systray and other spots with the dev environment.  After doing a bit of investigation, this will require a bit more work.
This is also the start of #873 which then will let us start shifting to allow a more complete revision number.  As this has pretty wide reaching changes, i'm just getting the build farm up and functional with this PR.
The script runs local as well as on the farm due to the relative path.
PR Checklist

[ ] Applies to #873
[ ] CLA signed. If not, go over here and sign the CLA
[ ] Tests added/passed
[ ] Requires documentation to be updated
[ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Info on Pull Request
What does this include?
Validation Steps Performed
How does someone test & validate?

@crutkas
can we split this PR in two, so we have one PR with only the changes strictly needed for the change how we set the version number?
We also need to make changes to the auto update logic to avoid having continues notification on the local builds or actually running the auto-update.

Yes, I may roll this out and resubmit. Looks like I fubared and branched off a different branch.

Basically it is just the power shell script and the tweak to versions prop

Did I miss the yaml changes?  Where does the script ps script get called from?


.equals() override missing from XReadArgs, among others

Bug Report
XReadArgs doesn't override the .equals() method. This problem extends to many other classes in the library, but the specific instance that motivated this bug report was the one in XReadArgs.
Current Behavior

Example code
var x = XReadArgs.Builder.block(Duration.ofSeconds(10));
var y = XReadArgs.Builder.block(Duration.ofSeconds(10));
assertEquals(x, y);

Expectation: x and y are equal, the assertion succeeds.
Reality: x and y are not equal, the assertion fails.
Environment

Lettuce version(s): 6.1.8.RELEASE

Possible Solution
Override .equals() in XReadArgs, and possibly others too.
Additional Context
I discovered this when I was trying to write unit tests and found a bunch of them were failing because of it.
I'd like to fix it so that I can write those unit tests without needing a refactor.

None of our args objects implements hashCode and equals because these objects weren't intended for equality checks.

@JamesBurnsCanva could you give an example where these are needed? A sample test case would be fine.


Calculating the chance for random drops

This might be complicated, but it would be great if the add-on would be able to calculate the chances for the random drops, i.e. Christmas cookies, rare and common Easter eggs and all this stuff.
You would see the percentage (for both wrinklers, golden/wrath cookies and reindeers) next to the season specials stats.

The calculations really are not that hard. Christmas and halloween cookies work exactly the same, only easter eggs are a bit harder.
You take the base fail rate and multiply with a bunch of multipliers based on unlocks (can easily be found in the source; lookup "halloween cookie drops" and "seasonPopup.spawn"). Then take pSucces = 1 - failrate. After that the chance to unlock a new cookie is pSuccess * (1 - have/total).
As for easter eggs the calculations are as follows (for failRate calculations lookup "DropEgg" in the source):
Chance of normal drop first chance:
pNormal1 = pSuccess * 0.9 * (1 - nHaveNormalEggs/nNormalEggs)
Chance of rare drop first chance:
pRare1 = pSuccess * 0.1 * (1 - nHaveRareEggs/nRareEggs)
Chance to get redrop
pRedropNormal = pSuccess * 0.9 * (nHaveNormalEggs/nNormalEggs)
pRedropRare = pSuccess * 0.1 * (nHaveRareEggs/nRareEggs)
pRedrop = pRedropNormal + pRedropRare
Change of normal drop 2nd chance
pNormal2 = pRedrop * 0.9 * (1 - nHaveNormalEggs/nNormalEggs)
Change of rare drop 2nd chance
pRare2 = pRedrop * 0.1 * (1 - nHaveRareEggs/nRareEggs)
Chance of normal drop:
pNormal = pNormal1 + pNormal2
Chance of rare drop:
pRare = pRare1 + pRare2
I could probably make a branch and do a pull request.

I'll get my head around this in a bit, too early in the morning =p


analyzer/consensus: insert on "events" violates FK constraint

Consensus analyzer sometimes creates INSERT statements for the events table that violates foreign key constraints
Sample error at height 8493489:
    "err": "ERROR: insert or update on table \"events\" violates foreign key constraint \"events_txn_block_txn_hash_txn_index_fkey\" (SQLSTATE 23503)",
    "sql": "\n\t\tINSERT INTO oasis_3.events (backend, type, body, txn_block, txn_hash, txn_index)\n\t\t\tVALUES ($1, $2, $3, $4, $5, $6)",
    "args": [
      "roothash",
      "ExecutorCommitted",
      "{\"commit\":{\"node_id\":\"hpsco0ffTxzXgY4qd22Q/p/lSPYEmGvYMzwVyUK2Tx (truncated 635 bytes)",
      8493489,
      "fa67b2079d5dfce288200d86778306fd740e4d4eb5c60fdbda797aa8f879d321",
      2
    ],

See full list of errors. Each error is logged three times, at three different layers. A little spammy but each layer has separate useful information ...
Notes:

We shouldn't be producing invalid references.
Notice how the reference is to a tx from the same height. So it's probably just that the event should be inserted after the tx, or (better) we should be using deferrable constraints as described in https://github.com/oasisprotocol/oasis-indexer/issues/50
The problem is, the block is retried and succeeds on second try. Does that mean we're not inserting all queries relating to a block inside a db transaction? If we were, the db transaction would fail, no data would be written to the db, and the retry should fail in the exact same way. Ohhh ... maybe there's a race between the events analyzer and the txs analyzer, and it depends which adds its sql statements first.

I think this is soft addressed by constraint removal in https://github.com/oasisprotocol/oasis-indexer/pull/188

what was the constraint?

what was the constraint?

https://github.com/oasisprotocol/oasis-indexer/blob/2687d24573c36306b125ea179ddc26e3453671a8/storage/migrations/01_oasis_3_consensus.up.sql#L63

do we use different goroutines to enqueue the queries for the tx and the events?


Update kafka-avro-serializer to 5.5.5

Updates io.confluent:kafka-avro-serializer from 5.5.4 to 5.5.5.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.confluent", artifactId = "kafka-avro-serializer" } ]

labels: library-update, semver-patch

Superseded by #137.