skip consistent hash ttl test cases (#48501)

Cherrypicking the commit : https://github.com/istio/istio/pull/48501

Hi @riya16. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

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.

@riya16: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test release-notes

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.

@riya16: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test release-notes

integ-basic-arm64_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-basic-arm64

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.

Sorry. I thought the cherrypick worked

@riya16: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test release-notes

integ-basic-arm64_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-basic-arm64

analyze-tests_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test analyze-tests

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.

@riya16: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test release-notes

integ-basic-arm64_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-basic-arm64

analyze-tests_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test analyze-tests

integ-ipv6_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-ipv6

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.

@riya16: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test release-notes

integ-basic-arm64_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-basic-arm64

analyze-tests_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test analyze-tests

integ-ipv6_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-ipv6

integ-ds_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-ds

lint_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test lint

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.

@riya16: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test release-notes

integ-basic-arm64_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-basic-arm64

analyze-tests_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test analyze-tests

integ-ipv6_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-ipv6

integ-ds_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-ds

lint_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test lint

integ-pilot_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-pilot

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.

@riya16: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test release-notes

integ-basic-arm64_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-basic-arm64

analyze-tests_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test analyze-tests

integ-ipv6_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-ipv6

integ-ds_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-ds

lint_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test lint

integ-pilot_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-pilot

gencheck_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test gencheck

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.

@riya16: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test release-notes

integ-basic-arm64_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-basic-arm64

analyze-tests_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test analyze-tests

integ-ipv6_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-ipv6

integ-ds_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-ds

lint_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test lint

integ-pilot_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-pilot

gencheck_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test gencheck

integ-distroless_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-distroless

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.

@riya16: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test release-notes

integ-basic-arm64_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-basic-arm64

analyze-tests_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test analyze-tests

integ-ipv6_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-ipv6

integ-ds_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-ds

lint_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test lint

integ-pilot_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-pilot

gencheck_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test gencheck

integ-distroless_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-distroless

integ-pilot-istiodremote-mc_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-pilot-istiodremote-mc

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.

@riya16: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test release-notes

integ-basic-arm64_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-basic-arm64

analyze-tests_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test analyze-tests

integ-ipv6_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-ipv6

integ-ds_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-ds

lint_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test lint

integ-pilot_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-pilot

gencheck_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test gencheck

integ-distroless_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-distroless

integ-pilot-istiodremote-mc_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-pilot-istiodremote-mc

integ-cni_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-cni

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.

@riya16: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test release-notes

integ-basic-arm64_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-basic-arm64

analyze-tests_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test analyze-tests

integ-ipv6_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-ipv6

integ-ds_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-ds

lint_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test lint

integ-pilot_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-pilot

gencheck_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test gencheck

integ-distroless_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-distroless

integ-pilot-istiodremote-mc_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-pilot-istiodremote-mc

integ-cni_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-cni

integ-ambient_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-ambient

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.

@riya16: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test release-notes

integ-basic-arm64_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-basic-arm64

analyze-tests_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test analyze-tests

integ-ipv6_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-ipv6

integ-ds_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-ds

lint_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test lint

integ-pilot_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-pilot

gencheck_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test gencheck

integ-distroless_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-distroless

integ-pilot-istiodremote-mc_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-pilot-istiodremote-mc

integ-cni_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-cni

integ-ambient_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-ambient

integ-pilot-istiodremote_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-pilot-istiodremote

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.

@riya16: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test release-notes

integ-basic-arm64_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-basic-arm64

analyze-tests_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test analyze-tests

integ-ipv6_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-ipv6

integ-ds_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-ds

lint_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test lint

integ-pilot_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-pilot

gencheck_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test gencheck

integ-distroless_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-distroless

integ-pilot-istiodremote-mc_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-pilot-istiodremote-mc

integ-cni_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-cni

integ-ambient_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-ambient

integ-pilot-istiodremote_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-pilot-istiodremote

integ-pilot-multicluster_istio_release-1.20
6d6f2f60124295f899d70a27ee3bb8db7e4a700b
link
true
/test integ-pilot-multicluster

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.


seeddb command not working with neo4j sandbox

I setup a neo4j sandbox DB, and ran npx create-grandstack-app. When I run npm run seedDb from /api subfolder, I get the following error message:
Error: Error: request to http://<IP_ADDRESS>:4001/graphql failed, reason: connect ECONNREFUSED <IP_ADDRESS>:4001

my api/.env file generated by npx :
NEO4J_URI=<copied from sandbox.neo4j.com bolt URL>
NEO4J_USER=<copied from sandbox.neo4j.com username>
NEO4J_PASSWORD=<copied from sandbox.neo4j.com password>

GRAPHQL_SERVER_HOST=<IP_ADDRESS>
GRAPHQL_SERVER_PORT=4001
GRAPHQL_SERVER_PATH=/graphql

To work with sandbox, what do I need to change here - HOST (I assume) / PORT / PATH ? - and what should the values be ?

Does this work if you use a local database? The error message seems like the client is not able to connect to the GraphQL API, so an error that occurs before the database connection.

@johnymontana we are not planning on using a local database - as we evaluate this technology stack, we are following the tutorial and using it against Neo4j sandbox. if that works, we will consider Aura managed Neo4j as a cloud service.

I am also getting this error. I am also unable to run a local DB because my company proxy is causing a self-sign cert error so I can't verify if it's my machine or sandbox. However, I downloaded the project fresh and ran into this error.

well, basically we're in the dark with regard to the following values, aren't we?
GRAPHQL_SERVER_HOST=<IP_ADDRESS>
GRAPHQL_SERVER_PORT=4001
GRAPHQL_SERVER_PATH=/graphql

to be found in the .env file in API - while the other env vars were correctly set by the init routine of setting up the project, what are the values that should be set here?

Random question, might seem silly at first. Are you running the GraphQL server before attempting a to run seed?
Sometimes it's better to get the obvious out of the way.
The seed process uses the GraphQL server to seed the DB, so that needs to be on for the seed to work. The error you're having seems to suggest that the seed process can't access the GQL server. If it's already running, then something might be interfering there. For example running it in a docker image without exposing the port, or something of that sort.


Remove Google Analytics from supported

Due to many bugs we need to remove it until we fix the bugs and have full coverage

@yaroncan : Thanks for your contribution! The author, @davidiseminger, has been notified to review your proposed change.

@yaroncan will make changes in private repo.


Questions about   simplified MAT

Thank you very much for your work！ I have a question: can you provide the reference code or some details for calculating the standard MAT 。

We use Q-mat, you can find the paper and the download link on this page:
https://github.com/clinplayer/SEG-MAT


Landing Page Content

Description
updated the landing page content.
Checklist
Remove any items which are not applicable.

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas

Good work! It all sounds awesome.


Enhancement: Optionally reset/unset key after checking the value in Tag Pass

This concept might need more refinement, but I have the following use case (this setup will repeat itself countless times),
where the player should be able to branch off somewhere, but they must have handled, in some way or another, a specific topic. If it failed, they may need to repeat some part.
And after each Tag Pass for said Character-tag-key, I want to reset the key, i.e. integrate purpose of Node 1y into Tag Pass. (I know that in case of 1w being False, it is not reset in the image below).

So something like this:

Although it's quite easy to implement, there are few matters to be considered.
It will somehow break the unwritten rule for Arrow's built-in nodes to be atomic. It is also a breaking change internally, because we have to keep a new value in the node's dataset, specially affecting users serializing the node in their own custom ways.
The other point is that I recommend developers to use tags as unique gates and keep them in memory, unless they are sure they would not check for them anymore, specially if they are having a lot of them. Tags are designed mainly for dynamic (global) event management and are not that resource intensive. For example, I would consider setting hero_revived as a global state (with or without a value to know revival quality as a zombie, a promoted mage, etc.) to be  a safer practice compared to revived = hero | cookie_monster | john_smith.
Finally we can not really propose a one-size-fits-all solution: An unset always on false, always on true, on author's choice, a reset to the initial value (if initialized in the editor) or a reset to blank, ... which one is the proper convention?
These are some of the reasons why I prefer to keep things atomic and encourage users to create their own composite/custom nodes and even better to make them open-source.
Let's now close this issue; but I'm open to more discussion.

we can not really propose a one-size-fits-all solution

Hm… indeed
Then either add a Tag Edit-like logic beneath Tag Pass or create a new Tag Pass Edit node, where beneath the existing Tag Pass GUI, you can add/remove lines (maybe use Godot's Tree) such as

Key
Operation
Value
On

cookie
Unset

Pass

health
To Initial

Fail

ice_cream_flavour
Set
Lemon
Fail

Operation would be an OptionButton and On can be CheckButton

That is probably the way to go if we wanted to create highly composite nodes built-in.
But the way I see it, from UX point of view, we are just replacing some slot connections with inspector fields that we will have to somehow display on the grid too. In other words, it is a matter of taste. Some developers may prefer more connections on the grid, some may prefer fields and bullet-points printed on the grid.


How do I replace neck with bifpn in the mask rcnn model

I use backbone swin transfomer

I have error as ValueError: too many values to unpack (expected 3)


Allow to set the name of the VM in the Vagrantfile

The name of the VM can be set in the Vagrantfile by means of xs.name.
If xs.name is not set, the traditional username/box_name/box_version
format is used.
Signed-off-by: Flavien Quesnel<EMAIL_ADDRESS>

Thanks @fquesnel! Sorry I didn't spot this PR sooner!

No problem @jonludlam. Thank you for the merge!


Merge prTesting_202004091921 branch to master branch

Docs Build status updates of commit 95464e9:
:clock10: Pending: waiting for processors (8 builds ahead of you)
:warning: Docs Build is busy, currently there are 8 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 95464e9:
:warning: Validation status: warnings

File
Status
Preview URL
Details

split/updateTestRef.md
:warning:Warning

Details

split/updateTestRef.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.
[Warning] Missing attribute: title. Add a title string to show in search engine results.
Line 1: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 04/01/2020.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Remember last opened side panel in the editor on page load

Please check the following:

[x] Do the tests still pass?[^1]
[x] Does the code comply with the style guide?

[x] Run make lint from the Wagtail root.

[x] For Python changes: Have you added tests to cover the new/fixed behaviour?
[ ] For front-end changes: Did you test on all of Wagtail’s supported environments?[^2]

[x] Please list the exact browser and operating system versions you tested:
Chrome 105.0.5195.125, Firefox 105.0.1, Safari 16.0
[ ] Please list which assistive technologies [^3] you tested:

Please describe additional details for testing this change.

Open the page/snippet editor
Open one of the side panels
Reload the page
The last opened side panel should remain open on initial page load
Close the side panel
Reload the page
The side panel should remain closed on initial page load
Go to the page explorer
Ensure that the behaviour of the side panel on the page explorer is completely independent of the page editor. It shouldn't remember the last opened side panel (i.e. it's always closed on initial page load) and opening/closing the side panel in the explorer shouldn't affect the side panel preferences in the page editor.

[^1]: Development Testing
[^2]: Browser and device support
[^3]: Accessibility Target

@laymonage would we worth tackling https://github.com/wagtail/wagtail/issues/9216#issuecomment-1249886893 while at it. That is, have the info panel open by default (if no previous "last opened side panel" state exists). @thibaudcolas what do you think?

@zerolab Not sure if that would be a good idea as that means the info panel would cover the entire screen on first load on smaller screens. We could add a check to only do this on a certain minimum device screen width, but I personally would rather avoid having such checks in JS.
Besides, it's only one click away for users to show the info panel and it stays there on page reload. I get the point that it'd be useful to have it open by default for users who are new to 4.0, though...

A few thoughts

Are we assuming too much for the user with this feature? Sometimes being too smart can cause confusion for the user. Refreshing the page intentionally usually means I want to reset the page state. Not against this but just trying to understand.
Why are we using local storage and not session storage? Won't local storage keep this setting for a long time and also across other pages. I would assume that if you open a different edit page in a different tab you don't want the panel opened?
When we use Local or Session storage we should not assume the device has given us permission - wrap it in a try / catch is usually a good practice (I know we may not do this elsewhere)
Is a URL query Param a better solution here? It will be able to be added without adding to the browser history easily and also will be 'kept' on duplicate tab, on top of this the URL can be read sever side so we can set intiial state / classes in the DOM without any additional JS complexity.

@thibaudcolas thanks for explaining - no further push back from me on this.
For session storage - we should wrap usage in a try / catch - for a small bit of progressive enhancement if the user has disabled some things in their browser.
Good point about the layout shift.
Thanks.
And thanks @laymonage for working on this.


Any reason to use crop?

I don't have idea why you crop the image if the ratio exceeds 2.
In the original faster rcnn, they don't consider that.
Is there any reason to crop the image? Does the accuracy differ a lot without crop?

@twmht most of the images in coco or pascal have the aspect ratios range in [0.5,2]. We crop the images so that they can be batched easily and save the GPU memory.


Faster scrolling?

I've tried this out but I've found setting the speed to 100 is still about 1/2 or 1/3 as fast as terminal.app is there anyway to set it above 100?

You probably need to update your settings, i found a error in the docs.
You need to put the number in quotes, and end the bracket for alternateScroll with a comma.
The correct syntax:
   // for hyperterm-alternatescroll plugin     alternateScroll: {       // 1 to 100 is supported       scrollSpeed: '90'     },

That seems to have done it.


How to unsubscribe from single event?

Hello,
how can i unsubscribe from a single event?
I need to subscribe sticky to FetchDataEvent and immediately unsubscribe from the FetchDataEvent so that i will get data updates only on load.
Thank you

You can not. You can only call EventBus.getDefault().unregister(). Otherwise adapt your event handling method to only handle the event once or whenever you choose. -ut


You continue it?

You continue it? Or say me how to find timer pointer please.

Yes I am still continuing it. The timer pointer has been updated in my Test-Environment branch. I will update the other branches soon, as the Updates/Improvements are proving to be stable enough for the master build.  :)

