Bump github.com/nats-io/nats-server

This also bumped golang.org/x/exp which included some breaking changes. We will move off golang.org/x/exp/slices onto the stdlib one soon.
Description of the PR

PR Checklist

[ ] All commits have a Developer Certificate of Origin (DCO) -- they are generated using -s flag to git commit.
[ ] All new changes are covered by tests
[ ] If GraphQL schema is changed, make generate has been run
[ ] If collectsub protobuf has been changed, make proto has been run
[ ] All CI checks are passing (tests and formatting)
[ ] All dependent PRs have already been merged

Supersedes #1315

Looks like ent and arango integration tests also need to be updated, will do that now.


Update index.html

Fixed start tag and end tag to same value.
Changed end tag from heading level 2 to heading level 3 for same level as start tag.

Good catch, thank you!


Pluseargs parsing fix

This commit fixes $value$plusargs sytem function error described in #497.

Thanks a lot @TAD-dev for this fix!


How can I make the workspace and documents persist across different environments?

I noticed it always create brand new instance whenever I install it on different environments.
For example, I initially installed anything-llm on my local machine, created workspaces and documents but when I had to install anything-llm on GCP, I had to recreate the workspaces and documents again. Then, I moved to Digital Ocean, I had to recreate the workspaces and documents once again.
Note that I used the same .env details across each installation.
Am I doing something wrong?
Expected result:
I should automatically find the workspaces and documents I created on a new environment

@ajosegun I was thinking of implementing your clear instruction on how to use anything-llm on GCP. Is there a notable benefit for deploying it on Digital Ocean instead? If so I would be much interested to know more if that is OK with you. Thanks in advance!

@ajosegun I was thinking of implementing your clear instruction on how to use anything-llm on GCP. Is there a notable benefit for deploying it on Digital Ocean instead? If so I would be much interested to know more if that is OK with you. Thanks in advance!

Deploying on AWS v GCP v XYZ is just a matter of preference

@ajosegun Just want to clarify you basically would like a way to backup/upload an entire environment from instance to instance - correct?

@timothycarambat yes, a way to backup/upload an entire environment from instance to instance

@ajosegun Just want to clarify you basically would like a way to backup/upload an entire environment from instance to instance - correct?

Yes

Maybe a way to persist the Workspace DB outside the volume.

@ajosegun roger that
https://github.com/Mintplex-Labs/anything-llm/issues/145
Working on it now

Thanks for working on this so fast.
I just tried it and I am getting "{"error":"No auth token found."}"
Note that I hosted it on GCP with AUTH_TOKEN and JWT_SECRET set in the .env file


Planemo integration: Testing tools from VSCode

Ref #95
Planemo basic integration
This sets the foundation to interact with planemo from the VSCode Galaxy Tools extension.
A new planemo icon has been added to the VSCode activity bar (on the left). For the moment it just displays a welcome message and provides a shortcut button to go directly to the settings related to the planemo configuration.

In the new settings, you can point to the planemo binary that will be used to launch all the planemo commands and you can also set the galaxy root directory used by some of them.
Planemo Tests
The first feature included in this PR is the ability to run tests for the currently opened tool directly from the Test Explorer.

The tests are automatically discovered by the galaxy-language-server when you open a tool or save the tool document (this can be changed in the settings).
You can then run all the tests from the Test Explorer by using planemo test in the background. Currently running individual tests is not supported as AFAIK planemo does not have an option to do so at the moment.
After successfully running the tests, the results will be displayed in a convenient way directly on your source XML.

The failing tests will be marked in red and the reason for failure can be seen directly beside the test definition in the same line or more detailed in the Output. You can also directly navigate to each of the tests XML source from the Test Explorer.
This can be very convenient especially when having a large number of tests in your tool.

The test integration in VSCode has been possible by implementing a Test Adapter for the Test Explorer UI Extension.
New requirements
The Test Explorer UI Extension will be now a required dependency extension that needs to be installed alongside the Galaxy Tools extension if the user doesn't have it already installed.

Amazing!


Report Grid: add lifecycle phase to the filter options

Description
Would be useful to add lifecycle phase to the filters.  Should work for

[ ] Change Initiatives
[ ] Applications
[ ] Filter Notes

Resourcing
We intend to contribute this feature

Probably don't want to do this as a custom one-off change as it breaks the current ways that filters are implemented and would lead to a lot of bespoke code for this one option.  Instead we should look to deprecate the column and add it to the entity field references.
We should also look to add a column like 'enumerable' to the field ref table.   This would indicate to the grid that the value could be turned into a set of options for filtering, rather than the default implementation which just gives: 'Provided' / 'Not Provided'


Elaborate an unsupported scenario

A customer was confused because the original sentence indicates Entra joined devices do not support RADIUS authentication for connecting to Wi-Fi access points in any scenarios. I added supplemental information to clarify the unsupported scenario.

@MicrosoftGuyJFlo

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


📓 Updated Hungarian translation

Acc there's an issue in this xlf file, it won't build -> lines 2963, 2983

@gave92 These files are very tricky, we should probably build the app before approving these PRs. For some reason the build pipeline doesn't find any issues even if they are there.

For some reason the build pipeline doesn't find issues when it comes to these files.

Yeah that was what got me xD


python312Packages.llama-parse: 0.5.14 -> 0.5.16

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.llama-parse is: Parse files into RAG-Optimized formats
meta.homepage for python312Packages.llama-parse is: https://pypi.org/project/llama-parse/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.5.16 with grep in /nix/store/m3jym5djc6a39ai0165j4jwx6m6mrskp-python3.12-llama-parse-0.5.16
found 0.5.16 in filename of file in /nix/store/m3jym5djc6a39ai0165j4jwx6m6mrskp-python3.12-llama-parse-0.5.16

Rebuild report (if merged into master) (click to expand)

7 total rebuild path(s)

7 package rebuild(s)

First fifty rebuilds by attrpath

python311Packages.llama-index
python311Packages.llama-index-readers-llama-parse
python311Packages.llama-parse
python312Packages.llama-index
python312Packages.llama-index-readers-llama-parse
python312Packages.llama-parse

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/m3jym5djc6a39ai0165j4jwx6m6mrskp-python3.12-llama-parse-0.5.16 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.llama-parse https://github.com/r-ryantm/nixpkgs/archive/b4c5c2da8134314c93b1777a646a86460ed6ce6c.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/b4c5c2da8134314c93b1777a646a86460ed6ce6c#python312Packages.llama-parse

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/m3jym5djc6a39ai0165j4jwx6m6mrskp-python3.12-llama-parse-0.5.16
ls -la /nix/store/m3jym5djc6a39ai0165j4jwx6m6mrskp-python3.12-llama-parse-0.5.16/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 12 packages built:

python311Packages.llama-index
python311Packages.llama-index-readers-llama-parse
python311Packages.llama-index-readers-llama-parse.dist
python311Packages.llama-index.dist
python311Packages.llama-parse
python311Packages.llama-parse.dist
python312Packages.llama-index
python312Packages.llama-index-readers-llama-parse
python312Packages.llama-index-readers-llama-parse.dist
python312Packages.llama-index.dist
python312Packages.llama-parse
python312Packages.llama-parse.dist

Maintainer pings
cc @fabaff for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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

Done in #362854.


Improve helm chart and docker delivery

Push docker images when a PR is merged on Master
Fix several issues in helm chart
Add documentation: how to deploy with helm chart.
Update and Fix default manual deployment

Codecov Report

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

@@           Coverage Diff           @@
##           master      #75   +/-   ##
=======================================
  Coverage   29.79%   29.79%
=======================================
  Files          17       17
  Lines        1638     1638
=======================================
  Hits          488      488
  Misses       1114     1114
  Partials       36       36

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 fcc2d4f...58fc89e. Read the comment docs.


use trained model to separate files

Hi, before we start, I know this question may be out of scope, but it's still something related to mmdetection, so come on, I'm getting to know the tool and I trained a model (autoassign) to recognize a certain type of animal (dog specifically) and I would like to use this model trained in a script to separate images into a folder with several images of the trained animal and garbage (everything that is not a dog), the problem is that I am at a loss when it comes to knowing when the animal was detected after making the inference, reading a little the argmax in the variable that received the result of the inference seemed to solve my problem since it always returns a fixed value when it recognizes the animal in the image, but it is not always, so I would like to know if there is another most reliable method of knowing when my model has recognized the animal in the image so I can separate it from the rest.

Have you seen https://github.com/open-mmlab/mmdetection/issues/8548#issue-1336286734, it seems quite similar to your situation.
As for having a reliable method, maybe add a parameter of --threshold in your separation script that puts the pictures of dogs in the folder if the result > threshold, and continues otherwise.


Fix .well-known response

I am currently using v5.0.1 and I am am realizing that both on Chrome and Firefox the .well-known response is not shown.
Here is the result for nytimes.com

The same issue is present on the following sites:

https://globalprivacycontrol.org/
https://global-privacy-control.glitch.me/
https://www.theatlantic.com/

So, it seems like displaying the .well-known is globally failing.
Can you look into that @Mattm27?

I have looked into this issue on my end to see if it was persisting and the well-known response is shown on my end for both Firefox and Chrome.
Chrome:

Firefox:

I have looked into this issue on my end to see if it was persisting and the well-known response is shown on my computer for both Firefox and Chrome.

Thanks, @Mattm27!
Did you update to v5.0.1 from the Chrome Web Store (i.e., are you using the dist version)? What OS etc. are you using?
For example, I am using v5.0.1 from the Chrome Web Store with the out of the box current Chrome (Version 125.0.6422.113 (Official Build) (arm64)) on most recent macOS, and under Website Response, "gpc:true}" is not shown, but it exists.
Can you post screenshots?

Yes I updated to v5.0.1 from the Chrome web store and am running mac OS v14.3.1
Here are screenshots:
Chrome:

Firefox:

I am not sure why there would be discrepancies with this behavior between devices.

This is resolved. It seems the reason this occurs is because when I updated OptMeowt, I did not enable the required permissions.

