Adds a plugin for the Android AlarmManager

I tried to run this, but it's failing during compilation. Does this require a different engine?
mit-macbookpro2:example mit$ flutter run -d A
Launching lib/main.dart on Android SDK built for x86 in debug mode...
Initializing gradle...                                0.6s
Resolving dependencies...                             6.7s
Running 'gradlew assembleDebug'...
/Users/mit/tmp/android-alarm-manager/packages/android_alarm_manager/android/src/main/java/io/flutter/androidalarmmanager/AlarmService.java:87: error: method runFromBundle in class FlutterView cannot be applied to given types;
      flutterView.runFromBundle(appBundlePath, null, entrypoint, true);
                 ^
  required: String,String
  found: String,<null>,String,boolean
  reason: actual and formal argument lists differ in length
1 error

FAILURE: Build failed with an exception.

Ah, looks like that is underway: https://github.com/flutter/flutter/pull/12692

The engine roll landed. This should work now. PTAL.

Great! I can build and run now, but I don't see any output from the print() statements. Where am I supposed to see those? And should I run this in some special way?

You don't have to run it any special way. 'flutter run' will work fine. The messages will be in the system log that you can see with 'logcat -d'.

I should also note that the maximum frequency for alarms on my device is 1 minute, and on more recent versions on Android the timing is not guaranteed to be exact. So in order to see something print in the log, you might have to wait around for 2 - 3 minutes, depending on what your version of Android thinks about alarm frequencies.

cc @demarco

Friendly ping.


Add recursion

If a page contains a link to another page of the blog, that page could be checked as well. Challanges may be to add an appropriate test method at the start

In addition the url of the page to check can not be part of the configuration since the target of the href is only available during test exectuion


[backport] Fix overfow in matmul test

Backport of #2403

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit 9290290dd45a8ee8d54f03d053fa803ec6203692, target branch v7) succeeded!


BUG: The carousel images are resizing when moving from one to another

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
When clicking the carousel image it messes up the entire size of the image.
Possible fix: the transformation property has to be changed.

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

issue has already been fixed by others.


[networking_mapper] Fix default handling of skip NM flag.

As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running
[x] Appropriate documentation exists and/or is up-to-date:

/approve


Can't get details and download a paid app that I paid with my account

Hey,
I can't get details and download a paid app that I paid with my account.
Is that something that isn't implemented in this lib ?
When I try to get details I get null for the version code and when I try to download with the correct version code, as I have the following message: RequestError: Can't install. Please try again later..

I had this issue because I wasn't providing a good androidId.
In fact, the Google PlayStore API doesn't tell you if your androidId is valid or not.
That caused the bad behavior that I had: sometimes I was able to get details of an app and sometimes not.
To get your deviceId you can do as said in the README install the application called deviceId but then when you will open the app you will first see something called androidId and just after GoogleFrameworkService Id, the id needed by the library is the GoogleFrameworkService Id and not the androidId !
Then all should work properly.


Compression level zero

Hi @MinhasKamal - first of all - thanks for this wonderful tool!   I find it extremely useful!
I'm using this link to download a zipped folder for iDempiere translation in German:
https://minhaskamal.github.io/DownGit/#/home?url=https://github.com/bxservice/tbayen.translations/tree/master/data/de_DE&fileName=de_DE&rootDirectory=false
The file returned is perfect for what is required to import the translation in the program.
The problem I see is that the ZIP is using compression level 0, this is, not compressing at all, the files weight 5.3MB, and is the same size of the zip file, at compression level 1 the file size is reduced to 799KB, with level 9 is 666KB.
Is it possible to add a flag maybe for the desired compression level, or compress by default in some useful level?
Regards,
Carlos Ruiz

Hello @CarlosRuiz-globalqss - I feel really happy that you found DownGit useful.
The thing is, when a link of directory is provided, DownGit traverses through that directory and downloads each file separately in uncompressed form from GitHub server. After all the files are downloaded, DownGit simply bundles them together.
Now, as all files are already downloaded, compressing them now will not reduce network usage in any way. Moreover, this compression procedure will simply add extra processing expense; and the user will have to decompress it again. That is why, I just bundled them without imposing any compression.

Thanks @MinhasKamal  for the fast answer, in my case I download the file not to decompress it, but to upload it into another application, same if somebody wants to download it to send it via email for example, then is required to decompress it, and recompress it with a better compression level.
Regards,
Carlos Ruiz

Yes, I understand your case, shall try to add this in future updates.

Thank you @MinhasKamal - very appreciated.


Browserified request + cheerio

Basic crawler libraries, browserified.
From the starting issue over at search-index
[...]
People often have sites/pages where they can't do much programming besides JavaScript.
What if we made an example that crawls all the pages and adds it to a search-index running in the browser. The user could define some boundaries for request and define some cheerio patterns for getting the content from the page.
This way, people can get a crawler with no or little effort. It'll be as easy as with Google Custom Search Engine, but you can make it a lot better if you put in more effort.
Seems there is a browserified version of the Node stream library also. That would go nice with search-index.
[...]

Just start with an array of url's, populate the page with what comes back from /request and go from there.

https://github.com/iriscouch/browser-request

Seems fetch() is doing what I need, so then it's already supported in browser:
Cheerio should be ready for browserify: https://github.com/cheeriojs/cheerio/pull/420

Remaining: Test a simple cheerio example on the HTML fetched.

https://www.reddit.com/r/node/comments/3avbnl/could_someone_help_me_to_browserify_the_cheerio/?st=jetprb0w&sh=08b33bb1

Or, if not, just go with jQuery for now :-(

Seems I need brfs to make it work.

brfs and moving all javascript to main.js did the trick. The node stream stuff is moved to another issue.


updated to ensure cat happens on CUDA

Patch Description
Observed during evaluating some models that the torch.cat operation in L732 took up 11.98GB of CPU memory. Used debugger to confirm that this was indeed because all tensors in shards_to_load function was on CPU. Because of this CPU operation, model loading using this function was slower than it needed to be. This speeds that up.
Testing steps
Observed memory traces generated using profiler. Made changes and saw that model loading time using this function dropped anywhere between 10-15% given the same baseline conditions.

Before vs after on the operation after moving it to GPU

wait wouldn't this then just take gpu memory and has potential to gpu oom?

I think we load model states on cpu and build model on gpu and then do all the state loading.
This way would keep two copies on the gpu of the shard of weights.

wait wouldn't this then just take gpu memory and has potential to gpu oom?

I did not see overall increase in GPU memory . This is most likely because this tensor is eventually moved to GPU anyway.

I think we load model states on cpu and build model on gpu and then do all the state loading.
This way would keep two copies on the gpu of the shard of weights.

Interesting. Why are we loading model states on CPU then? I don't see the reason behind this at all unless we have a genuine risk of OOM issues (which also doesn't seem to be case)

I think we load model states on cpu and build model on gpu and then do all the state loading.
This way would keep two copies on the gpu of the shard of weights.

Interesting. Why are we loading model states on CPU then? I don't see the reason behind this at all unless we have a genuine risk of OOM issues (which also doesn't seem to be case)

Cause then you will have two copies on gpu of the model shard that you are loading. This will quite likely gpu OOM the model hosting of 175B model on 8x80GB A100s

@ngoyal2707 would it be too messy to try and gate this logic as a function of model size and available memory?


Update CONTRIBUTING.md

:camel on travel is relevent

Not relevant unfortunately, please make a more useful contribution.

:camel: on travel


Added settings options for allowed network types