Okay i testing it x)

Ohh, cursor looks legit but he not smart :)

What do you exactly mean with buggy? Can you describe it for me? Because for me it seems to work fine.

okay i upload video on youtube

https://youtu.be/eyVyHobUECg

It looks like an issue with the threads being slow. The cursor is being updated to slow/the time is being read to slow. I run i7-7700k @ 4.8Ghz so thread speeds are not a issue I have tested.
If you cloned the source, see if increasing the thread sleep time (to a few milliseconds) improves performance.
I will increase the time on the source because I don't need the treads to be that fast tbh.

it? "this_thread::sleep_for(chrono::microseconds(100));"

yes by changing those in the "CursorMovement.h" you can change time between cursor updates.
And in "OsuBot.h" in "AutoPlay(wstring nowPlaying)" you can change time for main autoplay loop.

"this_thread::sleep_for(chrono::milliseconds(12))" is the delay for click and release mouse/keyboard key presses.

Does not help :'( Fucking slowest processor.


Modify the display width for Chinese characters and so on

The display width will not be right if there have Chinese characters in the display. It will overflow the line, if the Chinese characters are at the end of a line. And makes "lines" value not the right number of line rows,  which makes "239: fmt.Fprintf" produce wrong output.

Thanks!


codec(ticdc): reduce canal-json decode memory consumption by using buffered json decoder

What problem does this PR solve?

Issue Number: ref #11894
This is the second part to reduce the memory cost by the canal-json decoder when works with the consumer.
What is changed and how it works?

use json decoder to decode events, this looks takes relative little memory than the Unmarshal method, but still takes a lot.
add CanalJSONTxnDecoder, split related logic, to simplify the normal canal-json decoder.

After this PR, JSON decoder phase takes around 40% memory. Previous takes more than 60%.

Check List
Tests

Unit test
Integration test

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
`None`

How much memory will be reduced after applying this?

How much memory will be reduced after applying this?

previous, takes around 62%. now takes around 40%.
I tried several json library, all takes a lot of memory in the consumer scenario.

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest


provision dedicated fractal server

cf #78

Currently deprecated, as we moved towards the sudo approach - see recent comments in https://github.com/fractal-analytics-platform/fractal-server/issues/10.


ImportError: generic_type: type "option" is already registered!

Required Info

Camera Model
{ R200 / F200 / SR300 / ZR300 / D400 }

Firmware Version
(Open RealSense Viewer)

Operating System & Version
{ Ubuntu 16.04)

Kernel Version (Linux Only)
(e.g. <IP_ADDRESS>)

Platform
PC