In more detail:
Because of just doing the update instead of a reinstall, I never saw the permission popup. I only saw it once I navigated to the OptMeowt settings. Then, I enabled it. That did not solve the issue immediately, though. When I retried loading the site, it still did not work. Then, I cleared my local browsing cache, uninstalled OptMeowt, and reinstalled it. After a bit of reloading and cache clearing, that did it. Now, it is working for me in both Chromium (Chrome and Opera) and Firefox. As an aside, this issue did not only affect the Website Response but also the 3rd Party Domains, which were not displayed either. It is still the case for some sites that I need to reload them to get the Website Response but also the 3rd Party Domains, but that is OK for the time being.


More flexible SSL certificate verification configuration

The Python requests library has more flexible configuration for SSL certificate verification than the PDC client currently permits. This patch removes the insecure configuration option in favor of ssl_verify (in the class constructor keyword arguments) and ssl-verify (in the JSON configuration format). The value is passed through directly to the requests session.
This is particularly useful for validation against a specific certificate, which can be specified as a path. See the requests documentation for more information.

Coverage decreased (-0.9%) to 88.074% when pulling 03c910d6f26a9dccfd69f7bf1609de4617637048 on ahills:ssl-verify into 8bdbf01522290d888748cda505c17b310dfe4b63 on product-definition-center:master.

Coverage increased (+0.3%) to 89.254% when pulling 2355bc4d677e9fca7b4173c39355e64280c3e54f on ahills:ssl-verify into 8bdbf01522290d888748cda505c17b310dfe4b63 on product-definition-center:master.

Coverage increased (+0.3%) to 89.254% when pulling 2355bc4d677e9fca7b4173c39355e64280c3e54f on ahills:ssl-verify into 8bdbf01522290d888748cda505c17b310dfe4b63 on product-definition-center:master.

One thing is that no amount of specfile magic will help with config files in ~/.config. I think it would be nice to print an explicit error when the old option is is used (or print a deprecation warning and somehow still accept the old option).

Coverage increased (+0.05%) to 89.052% when pulling 9ecec974d373f3e2e4fba789821f8dfd9a8795f7 on ahills:ssl-verify into 8bdbf01522290d888748cda505c17b310dfe4b63 on product-definition-center:master.

@ycheng-aa @lubomir
After a long delay, the insecure option is back with a warning. Its behavior is almost the exact opposite of ssl_verify, so ssl_verify = not insecure is used to implement the old behavior.
A side effect of this particular implementation (intentional) is that the insecure option, if present, will override any given ssl-verify value. I can also change it to the opposite, if you think that's best.

@lubomir @ycheng-aa
I don't have write access; could one of you merge this for me? Thanks!

Coverage increased (+0.3%) to 89.265% when pulling 9ecec974d373f3e2e4fba789821f8dfd9a8795f7 on ahills:ssl-verify into 8bdbf01522290d888748cda505c17b310dfe4b63 on product-definition-center:master.

Done.


System Setup

add a back and front end

add a frontend
add a .NET backend

@albert118 @JaydenL33 please create any setup PR's and subsequent branches off this issue


deploy and dist with gulp

We can now test deployment locally with gulp webserver
And we can create a dist-ready directory with gulp dist or gulp dist-min

Let's clean up some of the hound-ci code style issues. And squash into 1 commit then we can merge. Good work :+1:

@creativepsyco cleaned and squashed :smiley:


Not able to run hugging_interface -> example.py