This allows the user to select other network connection types,
besides WiFi, for downloading media files.
The "Any" network type is added to allow downloading over USB network connections and probably bluetooth as well (didn't test that, as I do not have bluetooth on a device running Kodi).

@poisdeux
In the future please don't auto indent the whole file, only the lines you touch, so as to reduce the number of changes. Looking through all these changes is difficult and easy to miss something.
Also, make sure you always run lint (./gradlew build should do it) so as to catch the maximum number of issues.

Sorry about the diffs introduced by auto indenting. As my programming consists of a lot of copy/pasting I got used to auto indenting over the years. I do it without even thinking about it. I'll try to be more careful.

I'm probably going to create a "Advanced settings" section and move this setting to there, later.


python311Packages.dvc-data: 2.17.1 -> 2.18.1

Diff: https://github.com/iterative/dvc-data/compare/refs/tags/2.17.1...2.18.1
Changelog: https://github.com/iterative/dvc-data/releases/tag/2.18.1
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 259026 run on x86_64-linux 1

14 packages built:

dvc (python310Packages.dvc)
dvc-with-remotes
dvc-with-remotes.dist
dvc.dist (python310Packages.dvc.dist)
python310Packages.dvc-data
python310Packages.dvc-data.dist
python310Packages.dvclive
python310Packages.dvclive.dist
python311Packages.dvc
python311Packages.dvc-data
python311Packages.dvc-data.dist
python311Packages.dvc.dist
python311Packages.dvclive
python311Packages.dvclive.dist


Add more efficient ETHER_DST_ADDRESS_64() function

ETHER_DST_ADDRESS() returns a bounded list of uint8_t values for the bytes of the MAC address.  Profiles show this can become a bottleneck, by generating a lot of blist temporaries that dynamically allocate the bytes in the list.  This is fine, up to a point, where the thread local allocation cache for these extremely tiny allocations gets filled up, causing tcmalloc to try to juggle the process-wide cache.  With lots of threads all doing this simultaneously, it becomes quite a point of contention.
We can't just replace ETHER_DST_ADDRESS() with one returning a uint64_t directly, for backwards-compatibility reasons, so I added a new variant that can be used when we need the path to be very efficient.
The shift, mask, and or sequence looks a bit ugly in the inline, but pretty much all compilers on all 64-bit architectures should be able to optimize this fairly well, into just a couple of instructions.

Ugh. I thought that bounded lists were more efficient than ordinary lists. Thanks for tracking this down and fixing it.
We'll have a similar problem with IPv6 addresses when they become popular. Unfortunately, we won't be able to fix that problem as easily ...


python312Packages.weatherflow4py: 1.0.6 -> 1.2.0

Diff: https://github.com/jeeftor/weatherflow4py/compare/refs/tags/v1.0.6...v1.2.0
Changelog: https://github.com/jeeftor/weatherflow4py/releases/tag/v1.2.0
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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/)
24.11 Release Notes (or backporting 23.11 and 24.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.

Add a :+1: reaction to pull requests you find important.

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

5 packages built:

home-assistant-component-tests.weatherflow_cloud
python311Packages.weatherflow4py
python311Packages.weatherflow4py.dist
python312Packages.weatherflow4py
python312Packages.weatherflow4py.dist


Implement auto-discovery

Examples here: https://github.com/ioBroker/ioBroker.discovery/tree/master/lib/adapters

done...


Audit and make documentation for command HLEN consistent

The documentation of the command [HLEN](https://dicedb.io/commands/hlen/) present in the docs could have become stale. We need your help to ensure that the documentation is complete, correct, and consistent.  Completing this issue will give you much-needed exposure to how the command is implemented and the different parameters it accepts. Hence, this is a great way to build a good understanding of the project and its functionality. While still making a significant contribution. Here's what you need to do:

Go through the documentation of the command and run all the examples, making sure they all work as expected
If the same command is present in Redis, then the expected output of the DiceDB command is the same as the Redis output
If the command is not in Redis, then as per your judgment, raise an issue with this template or fix the documentation and raise a pull request.
The documentation should contain the following sections in the following order

short and concise introduction paragraph about the command covering what it does
Syntax
Parameters: List all the parameters the command accepts, and ignore the section if there are no parameters
Return values: List all possible return values and under what condition
Behaviour: Describe the behavior of the command, what it does, how it does it, some internal specifics if any
Errors: List all possible errors the command can throw and under what condition
Examples: List all possible examples of the command and the expected output. Assume CLI implementation

Note: The title of the sections should be the exact strings mentioned above, like "Examples", "Return values", etc.
Note: The description of the command in Frontmatter of the command.md file is the first paragraph (introduction) of the command.
Go through the DiceDB/dice repository and explore the command implementation

to understand all possible return values
to understand all possible error values and conditions
to understand different parameters the command accepts

Please use the documentation of the SET command as the reference point and structure the
documentation of this command in a very similar way, including the following points

if you see any "Conclusion" section, remove it
the headers (h1, h2, h3) should be appropriately used
the CLI prompt should be <IP_ADDRESS>:7379> and not anything else
Use markdown tables for parameters and return values (ref SET command documentation)
wrap any command or paramter in backticks (`) to highlight them
the section header should be capitalize as used in the SET command documentation

If you find any inconsistencies, please fix the documentation and raise the PR.
The core idea of this exercise is to ensure that the documentation is consistent, correct, and complete.
Make sure you comment on the other issues you created (if any) as a comment on this issue and also any PR (if any) that you created.
Thank you for picking this up and contributing to the DiceDB. It means a ton.

Hey @arpitbbhayani  - can I take a look at it?

Hello @santhosh2011,
There has been no activity on this issue for the past 5 days.
It would be awesome if you keep posting updates to this issue so that we know you are actively working on it.
We are really eager to close this issue at the earliest, hence if we continue to see the inactivity, we will have to reassign the issue to someone else. We are doing this to ensure that the project maintains its momentum and others are not blocked on this work.
Just drop a comment with the current status of the work or share any issues you are facing. We can always chip in to help you out.
Thanks again.

hey @arpitbbhayani @lucifercr07 Can you please assign issue to me?

@TecHAyusH6476 assigned, thanks for contributing.

Sorry @arpitbbhayani @lucifercr07 - I missed this notification. I see the issue is already reassigned and let @TecHAyusH6476 take it up.

Hello @TecHAyusH6476,
There has been no activity on this issue for the past 5 days.
It would be awesome if you keep posting updates to this issue so that we know you are actively working on it.
We are really eager to close this issue at the earliest, hence if we continue to see the inactivity, we will have to reassign the issue to someone else. We are doing this to ensure that the project maintains its momentum and others are not blocked on this work.
Just drop a comment with the current status of the work or share any issues you are facing. We can always chip in to help you out.
Thanks again.

hey @arpitbbhayani
Due to an unforeseen medical emergency, I was unable to actively work on this issue.
I will wrap it up ASAP

Hi, @TecHAyusH6476. #1162 addressed this issue.
@lucifercr07 Please mark this issue as closed.
Thanks

@c-harish ig you should also update the Example usage section to make it consistent with all the other DOCS.
For example


I NEED TO TM1621 EXAMPLE FOR ESP-IDF (IDFGH-10258)

IS ESP IDF DRIVER AVAILABLE FOR TM1621

Hi, @cyberumut, we can consider adding this to our development queue. However, we currently do not have any plans to support this LCD controller in the coming months.

Thanks for reporting, feel free to reopen.


docs: modify the wrong Chinese word

"阀值" is a wrong word in Chinese, "阈值" should be used here

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[x] Other, please describe: documents

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:

[x] It's submitted to the dev branch.
[ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[x] All tests are passing: https://github.com/vuejs/vue-test-utils/blob/dev/.github/CONTRIBUTING.md#development-setup
[ ] New/updated tests are included

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

why checks all run failed?

I guess we need to update the Netlify infrastructure. I have no idea how to do this, I will find out. Maybe @afontcu has some context 🤔 ?

any update?

I do not have access to the Netlify account to update the image, but I asked someone who does. Should be able to get this fixed this week.

Still no luck. I miss GH pages, it was a lot easier that having to manage access to multiple tools. Maybe we should move back to that.

Gonna merge this while I try to chase up a Netlify fix.


In database with hundreds of entries on Mac OSX 10, manual list shows empty

Find manually doesn't list any entries
Posted by A Google User
When I open a kdbx file and theres no match to the current site, I choose 'find manually' to browse the entire list, but it's empty (the file has several hundred entries)
Reply
Application version: 2<IP_ADDRESS>
Client version: 5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.118 Safari/537.36
Reported date: 4/17/15 3:03 PM
Reported by: A Google User

I was the one who posted this, happy to help with any debugging

Thanks!  When this happens, does it still work to type the name of the entry and find it, or does the list stay blank when that happens?

The list remains blank, even if I type in the name of a known entry

I was unable to reproduce, but I have released a new version 2<IP_ADDRESS> with a redesigned manual search.  Please let me know if this fixes the problem, thanks!

Hmm, just tried it there with the latest 2015.4.27, with the same result on MacOSX - no entries in the list. I'll do some more debugging locally on my side, in case it's my .kdbx file

Yes, there must be something unusual about one of the entries in your file.  Still a bug in CKP though.
It would help me to debug it if you go to the empty list and right click on it and select "Inspect Element".  This will bring up the dev tools, and if you click on "Console" there is probably some error there.  A screenshot of that would be great :)

It's my file, keepassService can't parse it properly. For info, I have both custom icons in my file, along with binary attachments. I'll keep digging.

Yep, it's the binary attachments, which don't seem to be removed from the database, even though I removed them from the entry. I exported the db, manually removed the Binary entries in the XML file, and re-imported into a new DB, which now populates the list correctly. In case you want to test it, I had 524 entries, 39 groups, and 13 attachments/binaries.

Ah, I think I understand what happened - when a kdbx database grows too large then it is split into multiple blocks, and the current code only handles the first block :(
Now that I know what to do, the fix should be simple.  Thanks for all your help and for reporting this!

No problem, and thanks! Confirming the latest build 2015.4.29 worked with both my files (one with the binaries, and one without)

Just to clarify when I say it worked on my file, I was using local git cloned copy from you repo, which I loaded as an unpacked extension - the store version is still not working for my file, so I'm just assuming it's not the latest version at the moment

Thanks for clarifying, I thought that must have been it.  As you surmised, the git version is newer than the one on the store.  Most likely I will publish it this weekend.


[Bug]: Error occurred while processing message: api_key is not present in llm_config or OPENAI_API_KEY env variable for agent ** primary_assistant**. Update your workflow to provide an api_key to use the LLM

Describe the bug
After inserting my OPEN_AI API Key and successfully testing the connection from the Models page, I receive the following error when pressing one of the "Travel", "Sine Wave", etc buttons on the Playground page.
A dropdown opens up and delivers the following message:  Error occurred while processing message: api_key is not present in llm_config or OPENAI_API_KEY env variable for agent ** primary_assistant**. Update your workflow to provide an api_key to use the LLM
Double-checked to ensure everything is pointing the the correct model.
New user here and I apologize in advance if I'm missing something obvious.
Steps to reproduce
Open VS Code and run 'autogensudtio ui' from venv in the terminal.
Step 1:  Insert OPEN_Ai API Key on models page and test.
Step 2:  Return to Playground and press the Travel button on the bottom of the screen.
Model Used
gpt-4-1106-preview
Expected Behavior
Should have gotten reply message?
Screenshots and logs
No response
Additional Information
Windows 10, Python 3.11

This seems to be a known issue related to model update not being propagated to workflows, the new branch we are working on should address this. cc @victordibia


⚠ Bofrost.be has degraded performance

In c732172, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2497 ms

Resolved: Bofrost.be performance has improved in 59ad513 after 26 minutes.


Deploying Rook sometimes fails in the CI

Sometimes deploying Rook fails, but no errors are available. The output looks like this:
...
configmap/rook-ceph-operator-config created
deployment.apps/rook-ceph-operator created
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  1187  100  1187    0     0  21196      0 --:--:-- --:--:-- --:--:-- 21196
[Pipeline] }

and also
...
cephfilesystem.ceph.rook.io/myfs created
cephblockpool.ceph.rook.io/replicapool created
Wait for rook deploy... 0s
...
Checking CEPH cluster state: []
Wait for rook deploy... 45s
The connection to the server <IP_ADDRESS>:8443 was refused - did you specify the right host or port?
error executing jsonpath "{.items[0].status.state}": Error executing template: array index out of bounds: index 0, length 0. Printing more information for debugging the template:
	template was:
		{.items[0].status.state}
	object given to jsonpath engine was:
		map[string]interface {}{"apiVersion":"v1", "items":[]interface {}{}, "kind":"List", "metadata":map[string]interface {}{"resourceVersion":"", "selfLink":""}}

More logging when deploying Rook is needed before this problem can be addressed.

Warning Failed 24s kubelet Error: ImagePullBackOff
Normal Pulling 10s (x2 over 25s) kubelet Pulling image "docker.io/ceph/ceph:v14.2.12
Warning Failed 10s (x2 over 25s) kubelet Failed to pull image "docker.io/ceph/ceph:v14.2.12": rpc error: code = Unknown desc = Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
Warning Failed 10s (x2 over 25s) kubelet Error: ErrImagePull

Hitting the rook deployment issue at https://github.com/ceph/ceph-csi/pull/1924

2021-04-06 10:45:08.684883 E | ceph-cluster-controller: failed to reconcile. failed to reconcile cluster "my-cluster": failed to configure local ceph cluster: failed to create cluster: failed to start ceph monitors: failed to initialize ceph cluster info: failed to save mon keyring secret: failed to create secret for rook-ceph-mons-keyring: etcdserver: request timed out

Error from server: error when creating "https://raw.githubusercontent.com/rook/rook/v1.4.9/cluster/examples/kubernetes/ceph/toolbox.yaml": etcdserver: request timed out

Multiple ci rook deployment fails at #1229

Failed again with logs:
Loaded image: ceph/ceph:v16
deploy rook
Error from server: error when creating "https://raw.githubusercontent.com/rook/rook/v1.6.2/cluster/examples/kubernetes/ceph/common.yaml": etcdserver: request timed out
kubectl_retry -f https://raw.githubusercontent.com/rook/rook/v1.6.2/cluster/examples/kubernetes/ceph/common.yaml failed, will retry in 10 seconds
+++ kubectl get nodes
+++ kubectl -n rook-ceph get events
No resources found in rook-ceph namespace.
+++ kubectl -n rook-ceph describe pods
No resources found in rook-ceph namespace.
+++ kubectl -n rook-ceph logs -l app=rook-ceph-operator
+++ kubectl -n rook-ceph get CephClusters -oyaml
error: the server doesn't have a resource type "CephClusters"
+++ kubectl -n rook-ceph get CephFilesystems -oyaml
error: the server doesn't have a resource type "CephFilesystems"
+++ kubectl -n rook-ceph get CephBlockPools -oyaml
error: the server doesn't have a resource type "CephBlockPools"
+++ exit 1
++ kubectl get nodes
NAME       STATUS   ROLES    AGE     VERSION
minikube   Ready    master   7m52s   v1.19.13
++ kubectl -n rook-ceph get events
No resources found in rook-ceph namespace.
++ kubectl -n rook-ceph describe pods
No resources found in rook-ceph namespace.
++ kubectl -n rook-ceph logs -l app=rook-ceph-operator
++ kubectl -n rook-ceph get CephClusters -oyaml
error: the server doesn't have a resource type "CephClusters"
++ kubectl -n rook-ceph get CephFilesystems -oyaml
error: the server doesn't have a resource type "CephFilesystems"
++ kubectl -n rook-ceph get CephBlockPools -oyaml
error: the server doesn't have a resource type "CephBlockPools"
++ exit 1
script returned exit code 1

A similar problem happened at https://github.com/ceph/ceph-csi/pull/2322#issuecomment-892769083 (logs)


netsniff-ng: 0.6.3 -> 0.6.4

Semi-automatic update. These checks were performed:

built on NixOS
ran /nix/store/gazzj2la9diafgf11ay2a9pgvvwvjvd2-netsniff-ng-0.6.4/bin/mausezahn help got 0 exit code
found 0.6.4 with grep in /nix/store/gazzj2la9diafgf11ay2a9pgvvwvjvd2-netsniff-ng-0.6.4
found 0.6.4 in filename of file in /nix/store/gazzj2la9diafgf11ay2a9pgvvwvjvd2-netsniff-ng-0.6.4

Failure on x86_64-darwin (full log)
Partial log (click to expand)
Package ‘netsniff-ng-0.6.4’ in /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/pkgs/tools/networking/netsniff-ng/default.nix:50 is not supported on ‘x86_64-darwin’, refusing to evaluate.

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Partial log (click to expand)
shrinking /nix/store/gazzj2la9diafgf11ay2a9pgvvwvjvd2-netsniff-ng-0.6.4/sbin/netsniff-ng
shrinking /nix/store/gazzj2la9diafgf11ay2a9pgvvwvjvd2-netsniff-ng-0.6.4/sbin/astraceroute
shrinking /nix/store/gazzj2la9diafgf11ay2a9pgvvwvjvd2-netsniff-ng-0.6.4/sbin/.trafgen-wrapped
gzipping man pages under /nix/store/gazzj2la9diafgf11ay2a9pgvvwvjvd2-netsniff-ng-0.6.4/share/man/
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/gazzj2la9diafgf11ay2a9pgvvwvjvd2-netsniff-ng-0.6.4/sbin
patching script interpreter paths in /nix/store/gazzj2la9diafgf11ay2a9pgvvwvjvd2-netsniff-ng-0.6.4
checking for references to /tmp/nix-build-netsniff-ng-0.6.4.drv-0 in /nix/store/gazzj2la9diafgf11ay2a9pgvvwvjvd2-netsniff-ng-0.6.4...
moving /nix/store/gazzj2la9diafgf11ay2a9pgvvwvjvd2-netsniff-ng-0.6.4/sbin/* to /nix/store/gazzj2la9diafgf11ay2a9pgvvwvjvd2-netsniff-ng-0.6.4/bin
/nix/store/gazzj2la9diafgf11ay2a9pgvvwvjvd2-netsniff-ng-0.6.4

Success on aarch64-linux (full log)
Partial log (click to expand)
shrinking /nix/store/g3ha03qrj52dkmg3y2vmxcgp631ybrbp-netsniff-ng-0.6.4/sbin/flowtop
shrinking /nix/store/g3ha03qrj52dkmg3y2vmxcgp631ybrbp-netsniff-ng-0.6.4/sbin/astraceroute
shrinking /nix/store/g3ha03qrj52dkmg3y2vmxcgp631ybrbp-netsniff-ng-0.6.4/sbin/netsniff-ng
gzipping man pages under /nix/store/g3ha03qrj52dkmg3y2vmxcgp631ybrbp-netsniff-ng-0.6.4/share/man/
strip is /nix/store/viv0il4zpdqj4p7yamwbmn2k9pb8dcnv-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/g3ha03qrj52dkmg3y2vmxcgp631ybrbp-netsniff-ng-0.6.4/sbin
patching script interpreter paths in /nix/store/g3ha03qrj52dkmg3y2vmxcgp631ybrbp-netsniff-ng-0.6.4
checking for references to /build in /nix/store/g3ha03qrj52dkmg3y2vmxcgp631ybrbp-netsniff-ng-0.6.4...
moving /nix/store/g3ha03qrj52dkmg3y2vmxcgp631ybrbp-netsniff-ng-0.6.4/sbin/* to /nix/store/g3ha03qrj52dkmg3y2vmxcgp631ybrbp-netsniff-ng-0.6.4/bin
/nix/store/g3ha03qrj52dkmg3y2vmxcgp631ybrbp-netsniff-ng-0.6.4


add multi-tenant possibility

the application should be storage files based on tenant.
The default file structure should be:
{$file.db.location} / {$tenant} / {$DEFAULT_STRATEGY_DIRECTORY: current_date} / {$FILE_ID}
where properties (except the last one) are folders and if not present then create :

file.db.location - base root where will be saved all files content
tenant - folder for related tenant
DEFAULT_STRATEGY_DIRECTORY - in future to be able to create folders based on different strategies. Currently it should be create a folder based on current date
FILE_ID - the id which is received from the client

available in 1.0.1 release.
keys:

if root directories where the file should be located does not exists then create all path;
if new tenant then new directory will be created (default strategy).


[FEATURE REQ] Publish quick-start doc about setting up a credential-free spring ecosystem kafka application with Key Vault

Context
A quick-start documentation introducing how to set up a spring ecosystem kafka application using Key Vault for authentication with Event Hubs should be delivered.
Next Step
Publish the quick-start documentation.

The parent issue to track all Key Vault related credential-free quickstarts has not been established.


What does --fps do?

In your colab example, you upsample a 25 fps video by 2x, which seems like it ought to produce 50fps, but then you encode it with --fps 60, and the output is in fact 60fps
does that mean every fifth frame is being repeated? or is it not actually 2x but rather some fraction above 2x

This parameter is used to control the number of frames played per second of the output video. I will adjust the colab code.

@hzwer I applied --fps 60 and my video became from 5 minutes long to 8 minutes long :(
!nvidia-smi
!python3 inference_video.py --exp=2 --video=/content/input.mp4 --fps=60

@hzwer I applied --fps 60 and my video became from 5 minutes long to 8 minutes long :(
!nvidia-smi
!python3 inference_video.py --exp=2 --video=/content/input.mp4 --fps=60

@hzwer I applied --fps 60 and my video became from 5 minutes long to 8 minutes long :(
!nvidia-smi
!python3 inference_video.py --exp=2 --video=/content/input.mp4 --fps=60

Same with exp=1

If you don't want to change the duration of your video, please do not set --fps.

@hzwer I applied --fps 60 and my video became from 5 minutes long to 8 minutes long :(
!nvidia-smi
!python3 inference_video.py --exp=2 --video=/content/input.mp4 --fps=60

Same with exp=1

If you don't want to change the duration of your video, please do not set --fps.


JS SDK vs REST API for Speaker Verification

The model scores for JS SDK and REST API in Text-independent Speaker verification are different. Is this the right behaviour? Because we would assume that internally Microsoft would be using the same model for Speaker verification. What is the reason for this discrepancy?

@ajay960singh From testing this with JS SDK, using the same four files to enroll and then verify, I'm getting different scores each time. Because JS SDK doesn't generate those scores, I can't provide you with the insight you're asking for. I will ping the backend service team and ask them to provide an explanation here.

@ajay960singh A few follow-up questions, in addition to files vs microphone. Which version of JS speech SDK are you using, and is this a custom version of JS SDK? Also, can you provide the JS code you're using to produce the verification result?

@ajay960singh Please provide the information so that we can help you further.

Closed since no further updates since May. Please open a new issue if more support is needed.


React Native (Color)

Type: Feature Request
In html css or React, whenever we use any color property like color, background color etc, it shows the color(as a little square box) with its color code or color name. But in react native, whenever I use any color it doesnt shows the color square box where on hover I can change/choose different color.
VS Code version: Code 1.81.1 (6c3e3dba23e8fadc360aed75ce363ba185c49794, 2023-08-09T22:22:42.175Z)
OS version: Windows_NT x64 10.0.22621
Modes:

Can you add a small code sample that illustrates this?

Can you add a small code sample that illustrates this?


Removing optional inputs

Hello,
I use the miniwdl workflow and I get an error in running the deepVariant analysis as:
check JSON input; couldn't construct DeepVariantModel? from "WomCompositeType {\n model ->
WomCompositeType {\n data -> File\ndata_index -> File \n}\nmetadata -> File \n}? (optional)" (in
humanwgs.deepvariant_model)

In the input.hpc.json, I gave the deepvariant version as 1.5.0. in line 65
Is there anything else to change or give the path:
  "humanwgs.deepvariant_version": "1.5.0",
  "humanwgs.deepvariant_model": "WomCompositeType {\n model -> WomCompositeType {\n data -> File\ndata_index -> File \n}\nmetadata -> File \n}? (optional)",
  "humanwgs.pbsv_call_mem_gb": "Int (optional, default = if N<=3: 64 else 96)",
  "humanwgs.glnexus_mem_gb": "Int (optional, default = 30)",
  "humanwgs.run_tertiary_analysis": "Boolean (optional, default = false)",
  "humanwgs.backend": "HPC",
  "humanwgs.preemptible": true
}

Thank you
Priya

Hi Priya, please remove the lines marked as (optional) from the json file and run it again.

@pb-dstucki is right.  The problems here are the optional inputs.  Some of the template values are the type of value, rather than the actual value (e.g. "Int", "String", "Boolean", "WomCompositeType").  These values need to be replaced or deleted, depending on whether they are optional or required.  Optional inputs can be deleted, like "humanwgs.deepvariant_model", if there's no need to change them.  You can remove:

humanwgs.deepvariant_version
humanwgs.deepvariant_model
humanwgs.pbsv_call_mem_gb
humanwgs.glnexus_mem_gb

If you don't need the tertiary analysis, you can remove humanwgs.run_tertiary_analysis and it default to false.  If you do need tertiary analysis, change this line to:
  "humanwgs.run_tertiary_analysis": true,

If the template says Int or Boolean, then the value needs to be bare (without quotes).  This is json syntax.

Hi all, The supplied GCP input json example is still giving errors:
Workflow input processing failed

(Caused by [reason 1 of 5]: Failed to evaluate input 'pbsv_call_mem_gb' (reason 1 of 1):
 For input string: "Int (optional, default = if N<=3: 64 else 96)")

(Caused by [reason 2 of 5]: Failed to evaluate input 'glnexus_mem_gb'
  	(reason 1 of 1): For input string: "Int (optional, default = 30)")

(Caused by [reason 3 of 5]: Failed to evaluate input 'run_tertiary_analysis'
  	(reason 1 of 1): No coercion defined from '"Boolean (optional, default = false)"' of type 'spray.json.JsString' to 'Boolean'.)

(Caused by [reason 4 of 5]: Failed to evaluate input 'preemptible'
  	(reason 1 of 1): No coercion defined from '"Boolean"' of type 'spray.json.JsString' to 'Boolean'.)

Caused by [reason 5 of 5]: Failed to evaluate input 'deepvariant_model'
  	(reason 1 of 1): No coercion defined from '"WomCompositeType {\n model -> WomCompositeType {\n data -> File\ndata_index -> File \n}\nmetadata -> File \n}? (optional)"' of type 'spray.json.JsString' to 'WomCompositeType { model -> WomCompositeType { data -> File data_index -> File } metadata -> File }?'.)

Can you all provide an input json that works right out of the box? Or at least some documentation on how to get it working?

As in the comment above, delete the optional inputs and set preemptible to truef;
this:
{
  ...
  "humanwgs.deepvariant_version": "1.5.0",
  "humanwgs.deepvariant_model": "WomCompositeType {\n model -> WomCompositeType {\n data -> File\ndata_index -> File \n}\nmetadata -> File \n}? (optional)",
  "humanwgs.pbsv_call_mem_gb": "Int (optional, default = if N<=3: 64 else 96)",
  "humanwgs.glnexus_mem_gb": "Int (optional, default = 30)",
  "humanwgs.run_tertiary_analysis": "Boolean (optional, default = false)",
  "humanwgs.backend": "HPC",
  "humanwgs.preemptible": "Boolean"
}

becomes this:
{
  ...
  "humanwgs.backend": "HPC",
  "humanwgs.preemptible": true
}

Are you sure backend should be HPC and not GCP if we are on Terra?

Sorry, yes, should be GCP for Terra.  I was copy/pasting from the comment above.


feat: Complex slice inputs for dynamic slice builtins

Description
Problem*
Resolves #3364
Summary*
This PR heavily changes the way slice intrinsics are implemented in ACIR gen. Following the fill_internal_slices pass nested slices now have dummy data automatically attached to them to enable known sizes to be used when fetching from an array with nested slices. Most of the slice intrinsics were written for non-complex inputs and also did not account for the addition of already included dummy data. With dummy data already included we cannot simply push back or push front elements for example, we need to make sure we do not alter the size of the internal slice we are using.
The slice intrinsic implementations essentially treat the input already as a dynamic array and perform the appropriate memory operations upon them. I considered alternatives and went with what I think is the most efficient way to implement these intrinsics, however, there is definitely room for cleanup and in the name of getting a first iteration working, we can consider how to optimize these intrinsics in another PR.
I have added comments in the ACIR gen itself to help with some of the logic for the implementation, but do let me know if something is not clear and I can document it further.
The fill_internal_slices pass now also accounts for slice constants passed as inputs to slice intrinsics as these must also be filled with dummy data when they are being attached to a nested slice.
Additional Context
A bug was found in the fill_internal_slices pass that was necessary to resolve this issue. Essentially the children fetched from a slice were not being accurately tracked when an array_get occurs. This fix is included in this PR as it did not come up until more complex operations with nested slices were attempted.
SliceInsert and SliceRemove now use a dynamic index. I only tested using a constant index in this PR and will have a followup PR that shows this tested out as this PR is already large enough.
Documentation*
Check one:

[ ] No documentation needed.
[X] Documentation included in this PR.
[ ] [Exceptional Case] Documentation to be submitted in a separate PR.

PR Checklist*

[X] I have tested the changes locally.
[X] I have formatted the changes with Prettier and/or cargo fmt on default settings.

I'm still definitely worried the slice handling code is too complex for one feature. This PR looks good but I could be missing something since it is hard to grok the whole context.

Thanks for the review. Yeah slice handling has gotten quite complex with the introduction of arbitrarily nested slices. As @TomAFrench is out today I was going to let him take a look before merging. He has been looking at how to optimize some of the dynamic array code and although I think a followup PR is better to add optimizations, perhaps there are some obvious inefficiencies I missed.


Woven methods lost their protected scope

Hi
A woven protected method lost it's "protected" scope.
class TargetClass {
    public function helloWorld()
    {
    }
    protected function helloHere()
    {
    }
}
$obj = new TargetClass();
$obj->helloHere();

Without weaving it throws "Error: Call to protected method ..."
But after weaving the method became "public" so we can call it without error.

This, as a fact, was a choice I have made, I will add an option in the kernel to either deactive this behaviour or keep it active.

Hello @WalterWoshid
Perhaps it's a good choice, I've no idea. What was your motivation for this behavior?
I just seen that when writing unit test ; it has no error while I was calling a protected method ;-)

Hi @Cyrille37,
good question! In my old job we used Magento 2, which is a module-based e-commerce framework for an online shop. Here we mostly bought other modules for good money and sometimes we had to adjust the logic of those modules with plugins. Those worked like AOP, but they were ugly and the biggest problem we had was that sometimes we couldn't intercept private and protected classes and I think maybe even final classes and methods. For this reason, and because sometimes a private method just NEEDS to be intercepted, I have allowed my library to do just that.
Encapsulation is a good thing, don't get me wrong, but only if it is implemented correctly, which I don't often see. For that reason I have implemented this "feature", which I will add as an option to the kernel, so that people can disable it if they want :)
Also I later want to add intercepting code structure (see issue https://github.com/okapi-web/php-aop/issues/46) which will take it to a more extrem approach of intercepting code.


ncurses detection fails when ncurses is built w/out suffixes

ncurses has the configure option --disable-lib-suffixes that drops "w" suffixes.
Please consider making your configuration more flexible and detect such situation.
In the FreeBSD port for ncurses the above option was added and musikcube now fails to find ncurses.

Thanks for the heads up. I recently setup a dedicated FreeBSD box but I'm very much a novice. Can I reproduce the problem by fetching the latest ports and trying to build musikcube from /usr/ports?

Thanks for the heads up. I recently setup a dedicated FreeBSD box but I'm very much a novice. Can I reproduce the problem by fetching the latest ports and trying to build musikcube from /usr/ports?

Can I reproduce the problem by fetching the latest ports and trying to build musikcube from /usr/ports?

Yes, musikcube from current ports would fail if you would remove the specific patch that I've added today to fix this problem.

Can I reproduce the problem by fetching the latest ports and trying to build musikcube from /usr/ports?

Yes, musikcube from current ports would fail if you would remove the specific patch that I've added today to fix this problem.

Got it. Even after reading some documentation I'm not quite sure how to detect whether or not the existing library on the system was compiled with the --disable-lib-suffixes switch, so I'm not sure how to automatically detect this configuration.
In the meantime, however, I added a custom cmake flag called NCURSES_DISABLE_LIB_SUFFIXES that can be specified manually to link against the non-suffixed libraries; while maybe not completely ideal, you won't have to have a custom patch any longer.
You should just be able to add the following to the port Makefile:
CMAKE_ARGS=     -DNCURSES_DISABLE_LIB_SUFFIXES=true
Oh, unrelated, I noticed the LICENSE in the musikcube port's Makefile is incorrect, musikcube uses a standard 3-clause BSD license, not GPLv2. https://github.com/clangen/musikcube/blob/master/LICENSE.txt

Got it. Even after reading some documentation I'm not quite sure how to detect whether or not the existing library on the system was compiled with the --disable-lib-suffixes switch, so I'm not sure how to automatically detect this configuration.
In the meantime, however, I added a custom cmake flag called NCURSES_DISABLE_LIB_SUFFIXES that can be specified manually to link against the non-suffixed libraries; while maybe not completely ideal, you won't have to have a custom patch any longer.
You should just be able to add the following to the port Makefile:
CMAKE_ARGS=     -DNCURSES_DISABLE_LIB_SUFFIXES=true
Oh, unrelated, I noticed the LICENSE in the musikcube port's Makefile is incorrect, musikcube uses a standard 3-clause BSD license, not GPLv2. https://github.com/clangen/musikcube/blob/master/LICENSE.txt

You could also call find_package twice with and without "w" and then require for at least one to be present.

You could also call find_package twice with and without "w" and then require for at least one to be present.

You could also call find_package twice with and without "w" and then require for at least one to be present.

I'll need to do a bit more research, but I think there may be issues doing this; musikcube doesn't support the "non-wide" version of ncurses -- or at the very least is highly untested. If we unconditionally link against non-suffixed libraries (in the absence of ones suffixed with "w") the app may not function properly. Ideally we'd be able to determine whether or not a non-suffixed library is actually a wide-character version.

You could also call find_package twice with and without "w" and then require for at least one to be present.

I'll need to do a bit more research, but I think there may be issues doing this; musikcube doesn't support the "non-wide" version of ncurses -- or at the very least is highly untested. If we unconditionally link against non-suffixed libraries (in the absence of ones suffixed with "w") the app may not function properly. Ideally we'd be able to determine whether or not a non-suffixed library is actually a wide-character version.

If removal of the "w" suffix also removes any part of functionality of ncurses - this was an erroneous change in the ncurses port.

If removal of the "w" suffix also removes any part of functionality of ncurses - this was an erroneous change in the ncurses port.

I am by no means an ncurses expert, and know various Linux distributions (e.g. Arch, Manjaro and likely others) only provide non-suffixed versions that always support the "wide-character" functionality. The wide-version, from my understanding, is a superset of the non-wide version.
This is one of my references: https://invisible-island.net/ncurses/ncurses.faq.html

The normal ncurses libraries support 8-bit characters. The ncurses library can also be configured (--enable-widec) to support wide-characters (for instance Unicode and the UTF-8 encoding). The corresponding wide-character ncursesw libraries are source-compatible with the normal applications. That is, applications must be compiled and linked against the ncursesw library.

...

The ncurses and ncursesw libraries are reasonably source-compatible. That is, an application written for "ncurses" will build with "ncursesw". But it will behave differently in response to your locale settings. (Some distributors, who do not care about the differences, have chosen to merge the names together as "ncurses").

So, applications built with historical, non-"w" versions of ncurses should be compatible with the "w" versions, but not the other way around.
Specifically, my past experimentation has shown that the non-wide version may not render non ASCII symbols properly. musikcube uses a handful of different Unicode characters to draw more complicated parts of the terminal UI.
For operating systems / distributions that only provide non-suffixed, "wide" versions of ncurses I've added special cases in the CMake files to not include the "w" suffix. If FreeBSD is heading in that direction, I can do it for that as well.

I am by no means an ncurses expert, and know various Linux distributions (e.g. Arch, Manjaro and likely others) only provide non-suffixed versions that always support the "wide-character" functionality. The wide-version, from my understanding, is a superset of the non-wide version.
This is one of my references: https://invisible-island.net/ncurses/ncurses.faq.html

The normal ncurses libraries support 8-bit characters. The ncurses library can also be configured (--enable-widec) to support wide-characters (for instance Unicode and the UTF-8 encoding). The corresponding wide-character ncursesw libraries are source-compatible with the normal applications. That is, applications must be compiled and linked against the ncursesw library.

...

The ncurses and ncursesw libraries are reasonably source-compatible. That is, an application written for "ncurses" will build with "ncursesw". But it will behave differently in response to your locale settings. (Some distributors, who do not care about the differences, have chosen to merge the names together as "ncurses").

So, applications built with historical, non-"w" versions of ncurses should be compatible with the "w" versions, but not the other way around.
Specifically, my past experimentation has shown that the non-wide version may not render non ASCII symbols properly. musikcube uses a handful of different Unicode characters to draw more complicated parts of the terminal UI.
For operating systems / distributions that only provide non-suffixed, "wide" versions of ncurses I've added special cases in the CMake files to not include the "w" suffix. If FreeBSD is heading in that direction, I can do it for that as well.

I think we worked this one out, but I can't remember. If there's something left to be done, let me know. Closing for now to clean up stale issues I'm not looking at.


YAML / simulated device: Need support for sending DNS-SD advertising messages individually

Problem
Need support for YAML to send/receive messages to a simulated device and send/receive messages from chip-tool so that we can verify the Node discovery/commissioning process on a step-by-step basis.
Note: this functionality is already present in device discovery / commissioning but cannot thoroughly be tested without constructing and sending DNS-SD advertising messages individually.
Examples

[TC-SC-4.3] Operational Discovery - Node test step 4 requires sending, intentionally, incorrectly formatted data so that the DUT can be sure it does not respond. https://github.com/CHIP-Specifications/chip-test-plans/blob/master/src/securechannel.adoc#343-tc-sc-43-operational-discovery---node

[TC-SC-4.4] Operational Discovery - Controller [DUT - Controller] needs to test steps at precise times so that it can verify all of the correct advertising data before trying another step.  https://github.com/CHIP-Specifications/chip-test-plans/blob/master/src/securechannel.adoc#344-tc-sc-44-operational-discovery---controller-dut---controller

@manjunath-grl can you try out the methods listed in https://github.com/project-chip/connectedhomeip/blob/master/src/app/tests/suites/TestDiscovery.yaml  and try out how many of the SC/CADMIN tests this unblocks us with ?


Unknown transform "name/cti/kebab"

Trying to use the basic example to generate a tailwind config. I have no idea what this means 🙃
Error:
Unknown transform "name/cti/kebab" found in platform "tailwind":
"name/cti/kebab" does not match the name of a registered transform.
at transformConfig (file:///Users/mattias/Code/c2-tokens-test/node_modules/.pnpm/style-dictionary@4.0.1/node_modules/style-dictionary/lib/transform/config.js:95:11)
at StyleDictionary.getPlatform (file:///Users/mattias/Code/c2-tokens-test/node_modules/.pnpm/style-dictionary@4.0.1/node_modules/style-dictionary/lib/StyleDictionary.js:561:28)
at async StyleDictionary.buildPlatform (file:///Users/mattias/Code/c2-tokens-test/node_modules/.pnpm/style-dictionary@4.0.1/node_modules/style-dictionary/lib/StyleDictionary.js:840:44)
at async Promise.all (index 0)
at async StyleDictionary.buildAllPlatforms (file:///Users/mattias/Code/c2-tokens-test/node_modules/.pnpm/style-dictionary@4.0.1/node_modules/style-dictionary/lib/StyleDictionary.js:885:7)

Node.js v20.15.0
 ELIFECYCLE  Command failed with exit code 1.

I have exactly the same issue right now

@traed Found the issue: You have to use Style Dictionary v3, not v4!

Thanks. I found that too, but sadly this whole ecosystem seem to have more issues than is fixable. This plugin only seem to support the legacy (non-W3C) format of design tokens. The exported design tokens I have don't follow any standard either and every implementation seem to do their own thing. I ended up writing my own parser that doesn't use style dictionary at all.


travis: fix Xenial tests not being run on master

Attempt number two (after https://github.com/containerd/containerd/pull/3606)

Ok; this looks to work so far; just filtering on pull_request events looks to exclude Xenial on PR's;
When opening the PR:

After a rebase/force-push (which was what I thought the push event filter was needed for);

@estesp PTAL; again, no idea if this works on master, but just filtering on pull_request so far looks hopeful.

Codecov Report

Merging #3614 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #3614   +/-   ##
=======================================
  Coverage   42.38%   42.38%
=======================================
  Files         126      126
  Lines       13901    13901
=======================================
  Hits         5892     5892
  Misses       7123     7123
  Partials      886      886

Flag
Coverage Δ

#linux
45.91% <ø> (ø)
:arrow_up:

#windows
37.2% <ø> (ø)
:arrow_up:

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 48fb479...cd79e0e. Read the comment docs.

Codecov Report

Merging #3614 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #3614   +/-   ##
=======================================
  Coverage   42.38%   42.38%
=======================================
  Files         126      126
  Lines       13901    13901
=======================================
  Hits         5892     5892
  Misses       7123     7123
  Partials      886      886

Flag
Coverage Δ

#linux
45.91% <ø> (ø)
:arrow_up:

#windows
37.2% <ø> (ø)
:arrow_up:

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 48fb479...cd79e0e. Read the comment docs.

Not a big fan of making these CI changes when we are about to start our release cycle. Let's merge and see if it works.

LGTM

it worked: https://travis-ci.org/containerd/containerd/builds/580494864; thanks @thaJeztah

Great!


chore Add 'sync' after stream_load in some cases

Proposed changes
When running regression testing in a multi-fe environment, sometimes test cases fail due to no rows selected.
Problem summary
Describe your changes.
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


feat: adds PING support to momento proxy resp impl

Overall, this works. I think it'd be cleaner for the pong response to be part of the RESP protocol implementation, as that will be useful when we add a redis compatible backend.


Container Apps DAPR config parameter

Does container apps support passing in a config parameter so I can scope secrets?  How would I do this in Container Apps?
Locally you can run your app and pass the config in.  Then your app can only access the secrets you define:
dapr run --app-id myApp --config config.yaml
config.yaml
apiVersion: dapr.io/v1alpha1
kind: Configuration
metadata:
  name: appconfig
spec:
  secrets:
    scopes:
      - storeName: vault
        defaultAccess: deny
        allowedSecrets: ["secret1", "secret2"]

Here are the docs from DAPR on this:
https://docs.dapr.io/developing-applications/building-blocks/secrets/secrets-scopes/#scenario-1--deny-access-to-all-secrets-for-a-secret-store

I think what you are requesting is DaprComponents. DaprComponents is used for config dapr related components. You could follow the doc to have a try to see if this met your requirements. https://learn.microsoft.com/en-us/azure/container-apps/microservices-dapr?tabs=bash


Update implementation status in Edge

The implementation status changed regarding Edge from Under Consideration => Preview Release.
Removing IE as it is not supported.

I believe script[type=module] is what is behind a flag, not any Loader stuff.

Okay. I was confused as Implementation Status linked to the MS dev page where it is marked as Preview Release

@matthewp Both, loader and grammar, are implemented.
https://twitter.com/nolanlawson/status/776787021108908032

It's not this loader though; it's the <script type="module"> loader.

You are right @domenic – #152 helps a lot.
Thanks @nolanlawson for re-clarifying implementation status on Edge. I think this PR can be closed then.


Make chicken fried steak

This hits #3 and #10

Actually, I would rather do something like these with cube steaks:

https://www.foodnetwork.com/recipes/ree-drummond/chicken-fried-steak-with-gravy-recipe-1925056
https://www.foodnetwork.com/recipes/alton-brown/chicken-fried-steak-recipe-1917219

saved these links in https://github.com/mikrostew/recipes/commit/c9d7dee6bb7ce7d69479470824b6bd3260ab7f27


Const Logic Wrong in ESS Calc

Description:
The recent update to the effective sample size code included logic to return NaNs when all of the draws across all of the chains were equal to the same constant value.  The implementation of that logic incorrectly implies that all single chains are constant with NaN effective sample sizes.
Reproducible Steps:
Compute effective sample size from a single chain.
Current Output:
nan
Expected Output:
Not nan
Additional Information:
Current Version:
develop

The same logic is used in compute_potential_scale_reduction.hpp.  Should I file a new issue to get that logic cleaned up too?

Yes, please!

On Sep 22, 2019, at 1:32 PM, Edward A. Roualdes<EMAIL_ADDRESS>wrote:
The same logic is used in compute_potential_scale_reduction.hpp https://github.com/stan-dev/stan/blob/develop/src/stan/analyze/mcmc/compute_potential_scale_reduction.hpp. Should I file a new issue to get that logic cleaned up too?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub https://github.com/stan-dev/stan/issues/2820?email_source=notifications&email_token=AALU3FX7XTBVC6PPPIAXNIDQK623ZA5CNFSM4IYN7AN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7JMHGA#issuecomment-533906328, or mute the thread https://github.com/notifications/unsubscribe-auth/AALU3FWJOSVJ64XZJUMSDL3QK623ZANCNFSM4IYN7ANQ.


Consider adding unhandledrejection/rejectionhandled

Chrome has added 2 new event types: unhandledrejection and rejectionhandled.  These are useful promise global rejection handlers, which I've personally used with Bluebird before and are now available with Chrome: https://googlechrome.github.io/samples/promise-rejection-events/

+1 this would be really nice

+1, I was looking for this earlier

+1

Now available at https://caniuse.com/#feat=unhandledrejection


MudForm fields should reflect FluentValidation client-side

Feature request type
Enhance component
Component name
MudForm
Is your feature request related to a problem?
I want to use FluentValidation since it's better to centralize validation to a single point in a lot of scenarios, but the issue I face is basically the fact that it's not reflected client-side and then I can't show a "*" for required fields or maxlength of inputs is always set to "524288" even though in the Validator it's at 100.
To get the actual "required" aspect of a field, I then need to add a class to the input which defeats the point of having the validator declaring the required aspect of it.
Describe the solution you'd like
It'd be great if the fact that, let's say a MudTextField with the For attribute could add an attribute "data-val-required" or something of the sort if the Validator defines it as "NotEmpty". It would allow for javascript interaction or even css adjustments. The main thing would be to not be forced to duplicate information at separate place rendering it hard to maintain in the long run.
Have you seen this feature anywhere else?
I think Blazored.FluentValidation does exactly that, though I think it uses EditForm instead.
Describe alternatives you've considered
No response
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I analyzed the code a bit and it looks like since all components already have the Required property from the FormComponent, maybe looking for the Required property when Validation is not null should look to see if it's required or not?


Use @autoclosure on build()

build() returns nil on first nil key

Oh, this is a great work! Thank you for the PR. :sparkling_heart:

Looks good! :+1:


[BACKLOG-16428] Spoon - Set up framework for repository file open/save

@bmorrise

Build Completed
:white_check_mark: This pull request has passed all validations.
Build Commands
mvn -B -fn -f plugins/pom.xml clean install && mvn -B -f plugins/pom.xml site

Cleanup Commands
mvn -B -f plugins/pom.xml build-helper:remove-project-artifact

Changed files
  plugins/file-open-save-plugin/.gitignore
  plugins/file-open-save-plugin/assemblies/pom.xml
  plugins/file-open-save-plugin/assemblies/src/main/feature/feature.xml
  plugins/file-open-save-plugin/impl/core/pom.xml
  plugins/file-open-save-plugin/impl/core/src/main/config/javascript/osgi/build.js
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/app.component.js
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/app.css
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/app.html
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/app.module.js
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/appTemp.html
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/breadcrumb/breadcrumb.component.js
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/breadcrumb/breadcrumb.css
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/breadcrumb/breadcrumb.html
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/card/card.component.js
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/card/card.css
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/card/card.html
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/error/error.component.js
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/error/error.css
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/error/error.html
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/files/files.component.js
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/files/files.css
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/files/files.html
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/folder/folder.component.js
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/folder/folder.css
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/folder/folder.html
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/add_folder.svg
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/breadcrumb_blue.svg
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/chevron_down_tree.svg
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/chevron_right_tree.svg
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/clear_blue.png
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/clear_gray.png
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/delete_folder_file.svg
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/folder.svg
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/home.svg
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/job_large.svg
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/job_small.svg
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/public.svg
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/recents.svg
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/search_blue.png
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/search_gray.png
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/sort_ascend.svg
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/sort_decend.svg
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/sort_down.svg
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/sort_none.svg
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/sort_up.svg
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/trans_large.svg
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/trans_small.svg
  plugins/file-open-save-plugin/impl/core/src/main/resources/META-INF/js/package.json
  plugins/file-open-save-plugin/impl/core/src/main/resources/OSGI-INF/blueprint/blueprint.xml
  plugins/file-open-save-plugin/impl/core/src/main/resources/app/css/fonts/opensans/opensans-light.eot
  plugins/file-open-save-plugin/impl/core/src/main/resources/app/css/fonts/opensans/opensans-light.svg
  plugins/file-open-save-plugin/impl/core/src/main/resources/app/css/fonts/opensans/opensans-light.ttf
  plugins/file-open-save-plugin/impl/core/src/main/resources/app/css/fonts/opensans/opensans-light.woff
  plugins/file-open-save-plugin/impl/core/src/main/resources/app/css/fonts/opensans/opensans-regular.eot
  plugins/file-open-save-plugin/impl/core/src/main/resources/app/css/fonts/opensans/opensans-regular.svg
  plugins/file-open-save-plugin/impl/core/src/main/resources/app/css/fonts/opensans/opensans-regular.ttf
  plugins/file-open-save-plugin/impl/core/src/main/resources/app/css/fonts/opensans/opensans-regular.woff
  plugins/file-open-save-plugin/impl/core/src/main/resources/app/css/fonts/opensans/style.css
  plugins/file-open-save-plugin/impl/core/src/main/resources/app/css/index.css
  plugins/file-open-save-plugin/impl/core/src/main/resources/app/index.html
  plugins/file-open-save-plugin/impl/core/src/main/resources/i18n/app/messages.properties
  plugins/file-open-save-plugin/impl/core/src/main/resources/i18n/app/messages_en.properties
  plugins/file-open-save-plugin/impl/pom.xml
  plugins/file-open-save-plugin/pom.xml
  plugins/pom.xml

Build Completed
:x: This pull request has errors. They will need to be addressed before it can be accepted. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f engine/build.xml clean-all resolve jacoco && ant -f engine/build.xml checkstyle publish-local
ant -Dtestreports.dir=bin/reports/unit-test -f ui/build.xml clean-all resolve jacoco && ant -f ui/build.xml checkstyle publish-local
ant -Dtestreports.dir=bin/reports/unit-test -f plugins/pdi-pur-plugin/build.xml clean-all resolve jacoco && ant -f plugins/pdi-pur-plugin/build.xml checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  engine/src/org/pentaho/di/core/LastUsedFile.java
  plugins/file-open-save-plugin/impl/core/pom.xml
  plugins/file-open-save-plugin/impl/core/src/main/java/org/pentaho/repo/controller/RepositoryBrowserController.java
  plugins/file-open-save-plugin/impl/core/src/main/java/org/pentaho/repo/endpoint/RepositoryBrowserEndpoint.java
  plugins/file-open-save-plugin/impl/core/src/main/java/org/pentaho/repo/model/RepositoryDirectory.java
  plugins/file-open-save-plugin/impl/core/src/main/java/org/pentaho/repo/model/RepositoryFile.java
  plugins/file-open-save-plugin/impl/core/src/main/java/org/pentaho/repo/model/RepositoryObject.java
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/app.component.js
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/app.html
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/app.module.js
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/breadcrumb/breadcrumb.component.js
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/breadcrumb/breadcrumb.html
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/card/card.component.js
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/card/card.html
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/files/files.component.js
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/files/files.html
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/folder/folder.component.js
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/folder/folder.html
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/services/data.service.js
  plugins/file-open-save-plugin/impl/core/src/main/resources/OSGI-INF/blueprint/blueprint.xml
  plugins/file-open-save-plugin/pom.xml
  plugins/pdi-pur-plugin/src/org/pentaho/di/repository/pur/PurRepository.java
  ui/src/org/pentaho/di/ui/spoon/Spoon.java

Unit test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.job.entries.evalfilesmetrics.JobEntryEvalFilesMetrics

Branch Change:  + .39%
Complexity Change:  + .51%
Instruction Change:  + .08%

org.pentaho.di.job.entries.evaluatetablecontent.JobEntryEvalTableContent

Branch Change:  + 1.01%
Complexity Change:  + 1.06%
Instruction Change:  + .17%

org.pentaho.di.job.entries.getpop.MailConnectionMeta

Branch Change: -1.00%:small_red_triangle_down:
Complexity Change: -1.41%:small_red_triangle_down:
Instruction Change: -.30%:small_red_triangle_down:

org.pentaho.di.job.entries.sql.JobEntrySQL

Instruction Change: -3.28%:small_red_triangle_down:
Line Change: -3.87%:small_red_triangle_down:

org.pentaho.di.job.entries.waitforsql.JobEntryWaitForSQL

Branch Change:  + 1.32%
Complexity Change:  + 1.85%
Instruction Change:  + .27%

org.pentaho.di.trans.steps.csvinput.CsvInputMeta

Instruction Change:  + .05%

org.pentaho.di.trans.steps.datagrid.DataGridMeta

Instruction Change:  + .09%

org.pentaho.di.trans.steps.dbproc.DBProcMeta

Instruction Change: -.11%:small_red_triangle_down:

org.pentaho.di.trans.steps.dimensionlookup.DimensionLookupMeta

Branch Change:  + .31%
Instruction Change:  + .06%
Line Change: -.23%:small_red_triangle_down:
Method Change: -1.02%:small_red_triangle_down:

org.pentaho.di.trans.steps.groupby.GroupByMeta

Branch Change: -1.04%:small_red_triangle_down:
Complexity Change: -1.05%:small_red_triangle_down:
Instruction Change: -.14%:small_red_triangle_down:
Line Change: -.37%:small_red_triangle_down:

org.pentaho.di.trans.steps.ldapoutput.LDAPOutputMeta

Instruction Change: -.06%:small_red_triangle_down:

org.pentaho.di.trans.steps.memgroupby.MemoryGroupByMeta

Branch Change: -2.35%:small_red_triangle_down:
Complexity Change: -2.70%:small_red_triangle_down:

org.pentaho.di.trans.steps.rowgenerator.RowGeneratorMeta

Instruction Change:  + .08%

org.pentaho.di.trans.steps.setvalueconstant.SetValueConstantMeta

Instruction Change: -.14%:small_red_triangle_down:

org.pentaho.di.trans.steps.sort.SortRowsMeta

Instruction Change: -.08%:small_red_triangle_down:

org.pentaho.di.trans.steps.uniquerows.UniqueRowsMeta

Instruction Change:  + .18%

org.pentaho.di.www.TransformationMap

Branch Change: -3.41%:small_red_triangle_down:
Complexity Change: -3.08%:small_red_triangle_down:
Instruction Change: -.94%:small_red_triangle_down:
Line Change: -1.54%:small_red_triangle_down:

org.pentaho.di.ui.spoon.Spoon

Branch Change: -.01%:small_red_triangle_down:
Complexity Change: -.01%:small_red_triangle_down:
Instruction Change: -.00%:small_red_triangle_down:
Line Change: -.00%:small_red_triangle_down:
Method Change: -.01%:small_red_triangle_down:

org.pentaho.di.repository.pur.PurRepository

Instruction Change: -.02%:small_red_triangle_down:
Line Change: -.03%:small_red_triangle_down:

License header violations

:heavy_exclamation_mark: Copyright year is not the current year on engine/src/org/pentaho/di/core/LastUsedFile.java. Found 2016. Was expecting 2017

:heavy_exclamation_mark: Couldn't find acceptable copyright on plugins/file-open-save-plugin/impl/core/src/main/java/org/pentaho/repo/controller/RepositoryBrowserController.java

:heavy_exclamation_mark: Couldn't find acceptable license on plugins/file-open-save-plugin/impl/core/src/main/java/org/pentaho/repo/controller/RepositoryBrowserController.java

:heavy_exclamation_mark: Couldn't find acceptable copyright on plugins/file-open-save-plugin/impl/core/src/main/java/org/pentaho/repo/endpoint/RepositoryBrowserEndpoint.java

:heavy_exclamation_mark: Couldn't find acceptable license on plugins/file-open-save-plugin/impl/core/src/main/java/org/pentaho/repo/endpoint/RepositoryBrowserEndpoint.java

:heavy_exclamation_mark: Couldn't find acceptable copyright on plugins/file-open-save-plugin/impl/core/src/main/java/org/pentaho/repo/model/RepositoryDirectory.java

:heavy_exclamation_mark: Couldn't find acceptable license on plugins/file-open-save-plugin/impl/core/src/main/java/org/pentaho/repo/model/RepositoryDirectory.java

:heavy_exclamation_mark: Couldn't find acceptable copyright on plugins/file-open-save-plugin/impl/core/src/main/java/org/pentaho/repo/model/RepositoryFile.java

:heavy_exclamation_mark: Couldn't find acceptable license on plugins/file-open-save-plugin/impl/core/src/main/java/org/pentaho/repo/model/RepositoryFile.java

:heavy_exclamation_mark: Couldn't find acceptable copyright on plugins/file-open-save-plugin/impl/core/src/main/java/org/pentaho/repo/model/RepositoryObject.java

:heavy_exclamation_mark: Couldn't find acceptable license on plugins/file-open-save-plugin/impl/core/src/main/java/org/pentaho/repo/model/RepositoryObject.java

Checkstyle violations
The code submitted is not complying with one or more of our guidelines. To perform these checks locally, please use this tool.
/home/buildguy/project/ui/src/org/pentaho/di/ui/spoon/Spoon.java

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 5,120 Column: 78

Build Completed
:white_check_mark: This pull request has passed all validations.
Build Commands
mvn -B -fn -f plugins/pom.xml clean install && mvn -B -f plugins/pom.xml site

Cleanup Commands
mvn -B -f plugins/pom.xml build-helper:remove-project-artifact

Changed files
  plugins/file-open-save-plugin/.gitignore
  plugins/file-open-save-plugin/assemblies/pom.xml
  plugins/file-open-save-plugin/assemblies/src/main/feature/feature.xml
  plugins/file-open-save-plugin/impl/core/pom.xml
  plugins/file-open-save-plugin/impl/core/src/main/config/javascript/osgi/build.js
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/app.component.js
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/app.css
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/app.html
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/app.module.js
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/appTemp.html
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/breadcrumb/breadcrumb.component.js
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/breadcrumb/breadcrumb.css
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/breadcrumb/breadcrumb.html
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/card/card.component.js
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/card/card.css
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/card/card.html
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/error/error.component.js
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/error/error.css
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/error/error.html
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/files/files.component.js
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/files/files.css
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/files/files.html
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/folder/folder.component.js
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/folder/folder.css
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/components/folder/folder.html
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/add_folder.svg
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/breadcrumb_blue.svg
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/chevron_down_tree.svg
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/chevron_right_tree.svg
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/clear_blue.png
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/clear_gray.png
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/delete_folder_file.svg
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/folder.svg
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/home.svg
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/job_large.svg
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/job_small.svg
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/public.svg
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/recents.svg
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/search_blue.png
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/search_gray.png
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/sort_ascend.svg
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/sort_decend.svg
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/sort_down.svg
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/sort_none.svg
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/sort_up.svg
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/trans_large.svg
  plugins/file-open-save-plugin/impl/core/src/main/javascript/app/images/trans_small.svg
  plugins/file-open-save-plugin/impl/core/src/main/resources/META-INF/js/package.json
  plugins/file-open-save-plugin/impl/core/src/main/resources/OSGI-INF/blueprint/blueprint.xml
  plugins/file-open-save-plugin/impl/core/src/main/resources/app/css/fonts/opensans/opensans-light.eot
  plugins/file-open-save-plugin/impl/core/src/main/resources/app/css/fonts/opensans/opensans-light.svg
  plugins/file-open-save-plugin/impl/core/src/main/resources/app/css/fonts/opensans/opensans-light.ttf
  plugins/file-open-save-plugin/impl/core/src/main/resources/app/css/fonts/opensans/opensans-light.woff
  plugins/file-open-save-plugin/impl/core/src/main/resources/app/css/fonts/opensans/opensans-regular.eot
  plugins/file-open-save-plugin/impl/core/src/main/resources/app/css/fonts/opensans/opensans-regular.svg
  plugins/file-open-save-plugin/impl/core/src/main/resources/app/css/fonts/opensans/opensans-regular.ttf
  plugins/file-open-save-plugin/impl/core/src/main/resources/app/css/fonts/opensans/opensans-regular.woff
  plugins/file-open-save-plugin/impl/core/src/main/resources/app/css/fonts/opensans/style.css
  plugins/file-open-save-plugin/impl/core/src/main/resources/app/css/index.css
  plugins/file-open-save-plugin/impl/core/src/main/resources/app/index.html
  plugins/file-open-save-plugin/impl/core/src/main/resources/i18n/app/messages.properties
  plugins/file-open-save-plugin/impl/core/src/main/resources/i18n/app/messages_en.properties
  plugins/file-open-save-plugin/impl/pom.xml
  plugins/file-open-save-plugin/pom.xml
  plugins/pom.xml

Unit test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.trans.steps.googleanalytics.GaInputStepMeta

Instruction Change: -.07%:small_red_triangle_down:


Revert #19074 and #19082 to fix broken AMDGPU tests.

Failing tests from the first PR: https://github.com/iree-org/iree/actions/runs/11748241815/job/32733175285#step:8:482
Second PR was landed on top, preventing a clean revert without also reverting that.

Got one workflow back to green: https://github.com/iree-org/iree/actions/runs/11749278696/job/32735553110?pr=19086. Others are still running, queued due to other runners being stuck on jobs that were never finishing. Merging before that gets worse.

Thanks for catching this I will take a look at the tests and try to re-land once they are fixed.


Add rules to convert .map(_ => f) to .as(f) and .map(_ => ()) to .void

Thanks for the PR! We have to be thoughtful about this one I think. The .map(_ => ()) rule is very good 👍
The .map(_ => f) to .as(f) is a bit trickier, because in the first f is lazily evaluated but in the second it is strictly evaluated. This can have implications for performance or recursion. Thus it's only safe to make this substitution if f is a val (and not a lazy val, def, or expression`).
Apologies if that's what you've already coded here (I'm not very good at reading scalafix :) in which case we should definitely add some tests cases for it


Move the contributing to .github templates

Is your feature request related to a problem? Please describe.
Recently @vr-varad did a PR about how to contribute to this repo, and this is polluting the core info in the readme, the ideal would be to create a contribute template with this info. I am leaving the info here.
## How to Contribute

### Starting Stack

- Clone the repository:

    ```bash
    git clone https://github.com/metacall/landing-page.git
    cd landing-page
    ```

### How to Run

1. Install `docsify-cli` globally:

    ```bash
    npm install docsify-cli -g
    ```

2. Initialize docsify in the "./docs" directory:

    ```bash
    docsify init ./docs
    ```

3. Run the local server with docsify:

    ```bash
    docsify serve docs
    ```

    You can now preview your site in your browser by navigating to [http://localhost:3000](http://localhost:3000).

Done: https://github.com/metacall/landing-page/pull/14#issuecomment-2018919136


feat(textlint-tester): add description field

This PR attempts to add the  description option to textlint-tester.
closes: https://github.com/textlint/textlint/issues/1005

Thanks!


MM-23524: Integrate Dependency-Check into CircleCI

Before submitting, please confirm you've

[x] read and understood our Contributing Guidelines
[x] completed Mattermost Contributor Agreement
[ ] executed npm run lint:js for proper code formatting

Please provide the following information:
Summary
Adds a check-deps job to the CircleCI workflow.
Issue link
https://mattermost.atlassian.net/browse/MM-23524
Test Cases
Additional Notes

The file .circleci/config.yml is in the blacklist and should not be modified from external contributors, please if you are part of the Mattermost Org submit this PR in the upstream.
/cc @mattermost/core-security @mattermost/core-build-engineers

The file .circleci/config.yml is in the blacklist and should not be modified from external contributors, please if you are part of the Mattermost Org submit this PR in the upstream.
/cc @mattermost/core-security @mattermost/core-build-engineers


Doc is not up to date

"The deployment options page appears while syncing." ITy doesn't. It takes you through Kudu instead.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 52d4b59f-07fd-b894-01f7-9bc2fc06e98a
Version Independent ID: 1cb6913e-21a7-48d2-8b83-cb416304b0c5
Content: Publish a Node.js app to Linux App Service - Visual Studio
Content Source: docs/javascript/publish-nodejs-app-azure.md
Product: visual-studio-dev15
GitHub Login: @Mikejo5000
Microsoft Alias: mikejo

Doc needs a refresh for validation. Creating a work item and closing this.


Other regulation GVL support

Are we going to support GVLs for different regulations in the library? For example IAB Canada GVL for  tcfca ?

Yes, Canada has a separate GVL from Europe.
EU: https://vendor-list.consensu.org/v3/vendor-list.json
Canada: https://vendor-list.consensu.org/v2/ca/vendor-list.json

@HeinzBaumann thanks, so we need to have update GPP lib logic to make it multi-GVL ready. Maybe, I am not sure, but API need to be updated also as now these two guys (see the snippet) looks very IAB TCF EU GVL specific:
getGvlFromVendorList(vendorList: VendorList): GVL
async getGvlFromUrl(gvlUrlConfig: GVLUrlConfig): Promise<GVL>

Another question regarding US regulations and vendors. No vendors related signals in US segments (sub-strings) are present, is it correct? The vendors are related ONLY to tcfeuv2 and tcfcav1, right?

As far as I know, yes, so far vendor signals only apply to tcfeuv2 and tcfcav1.

@HeinzBaumann thanks, so we need to have update GPP lib logic to make it multi-GVL ready. Maybe, I am not sure, but API need to be updated also as now these two guys (see the snippet) looks very IAB TCF EU GVL specific:
getGvlFromVendorList(vendorList: VendorList): GVL
async getGvlFromUrl(gvlUrlConfig: GVLUrlConfig): Promise<GVL>

The format and mechanism to retrieve the GVL is the same between EU and Canada. But in a GPP it require to cache both at the same time. So I would think spoec and library will need to account for this.

Yes, we could update GVL type to make it more genetic and include Canada specific fields like impConsPurposes, but it will create a mess that it's difficult to manage and support.
For example now GPP GVL still has TCF v2 properties like policyUrl (optional) that need to be deprecated and urls also optional that must be present for TCF v2.2. It will be better to have separate types like EuGVL and CaGVL and then GVL = EuGVL | CaGVL if needed.
The other problem with VendorList interface that also need to be regulation specific under the hood as now it holds Vendor form EuGVL.
So, maybe it will be easier to have regulation specific functions, like
getEuGvlFromVendorList(vendorList: EuVendorList): EuGVL
async getEuGvlFromUrl(gvlUrlConfig: GVLUrlConfig): Promise<EuGVL>

What do you think @HeinzBaumann

That works for me.


Composer Support

Is there a support for composer planned?

Honestly, not anytime soon. I'm incredibly busy lately and haven't had the time to give this project much love. If you're interested on working on that, I'm super happy to have other people contributing to the project.


How to generate using multiple data elements like form data

HI
I would like to generate QR code with form data like..I will be having one form which contains Name, DOB, Gender, Phone etc and when I submit it should generate QRCode and when I scan it should display all fields and values. Is there any option or anyway to add multiple data elements.? Please Suggest me. Thank you!

data is just the text written on qrcode.
You should maybe make your multiple form and concatenate all in the data field

You can store your form data as JSON form. You can easily manipulate JSON data anywhere.
Like:
{"fullName":"Numan Naseer Nomi", "nickName":"Nomi", "company":"NOMi"}