SDK Version
{ legacy / 2.12 }

Language
{ python }

Issue Description
I am using python wrapper provided by librealsense to control camera.
There are two requirement: 1 take color/depth picture. 2 provide an api interface to control the brightness, contrast of the camera.
So I "import  pyrealsense2" to take color picture, and "import pybackend2" to control the brightness.
However, if this two modules import in one python file, ERR "ImportError: generic_type: type "option" is already registered!"  happened.
May I know how can I solve this problem?
Or is there any other method how can I meet the two requirement by python. Thanks

Hi @chencheng1560
You can get the same result with pyrealsense2 only, I would strongly advise against using pybackend2.

[Realsense Customer Engineering Team Comment]
Hi @chencheng1560,
Thanks for your code shared. Will close this since your have resolved it. If any more concern, you still can re-open or create another ticket.


typos (116)

Pull request checklist
Use the following list to make sure your PR fits the EthSigner doc quality standard.
Before creating the pull request
Make sure that:

[ ] you have read the contribution guidelines.
[ ] you have tested your changes locally before submitting them to the community for review.

After creating your pull request and tests finished
Make sure that:

[ ] you have fixed all the issues raised by the tests, if any.
[ ] you have verified the rendering of your changes on
ReadTheDocs.org PR preview
and updated the testing link (see Testing).

Describe the change
fixes #116

Issue fixed

Impacted parts
For content changes

[ ] Doc content
[ ] Doc pages organisation

For tools changes

[ ] CircleCI workflow
[ ] Build and QA tools (lint, vale,…)
[ ] MkDocs templates
[ ] MkDocs configuration
[ ] Python dependencies
[ ] Node dependencies and JavaScript
[ ] ReadTheDocs configuration
[ ] GitHub integration

Testing

Screenshots / recording

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


First pass - Documentation improvement

What type of PR is this?
/kind documentation

What this PR does / why we need it:
Documentation changes to address the insights from UX study sessions:
https://docs.google.com/document/d/1xbN46OLuhsXXHeqZrKrl9I57kpFQ2yqiYdOx0sHZC4Q/edit
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

/ok-to-test

FYI @cortespao

/approve
/label tide/merge-method-squash
Leaving the LGTM to @cortespao

/lgtm
Thanks!


upgrade chroma to 0.4.0

** This should land Monday the 17th **
Chroma is upgrading from 0.3.29 to 0.4.0. 0.4.0 is easier to build, more durable, faster, smaller, and more extensible. This comes with a few changes:

A simplified and improved client setup. Instead of having to remember weird settings, users can just do EphemeralClient, PersistentClient or HttpClient (the underlying direct Client implementation is also still accessible)

We migrated data stores away from duckdb and clickhouse. This changes the api for the PersistentClient that used to reference chroma_db_impl="duckdb+parquet". Now we simply set is_persistent=true. is_persistent is set for you to true if you use PersistentClient.

Because we migrated away from duckdb and clickhouse - this also means that users need to migrate their data into the new layout and schema. Chroma is committed to providing extension notification and tooling around any schema and data migrations (for example - this PR!).

After upgrading to 0.4.0 - if users try to access their data that was stored in the previous regime, the system will throw an Exception and instruct them how to use the migration assistant to migrate their data. The migration assitant is a pip installable CLI: pip install chroma_migrate. And is runnable by calling chroma_migrate
Please reference the readme at chroma-core/chroma-migrate to see a full write-up of our philosophy on migrations as well as more details about this particular migration.
Please direct any users facing issues upgrading to our Discord channel called #get-help. We have also created a email listserv to notify developers directly in the future about breaking changes.
TODO

[x] Migrated any duckdb+parquet strings to the new format
[ ] Notified users about the breaking change (this PR, other suggestions?)

@jeffchuber Thanks.  I tried it temporarily but there are a few code changes needed, and it seemed to complaint about migration when starting up.  I need to investigate more.

@pseudotensor thanks! let me know how i can help here. More context on this upgrade: https://www.trychroma.com/blog/chroma_0.4.0


[46] feat: load section 3 data from api

Description

load api data for section 3 via new function to map data from the api for the form
installed and use toast messaging (for api error)
created and used reusable loading indicator
rudimentary layout (useful for positioning loading indicator in center of screen)

Closes #46
Type of change
Please delete options that are not relevant.

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

Instructions
Navigate to the restoration aims page. Note the initial loading indicator and that the form is populated on load from the api when loading is complete
How Has This Been Tested?

see instructions
test toast on api fail by adding junk to api string.

Checklist:

[ ] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

there's some conflicting peer dependencies for this app.. has to do with story book and the react version we're using

there's some conflicting dependencies for this app.. has to do with story book and the react version we're using ... you can see it in the details section where the checks are happening
Its a heroku thing. Question is do we spend time on that?

I accidentally edited your comment. Sorry. Ill ask in the main channel how do we proceed with the heroku thing.

there's some conflicting dependencies for this app.. has to do with story book and the react version we're using ... you can see it in the details section where the checks are happening
Its a heroku thing. Question is do we spend time on that?

I accidentally edited your comment. Sorry. Ill ask in the main channel how do we proceed with the heroku thing.

it's a problem in package.json, we need to clarify what version of storybook we need to work with react 18 @mmnoo


Add chinese doc of  API--fluid.conv2d

Add a new conv2d API interface, which support conv API 's filter input is tensor;

Please add the PR to http://wiki.baidu.com/pages/viewpage.action?pageId=917662867

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Can one of the admins verify this patch?


Theme doesn't apply

I followed the docs and tried to convert a README into a site. Everything works locally, but there is no theme after deploy on GitHub Pages.
Here is a site:
https://artemnovichkov.github.io/awesome-swift-charts/
Here is a source code:
https://github.com/artemnovichkov/awesome-swift-charts
Toucan version: 1.0.0-beta.1
What am I doing wrong?

Got it. Because the final link is https://artemnovichkov.github.io/awesome-swift-charts/, the stylesheet paths must be:
<link rel="stylesheet" href="/awesome-swift-charts/css/theme.css">
<link rel="stylesheet" href="/awesome-swift-charts/css/style.css">

But it doesn't work locally.

Have to add {{site.baseUrl}} before the css links, since GitHub page URLs contain a folder…

Also, would you like to showcase your site on toucansites.com? I'd be happy if we could add it as a reference. 🙏

Yes, sure, why not! I'm going to improve it, and maybe I'll write a blog post.


notmuch and bindings to ruby