I followed the instructions in the Readme and tried running the example.py file, but got this error:
$ python3 example.py
Traceback (most recent call last):
  File "/Users/devkrishna/Desktop/Playground/indic-language-stuff/indic-trans-2/IndicTrans2/huggingface_interface/example.py", line 176, in <module>
    en_indic_tokenizer, en_indic_model = initialize_model_and_tokenizer(
  File "/Users/devkrishna/Desktop/Playground/indic-language-stuff/indic-trans-2/IndicTrans2/huggingface_interface/example.py", line 105, in initialize_model_and_tokenizer
    tokenizer = AutoTokenizer.from_pretrained(ckpt_dir, trust_remote_code=True)
  File "/Users/devkrishna/miniconda3/envs/itv2_hf/lib/python3.9/site-packages/transformers/models/auto/tokenization_auto.py", line 906, in from_pretrained
    return tokenizer_class.from_pretrained(
  File "/Users/devkrishna/miniconda3/envs/itv2_hf/lib/python3.9/site-packages/transformers/tokenization_utils_base.py", line 2032, in from_pretrained
    return cls._from_pretrained(
  File "/Users/devkrishna/miniconda3/envs/itv2_hf/lib/python3.9/site-packages/transformers/tokenization_utils_base.py", line 2272, in _from_pretrained
    tokenizer = cls(*init_inputs, **init_kwargs)
  File "/Users/devkrishna/.cache/huggingface/modules/transformers_modules/ai4bharat/indictrans2-en-indic-1B/bb1e8f494be5855fa00cf845bae310dc4f22a20e/tokenization_indictrans.py", line 97, in __init__
    raise KeyError("<unk> token must be in vocab")

I am running on macOS using miniconda.

We attempted to replicate the issue on our end by setting up a fresh environment and observed that example.py runs without any problems.
I would recommend you to double-check your setup.
You can use the install.sh script to ensure that the recommended versions of all dependencies are appropriately installed.

I didn't run the 2nd step in the readme, because I didn't understand what the checkpoint_best.pt should be. I assumed it is meant for when we are using our finetuned model checkpoints. Is my assumption wrong? Where do I get this checkpoint if this step is necessary?
Converting
In order to convert the fairseq checkpoint to a PyTorch checkpoint that is compatible with HuggingFace Transformers, use the following command:
python3 convert_indictrans_checkpoint_to_pytorch.py --fairseq_path <fairseq_checkpoint_best.pt> --pytorch_dump_folder_path <hf_output_dir>

<fairseq_checkpoint_best.pt>: path to the fairseq checkpoint_best.pt that needs to be converted to HF compatible models
<hf_output_dir>: path to the output directory where the HF compatible models will be saved

You can use the install.sh script to ensure that the recommended versions of all dependencies are appropriately installed.

I had run the source install.sh command as per the readme, but mosestokenizer, nltk and protobuf didn't get installed; which I had to then manually pip install later.

https://github.com/AI4Bharat/IndicTrans2/issues/107#issuecomment-2543858369
The conversion process is not necessary if you plan to use the pre-trained models directly.
The "Conversion" section in the README provides instructions on how to convert your own Fairseq models into HuggingFace format. The "best checkpoint path" refers to the location of your trained Fairseq model.
If your goal is simply to run inference with the pre-trained models, you can skip the Conversion section and instead follow the instructions in the "Inference" section of the README.
You can additionally check out this Colab notebook, which includes the same code as the example.
We've tested it, and it works as expected.

Same error I am facing too, are you able to solve the issue

ile ~/.cache/huggingface/modules/transformers_modules/ai4bharat/indictrans2-en-indic-1B/bb1e8f494be5855fa00cf845bae310dc4f22a20e/tokenization_indictrans.py:97, in IndicTransTokenizer.init(self, src_vocab_fp, tgt_vocab_fp, src_spm_fp, tgt_spm_fp, unk_token, bos_token, eos_token, pad_token, do_lower_case, **kwargs)
95 self.encoder = self._load_json(self.src_vocab_fp)
96 if self.unk_token not in self.encoder:
---> 97     raise KeyError(" token must be in vocab")
98 assert self.pad_token in self.encoder
99 self.encoder_rev = {v: k for k, v in self.encoder.items()}
KeyError: ' token must be in vocab'

Same error I am facing too, are you able to solve the issue

Unfortunately no, doesn't seem to work. I keep getting a similar error as you're facing
KeyError("<unk> token must be in vocab")

I have run the google colab same error I have faced

#107 (comment)
The conversion process is not necessary if you plan to use the pre-trained models directly.
The "Conversion" section in the README provides instructions on how to convert your own Fairseq models into HuggingFace format. The "best checkpoint path" refers to the location of your trained Fairseq model.
If your goal is simply to run inference with the pre-trained models, you can skip the Conversion section and instead follow the instructions in the "Inference" section of the README.
You can additionally check out this Colab notebook, which includes the same code as the example.
We've tested it, and it works as expected.

Just now I have run the google colab notebook same error

The issue may have been caused by changes in the Transformers library, leading to a type mismatch in how special tokens were handled in the latest versions.
The issue has been resolved and you should be able to run inference now.

The issue may have been caused by changes in the Transformers library, leading to a type mismatch in how special tokens were handled in the latest versions.
The issue has been resolved and you should be able to run inference now.

if feasible can you please let us know what went wrong that would be really helpful.

Refer this commit

Thanks a lot it is working now.


PageLoadingTable Message Translations

Current Behavior
Currently we don't have any way to support messages with translation for PageLoadingTable. Since it is using Table component under the hood to render the Table and Table component supports noRowsMsg prop to display message so in PageLoadingTable component I introduced noRowsMsg prop for Table component to render messages in PageLoadingTable.
Expected Behavior
PageLoadingTable component should display provided message and its translation in EN and DE.
Steps To Reproduce
Technical User Management is one of Page which is using PageLoadingTable component .

Login to Portal App.
Navigate to the Technical user management.
Search for data that doesn't exist (No search data case).
View the table when no data is present (Empty Table case).

@Usmanfee currently the shared components don't support i18n at all. All texts and messages have to be translated before and passed as props by the calling application. So I guess this means we have to expose the nowRowsMsg in the API.
On the long run it would be nice to have shared components handle translations but if we decide to do that we should implement a solution that works for all components.


Error in Description of new Security Jars.

New Security Jars referenced in the Document seems to invalid.
File: Migration_SAPJavaBuildpackProjects.md
Description Provided:
The above mentioned dependencies should be removed / replaced with this one:
<dependency>
    <groupId>com.sap.cloud.security.xsuaa</groupId>
    <artifactId>api</artifactId>
    <version>2.7.3</version>
    <scope>provided</scope> <!-- provided with buildpack -->
</dependency>

But in essence the Replacement Jars are:
<dependency>
    <groupId>com.sap.cloud.security</groupId>
    <artifactId>java-api</artifactId>
    <version>2.7.3</version>
    <scope>provided</scope> <!-- provided with buildpack -->
</dependency>

Please check and Advice.

Hi @harishannamalai
yeah, that's confusing, but its correct.
SAP Java Buildpack >= 1.26 provides two open-source "api"s.

com.sap.cloud.security.xsuaa:api (for compatibility reasons) as described in Migration Part 1
com.sap.cloud.security:java-api as described in Migration Part 2

Enjoy your weekend!
Nena


Add retry logic to download operations during dev release

Sometimes the appropriate latest ECR images/S3 artifacts may not be available for some projects during dev release. Usually this may happen when the corresponding artifact is still being built. This causes the dev release to fail looking for the missing objects. A better approach is to add retries to the download phase so that the dev release process can wait till the corresponding image/S3 artifact is available and then proceed.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@abhay-krishna: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

eks-anywhere-release-tooling-presubmit
ebcd3f16d910e10c540012366ff9dbd2e2c1e0b3
link
/test eks-anywhere-release-tooling-presubmit

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: abhay-krishna, g-gaston
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [abhay-krishna,g-gaston]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Nuke anchor fixes + cargo sell blacklist

About the PR
i hate players
:cl:

fix: Nukes can no longer be unanchored once they are armed, without disarming the nuke.
fix: The nuke and disk can no longer be sold to cargo.

How am I going to buy 25 corgi crates now 😔


Series without data breaks chart

Hi,
if you got a series defined and no field in the data it breaks your whole chart. Means all other series are not drawn anymore.
See: http://codepen.io/anon/pen/vNQyKX
If you enable "Series without data" by clicking on the legend it breaks the chart.
I cannot remove the series in my case because I need the legend label.

Hey, we're closing this because it's been a while and we're trying to avoid zombie issues. If the problem persists, please open a new issue (and don't forget, your issue is much more likely to be fixed if you provide a working CodePen : easier for us, faster for you !).
Thanks again for helping us making n3-charts awesome.
--
Sébastien & Christoph


[New Plugin]: pDf Reference Opcodes Or reGisters (DROOG)

Plugin Description
Per the README's Usage section,

This is a glorified PDF search for tokens that show up in tables of contents.
Select a token like an instruction or a register, and "Plugins" -> "DROOG" -> "Search Reference Headings..." will show pages from PDFs available for the current architecture. Click an image to open the PDF at that page in your browser.
For unfamiliar architectures, bind the search to a hotkey. There's also a command to peek at table of contents headings in the status bar for quickly reviewing mnemonics.

See repo README for a screenshot.
I added the pymupdf dependency as "dependencies": "pymupdf>=1.19.0\n", which I think is right but isn't in docs/testable? If it only works in official channel, I'll change it.
Plugin Repository URL
Repo URL: https://github.com/amtal/droog
Real Release

[X] I have made a real release

Dependencies are specified in requirements.txt (documented here). So you'll probably want to do a new release with that. It's actually a bug that the plugin.json dependencies field is overwritten by requirements.txt during generation of the master list regardless of whether the json contains it as well.
That particular bug is fixed in our new plugin/extension infrastructure which we'll be releasing soon.

Thank you for clear explanation. 1.0.1 minted to suit!

Thanks! Updated.


ADDV2 authentication Sign in wroking in  emulator but it is not working in published bot in msteams. No pop  up open on click of sign in

This is not for asking questions or filing bugs
To get help with an issue with your bot

"How To" questions should be submitted on Stack Overflow.

To file an issue against a component please go to the components repo

Create Azure Bot Framework Service or Channel issue
Create Bot Builder Tools issue
Create Bot Builder SDK V3 (.NET or Javascript) issue
Create Bot Builder SDK V4 .NET issue
Create Bot Builder SDK V4 Javascript issue
Create Bot Builder SDK V4 Java issue
Create Bot Builder SDK V4 Python issue

Issue
Describe the issue you are addressing
Proposed change
Describe the proposed solution
Component Impact
Describe which components need to be updated
Customer Impact
Describe the impact on customers
Tracking Status
Dotnet SDK

[ ] PR
[ ] Merged

Javascript SDK

[ ] PR
[ ] Merged

Java SDK

[ ] PR
[ ] Merged

Python SDK

[ ] PR
[ ] Merged

Emulator

[ ] PR
[ ] Merged

Samples

[ ] PR
[ ] Merged

Docs

[ ] PR
[ ] Merged

Tools

[ ] PR
[ ] Merged

[dcr]

Hi @poonam0025. I'm closing this issue because this repo is for DCR's only.
To file an issue against a component please go to the components repo

Create Azure Bot Framework Service or Channel issue
Create Bot Builder Tools issue
Create Bot Builder SDK V3 (.NET or Javascript) issue
Create Bot Builder SDK V4 .NET issue
Create Bot Builder SDK V4 Javascript issue
Create Bot Builder SDK V4 Java issue
Create Bot Builder SDK V4 Python issue

Also consider:

"How To" questions should be submitted on Stack Overflow.


fix: image-override should not update the version/repo in submariner cr

The image-override flag was updating the repo and version values.
This behaviour is confusing.
Closes #1303
Signed-off-by: Steve Mattar<EMAIL_ADDRESS>

(removing from the 0.9 board, because this is already being tracked there via the parent Issue)

(removing from the 0.9 board, because this is already being tracked there via the parent Issue)

oops, sorry, I keep adding PRs also, I'll stop doing for ones with parent issues


pixel value larger than 255 when using movingmnist_iterator script to generate data

my code using script to generate data
from nowcasting.movingmnist_iterator import MovingMNISTAdvancedIterator
import numpy as np

def preprocess_data(data):
    """Permute the axis to make the channel the last one and scale.

    Args:
        data: [time, batch_size, channel, height, width]

    Returns:
        processed data of shape [time, batch_size, height, width, channel]
    """
    data = np.transpose(data, [0, 1, 3, 4, 2])
    #scale
    #data = np.divide(data, 255.0)
    #to normalize in range [-1, 1]
    data = 2 * data / 255 + (-1)
    return data

ROTATION = (-15, 15)
test_total = 2000
seqlen = 16
PATH = str(seqlen) + '-testdata'
mnt_generator = MovingMNISTAdvancedIterator(rotation_angle_range=ROTATION)
test_vid, _ = mnt_generator.sample(batch_size=test_total, seqlen=seqlen)
print(np.amax(test_vid))
print(np.amin(test_vid))
test_vid = preprocess_data(test_vid)
print(np.amax(test_vid))
print(np.amin(test_vid))
np.save(PATH, test_vid)
print(test_vid.shape)

The result is as follows:
424.88824
0.0
2.3324568
-1.0
(16, 2000, 64, 64, 1)
where you can see the maximum value is 424.88824.

Yes, the script will generate pixel values larger than 255. @gaozhihan has a fix for that.

you mean @gaozhihan has fixed it already? Could you tell me in which repository?

you mean @gaozhihan has fixed it already or it's in progress?  If it's done, could you tell me where to find it ? I have looked at his repositories, but nothing found.

Thank you! Looking forward to seeing it.

I'm sorry that I didn't post it in this repo. Thanks for your comments. Please replace line 404 in movingmnist_iterator.py with (appearance_mult ** -(2 * (((i - 1) // 5) % 2) - 1))

I have noticed that line. But due to the use of modulo of 2,  2 * ((A // 5) % 2))  is either 0 or 2 no matter A is i or i - 1. So -(2 * ((A // 5) % 2) - 1)  is either  -1 or 1,  which will make  Term B larger than 1 when appearance_mult is less than 1. When Term B is larger than 1, then it's possible to have pixel value larger than 255.
Term B: (appearance_mult ** -(2 * (((i - 1) // 5) % 2) - 1))

But appearance_variants[i, :] won't be bigger than their initial values, since the loop starts with the maximum values

why won't appearance_variants[i, :]  be bigger than their initial values?
appearance_variants[i, :] = appearance_variants[i - 1, :] *\
                                     (appearance_mult ** -(2 * (((i - 1) // 5) % 2) - 1))

In above code snippet, if (appearance_mult ** -(2 * (((i - 1) // 5) % 2) - 1)) is larger than 1, then it could be larger than initial values.
Besides after changing that line, I try to generate test dataset, the maximum value is still larger than 255 in some settings (seqlen, batch_size).

Because they first decrease and then return to the initial values. You may print the value of Term B out to check the change trend. In my experiment settings, the above mentioned problem does not appear anymore. If it still goes wrong, please simply clip the values that are larger than 255. It doesn't affect a lot since it is a synthetic dataset.

Thank you very much for your response especially on holiday.  :coffee:


Alternate templating engine

Is it possible to configure another templating engine instead of Mustache?

Do you mean the delimiters?
For example, the delimiters {, } would look like:
<h1>{foo}</h1>

I just re-read the docs:

Moon has a custom templating syntax similar to Mustache.

i'ts not actually the Mustache engine

@kokujin Ahh, yes. Moon's templating engine is custom-made and a little different from mustache.

I would have to try some things out to solve that problem then. Thanks.


I can't understand how you manage nuget packages?

Hi, Marin.
I'm interesting to understand how you publish your nuget packages, especially all package.
Could you write several words?
It is not obvious, I can't find any script, but very interesting.

Hi @rpokrovskij,
I am not entirely sure if this is what you mean, but these are the PowerShell scripts I used to package and publish the 0.12.0 version of the Core Nuget packages.
ForEach ($folder in (Get-ChildItem -Path Core -Directory)) { dotnet pack $folder.FullName -c Release }
ForEach ($folder in (Get-ChildItem -Path Core -Directory)) { nuget push "$($folder.FullName)\bin\Release\$($folder.Name).0.12.0.nupkg" }

I change Core to Modules and Bundles to deploy the rest of the packages. And of course, I change the 0.12.0.nupkg version to whatever is the version currently being deployed.
You must set up Nuget CLI locally in order to use nuget push.
Please let me know if this helps clear things up or if you have any other questions.

Hi @rpokrovskij. I have added a script for packaging and publishing all projects to nuget.org.


Inc. solution for AutoGraph loop conversion

Included solution for AutoGraph's conversion of for loops to while_loops with parallel iterations on the GPU

Hey @gavinlive!
Thanks for tracking down and reporting this source of non-determinism. I want to capture this knowledge into the document, but I don't believe that Confirmed Current GPU-Specific Sources of Non-Determinism (With Solutions) is the correct location. Without thoroughly exploring the underlying cause, it's not clear to me that this is about a purely GPU-related source of non-determinism. Do you agree with that assessment? if so, I think that it should be covered in two places:

Additional Ingredients in the Determinism Recipe
Sources of Non-Determinism in TensorFlow Unrelated to GPU

I also think that this information can be made more general. The use of tf.while_loop when parallel_iterations is greater than 1 (noting that 10 is the default) may introduce non-determinism into model functionality. Then, additionally, the AutoGraph Transformations caused by tf.function may lead to loops being implemented using tf.while_loop and therefore parallelized, which may introduce non-determinism into model functionality.
Please will you enhance this PR appropriately?
Finally, I would like to add your name to the credits. I can simply add @gavinlive, if you want, or if you give me your first and last name then I will add that.

Hey @gavinlive!
Thanks for tracking down and reporting this source of non-determinism. I want to capture this knowledge into the document, but I don't believe that Confirmed Current GPU-Specific Sources of Non-Determinism (With Solutions) is the correct location. Without thoroughly exploring the underlying cause, it's not clear to me that this is about a purely GPU-related source of non-determinism. Do you agree with that assessment? if so, I think that it should be covered in two places:

Additional Ingredients in the Determinism Recipe
Sources of Non-Determinism in TensorFlow Unrelated to GPU

I also think that this information can be made more general. The use of tf.while_loop when parallel_iterations is greater than 1 (noting that 10 is the default) may introduce non-determinism into model functionality. Then, additionally, the AutoGraph Transformations caused by tf.function may lead to loops being implemented using tf.while_loop and therefore parallelized, which may introduce non-determinism into model functionality.
Please will you enhance this PR appropriately?
Finally, I would like to add your name to the credits. I can simply add @gavinlive, if you want, or if you give me your first and last name then I will add that.

Hi @duncanriach,
I will enhance this PR. You can add me as Gavin Seegoolam, thank you!

Oh, hey Gavin! We interacted by email recently. Did you get my response to your email?

Oh, hey Gavin! We interacted by email recently. Did you get my response to your email?

Yes, I received you response. I believe I responded to it but just in case, basically I added a new TensorFlow issue here: https://github.com/tensorflow/tensorflow/issues/39751 and also added another pull request to this repo which references this.
Hope you're doing well!

I didn't receive an email response from you, but I'll get to that other pull request, and the TF issue, soon.

Hey @gavinlive, I want to get this PR merged before it starts conflicting. I'm planning to merge it and then do the enhancements I mentioned above.


Custom configuration for architecture

In sonar-devon4j-plugin we are using Devon4jPackage to parse packages and derive architecture infomation (component, layer, scope). This is perfectly fine for devon4j projects and support for devon4j architecture checks with zero configuration shall obviously be kept.
However, it would be awesome for projects not exactly following devon4j architecture to be able to configure the architecture to overrule the default devon4j architecture.
This should be done in architecture.json file like this:
{
  "architecture": {
    "packages": {
        "pattern": "([a-zA-Z0-9_]+\.)+(persistence|core|service|gui)\.([a-zA-Z0-9_]+)\.(api|base|impl)(\.[a-zA-Z0-9_]+)*",
        "groups": [ "root", "layer", "component", "scope", "detail" ],
        "mappings": {  "persistence": "dataaccess", "core": "logic", "gui": "client"}
    }
  }
}

The pattern is the regular expression to match the package.
The groups map the groups of the regex to specifc functions. You may additionally use any other group-id here to ignore a group (e.g. in case of nested paranthesis).
With mappings custom names for layers, scopes, or even components (like general or app) can be mapped to devon4j standards in order to be understood properly.

For implementation a first step should be to encapsulare or even remove the usage of Devon4jPackage without changing the current behaviour.
A next step (maybe separate PR) would be to change the defaults as configured in architecture.json like described above.

To get started some hints to find the right spots in the code:

config needs to be added here: https://github.com/devonfw/sonar-devon4j-plugin/blob/master/src/main/java/com/devonfw/ide/sonarqube/common/api/config/Architecture.java
Devon4jPackage is created here and passed arround pretty much to every other rule: https://github.com/devonfw/sonar-devon4j-plugin/blob/master/src/main/java/com/devonfw/ide/sonarqube/common/impl/check/DevonArchitectureCheck.java#L164
See also here: https://github.com/devonfw/sonar-devon4j-plugin/blob/master/src/main/java/com/devonfw/ide/sonarqube/common/impl/check/DevonArchitectureCheck.java#L33
As you can see there are various methods used on this current Devon4jPackage like here: https://github.com/devonfw/sonar-devon4j-plugin/blob/master/src/main/java/com/devonfw/ide/sonarqube/common/impl/check/DevonArchitectureCheck.java#L190
So my suggestion would be to define a new class DevonArchitecturePackage as a kind of "wrapper" for Devon4jPackage that offers the same API methods and delegates them to an internal Devon4jPackage instance. Could you create a PR for this as a first step?

I have assigned @suvmanda several devon4j issues. Since he was busy with other tasks and has not started with this issue, it can go back to backlog and be addressed by sonar plugin team.

@adprus are you working on this? If so please assing yourself.

Finished with PR #106 and #107

It was wrong to close this issue as the feature is still not implemented. As you can see still the Devon4jPackage is used internally (also this class has no javadoc and will not match our code-style and might fail in sonarcloud check as well):
https://github.com/devonfw/sonar-devon4j-plugin/blob/master/src/main/java/com/devonfw/ide/sonarqube/common/api/config/DevonArchitecturePackage.java#L5
We have only prepated the feature but it still needs to be implemented.
@lmarniazman could you take this over as the people working on this are no more available.
Change this code-line:
https://github.com/devonfw/sonar-devon4j-plugin/blob/master/src/main/java/com/devonfw/ide/sonarqube/common/impl/check/DevonArchitectureCheck.java#L222
And instead use this method to get the configuration:
https://github.com/devonfw/sonar-devon4j-plugin/blob/master/src/main/java/com/devonfw/ide/sonarqube/common/api/config/Architecture.java#L88
and pass the resulting Packages instance as additional argument here:
https://github.com/devonfw/sonar-devon4j-plugin/blob/master/src/main/java/com/devonfw/ide/sonarqube/common/api/config/DevonArchitecturePackage.java#L9
Then as a final step, kick out Devon4jPackage and reimplement the required (!) methods of DevonArchitecturePackage based on the Packages instance. You can remove all unused methods from DevonArchitecturePackage.

Finally done with all PRs merged.


peerDependencies aren't bumped

Describe the bug
Hi, I have two packages A,B. B has a peerDependency to A.
{
  "name": "B",
  "peerDependencies": {
    "A": "workspace:^0.105.1"
  },
  "dependencies": {
    "A": "workspace:^0.105.1"
   }
}

After publishing A to 0.106.0 the version in dependencies was updated correctly but not for the peer-dependency.
I tried it as fixed constraints 0.105.0 and without the workspace protocol. In all cases, the peer-dependency was not bumped.
See https://github.com/lerna/lerna/issues/955
Expectation
I'd expect that the peer dependency is updated to the next compatible version based on the version constraint.
A bumps with semver ^0.105.0 to 0.105.2 => B  bumps with semver ^0.105.0 => 0.105.2 :heavy_check_mark:
A bumps with semver 0.105.0 to 0.106.0 => B bumps with semver 0.105.0 => 0.106.0 :x: because it is not compatible
Reproduction
See above.
Lerna config and logs
lerna.json

<!-- Please paste your `lerna.json` here -->

lerna-debug.log

<!-- If you have a `lerna-debug.log` available, please paste it here -->
<!-- Otherwise, feel free to delete this <details> block -->

Environment Info
| Executable        | Version |
| ----------------- | ------- |
| `lerna --version` | VERSION |
| `npm --version`   | VERSION |
| `yarn --version`  | VERSION |
| `node --version`  | VERSION |

---
OR simply run `npx lerna info` command and copy+paste the result here

Used Package Manager
pnpm
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion.
[X] The provided reproduction is a minimal reproducible example of the bug.

If we're reading a few of the comments associated to the issue you referenced, it seems that the original Lerna maintainer (evocateur) purposely left it this way because it's a rather sensitive subject that can be interpreted differently. Basically this post  is explaining it broadly

peer deps should never be forcefully updated; updating a minimum peer dep range is a breaking change. Peer dep ranges should always remain as broad as is possible.

and then if we scroll up a little and we click on the issue right above that post which is this issue

peerDependencies shouldn't be updated by lerna publish

and start reading what everyone says, it seems that everyone have different opinion on the subject.
In summary, I'm not so sure that I should deviate from the same implementation as to what Lerna already does, at this point in time, the code in Lerna-Lite follows the same logic as Lerna (which is to say again that evocateur didn't want to change/fix the issue you referenced). I think the best I could do would be to implement 1 of these 2 things

update only if it doesn't detect a version range that includes an operator (ie: "a": ">=1.0.0")
provide a flag to force update peer dependencies (not sure how to call it though, please provide name suggestion)

to be clear the force push is only for when the bump is actually possible

we could also go for a mix of 1 and 2, that is when the flag is enabled and we have an version range

I would rather go with option 2 which is to add a flag (need a name) and that wouldn't be too hard to implement in Lerna-Lite because I had already extracted the deps update into a new separate function retrievePackageDependencies to fix another peer deps issue you had opened a few months back, so I basically just need to provide true as the 2nd argument to this new function and that might just be enough but I don't want to implement it for everyone by default so we would have to go with 1 of these 2 approach
https://github.com/ghiscoding/lerna-lite/blob/9815d64388e14e3eb3eb1970c3a083c0dcb54ac2/packages/core/src/package.ts#L361-L384

Thank you for the explanation. I'll come up with a proposal.

I tested a few code change and found out that there's actually another indirect issue in both Lerna/Lerna-Lite. The way that the code is implemented is that it will only update the first dependency it finds (following this order: 1. dependencies, 2. localDependencies, 3. devDependencies and 4. peerDependencies) and so if we define the same dep in both properties dependencies and peerDependencies, well it will only update the first one and never the peer one. So I think adding an extra loop just for the peer deps might be required to fix this
in other words, if we take the demo you have
{
  "name": "B",
  "peerDependencies": {
    "A": "workspace:^0.105.1"
  },
  "dependencies": {
    "A": "workspace:^0.105.1"
   }
}

it would only update the first dependencies because of it's primary order even though defining both of these properties should be totally fine (it's only fine for peer deps, technically speaking it's the only time we should allow the same dep repeated)

@StarpTech could you please review the PR #362 which will close this issue

Yes, thank you :+1:


Support Mesh-based particles in 3D

Currently only simple billboard (flat texture) particles are supported. Would be nice to have a method of creating mesh-based particles (especially if more primitives, like spheres and cubes are added, as requested by #1381)
Is there a plan to implement mesh-based particles any time soon or should I just write a script for it?

Is there a plan to implement mesh-based particles any time soon or should I just write a script for it?

No plan that I know of, but I guess you inferred it when getting no answer ;) It's still an interesting idea though.

I also hope this will arrive in v3. Many 3D games wouldn't be as flashy and nice looking without 3D mesh particles

Bumping for the sake of it not being forgotten for 3.0 :smile:

working on it
On Tue, Dec 27, 2016 at 10:28 AM, Bojidar Marinov<EMAIL_ADDRESS>wrote:

Bumping for the sake of it not being forgotten for 3.0 😄
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/1418#issuecomment-269326052,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-Z27YSOQDjQpe3-rVcZA0p2eH4Y00eks5rMRKWgaJpZM4Dj7gg
.

subscribing. Looking for a way to do this for my current project!

This was implemented in the master branch.


Image API 3.0?

Hello,
Just came across this and am excited to test it out, but was wondering if there are any plans to upgrade this to IIIF Image API 3.0 in the near future?

@fitnycdigitalinitiatives There's currently an upstream dependency PR that would implement Image API v3.0, which would follow along here shortly after merge/release.

Excellent!


Set organizationName and regenerate headers

Ross's arguments look convincing to me. And I'm happy to merge this as is.


Error passing model with @computed() or pagination to Inertia.js

Package version
1.0.0-25
Describe the bug
I'm experiencing an error when passing models that contain @computed() or when using pagination with Inertia.js in my project. It seems that an error is occurring within the @adonisjs/inertiajs package.
The problem arises when a model with @computed() is passed to Inertia.js, resulting in a process failure. In addition, when using pagination, the same error also occurs.
I would like to request a review of this issue and possible fixes in the @adonisjs/inertiajs package to properly handle these scenarios.
Reproduction repo
https://github.com/lncitador/computed-and-pagination-error

Hello
You just need to serialize the data you send, otherwise you will get hydration errors
Your TestsController should be :
  async handle({ inertia, auth }: HttpContext) {
    const posts = await auth.user?.related('posts').query().paginate(1, 10)
    return inertia.render('test', { posts: posts?.serialize(), user: auth.user })
  }

and that's it

right, I know that you have to give .serialize(), but besides the fact that in the end it will infer a ModelObject type because of the method, this ends up being a nuisance when you have to do it over and over again in every controller handle, so I created a serialize function that already infers the type, take a look at the 'fixed' branch.

with this I created another branch for you to test my changes that I sent pull resquet, take a look at the 'feature' branch

Actually, I don't think it's a good idea to handle this directly in @adonisjs/inertia:

We tightly couple @adonisjs/inertia with Lucid. If I use Kysely instead of Lucid in my application, then your fix won't work. I'll inevitably need to install @adonisjs/lucid.
Here, you're only handling serialization specific to Lucid. But the problem will remain the same if we send any other class or object that needs to be serialized. even for a simple Date. If you're doing SSR and you don't serialize your Date instance before calling inertia.render, you'll also get a hydration error. The same goes for Map, Set, or any other non-primitives

That's why, for me, the responsibility of serialization should be on the user side, not on the @adonisjs/inertia side

@adonisjs/inertia being dependent on lucid is complicated when someone wants to use another querybuilder, about the serialization of non-primitives I was developing a solution with superjson, which I had used in another lib. but the lucid issue made me review everything and I saw that it is impossible to have this feature of automatic serialization

Yeah I don't think we should impose superjson or similar alternative, if people want to use it then they can quite easily add it on their side
In any case, thanks for the detailed reproduction! Same goes for PR


dovecot: Fix wrong type in configFile option

Motivation for this change
The option services.dovecot2.configFile is non-functional because it needs to be of type path since it's fed into environment.etc."dovecot/dovecot.conf".source.
Things done
FIxed services.dovecot2.configFile to require path rather than string.
Tested on our mail deployment.
Notify maintainers
None specified.

Let's try to notify @hrdinka who did the previous refactor of this module


Send auth information on first request

As per the RestAssured docs, we can use preemptive basic authentication:
This will send the basic authentication credential even before the server gives an unauthorized response in certain situations, thus reducing the overhead of making an additional connection. This is typically what you want to use in most situations unless you're testing the servers ability to challenge.

This will fix the issue raised in #30
What do you think?
fixes #30

Looks fine!
Thank you for your contribution.


Separate build command line for debug/release

In some situations you want to execute separate pre-build or post-build commands for debug and release configurations. For example, with Haxe-JS projects, you might want to automatically pass the generated JS through Google Closure or YUI on release builds, but not on debug builds.
There currently isn't a straightforward way to do that, however - only moving the config-specific commands into a separate file and using BuildConfig template variable with branching to execute or not execute it.
Visual Studio is a good reference for this kind of functionality.

It seems like there is already DEBUG: and RELEASE constants.
Just tried it myself:


Re-enable HMM tests

looks good
http://math-ci.amd.com/job/main/job/precheckin/job/rocPRIM/job/PR-661/1/pipeline-graph/
passed all tasks except ubuntu 22, seemingly due to machine issue
http://math-ci.amd.com/job/main/job/precheckin/job/rocPRIM/job/PR-661/2/pipeline-graph/
triggered a rerun here to confirm it was machine issue


feat: introduce error codes

Introduce error codes to the telemetry for easier tracking.

I'm actually going to hold off on this for now. I might improve it and come back with a better version later, but also the error cases in the telemetry are working fairly well at this point.


Clean URL before opening modal

When cycling throughout all the modals, if one sets params on the URL, that value stays there.
This PR triggers a replaceState with a clean URL before opening a modal. Also triggers a pushState with a clean URL after closing.

Nice! Thank you!!


Unable to rename columns in streaming dataset

Describe the bug
Trying to rename column in a streaming datasets, destroys the features object.
Steps to reproduce the bug
The following code illustrates the error:
from datasets import load_dataset
dataset = load_dataset('mc4', 'en', streaming=True, split='train')
dataset.info.features
# {'text': Value(dtype='string', id=None), 'timestamp': Value(dtype='string', id=None), 'url': Value(dtype='string', id=None)}
dataset = dataset.rename_column("text", "content")
dataset.info.features
# This returned object is now None!

Expected behavior
This should just alter the renamed column.
Environment info
datasets 2.6.1

Hi @peregilk this bug is directly related to https://github.com/huggingface/datasets/issues/3888, and still not fixed... But I'll try to have a look!

Thanks @alvarobartt. It is great if you are able to fix it, but when reading the explanation it seems like it is possible to work around it.
We also tried keeping the 'info.features' and then adding a modified version back after the remove/rename. Unforutunately that leads to a dataset that is not possible to iterate over.

So if you iterate over the IterableDataset as next(iter(ds)) and then run rename_columns when checking that data it will work, but at the end, it's just renaming the column one example/batch at a time, not renaming the column name for all the entries in the dataset, which is the ideal.

@alvarobartt Thanks. My use case was that I wanted to do multiple things, ie removing all unnecessary columns, renaming some valid columns, and then using cast (in my case checking if the audio is not 16K and casting it). It is just convenient to look into the info.features between each of these operations. Alternatively, I will just plan ahead...;) To me it seems like all the operations are working.
Thanks for the advice. It was very useful.

If we know the features before renaming, then we know the features after renaming, so we can pass the new features to the returned dataset in rename_column indeed ! If anyone is interested in contributing, feel free to open a PR and I'd be happy to help / give some pointers :)

#self-assign


[Geneva] Importing a specific invalid YAML DeviceProfile causes all subsequent device profile queries to fail

🐞 Bug Report
Affected Services
Metadata
Is this a regression?
No
Description and Minimal Reproduction
This is the corresponding issue of #2596 for Geneva branch

fixed by #2657


Ok 6 liking and disliking genres

Jira Link:
[Jira: ](https://champlainsaintlambert.atlassian.net/browse/OK-6?atlOrigin=eyJpIjoiYWVhMmMyOWM4M2U1NGE3Yzg1MWFjNDYwYTI5ZWM5ODUiLCJwIjoiaiJ9)
Context
Allow users to choose which genres they enjoy so that the recommendations system can make better predictions
Changes

Added firebase functions to get all genres, get liked genres for the user, and  update liked genres for the user
Added genre-lister and genre-item components to display genre information
Added genre type
Deleted useless wrong profile component
Made recoms and genre buttons only available for the logged in users profile

Before and After UI (Required for UI-Impacting PRs)
Before:

After:

LGTM, 2 things though:

Why change all the getFirestore to importing firestore directly?
Are the console.logs necessary? it causes unnecessary slowdowns

I changed the getFirestore() to the firestore variable because that variable is already equal to getFirestore() therefor for the sake of consistency I just made it all the same thing. Everything works the same I just wanted the code to be nicer and possibly more efficient.
I am keeping the console.logs until we are done with the project because they have saved me a few times and are a good indicator of how efficient the system is. They will all be removed in the final version don't worry.


Typing issue with Pinecone

Checklist

[X] I added a very descriptive title to this issue.
[X] I included a link to the documentation page I am referring to (if applicable).

Issue with current documentation:
If you update all pinecone/langchain packages to their latest versions:
↑ @langchain/community 0.2.4 → 0.2.6
↑ @pinecone-database/pinecone 2.2.1 → 2.2.2
↑ langchain 0.2.4 → 0.2.5

# having<EMAIL_ADDRESS>
Then the following code starts failing (in build-time):
// My index with or without custom type; doesn't matter
const pinecone = new Pinecone();
const pineconeIndex = pinecone.Index<{
  helpMePlease: string;
}>('index-prod-eu');

const vectorStore = await PineconeStore.fromExistingIndex(embeddings, {
    pineconeIndex, // <-
    namespace: 'books'
  });

Error with custom type:

Error without custom type:

Idea or request for content:
No response

Hey @dejoma, sorry you're running into this - could you share your lockfile? I'm unable to repro with my local setup.
Additionally (a bit of a shot in the dark) - can you try explicitly resolving your @langchain/core to a single version?
https://js.langchain.com/v0.2/docs/how_to/installation/#installing-integration-packages

I still get this error..
"dependencies": {
"@langchain/anthropic": "^0.2.3",
"@langchain/community": "^0.2.17",
"@langchain/langgraph": "^0.0.26",
"@langchain/pinecone": "^0.0.7",
"@pinecone-database/pinecone": "^3.0.0",
"dotenv": "^16.4.5",
"langchain": "^0.2.8",
"langsmith": "^0.1.36"
},
"overrides": {
"@langchain/core": "^0.2.14"
},

Going back to version 2.2.0 of @pinecone-database/pinecone solves the issue....

Good to know thanks! Will look into this

Hey @dejoma I just released @langchain/pinecone v0.0.8. Could you try again with that version?

Facing same issues with
"@pinecone-database/pinecone": "4.0.0",
"@langchain/pinecone": "0.1.1",

@bracesproul

Facing same issues with
"@pinecone-database/pinecone": "4.0.0",
"@langchain/pinecone": "0.1.1",

+1, also facing issues with these specific versions.

Going back to 3.0.3 is fixing the problem but it is a returning issue….


Added calculator app

Issue reference:
Proposed changes:
Added new project for beginners
Type of change:
New project
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] My changes generate no new warnings

Additional info (if any):

Nice work


Provide a script for easy debugging

script may

install vim
loosen php for cli access
Other idea welcome

How you can use it,
You can ssh into the VM, get into the container and run the script, then you'll be able to debug your app easily.

The suhosin extension is already in the simulation mode by default. Closing this for now.


Please Enhance the Scalability to Apply Also to RichText

Hello, I am currently making good use of the package you've provided. However, when specifying styles for each character using RichText and TextSpan, I cannot use XtyleText, and it is inconvenient to have to insert the font family manually for each one. Is there a solution for this case, or do you have any plans to upgrade the package in the future?

You can use XtyleText.rich constructor.
However, I have confirmed that the 0.1.3 version of the Xtyle.rich widget is not working as intended.
from version 0.2.0, You can use it  the same way as Text.rich.
XtyleText.rich(
                TextSpan(
                  text: 'Hello',
                  children: [
                    TextSpan(text: ' 안녕', style: TextStyle(color: Colors.red)),
                    TextSpan(text: ' World', style: TextStyle(color: Colors.blue)),
                  ],
                  style: TextStyle(fontWeight: FontWeight.bold),
                ),
                style: TextStyle(fontSize: 24), // default text style
              )


Substance Painter: Add support for sync workfile version

Changelog Description
This PR is to add sync workfile version option into substance painter host.
Additional info
Build the latest version of core addon and substance painter addon
Testing notes:

Enable Follow workfile version in ayon+settings://core/publish/CollectAnatomyInstanceData/follow_workfile_version
Publish
TextureSet and Workfile version should be aligned

One small comment:
@moonyuet  would it be possible to keep visible that option Follow workfile version on the Publish Instance so user could potentially switch the behaviour?? not sure if possible and also if good to have it exposed for ever...

@moonyuet would it be possible to keep visible that option Follow workfile version on the Publish Instance so user could potentially switch the behaviour?? not sure if possible and also if good to have it exposed for ever...

I wouldn't actually make that an artist's choice - that's a studio choice usually. Can you think of a use case where an artist really wants to take that control?

@BigRoy I get your point, makes sense
@moonyuet  But now we can control it only globally within Ayon Core Addon with this setting ?

I think we need to allow user to set it within Substance Painter addon imho....kind of local override so it doesnt follow global settings only imho?
@BigRoy opinion on this?

@moonyuet But now we can control it only globally within Ayon Core Addon with this setting ?

Yes, it is

I think we need to allow user to set it within Substance Painter addon imho....kind of local override so it doesnt follow global settings only imho?

@BigRoy I think we can do this too by using instance.data["followWorkfileVersion"]

But now we can control it only globally within Ayon Core Addon with this setting ?

I think we need to allow user to set it within Substance Painter addon imho....kind of local override so it doesnt follow global settings only imho?

Currently this is global to all I believe, and yes - that's how we use it. If we want to make that "profile" based so that we can go more complex there I'd make that a separate issue and separate PR but it's a valid request I suppose.

But now we can control it only globally within Ayon Core Addon with this setting ?

Looking at the logic now it's still in the creator - and not "globally" like in other hosts. Is it correct that you still need to implement it so that it matches e.g. the maya/houdini, etc. logic?

But now we can control it only globally within Ayon Core Addon with this setting ?

I think we need to allow user to set it within Substance Painter addon imho....kind of local override so it doesnt follow global settings only imho?

Currently this is global to all I believe, and yes - that's how we use it. If we want to make that "profile" based so that we can go more complex there I'd make that a separate issue and separate PR but it's a valid request I suppose.

I think we can do this too by using instance.data["followWorkfileVersion"]

I think profiles filtering logic can be used for this - but I'd not merge that into this PR.

I actually implement the logic here for temporary use. And once the profile setting has been finished we can make changes on
that.

I actually implement the logic here for temporary use. And once the profile setting has been finished we can make changes on
that.

I'd make the logic here match the other integrations - so it's aligned and once we move things over it works for all. Best not to deviate here, especially if it's "temporary".

I actually implement the logic here for temporary use. And once the profile setting has been finished we can make changes on
that.

I'd make the logic here match the other integrations - so it's aligned and once we move things over it works for all. Best not to deviate here, especially if it's "temporary".

I already restored the creator logic and the sync workfile version can only sync through the global settings and we can integrate profile setting later.


Library components and mac distribution

A first look at what a solution to #43 and/or #33 would look like. Would be interested on discussion, feedback and design considerations
Focus was to take some of the separate features of the library and define these components as separate cocoapod subspecs. This could be taken further, with other features like offline, but begins with specs of

MicrosoftAzureMobile/Core
MicrosoftAzureMobile/Login
MicrosoftAzureMobile/Push

Key feature would be to allow developers to only include the components of the library they need. The default install for the pod would remain as before (installing all of these subspecs and hence the complete library) avoiding breaking changes for existing developers or the quick start to include everything.
This change would also enable distribution of the Mac framework via cocoapods while limiting the install of the login subspec to iOS as there currently isn't a mac compatible implementation.

Hey @damienpontifex just a heads up, @shrishrirang is on vacation so it will probably be a few weeks before there is more action on this. We also have to figure out internally what infrastructure we need in order to test our OS X support, assuming we accept this PR.

Thanks @paulbatum although this was a while ago now. Things might be a little out of date.
It was a sample to play around with how it might work. Regardless of accepting or not, interested to open up/begin the discussion.

Hey @damienpontifex, thanks for the PR! Sorry to get back to you so late on this.
Overall, this seems like a good approach to sharing code between the two targets (iOS and OS X). After discussing in the team today we decided to park the changes for now. We will take up these changes when we plan to implement the login UI for OS X. We will continue to use  https://github.com/Azure/azure-mobile-apps-ios-client/issues/33 to track this. This PR will be a good starting point when we get back to this!

As mentioned in an earlier comment, this will be taken up later.


Add the ability to emit a diagnostic for broken URL links

Feature Name
URL destination checking
Description
I recently found and fixed a number of broken links from The Swift Programming Language (TSPL) to the Swift standard library documentation.  As far as I can tell, DocC doesn't currently have a way to detect dead links, so I built a script by hand using cmark and curl to check for this in the TSPL build script.
This seems like functionality that other projects besides TSPL could use, so it would be beneficial to incorporate it as a diagnostic for DocC.  Because checking the validity of links takes time and requires a network connection, it's probably something that should be opt-in.
Motivation
No response
Importance
No response
Alternatives Considered
No response

For reference, here's what I added to the TSPL preflight script:
cmark --to xml TSPL.docc/*/*.md |
xpath -q -n -e '//link/@destination' |
sort -u | cut -f2 -d= | grep -v '^"doc:' | sed 's/^"//; s/"$//' |
while read url
do
    if curl --silent --output /dev/null --fail --head $url
    then
        echo "     $url"
    else
        echo "BAD: $url"
        exit_status=1
    fi
done

I would argue that making web requests to verify that web links aren't broken is not something that DocC itself should do.
The specific issue with links to the Swift standard library would probably be better solved by #208 or #419.
What we could possibly do is create another opt-in digest file with all web links in the content so that other scripts don't need to parse the markdown, in-source comments, and tutorial files to find all the links themselves.


Forked Repo will not build inside other project

I forked the repo, and replaced my node_module with the forked repo. However now it complains that it cannot find 'lib:
ERROR in ./node_modules/react-dates/index.js
Module not found: Error: Can't resolve './lib' in '/Users/seb/repo/bonline/offer-marketplace/node_modules/react-dates'
 @ ./node_modules/react-dates/index.js 2:17-33
 @ ./resources/assets/js/shared/jobs/Panels/items/InformationJob/informationJobPanel.js
 @ ./resources/assets/js/shared/jobs/Panels/items/InformationJob/index.js
 @ ./resources/assets/js/views/singleJob/cards/InformationJobCard.js
 @ ./resources/assets/js/views/singleJob/cards/index.js
 @ ./resources/assets/js/views/singleJob/index.js
 @ ./resources/assets/js/views/jobs/index.js
 @ ./resources/assets/js/index.js
 @ multi ./resources/assets/js/index.js

ERROR in ./node_modules/react-dates/initialize.js
Module not found: Error: Can't resolve './lib/initialize' in '/Users/seb/repo/bonline/offer-marketplace/node_modules/react-dates'
 @ ./node_modules/react-dates/initialize.js 2:0-27
 @ ./resources/assets/js/index.js
 @ multi ./resources/assets/js/index.js

Solution:
open .gitignore file and remove items:
lib
esm

Now Commit your Lib and ESM folders, you can now install the module direct from GitHub


ckk.ai(Loan2Host) not Bypassing

Domain
https://ckk.ai/hnXhv7
Link
https://ckk.ai/hnXhv7
Version
0.0.0
What browsers are you seeing the problem on?
Firefox, Chrome
What OS are you seeing the problem on?
No response
Anything else?
No response

Duplicate of #668.


Make leb64 encoding fully safe

This removes all unchecked indexing as well as the usage of MaybeUninit::uninit().assume_init() from the leb64 encoding logic.
Resulting binary size change for the log binary:
   text	   data	    bss	    dec	    hex	filename
  33708	      0	      8	  33716	   83b4	log-main
  33508	      0	      8	  33516	   82ec	../../target/thumbv7m-none-eabi/release/log

That's right, it's 200 Bytes smaller.
I've also tried keeping MaybeUninit in place, which reduces binary size by like 400 more bytes. That seemed spooky, so I didn't go for that (zeroing 10 bytes shouldn't take 400 Bytes of code space? does it pull in memset? does it miscompile something due to the UB?). Haven't investigated that further.

bors r+

bors r+

was that with opt-level=3?

It was cargo build --release in the firmware/qemu directory, which should be opt-level=3, LTO=fat.

was that with opt-level=3?

It was cargo build --release in the firmware/qemu directory, which should be opt-level=3, LTO=fat.

needs a rebase but feel free to submit to bors once that's resolved

needs a rebase but feel free to submit to bors once that's resolved

bors r=japaric

bors r=japaric


Fix NoSuchMethodError on newer versions of PowerRanks

A recent(-ish) patch in PowerRanks ended up in the deletion of the PowerConfigurationSection causing a NoSuchMethodError to be thrown at runtime. This was replaced with Bukkit's ConfigurationSection
Untested, although it should work fine.

Does it compile?

Well yes, but actually no. It does not compile for 1.9.2, the current target version in the gradle script, but it does with newer versions of PR (after 1.9.7) but, y'know, us mortals don't have access to your maven repo so yeah I probably should've mentioned (don't know how I missed that one :sweat_smile:)

Thanks :)


Remote plan with an invalid url gives a traceback

Reproducible easily:
plan:
    import:
        url: https://some.weird.url/

Exploring the tree with tmt gives:
Traceback (most recent call last):
  File "/home/psss/.virtualenvs/tmt/bin/tmt", line 7, in <module>
    exec(compile(f.read(), __file__, 'exec'))
  File "/home/psss/git/tmt/bin/tmt", line 20, in <module>
    tmt.cli.main()
  File "/home/psss/.virtualenvs/tmt/lib/python3.10/site-packages/click/core.py", line 1128, in __call__
    return self.main(*args, **kwargs)
  File "/home/psss/.virtualenvs/tmt/lib/python3.10/site-packages/click/core.py", line 1053, in main
    rv = self.invoke(ctx)
  File "/home/psss/.virtualenvs/tmt/lib/python3.10/site-packages/click/core.py", line 1637, in invoke
    super().invoke(ctx)
  File "/home/psss/.virtualenvs/tmt/lib/python3.10/site-packages/click/core.py", line 1395, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/psss/.virtualenvs/tmt/lib/python3.10/site-packages/click/core.py", line 754, in invoke
    return __callback(*args, **kwargs)
  File "/home/psss/.virtualenvs/tmt/lib/python3.10/site-packages/click/decorators.py", line 26, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/home/psss/git/tmt/tmt/cli.py", line 148, in main
    tmt.Plan.overview(tree)
  File "/home/psss/git/tmt/tmt/base.py", line 1218, in overview
    style(str(plan), fg='red') for plan in tree.plans()]
  File "/home/psss/git/tmt/tmt/base.py", line 2120, in plans
    return [plan.import_plan() or plan for plan in plans]
  File "/home/psss/git/tmt/tmt/base.py", line 2120, in <listcomp>
    return [plan.import_plan() or plan for plan in plans]
  File "/home/psss/git/tmt/tmt/base.py", line 1616, in import_plan
    node = fmf.Tree.node(
  File "/home/psss/git/fmf/fmf/base.py", line 634, in node
    tree = utils.fetch_tree(
  File "/home/psss/git/fmf/fmf/utils.py", line 653, in fetch_tree
    repository = fetch_repo(url, ref)
  File "/home/psss/git/fmf/fmf/utils.py", line 774, in fetch_repo
    raise FetchError("{0}".format(error), error)
fmf.utils.FetchError: Command 'git clone https://some.weird.url/ /home/psss/.cache/fmf/https:__some.weird.url_' returned non-zero exit status 128.

@adiosnb, interested to look into this?

Is this issue about gracefully skipping a plan with an invalid URL?

I'd say correctly terminating run with a nice error message.


Extends tests for software update resource

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (70c0615) 67.03% compared to head (7ad5fc8) 67.30%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #414      +/-   ##
==========================================
+ Coverage   67.03%   67.30%   +0.27%
==========================================
  Files          80       80
  Lines        5496     5502       +6
==========================================
+ Hits         3684     3703      +19
+ Misses       1394     1384      -10
+ Partials      418      415       -3

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


请问，如何设置选中的文本的背景颜色

Attach (recommended) or Link to PDF file here:
Configuration:

Web browser and its version:
Operating system and its version:
PDF.js version:
Is a browser extension:

Steps to reproduce the problem:
1.
2.
What is the expected behavior? (add screenshot)
What went wrong? (add screenshot)
Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):

Wow, I tried google translate and it is a real text:
"How can I set the background color of the selected text?"

Closing since this should be achieved by some CSS. Moreover, we can only provide assistance in English.


Babel7

After much pain and tears, should be close to mergeable

[x] Use rollup for build
[x] Upgrade to Babel 7
[x] gulp build
[x] gulp test
[x] Remove a lot of unused stuff
[x] Fix doc/tests

Merged 🤞


feat: add support for batching transactions in a userop

This PR adds support for batching TXs in a UserOp.
This is a breaking change for existing users because it changes the typing on sendUserOperation to accept a typed object for the callData or an Array of that object.
Also adds a method for sendTransactions similar to the sendTransaction method which accepts a Transaction object instead of a UO.
In the next PR (once the rest of this stack is approved), I'll update the README to include the new usage.
addresses: https://github.com/alchemyplatform/aa-sdk/issues/5

Current dependencies on/for this PR:

main

PR #6

PR #7   👈

This comment was auto-generated by Graphite.

@moldy530 started a stack merge that includes this pull request via Graphite.

Graphite rebased this pull request as part of a merge.

@moldy530 merged this pull request with Graphite.


Update prereq script

added support for ubuntu 20.04

tested on clean UB18:
root@srs-ub181:~# ansible --version
ansible 2.10.10
config file = None
configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/local/lib/python3.6/dist-packages/ansible
executable location = /usr/local/bin/ansible
python version = 3.6.9 (default, Jan 26 2021, 15:33:00) [GCC 8.4.0]
and clean UB20:
root@srs-ub201:~# ansible --version
ansible 2.10.10
config file = None
configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/local/lib/python3.8/dist-packages/ansible
executable location = /usr/local/bin/ansible
python version = 3.8.5 (default, May 27 2021, 13:30:53) [GCC 9.3.0]


NIFI-7770 Add features to csv lookup services

Add the following functionalities:

Custom value separator (default is comma)
Custom quote char to use (default is " i.e. quote sign)
Quote mode
Escape character to use (default is no escape character)
Comment marker
Trim fields
Character set to use

The above features use a common implementation with "CSVReader".
Also append a sentence to the capability description that first line of
csv file is considered header. Setting custom header instead of using
the first line is not supported (yet).
Also, a minor refactor: CSVRecordLoopkupService and
SimpleCsvFileLookupService now share common logic in implementation.
CSV Format is extended to the same list as CSVReader. In addition,
lookup services still have the "default" csv format for compatibility
reasons.
For all changes:

[X] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[X] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[X] Has your PR been rebased against the latest commit within the target branch (typically main)?

[X] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[X] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[X] Have you written or updated unit tests to verify your changes?
[X] Have you verified that the full build is successful on JDK 8?
[X] Have you verified that the full build is successful on JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

Merged to main @Wastack, thanks!


Feature: Dockerize

docker-compose up should start craftcms and nextjs

I wonder well how DDEV would work here. I use it to stand up my twig/craftcms projects. Would like to move to Next (have moved to React and headless Craft) with Vite for bundling.


Spot fleet bid price logic differs from AWS defaults

Issue
On setting up a spot fleet, I came across what seems to be a difference between default AWS and default kube-aws bid price logic for spot fleets.
According to the CloudFormation docs and the Spot Fleet docs, By default, the Spot fleet uses [the global Spot price] as the bid price for each of its launch specifications.
However, the kube-aws default is worker.spotFleet.spotPrice * weightedCapacity.
I think maybe the confusion comes from this part of the AWS docs:
By default, the Spot price that you specify represents your bid price per instance hour.
When you use the instance weighting feature, the Spot price that you specify represents
your bid price per unit hour. You can calculate your bid price per unit hour by dividing
your bid price for an instance type by the number of units that it represents.

As far as I can see we always have instance weighting turned on in kube-aws and no flag to turn it off (but it is optional in CF).
Example
Here is an example of the difference. Say we setup this basic spot fleet of C4 class instances:
spotFleet:
  targetCapacity: 4
  spotPrice: 0.036
  launchSpecifications:
    - weightedCapacity: 1
      instanceType: c4.large
    - weightedCapacity: 2
      instanceType: c4.xlarge
    - weightedCapacity: 4
      instanceType: c4.2xlarge

Each larger instance step is double the CPU/memory of the one prior so normally we'd weight as 1/2/4 respectively.
Writing these values into CF directly, this spot fleet would mean:

we want total capacity of 4 units made up of either 1 x c4.2xlarge, 2 x c4.xlarge, 4 x c4.large or some combination
we want to bid 0.036 per weighted capacity

Expected Result
We're using weighted spot fleet and the spot fleet bid price is the same here. Since the default AWS logic would be for the spot fleet bid price to represent the bid price per unit hour and (bid price per unit hour * weighted capacity == bid price per instance type), I'd expect bid prices of:

0.036 for c4.large
0.036 x 2 == 0.072 for c4.xlarge
0.036 x 4 == 0.144 for c4.2xlarge

Actual Result
kube-aws seems to override the AWS default for spot fleet launch specifications with worker.spotFleet.spotPrice * weightedCapacity. So what we get inside the kube-aws generated CF template is:

0.036 for c4.large
0.072 for c4.xlarge
0.144 for c4.2xlarge

But then in AWS it will result in these bid values:

0.036 for c4.large
0.072 x 2 == 0.144 for c4.xlarge
0.144 x 4 == 0.576 for c4.2xlarge

Workaround
Specifying overrides back to the AWS default does the trick:
spotFleet:
  targetCapacity: 4
  spotPrice: 0.036
  launchSpecifications:
    - weightedCapacity: 1
      instanceType: c4.large
    - weightedCapacity: 2
      instanceType: c4.xlarge
      spotPrice: 0.036 # instance bid price with be 2x == 0.072
    - weightedCapacity: 4
      instanceType: c4.2xlarge
      spotPrice: 0.036 # instance bid price with be 4x == 0.144

@c-knowles Thank you very much for the report with a detailed explanation 👍
This seems to be a long-standing bug since the very beginning of the spot fleet support.
The fix could be made in this block in our code-base.


Analyzer broken

Not sure if this is a Flutter issue or a Dart/IDE issue, but it seems that simple Dart code can totally confuse the Analyzer.
Did anybody come across something like that and is there a fix?
Steps to Reproduce
Repo to reproduce and details can be found here
https://github.com/davidmarne/flutter_built_redux/issues/6

I recommend filing this in the Analyzer's bug database at https://github.com/dart-lang/sdk/issues

cc @pq

Thanks @Hixie .
Maybe @bwilkerson @scheglov have thoughts.  I can take a look later today...

@pq I've assigned this bug to you for now but please close it once you've determined if it should be filed in the Dart bug database or if it's INVALID/WONTFIX. Thanks!

A little follow-up on the initial report.  The rub is we're not able to repro.  Closing this and tracking the original in case anyone gets any leads that help reproduce.


wazero: 1.7.1 -> 1.7.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/tetratelabs/wazero/releases.
meta.description for wazero is: A zero dependency WebAssembly runtime for Go developers
meta.homepage for wazero is: https://github.com/tetratelabs/wazero
meta.changelog for wazero is: https://github.com/tetratelabs/wazero/releases/tag/v1.7.2
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.7.2 with grep in /nix/store/87n4ggk8nqhsaz0d8m2lc6r5fkzp5bjw-wazero-1.7.2
found 1.7.2 in filename of file in /nix/store/87n4ggk8nqhsaz0d8m2lc6r5fkzp5bjw-wazero-1.7.2

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

wazero

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/87n4ggk8nqhsaz0d8m2lc6r5fkzp5bjw-wazero-1.7.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A wazero https://github.com/r-ryantm/nixpkgs/archive/170117170ade927f2388ef78c506322520c5af92.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/170117170ade927f2388ef78c506322520c5af92#wazero

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/87n4ggk8nqhsaz0d8m2lc6r5fkzp5bjw-wazero-1.7.2
ls -la /nix/store/87n4ggk8nqhsaz0d8m2lc6r5fkzp5bjw-wazero-1.7.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

wazero

Maintainer pings
cc @figsoda for testing.

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

1 package built:

wazero


Is it possible to show wtform validation error on modal?

The #1366 issue mentions whether a validation error can be displayed on the modal form, the old issue has been closed, and I added the pictures to resubmit this issue.
I debugged the code, the rendering of the view was re-executed, resulting in the loss of the modal form. It may be necessary to re-enable the modal on the template page via the js code.
Is it possible to directly render form fields into bootstrap js-based checks in flask-admin without using wtform validation?

any updates?


Add xml signature to HTTP POST AuthnRequest

As per SAML RFP, the signature in a HTTP-POST have to be included inside the xml.

When you say "per SAML RFP", please provide a specific link or section reference to the section being implemented or corrected.
Thanks for the contribution.
Note there are recent changes to support multiple AuthnRequests which may impact this work.

@tmoiron Since it appears you are increasing our spec-compliance, your contribution is welcome here


fix: cast args when applying mockFunctionValDef in scala 3

Pull Request Checklist

[x] I agree to licence my contributions under the MIT licence
[x] I have added copyright headers to new files
[x] I have added tests for any changed functionality

Fixes
Whilst mocking a trait or class with a method that took a type parameter worked in scala 3 for many cases, it did not work when the type parameter was used as the input for a function arg to that method. The newly-added test case failed in those instances (i.e. def p[T]) with the following:
[error] 43 |    val mockedTrait = mock[Foo]
[error]    |                               ^
[error]    |                               Found:    (t : Seq[Toot] => Seq[String])
[error]    |                               Required: Seq[?] => Seq[String]
[error]    |
[error]    | longer explanation available when compiling with `-explain`

This is a regression from scala 2
Purpose
This pr casts the args when passing them to the mock method implementation, which avoids the above error.
Background Context
This seemed the least intrusive way of getting the new test case to work

So this is the final change I needed to make everything compile for mah downstream project that I'm trying to migrate to scala 3. I have yet to get all the tests to pass, but I don't think any of the proposed changes have broken anything. So very anecdotal test case for your consideration. I guess that the maintainers (@barkhorn) probably have downstream clients they want to make sure I haven't broken. I am happy to attempt to address any issues that this or the other two prs cause.

@barkhorn anything I can/should do on this pr to help it on its way?

Hi, looks fine, lets merge


Drop support for Kubernetes v1.28

What this PR does / why we need it:
Active support for Kubernetes v1.28 is over and maintenance support ends on 28 Oct 2024.
https://endoflife.date/kubernetes
Which issue(s) this PR fixes:

Fixes #
What type of PR is this?

/kind cleanup
Special notes for your reviewer:
Does this PR introduce a user-facing change? Then add your Release Note here:

Support for Kubernetes v1.28 has been removed

Documentation:

NONE

/approve
/lgtm


Incorrect "Missing match arm" error in tooltip

The following code compiles correctly using cargo/rustc with no warnings or errors:
use std::cmp::Ordering::*;

#[allow(dead_code)]
fn foo(a: u32, b: u32, c: u32) {
    match (a.cmp(&b), a.cmp(&c), b.cmp(&c)) {
        (Less | Equal, Greater, _) => (),
        (Greater, Less | Equal, _) => (),
        (Greater, Greater, Less) => (),
        (Greater, Greater, Greater) => (),
        (Less | Equal, Less | Equal, Less) => (),
        (Less | Equal, Less | Equal, Greater) => (),
        (_, _, Equal) => (),
    }
}

but rust-analyzer continues to show the red underline indicating an error (even after file save, language server restart, VSCode window reload, and VSCode editor restart). Hovering over the underline shows this tooltip:

which states that rust-analyzer believes there is a missing match arm, despite all possible cases being covered.
Rust Analyzer version: v0.2.538
VSCode version information:
Version: 1.54.3 (system setup)
Commit: 2b9aebd5354a3629c3aba0a5f5df49f43d6689f8
Date: 2021-03-15T10:55:45.459Z
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19042

Rust version: rustc 1.53.0-nightly (07e0e2ec2 2021-03-24)
Rust toolchain: nightly-x86_64-pc-windows-msvc
Compilation target triple: x86_64-pc-windows-msvc

The problem seems to be with or_patterns:
enum Either {A, B}

fn main() {
    match (Either::A, Either::B) {
        //^^^^^^^^^^^^^^^^^^^^^^ Missing match arm
        (Either::A | Either::B, _) => (),
    }
}

Ye most likely those aren't really implemented at all yet in our usefulness checks I think. I got interested in checking that part out recently actually as I read through the paper it (and rustc's check) is based on.


Creating multiple clips from the same video

Q
A

Bug?
no

New Feature?
no

Version Used
Specific tag or commit sha

FFmpeg Version
FFmpeg or AVConv and version

OS
Ubuntu 16.04.3 LTS

Expected Behavior
What is the behavior you expect?
To cut multiple clips from a video and concatenate them into a single output video
Apologies but considering there were no documentation on this possibly advanced feature, had to come by and raise a ticket.
Was just wondering how would one go around creating multiple clips from a single video and concatenating them into a single video.

I'm not sure what you mean?
https://github.com/PHP-FFMpeg/PHP-FFMpeg#concatenation
Is this what you want to do?

I see, yes I have attempted to cut it and save them individually before concatenating them. However, felt it to be rather a long roundabout way and figured I could clip videos, concatenate and then save.
I will play around with the the package and hopefully streamline it and help with the docs :)

Alright. Closing this. If you have any questions, feel free to write a comment.


Update console overview for recent changes

What changed, and why it matters
The console overview article has been updated to reflect the current state after several changes to the UI and admin, billing, and other functionality.
Relies on changes made in #1942.

#1942 needs to be merged before this and after rebasing the errors will be fixed.


chore(deps): update dependency webpack to v4.42.1

This PR contains the following updates:

Package
Type
Update
Change

webpack
devDependencies
patch
4.42.0 -> 4.42.1

Release Notes

webpack/webpack
v4.42.1
Compare Source
Bugfixes

update webassemblyjs dependencies for instruction update
update mkdirp dependency for security reasons

Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

Available now for Enterprise: Renovate Pro with real-time webhook handling and priority job queue.

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

v3.2.3
GitHub release

Your semantic-release bot :package::rocket:


Update django conf locale az translation

Translations are managed on Transifex rather than through GitHub. See Localizing Django for details.


feat(container): Pass resolverData when new DefaultContainer()

Check issue-286

Closing for a housekeeping purposes as looks like #286 has been resolved 🔒