Issue description
How to get / use notmuch bindings to ruby? I want to use notmuch plugin in vim which requires ruby binding.
Steps to reproduce
> nix-shell -p ruby notmuch
> ruby -e 'require "notmuch"'
/nix/store/f3svdpbdciz3c91nc8bj8qi0adc6p5zl-ruby-2.4.4/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:59:in `require': cannot load such file -- notmuch (LoadError)
        from /nix/store/f3svdpbdciz3c91nc8bj8qi0adc6p5zl-ruby-2.4.4/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:59:in `require'
        from -e:1:in `<main>'

Technical details

system: "x86_64-linux"
host os: Linux 4.17.2, NixOS, 18.09.git.c51ac5e (Jellyfish)
multi-user?: yes
sandbox: no
version: nix-env (Nix) 2.0.4
channels(milan): "nixos-17.03pre96925.1c50bdd"
channels(root): ""
nixpkgs: /etc/nixos/nixpkgs

I also ran into this today. We are building the notmuch ruby binaries but we are never packaging them. They are just being discarded at the end of the build. I am not familiar with the ruby tooling to figure out how to install them properly. I can probably botcher it somehow...

this was fixed recently


Support for Parse.File.save()

This is a combo question / feature request.
I just want to confirm that Parse.File.save() doesn't work on marse-mockdb.
When I do:
    const parseFile = new Parse.File('test.json', { base64: "{}".toString('base64') });
    await parseFile.save();

I get no error, but when I try to save the object the file is set on, I get "Tried to encode an unsaved file."
Is there a workaround for mocking parse files? And if not, has anyone looked into what it'll take to mock it. I can look into it, but want to be sure no one else is doing it (or has decided that it's not possible / worth the effort).

If you wanted to send a PR for that, I think that would be great!


Activate document type filter

Note: This merge will work once Vincent merges the staging oipa changes with the production oipa.
devtracker.rb - Added a new parameter for the document type filter.
helpers/country_helpers.rb - Added the document type filter.
helpers/region_helpers.rb - Added the document type filter.
helpers/search_helper.rb - Added the document type filter.
helpers/sector_helpers.rb - Added the document type filter.
public/javascripts/searchPageFilters.js - Added necessary js codes for the document type filter to work.
views/countries/projects.html.erb - Added the document type filter parameter.
views/partials/_project_list.html.erb - Added the document type filter dependent template codes.
views/regions/projects-home.erb - Added the document type filter dependent template codes.
views/regions/projects.html.erb - Added the document type filter dependent template codes.
views/search/search.html.erb - Added the document type filter dependent template codes.
views/sector/projects.html.erb - Added the document type filter parameter.

Coverage decreased (-0.2%) to 21.286% when pulling e1d54611aaf22fe74d286be09645b258295b8056 on activate-document-type-filter into 3b9543beb64cdeb97baa09c2d5aa2c95148d3e62 on master.

Changes Unknown when pulling bf1e6576fd25187e1a2bc0e4f142390e04c04470 on activate-document-type-filter into ** on master**.

This branch has been merged with the following branch:
https://github.com/DFID/devtracker-from-api/tree/activate-date-range-filter


Improvements to mathematica language

Update the list of symbols using Mathematica 12.0 and a few other fixes.

Hi @poeschko,
although I'm not familiar with Mathematica/Wolfram, the changes make sense for me.
Can you please also add the new alias to docs/css-classes-reference.rst?

Oh yeah, absolutely.

Thanks, merged.
P. S. Markup tests for Mathematica are highly welcome! There's not one now.


New windows close immediately when opened from a popup menu (DisplayServer regression)

Godot version:
4.0 dev<PHONE_NUMBER>b6c25009efab69dc39650e0d76c56d)
OS/device including version:
Ubuntu 20.04 64-bit
Issue description:
New windows close immediately after being opened if they where opened from a popup menu.
This includes windows opened from:

The main menu, e.g.: Editor Settings, Project Settings, Export, Manage Export Templates....
The context menu of the FileSystem, e.g.: "New Folder/Scene/Script/Resource..., Rename..., Move To...`.
The context menu of the Scene dock, e.g.: Add Child Node, Instance Child Scene, Attach Script.

In some weird cases I've managed to open Editor Settings without it closing immediately, but this seems too random.
Windows that are not opened from a popup menu on the other hand stay open as expected.
This includes windows opened from:

The Scene dock toolbar, e.g.: Add Child Node, Instance Child Scene, Attach Script (these are the same I mentioned before which don't work when opened from the context menu).
The Inspector dock toolbar, e.g.: Create New Resource, Open A File.
The Make Floating button when changing a dock's position. Notice how this one works even though it's open from the Dock Position popup, so this seems to be specific to popup menus.

Steps to reproduce:
Open the editor and try to open the Editor Settings from the main menu. It should close immediately.

I wonder if I'm the only one experiencing this bug as I couldn't find any other issue about it and it's not listed in #37734.

It seems to be Linux specific issue. I even suspect it to be Ubuntu 20 specific issue.

Oops, yes. Forgot to say that. I cannot reproduce on Windows 10 either.

I wasn't able to reproduce on Ubuntu 16.04 LTS 64-bit. Windows that were opened from the popup window seemed fine and persisted, as seen from this video.
However, they did automatically close when they went out of focus when I clicked on something else (not sure if that is a feature or a bug).

I also experience this issue on Ubuntu 18.04. It seems that when my mouse leaves the popup it closes.

I also experience this on two separate Ubuntu 19.04 systems with different hardware. It's more or less everywhere making it clunky to use.
I suspect it's the same issue when creating new projects, where the popups there for choosing directories close the parent window (the "New Project/Create New Project" view)
As for the particular details mentioned in the original post are a bit different for me (Currently running a fresh 84abf5a97). For instance Project Settings and Editor Settings work without issue, but for example deleting a node using  -> Delete Node(s) causes the deletion-confirmation-popup to auto-close as soon as it shows up. I've tried this many times now, and occasionally it does stay open. Something like 1/20 stay open.
Getting the same popup using <del> never has this issue.
Also, the relative path from the mouse to the popup is off. The context menu does not appear from the cursor position but rather at some fixed position on the left side of screen (coordinates 132,148). This is regardless of mouse position and window position. Though, if the godot editor is on the right monitor, the popup location is touching the left edge. New windows also pop up on the left monitor even if the window is on the right. Which monitor the initial start was on has no effect on this.
The reason why I mention all of these things in this issue is that could all be related to the display server.

Running some bisecting to narrow it a bit down. The faulty behavior in question seems to emerge between 09ba290364a (newer) and 543fb1c4dadd7 (older by 3 commits) . In the latter, the popups appear in the right position and do not disappear immediately after creation. There are however other issues though, like the inability to register clicks within some windows. Hopefully this is of some help.

is my bug possibly related? https://github.com/godotengine/godot/issues/39555

is my bug possibly related? #39555

No. That issue is present in Windows too is related to another issue.

Seems fixed on latest master. cc @reduz Any idea what commit could have fixed it?

Likely fixed by #39993.

Still not fixed in 4.1.1. My symptoms align with those outlined here (i.e. Project Settings are fine, but something like Add Node closes). Sometimes it works as expected, but most of the time it just doesn't work. Just for the sake of adding extra data points, my Godot is from Flathub and I'm running a Wayland session.

As a workaround, enabling "Single Window Mode" in Editor Settings seems to fix the issue since it's not using Linux's window manager.

I am having a similar issue. This is the mostly closely related existing issue I could find and enabling "single window mode" as suggested above fixes my issue too, so I will share details here:
Godot v4.1.2.stable.flathub [399c9dc39]
Gnome 44.4 with Wayland on Fedora 38
To reproduce:

Attach a new script to a node - the "Add Node Script" dialogue works as expected
Open the "Choose Location" dialogue - this works as expected
Change the path and click Open

The updated "Add Node Script" dialogue should now be visible, but instead it is sent to the background (it is visible in the Activities overview of Gnome) and is unable to be brought to the foreground to use, but it can still be closed.


15 create and test docker files that do stuff

Added Dockerfile and a scripit to automatically build containers.
Opened two new issues on integrating docker with DVC and continius integration.

More debugging is needed to make docker fit with the newest updata


Lock doesn't appear to be released after failed restore

Output of restic version
restic 0.3.2 (v0.3.2-4-gb0997d0)
compiled with go1.7.4 on darwin/amd64
Expected behavior
An exclusive lock should not be held after an operation is complete and the process terminates.
Actual behavior
$ restic restore latest --path "path/that's/not/found" --target ~/restoretest/
latest snapshot for criteria not found: no snapshot found Paths:[path/that's/not/found] Host:

$ restic check
Create exclusive lock for repository
repository is already locked by PID 57750 on Shadowfax.home by matt (UID 501, GID 20)
lock was created at 2016-12-27 08:33:22 (50.993236973s ago)
storage ID 082d53a5
the `unlock` command can be used to remove stale locks

Steps to reproduce the behavior
As far as I know, just try to do a restore on a path that's not found, and then run restic check and it seems the lock didn't release after the failed restore. The process with ID 57750 had terminated nearly a minute earlier.
The unlock command did the trick but it seems a bit unnecessary? Should I just run restic unlock after every restic command or is that a bad idea. (Going for unsupervised execution here.)

Ha, thanks for the report. This is indeed a bug. Apart from when a panic occurs, restic should clean up locks. Please note that the restore command created a non-exclusive lock, which was left in the repo. The check command (by default) creates an exclusive lock.

Is this bug fixed?

Yes, it was resolved in #709.


Translate object

How could I translate something like this in my json?
  "test": {
    "test1": "hi"
  },

Found it:
Translate with pluralization:

translatePlural('plural.demo', yourNumericValue);
JSON:

"plural": {
    "demo": {
        "0": "Please start pushing the 'plus' button.",
        "1": "You have pushed the button one time.",
        "else": "You have pushed the button {{value}} times."
    }
}


ORA-01110 cannot find data files at database startup

ENV: Oracle single database 19.3 deployed in Azure.
We persisted /opt/oracle/oradata folder in a PV (with Retain policy) but the data files are created by default in /opt/oracle/product.
We created different custom schemas with tablespaces and data files.
The consequence is the database will still work after a pod restart but it will not survive a node shutdown.
When the database tries to start after the k8s cluster was stopped, those errors are thrown:
SQL> SQL>    alter database mount
*ERROR at line 1:
ORA-01100: database already mounted
SQL>    alter database open
*ERROR at line 1:
ORA-01157: cannot identify/lock data file 13 - see DBWR trace file
ORA-01110: data file 13:
'/opt/oracle/product/19c/dbhome_1/dbs/.dbf'
SQL>    alter pluggable database all open
*ERROR at line 1:
ORA-01109: database not open
Can you expose the db_create_file_dest variable to the Docker env to be able to change it?
Thanks

I also just got hit by this. Created per-user tablespace which the documentation itself lists as permanent. The node restarted for an upgrade, and now all user tablespace files are gone. I'm not sure if the issue is that this needs to be configurable, as much as this seems like data that should have been persisted in the first place.

For the time being, I've tested manually providing the full path when creating your tablespace. It's not ideal, but it will get you through a pod deletion/node restart. Unfortunately, running Oracle Database on Azure is currently a mess.


sap_swpm: Add nw_config_webdisp_generic for WDP installation

This PR makes it possible to install the web dispatcher in default mode:
 - ansible.builtin.include_vars: ./vars/wdp.sample.yml
      - ansible.builtin.include_role:
          name: community.sap_install.sap_swpm
      vars:
        sap_swpm_ansible_role_mode: default

It can use the default sample-variables-sap-swpm-default-mode-webdisp-install.yml from the playbooks/vars directory.

The Ansible Role default variables will not be altered, they are currently set to a generate an inifile.params which will perform an SAP S/4HANA installation by default - but could also be used for SAP S/4HANA System Copy or for SAP NetWeaver + SAP HANA without causing catastrophic failures.
It is documented that the user should configure their own variables, using either this "Default mode" or any of the others "Default Templates mode", "Advanced mode", "Advanced Templates mode", "Reuse inifile mode". The user only needs to append their own variables within an Ansible Playbook and this default is immediately overwritten - see Ansible Vars precedence > https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_variables.html#variable-precedence-where-should-i-put-a-variable
This PR cannot be accepted for the above reasoning. If you need further assistance please reach out again


PHP 8.1 compatibility

Hey there. Thanks for the cool tool.
It seems the Ploi CLI is not compatible with PHP8.1. I get the following error:
Deprecated: Return type of HumbugBox3130\KevinGH\RequirementChecker\RequirementCollection::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/robdekort/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/.box/src/RequirementCollection.php on line 12

Deprecated: Return type of HumbugBox3130\KevinGH\RequirementChecker\RequirementCollection::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/robdekort/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/.box/src/RequirementCollection.php on line 16

Deprecated: Return type of Illuminate\Container\Container::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/robdekort/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/illuminate/container/Container.php on line 1405

Deprecated: Return type of Illuminate\Container\Container::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/robdekort/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/illuminate/container/Container.php on line 1416

Deprecated: Return type of Illuminate\Container\Container::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/robdekort/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/illuminate/container/Container.php on line 1428

Deprecated: Return type of Illuminate\Container\Container::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/robdekort/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/illuminate/container/Container.php on line 1441

Deprecated: Return type of PhpOption\Some::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/robdekort/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/phpoption/phpoption/src/PhpOption/Some.php on line 152

Deprecated: Return type of PhpOption\None::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/robdekort/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/phpoption/phpoption/src/PhpOption/None.php on line 118

Deprecated: Return type of Illuminate\Config\Repository::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/robdekort/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/illuminate/config/Repository.php on line 141

Deprecated: Return type of Illuminate\Config\Repository::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/robdekort/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/illuminate/config/Repository.php on line 152

Deprecated: Return type of Illuminate\Config\Repository::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/robdekort/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/illuminate/config/Repository.php on line 164

Deprecated: Return type of Illuminate\Config\Repository::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/robdekort/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/illuminate/config/Repository.php on line 175

Deprecated: Return type of Symfony\Component\Finder\Finder::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/robdekort/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/symfony/finder/Finder.php on line 608

Deprecated: Return type of Symfony\Component\Finder\Finder::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/robdekort/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/symfony/finder/Finder.php on line 690

Deprecated: Return type of Symfony\Component\Finder\Iterator\FileTypeFilterIterator::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/robdekort/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/symfony/finder/Iterator/FileTypeFilterIterator.php on line 42

Deprecated: Return type of Symfony\Component\Finder\Iterator\ExcludeDirectoryFilterIterator::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/robdekort/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/symfony/finder/Iterator/ExcludeDirectoryFilterIterator.php on line 55

Deprecated: Return type of Symfony\Component\Finder\Iterator\ExcludeDirectoryFilterIterator::hasChildren() should either be compatible with RecursiveIterator::hasChildren(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/robdekort/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/symfony/finder/Iterator/ExcludeDirectoryFilterIterator.php on line 74

Deprecated: Return type of Symfony\Component\Finder\Iterator\ExcludeDirectoryFilterIterator::getChildren() should either be compatible with RecursiveIterator::getChildren(): ?RecursiveIterator, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/robdekort/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/symfony/finder/Iterator/ExcludeDirectoryFilterIterator.php on line 82

Deprecated: Return type of Symfony\Component\Finder\Iterator\FilenameFilterIterator::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/robdekort/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/symfony/finder/Iterator/FilenameFilterIterator.php on line 28

Deprecated: Return type of Symfony\Component\Finder\Iterator\PathFilterIterator::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/robdekort/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/symfony/finder/Iterator/PathFilterIterator.php on line 27

I'm not sure if it's related but whenever I attempt to do anything with Ploi CLI I get the same deprecations :(
Deprecated: Return type of HumbugBox3130\KevinGH\RequirementChecker\RequirementCollection::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/ryan/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/.box/src/RequirementCollection.php on line 12

Deprecated: Return type of HumbugBox3130\KevinGH\RequirementChecker\RequirementCollection::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/ryan/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/.box/src/RequirementCollection.php on line 16

Deprecated: Return type of Illuminate\Container\Container::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/ryan/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/illuminate/container/Container.php on line 1405

Deprecated: Return type of Illuminate\Container\Container::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/ryan/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/illuminate/container/Container.php on line 1416

Deprecated: Return type of Illuminate\Container\Container::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/ryan/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/illuminate/container/Container.php on line 1428

Deprecated: Return type of Illuminate\Container\Container::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/ryan/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/illuminate/container/Container.php on line 1441

Deprecated: Return type of PhpOption\Some::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/ryan/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/phpoption/phpoption/src/PhpOption/Some.php on line 152

Deprecated: Return type of PhpOption\None::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/ryan/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/phpoption/phpoption/src/PhpOption/None.php on line 118

Deprecated: Return type of Illuminate\Config\Repository::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/ryan/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/illuminate/config/Repository.php on line 141

Deprecated: Return type of Illuminate\Config\Repository::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/ryan/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/illuminate/config/Repository.php on line 152

Deprecated: Return type of Illuminate\Config\Repository::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/ryan/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/illuminate/config/Repository.php on line 164

Deprecated: Return type of Illuminate\Config\Repository::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/ryan/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/illuminate/config/Repository.php on line 175

Deprecated: Return type of Symfony\Component\Finder\Finder::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/ryan/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/symfony/finder/Finder.php on line 608

Deprecated: Return type of Symfony\Component\Finder\Finder::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/ryan/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/symfony/finder/Finder.php on line 690

Deprecated: Return type of Symfony\Component\Finder\Iterator\FileTypeFilterIterator::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/ryan/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/symfony/finder/Iterator/FileTypeFilterIterator.php on line 42

Deprecated: Return type of Symfony\Component\Finder\Iterator\ExcludeDirectoryFilterIterator::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/ryan/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/symfony/finder/Iterator/ExcludeDirectoryFilterIterator.php on line 55

Deprecated: Return type of Symfony\Component\Finder\Iterator\ExcludeDirectoryFilterIterator::hasChildren() should either be compatible with RecursiveIterator::hasChildren(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/ryan/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/symfony/finder/Iterator/ExcludeDirectoryFilterIterator.php on line 74

Deprecated: Return type of Symfony\Component\Finder\Iterator\ExcludeDirectoryFilterIterator::getChildren() should either be compatible with RecursiveIterator::getChildren(): ?RecursiveIterator, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/ryan/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/symfony/finder/Iterator/ExcludeDirectoryFilterIterator.php on line 82

Deprecated: Return type of Symfony\Component\Finder\Iterator\FilenameFilterIterator::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/ryan/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/symfony/finder/Iterator/FilenameFilterIterator.php on line 28

Deprecated: Return type of Symfony\Component\Finder\Iterator\PathFilterIterator::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in phar:///Users/ryan/.composer/vendor/schmidfelix/ploi-cli/builds/ploi/vendor/symfony/finder/Iterator/PathFilterIterator.php on line 27```

Nice. Thanks for the merge. Would you tag a release as well? :-)

Sorry, completely forgot that - already done :)

Woop! Lovely. Thanks for all your work on this.


Added setConfigProperty to dynamically set configurations

this method might be used to dynamically add configurations or to swap/change headers between groups of multiple requests and avoid adding configs to each request.

This allows the client to be mutable, which contradicts the design decision that was made to keep the client immutable. Perhaps we could add a mutable client implementation, but I don't want to add a single mutable method to an otherwise immutable client.


[SSoC'23] Bucket Sort Algorithm Implementation

Bucket sort is mainly useful when input is uniformly distributed over a range. For example, consider the following problem.
Sort a large set of floating point numbers which are in range from 0.0 to 1.0 and are uniformly distributed across the range. How do we sort the numbers efficiently?
A simple way is to apply a comparison based sorting algorithm. The lower bound for Comparison based sorting algorithm (Merge Sort, Heap Sort, Quick-Sort .. etc) is Ω(n Log n), i.e., they cannot do better than nLogn.
Can we sort the array in linear time? Counting sort can not be applied here as we use keys as index in counting sort. Here keys are floating point numbers.
The idea is to use bucket sort. Following is bucket algorithm.
bucketSort(arr[], n)

Create n empty buckets (Or lists).

Do following for every array element arr[i].
.......a) Insert arr[i] into bucket[n*array[i]]

Sort individual buckets using insertion sort.

Concatenate all sorted buckets.
//TIME COMPLEXITY:  O(N)
//SPACE COMPLEXITY: O(N)

@Kumar-laxmi please assign me this under SSoC'23.

It is already implemented using C and Python. I will do it with C++ and java.

refer #674

It's in C and python i will do it with C++ and Java.

@Kumar-laxmi It's in C and python i will do it with C++ and Java.


Don't lose the stack when rethrowing exceptions from TestHost

I'm seeing the following when trying to run vstest:
Microsoft (R) Test Execution Command Line Tool Version 15.5.0-dev
Copyright (c) Microsoft Corporation.  All rights reserved.

Starting test execution, please wait...
Testhost process exited with error: Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'System.Threading.Thread, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
   at Microsoft.VisualStudio.TestPlatform.TestHost.Program.Main(String[] args)

The strack trace for the exception is lost since it's not re-thrown properly.

@dfederm,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@dotnet-bot Please test Windows_NT / Debug Build .


[Appreciation] Thanks for making this!

Hi there. I'm a new user of mkdocs. I've been searching for a theme that I like. Most of the popular themes, aside from the ubiquitous material theme, feel slightly outdated. I was starting to feel disappointed.
Until I found mkdocs-terminal. Perhaps I've yet to encounter something I don't like, but so far it's everything I could want from a documentation theme. It's timeless minimalism that gets out of the way. Nothing flashy and superbly readable. Reloading the page and seeing my docs rendered à la terminal.css for the first time was a moment of true satisfaction.
So I just wanted to say thanks for your work on this! 🙇♂

:)!!!!
thank you @lemontheme!  i appreciate the feedback.
how are things going so far?  still using mkdocs-terminal?  any issues/ideas for new features?
i have a new job so i have a bit less time to work on this project than i did earlier in the year but knowing that people are using the theme and enjoying it does make me want to continue adding to it.

I  agree! I use this now for a static, personal website.


Tool is not in accordance with my beliefs

VSCode Version: all
OS Version: al

Hello, I live on planet earth with billions of people, but I can't accept that there are projects or people with different cultures or religions than mine. I would like the company to modify the tool to put a reminder of my birthday and my wedding anniversary. Increment the photo of my dogs on the icon.
It's still unacceptable to have companies that I don't control.

Thanks for creating this issue. We think this issue is unactionable or unrelated to the goals of this project. Please follow our issue reporting guidelines.
Happy Coding!

Why is it closed? @chrisdias why did you offend him?
Look how many people agree with this idea.


Support negative globs for test_sources section in project file

Description of the feature request:
There are cases when valid utility classes are defined under a test file declared under the test_sources section. It would be nice to be able to do something like
test_sources:
  SomeDir/src/test/**
  -SomeDir/src/test/specific/java/file.jva

This comes after I run in some issues with classes declared under a test directory in https://github.com/bazelbuild/intellij/issues/6641. The issue has a pretty long winded explanation thats not worth reading but it the tl;dr is I didn't notice a source being under src/test instead of src/main and was not being indexed and that send me down a rabbit hole to find an issue with indexing that wasn't really an issue. I understand having non test classes under src/test is a pretty big code smell, but I'm working in a large codebase whith a bunch of legacy stuff that I dont control.
Which category does this issue belong to?
Intellij
What underlying problem are you trying to solve with this feature?
No response
What operating system, Intellij IDE and programming languages are you using? Please provide specific versions.
No response
Have you found anything relevant by searching the web?
No response
Any other information, logs, or outputs that you want to share?
No response

Looks like this is a bit more complicated to implement that originally thought. Sources are tracked at the directory level and not file level, so excluding individual files seems like a non starter here


Make timeout configurable

My ssh commands can take over 30min to succeed
https://github.com/loafoe/terraform-provider-ssh/blob/dc216fd420641c55fec1546e709501bb95fb0367/ssh/resource_resource.go#L284

Thanks for the request, makes perfect sense, will implement

@innovate-invent available in v1.1.0 of the provider


store packet payloads as frame-slices

Right now, packet payloads are stored as byte-slices. If we store them as Frame-Slices, we can remove old ACKs before retransmitting a packet.

This can be closed, right? :)

Fixed in 4659bf7


Support metric tags based on metric name regex

Is your feature request related to a problem? Please describe.
Data Prepper supports metricTags where you can define a map of key, value pairs to be added to all metrics. There is no way to add tags based on a regex or a prefix of metric. Users should have more control over the metric tags.
Describe the solution you'd like
Data Prepper user can configure metricsTags as a list of regex with map of tags to apply to the metrics which match to the regex. The regex patterns will be checked in order till a match occurs and a maximum of one regex will be matched. With this user can add tags to specific set of metrics instead of all metrics.
Data Prepper plugin metrics are prefixed with <pipeline-name>.<plugin-id>.  So users can use the prefixes and to set tags for any specific prefix.
metricsTags:
  - regex: "log-pipeline.*"
    tags:
      key1: value1
  # adds following tags to all metrics which didn't match any previous regex
  - regex: ".*"
    tags:
      key2: value2

This solution can be a breaking change. Instead, we can create a new option (metricTagsFilter) instead of replacing metricTags and iterate over all regex pattern's in metricTagsFilter and if nothing matches, we can apply the metricTags at the end. And metricTags can be removed in next major version.
Describe alternatives you've considered (Optional)
Alternatively, we can add an option metricTagFilters where you can specify the metrics to which tags shouldn't be applied.
metricTags:
  key1: value1
metricTagFilters: ["core.peerforwarder"]

In the above example tags will be applied to all metrics other than metrics starting with core.peerforwarder
This allows users to have more control over the tags. Here are some of the use cases

Allows customers with connected pipelines tag metrics by pipeline
Users can add separate tags to Peer Forwarder, plugin metrics
This will allows users to add tags to AWS SDK metrics mentioned here https://github.com/opensearch-project/data-prepper/issues/2087

The proposal for metricsTags would give users quite a bit of flexibility. With the metricsTagFilter we'd only be to remove the common tags. Plus, what if we have a subset of metricTags which we want to have filtered?
The approach does have to be non-breaking. So, the first proposal probably needs a new name. Maybe something like metricTagRules?

Another thought is about the pattern matching.
This proposal is to use Java regex patterns. These are powerful, but a little complex.
For example, the example you gave - "log-pipeline.*" - matches log-pipeline2.opensearch.bulkBadRequestErrors. That might not be what a user expects.
Might it be better to use a modified Ant-path pattern matcher? Metric names follow a fairly straight-forward pattern making them suitable for a simpler syntax. Plus, . is used throughout metric names and is a Java regex pattern character.
Here is a short Javadoc with some examples and explanation.
https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/util/AntPathMatcher.html
For the example above with log-pipeline.*, it would need to be replaced by log-pipeline.**, but it would match what you expect.
Say we have an Ant-path style matcher like this: entry-pipeline.**.*Errors. It would get all metrics from the entry-pipeline that end in Error.
Also, I suppose we could support both (regex: and ant_pattern:) options.

The approach does have to be non-breaking. So, the first proposal probably needs a new name. Maybe something like metricTagRules?

This will be a non-breaking change. metricTagFilters is the new option.

Might it be better to use a modified Ant-path pattern matcher?

Yes, I think this suits the use-case better.

Also, I suppose we could support both (regex: and ant_pattern:) options.

I think, using both might introduce a confusing behavior. We should just stick with one for now (Ant path)


Tag size seen as larger than file size error

I'm one of the pygame contributors, and we use SDL_mixer for all the audio decoding.
One of our users came in with this message printed to stdout every time they loaded a certain file:
INFO: parse_id3v2: Tag size bigger than actual file size
They went into a hex editor to investigate and found that this was not the case.
The tag size is ox00000036 AKA 54

After the header there are in fact 54 bytes

According to the spec

The ID3v2 tag size is the size of the complete tag after unsychronisation, including padding, excluding the header but not excluding the extended header (total tag size - 10). Only 28 bits (representing up to 256MB) are used in the size description to avoid the introducuction of 'false syncsignals'.

The tag size should include the size of the extended header, I believe this is where the parser in SDL_mixer messes up.
https://github.com/libsdl-org/SDL_mixer/blob/main/src/codecs/mp3utils.c#L487-L507
If it sees an extended header it skips over it. But the tag length (tag_len) includes the size of the extended header, so the parser thinks its going to run over the end.
Here's the file (zipped into a folder, GitHub wouldn't let me just drop the WAV in):
100.zip

So, the fix would be the following? (CC: @Wohlstand )
diff --git a/src/codecs/mp3utils.c b/src/codecs/mp3utils.c
index 830e96c..0ef9a1f 100644
--- a/src/codecs/mp3utils.c
+++ b/src/codecs/mp3utils.c
@@ -491,7 +491,6 @@ static SDL_bool parse_id3v2(Mix_MusicMetaTags *out_tags, struct mp3file_t *src)
     }

     if (tag_extended_len) {
-        total_length += tag_extended_len + 4;
         MP3_RWseek(src, tag_extended_len + 4, RW_SEEK_CUR); /* Skip extended header and it's size value */
     }

I'll take a look today.

I understand the problem, but, it's not good that your example lacks title/artist/album/copyright fields filled, and I am required to verify that these tags get parsed. Actually, I am trying to find any MP3 file in my collection that has an ID3 tag with an extended header...

Okay, I actually fixed this bug, and I also found an MP3 file example with an extra header and title tag.

@Starbuck5: Does the patch at #477 fix your issue?

I looked at the patch logic and it seems like it will.
I’m not sure if I’ll be able to test later today, but I’ll try to test later today or sometime tomorrow.
Thanks for such a quick response and PR!

Yes, that fixes it.


Implement ind_from_latlon using a BallTree

I tried using ind_from_latlon on with the new ICON-1 domain of MCH and it was kinda slow (20 Min). I implemented a new version using a BallTree.
I also added functionality to return the n closest points. That is super useful if one want to compare against instruments and avoid double penalties by slight location offsets.

Note, an version for spherical earth can be found here:
https://github.com/Unidata/python-workshop/blob/fall-2016/notebooks/netcdf-by-coordinates.ipynb

Thanks for the update/improvement! I'm still going through it but one thing I'm not sure of yet, would ind[0] be the closest of the closest points?

@AnnikaLau
I think the distinction is made by either passing k=n  or k=[n] to cKDTree.query, see here.
Would it help if I re-implemented the verbose option for ind_from_latlon ?

@AnnikaLau I think the distinction is made by either passing k=n or k=[n] to cKDTree.query, see here.
Would it help if I re-implemented the verbose option for ind_from_latlon ? Then you can test.

Yes I think the verbose option is useful for the case k=1, which we use for the icon-vis examples. So that the users are aware of that the location of the nearest point might be quite different. So it would be great if you could re-implement it for that case.

@AnnikaLau
So that the users are aware of that the location of the nearest point might be quite different.
I dont understand. Does it yield a different location for your case?

I created a corresponding merge request for icon-vis: https://github.com/C2SM/icon-vis/pull/39

@AnnikaLau
I realized that my approach did not work with global domains. I now use another Tree Data Structure and Haversines to compute the distances. The downside is that it adds another dependency: skikit-learn.


Reverse filtering of Photoshop Express

Hello, this was an excellent work, it's easy but effective and we wanna follow it. However, we're confused about the "Defilter" operation on noise removal in Photoshop Express which is mentioned in paper. How could you know the func of noise removal in Photoshop Express ？The algorithm needs to know the filtering process as J = f(I), but your code doesn't contain the noise removal filtering process.

We did not know the operator. But we put our image into Photoshop, and process it using noise removal function and save out to our code.


python310Packages.pydevd: fix darwin

Description of changes
@onny I've got 2 tests reliably failing on darwin. Are you ok to disable them ? Or do you want me to put this behind a darwin flag ?
Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

I've cured my laziness and disabled the tests only for darwin. Let me know if anything.

@onny let me know about this when you have a moment.

Thank you for improving the package on Dariwn :)

Thank you for maintaining the package !


Minecart with command block not working

The id is command_block_minecart but the translation value is Minecart with Command Block
bruh


permutation that supports more than 8 combinators

I notice that there is the following used in the permutation combinator,
// HACK: for some reason, Rust 1.11 does not accept $res.$it in
// permutation_unwrap. This is a bit ugly, but it will have no
// impact on the generated code
#[doc(hidden)]
#[macro_export]
macro_rules! acc (
  (0, $tup:expr) => ($tup.0);
  (1, $tup:expr) => ($tup.1);
  (2, $tup:expr) => ($tup.2);
  (3, $tup:expr) => ($tup.3);
  (4, $tup:expr) => ($tup.4);
  (5, $tup:expr) => ($tup.5);
  (6, $tup:expr) => ($tup.6);
  (7, $tup:expr) => ($tup.7);
);

https://github.com/Geal/nom/blob/e5da7f1753629a30a39e067d06a6d033e53d8640/src/branch.rs#L459
Is this a limitation that no longer exists after rust 1.11, or is it still a problem in 1.12, 1.13, and onward?
The permutation operator is a bit complex, I assume that it has to try each combinator over and over until it finds a permutation that works, else it fails. Is that correct? I'd expect that long permutations will generate quite a bit of code. Is it even wise to have a long permutation in a parser?

Hi!
You're right, that's how permutation works here. Compared to other parsers, this one will generate code that's kind of flat:

create a tuple of None values: https://github.com/Geal/nom/blob/e5da7f1753629a30a39e067d06a6d033e53d8640/src/branch.rs#L380
unwrap all the options: https://github.com/Geal/nom/blob/e5da7f1753629a30a39e067d06a6d033e53d8640/src/branch.rs#L412
this is where the most code is generated: https://github.com/Geal/nom/blob/e5da7f1753629a30a39e067d06a6d033e53d8640/src/branch.rs#L387 but for each child parser it only generates this: https://github.com/Geal/nom/blob/e5da7f1753629a30a39e067d06a6d033e53d8640/src/branch.rs#L502-L517

I could support more than 8 combinators, but I won't remove that hack right away, since I plan to support older versions of Rust for some time. I have not tested if the hack is still needed anyway.

which kind of format do you have with a large number of permutations?

I just bumped the number of child parsers to 20, I hope it will be enough :) d8b2e57


Easy Rpg Cheat Searching

RG353P EasyRpg Cheat Searching Can't Be Used, It Says Something Like Cheat Not Starting Or Like That, Please Fix It

I have no idea what EasyRpg Cheat searching is and I don't support the rg353p.


renv

Something to look into in the future

##############################################################################################
#' @title Initialize renv lockfile for Scripts used in the [minnowTraits](https://github.com/hdr-bgnn/minnowTraits) project

#' @author
#' Meghan Balk<EMAIL_ADDRESS>\cr

#' @description Initializes/re-initializes the renv.lock file for the scripts
# in the /Scripts folder in the repository. The renv.lock file is a listing of
# the exact packages used by the scripts in the folder and their versions.
#
# If a lockfile (renv.lock) already exists, the user will be interactively asked
# whether to restore from it or reinitialize it from the current top-facing
# library. Do not use this script to update the lockfile after installing
# packages in the packrat library
#'
#' @return Lockfile listing  library dependencies in the Scripts directory

#' @references
#'

#' @keywords Currently none

# changelog and author contributions / copyrights
#   Meghan Balk (2022-07-21)
#     original creation
#     modified from code writted by Cove Sturtevant (@covesturtevant)
##############################################################################################

# ------ Choose options --------

# Scripts directory
dirWork <- '~/minnowTraits/Scripts'

# Keep and use the local project that renv creates when creating/updating the
# lockfile in dirWork? If TRUE, note .Rprofile and .Rproj files will be
# created/retained in dirWork, and R will be restarted in this new or existing
# project. If FALSE, any resulting .Rprofile and .Rproj files will be deleted.
# R may or may not restart depending on the options selected below.
KeepProj <- FALSE

# Keep the local library in dirWork that results from creating/updating the
# lockfile? If TRUE, the local library is retained. If FALSE, it is deleted.
# Cannot be FALSE if KeepProj is TRUE.
# NOTE: Only the renv.lock file is needed for restoring dependencies, and is
# still retained if this option is TRUE.
KeepLocalLib <- FALSE

# Use the local library created/updated in dirWork after creating/updating the
# lockfile? If TRUE, any package updates or new installations will be installed
# in the local library. Any libraries used in the R session will first be loaded
# from the local library. If FALSE, the R session will quit and must be
# reloaded. Cannot be TRUE if KeepLocalLib is FALSE, and cannot be FALSE if
# KeepProj is TRUE. In other  words, you cannot use a local library you chose to
# delete, and you must use the local library if you decided to keep the
# created/existing project files.
UseLocalLib <- FALSE

#----------------------- Begin Program -----------------------

# Error check the options
if(KeepProj == TRUE && KeepLocalLib == FALSE){
  stop('KeepLocalLib cannot be FALSE if KeepProj is TRUE. Check options.')
} else if (KeepLocalLib == FALSE && UseLocalLib == TRUE) {
  stop('UseLocalLib cannot be TRUE if KeepLocalLib is FALSE. Check options.')
} else if (KeepProj == TRUE && UseLocalLib == FALSE){
  stop('UseLocalLib cannot be FALSE if KeepProj is TRUE. Check options.')
}

# Ensure that package 'renv' is installed
if(!("renv" %in% rownames(installed.packages()))) install.packages("renv")

# Change the working directory to the module/package directory
# MUST DO THIS - if not the ignored packages are not actually ignored
base::setwd(dirWork)
base::suppressWarnings(base::unlink(base::paste0(dirWork,'/renv.lock'))) # For some reason it works best to do a complete rewrite

# Initialize dependency management
renv::settings$ignored.packages(PackIgnr)
renv::init(dirWork,restart=KeepProj)

# If there is already a lockfile, you will be asked whether to restore from the lockfile,
# discard the lockfile and re-initialize it, or to activate the project but do nothing else.
# Choose the option that suites the desired use of this script. For example, if wanting to
# In any case, a .Rprofile file will be created, and potentially a *.Rproj file. Delete them.
if(KeepProj == FALSE){
  base::suppressWarnings(base::file.remove(base::paste0(dirWork,'/',c('*.Rproj','.Rprofile','.Rhistory'))))
}

# Remove the local library
if(KeepLocalLib == FALSE){
  base::suppressWarnings(base::unlink(base::paste0(dirWork,'/renv/'), recursive=TRUE))
}

# Don't use the local library
if(UseLocalLib == FALSE){
  base::quit()
}


[Design pattern] Add NS-forest markers

Context
NS-Forest algorithm identifies minimal combinations of marker genes that can accurately classify and define cell types from single-cell RNA sequencing datasets. We need a design pattern to add these markers to existing cells (Logically and textually).
Tasks

[ ] Update logical definition of cells that have a NS-forest marker
[ ] Update comments with information about the markers and the Fbeta score
[ ] Update relations guide to include new standard pattern for %CL class%

Comments
Markers should be PR terms.

We should follow the design pattern in this paper -
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC9873614/ - or something v.close to it.
This will work well with Knowledge Graphs and corresponds to the pattern used in HubMap.
For examples, see PCL & also pattern here: https://github.com/obophenotype/brain_data_standards_ontologies/blob/master/src/patterns/dosdp-patterns/taxonomy_marker_set.yaml

Markers should be PR terms.

I think this is problematic - we don't strictly know if the proteins are markers - just the transcripts.  We need a general policy on how to refer to genes.  In this case maybe HGNC IDs are sufficient as lung datasets are human.  NCBI or Ensembl also possible.  @cmungall @scheuerm  - comments?

My 3 cents:
There are also microRNA and splicing variants that are cell-type specific, so maybe in the long run we should have ways to consider that?
I feel almost like the "cell type marker" relation is more about gene annotations than species-neutral cell-type annotations, similar to the way GO does gene curation (https://geneontology.org/docs/go-annotations/) using Evidence Codes for details.
By the way, on Wikidata, we use the "has marker" property to link species-specific cell terms to species-specific terms, but I don't think this design pattern is usable around here.

There are also microRNA and splicing variants that are cell-type specific, so maybe in the long run we should have ways to consider that?

Yep.  And we have cases of lnRNA in NS-Forest markers.

In the past, we used HGNC IDs, but is there not a true "gene ontology" that we might want to consider.  Having said that, we have tired to be explicit that we are referring to gene transcripts when talking about these cell type biomarkers.  In theory, we could use Ensemble IDs for these.  However, the reference-based alignment methods that we use to produce the count data are not great at distinguishing between different alternative splicing isoforms.  And so, although we do have mappings to Ensemble IDs, I would be concerned about their accuracy.

I think we should try and pick a single ID space per species for genes/proteins. This should be based on bioinformatics considerations. Of course genes, transcripts, proteins and other products are ontologically distinct, but we should use mechanisms such as the predicate to determine which aspect we are referring to. How common is it to need to refer to isoforms? Would a policy of ENSG and then ENST if isoform specificity is required work?

Until we start to see the use of long read technologies in the scRNAseq space, reliable splice isoform data will probably not be available.  Yes, I think ENSG and then ENST if isoform specificity is required would work


Reduce build time

[x] Move DB folder to tmpfs (need drone 0.8.0:latest)
[x] Create test-integration group (parallelize tests on mysql/postgres)
[x] Create dockerimage group (parallelize tasks)

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@bradrydzewski tmpfs removed


Firmware

Hi, is it possible to upload the untouched firmware, please? I'm trying to repair my console and will need to replace the damaged STM. Thank you.

I've sent you an email but I can't upload the firmware here


Behavex exits almost instantly when running parallel processes for tags

I'm trying to use Behavex to concurrently execute several different feature files. To identify the feature files I want run, I've used tags. However, whenever I try to run Behavex it almost instantly exits (I don't even reach my before_all)
This is the command I am using: behavex -texample -ttest --parallel-processes 2 --prarallel-scheme feature
Where I have two separate feature files tagged with @example and @test respectively.
The problem only occurs when I specify more than 1 tag in the command.
E.g.  behavex -texample --parallel-processes 2 --prarallel-scheme feature runs fine for me.
I'm using Windows 10 with Python 3.10.0, behave 1.2.6 and behavex 1.6.0

Hi @EuanMor , basically the issue you are having is due to the logical implementation of tags:
-texample -ttest means that you will only execute the tests that have the example tag AND the test tag (this is a logical AND). So if the scenario does not have both tags it will not run.
On the other hand, what you need is a logical OR, and this is done in the following way:
-texample,test