Cannot Authenticate to Google Artifact Registry

Checks

[X] I have checked that this issue has not already been reported.

[X] I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example
Hello,
I have some issues downloading python packages from my private Google Artifact Registry.
Here is my pixi.toml
[project]
name = "pypitest"
channels = ["conda-forge"]
platforms = ["linux-64"]

[dependencies]
python = "3.10"

[pypi-dependencies]
private_package = "*"

[pypi-options]
index-url = "https://pypi.org/simple"
extra-index-urls = ["<Google_artifact_registry>/simple"]

I followed the doc and ran:
# Install pipx if you haven't already
pixi global install pipx
pipx install keyring
# For Google Artifact Registry, also install and initialize its keyring backend.
pipx inject keyring keyrings.google-artifactregistry-auth --index-url https://pypi.org/simple
gcloud auth login

Then I m running
pixi install --pypi-keyring-provider subprocess

And getting:
failed to solve the pypi requirements of 'default' 'linux-64'
  ├─▶ failed to resolve pypi dependencies
  ╰─▶ HTTP status client error (401 Unauthorized) for url (https://<mygoogle_artifact_registry>/simple/private_package/)

Issue description
I cannot download use pixi with my private python registry hosted on a private Google Artifact Registry.
Expected behavior
Pixi runs fine.
Is there something I m doing wrong?
Thanks for your help!

Hi @clement-chaneching, thanks for the issue! could you re-run with -vv. Could you run an install with the same keyring settings using uv directly: uv pip install <pkg> --extra-index-urls https://<mygoogle_artifact_registry>/simple and see if that does work?

I'm also looking into testing with our own private gcs index.

Okay, so I think I found out.
You need to add<EMAIL_ADDRESS>for the URL, the breaking changes are listed here: https://github.com/astral-sh/uv/blob/main/CHANGELOG.md#0133 I'll update the documentation to reflect this, as well as add an example I used to test uploading.
Let me know if that changes things.

Oh yes cool it works, adding oauth2accesstoken fixes it !
Thanks a lot for your help!

Unless I am mistaken, when my token expires, pixi does not request another GCP token.
It keeps trying to reauthenticate with the expired token stored in the keyring.
It does work when I use this
extra-index-urls = ["https://oauth2accesstoken:@/simple"]
Thanks for the help!

I think UV caches credentials. If the TTL is longer than the token validity, this will create issues indeed.

I think the cache is a per process cache, if I'm reading the UV source correctly. Maybe @olivier-lacroix could give that code a second glance to see if I'm correct.
So I'm a bit uncertain why it would re-use the token, could also maybe happen in keyring itself, although again reading that source it does not seem so.
Does it make a difference if you delete the rattler cache, which would also contain the uv cache (not it's a different location then when using uv directly). You should be able to find it using pixi info
Sorry for the problems with this. We've communicated with one of the maintainers and we are working on adding custom middleware. This should give us back a bit more control: https://github.com/astral-sh/uv/pull/3502

No problem @tdejager , appreciate your help!
I have already tried to delete the whole rattler cache dir and same behavior unfortunately.
Let me know if you find anything, I will also try to look on my side.

Another thing you could try to rule out keyring:
With this pixi.toml
[project]
name = "keyring"
version = "0.1.0"
description = "Add a short description here"
authors = ["Tim de Jager<EMAIL_ADDRESS>channels = ["conda-forge"]
platforms = ["osx-arm64"]

[tasks]

[dependencies]
python = ">=3.12.3,<3.13"
# Used for gcp authentication by twine
keyring = ">=25.2.0,<25.3"
"keyrings.google-artifactregistry-auth" = ">=1.1.1,<1.2"
ipython = ">=8.24.0,<8.25"

Run the following python commands in IPython or w/e:
import keyring
# replace this with your own repository
k = keyring.get_credential('https://europe-west4-python.pkg.dev/test-artifact-registry-423208/test', None)
k.password

And see if that produces the same token once its expired.

BTW I've created this PR that documents some of the findings we had over the last days: https://github.com/prefix-dev/pixi/pull/1380

It actually looks like the authentication to my Google Registry is now still working after 3 hours so not sure what happened this morning.
I will wait to see what happens tomorrow and close this issue if everything is fine!

That keyring program script at least is producing different results for me after a while, so we can rule that one out :)

It looks like it s working, maybe because I needed to add the keyrings as dependencies or had a wrong version:
keyring = ">=25.2.0,<25.3"
"keyrings.google-artifactregistry-auth" = ">=1.1.1,<1.2"
I ll let you know if I find any other issues, thank you!

Hello @tdejager
I m reopening this issue once again because I have some cache errors:
So I m using github action to build my app and pulling images from my private Google Artifact Registry.
Everything worked fine at the beginning, but then it looks like I have some cache issues:
injected package keyrings-google-artifactregistry-auth into venv keyring
× Failed to download distributions
  ├─▶ Failed to fetch wheel: <package>==1.2.3
  ╰─▶ HTTP status client error (401 Unauthorized) for url (https://
      <registry>/<registry>/<package>/<package>-1.2.3-py3-none-
      any.whl#sha256=3cac92fb4a69dcdb0ef5be1846a3441ae8eaec44fa58d0691cf3dc[43]

It tries to fetch a specific sha sum package, which i dont know where it s from.
With pip, we can specific --no-cache-dir option to force it to retrieve them from the GAR every time, but didnt find any similar options for pixi.
Any ideas on how to fix this?

Ah that's annoying, still not really sure what is caching what. Seeing as the uv code should not, could you try running the keyring commands listed above just to be sure :)?

Yep sorry, it was not really clear to me where the error was.
But I think the issue occurs because of the lockfile and how the keyring authentication is managed for the url.
When running pixi with my private packages without the lockfile (with just pyproject.toml), it always works and creates my pixi.lock file:
- kind: pypi
  name: private-package
  version: 1.2.3
  url: https://registry/package-1.2.3-py3-none-any.whl#sha256=3cac92fb4a69dcdb0ef5be1846a3441ae8eaec44fa58d0691cf3dc43f408d5c5
  sha256: 3cac92fb4a69dcdb0ef5be1846a3441ae8eaec44fa58d0691cf3dc43f408d5c5

But if I copy my pixi.lock and pixi.toml files in a different folder (like it is working in my dockerfile) and run pixi install once again, it will throw me the error:
HTTP status client error (401 Unauthorized) for url (registry/package-1.2.3-py3-none-any.whl#sha256=3cac92fb4a69dcdb0ef5be1846a3441ae8eaec44fa58d0691cf3dc43f408d5c5)

Hope that helps!

It helps! But it makes it extra strange 😆 , can you try running with -vvv and check what the output is?

Sure, here is the output with pixi.lock file when running:
pixi install --pypi-keyring-provider subprocess -vvv

DEBUG download{total=11}:get_wheel{name=cloud-store==1.2.3 size=None url="https://australia-southeast1-python.pkg.dev/python-artifact-registry-5b23/enea-python-packages/cloud-store/cloud_store-1.2.3-py3-none-any.whl#sha256=3cac92fb4a69dcdb0ef5be1846a3441ae8eaec44fa58d0691cf3dc43f408d5c5"}:get_or_build_wheel{dist=cloud-store==1.2.3}:get_serde:get_cacheable:fresh_request{url="https://australia-southeast1-python.pkg.dev/python-artifact-registry-5b23/enea-python-packages/cloud-store/cloud_store-1.2.3-py3-none-any.whl#sha256=3cac92fb4a69dcdb0ef5be1846a3441ae8eaec44fa58d0691cf3dc43f408d5c5"}:Connection{peer=Client}: h2::codec::framed_read: received frame=Headers { stream_id: StreamId(1), flags: (0x4: END_HEADERS) }
DEBUG download{total=11}:get_wheel{name=dash-extensions==1.0.15 size=None url="https://files.pythonhosted.org/packages/1e/9c/f35d67e9564678b2e0a93e0b85085362119b84a5b3b915cc4a3cb3a4964a/dash_extensions-1.0.15-py3-none-any.whl"}:get_or_build_wheel{dist=dash-extensions==1.0.15}:get_serde:get_cacheable:fresh_request{url="https://files.pythonhosted.org/packages/1e/9c/f35d67e9564678b2e0a93e0b85085362119b84a5b3b915cc4a3cb3a4964a/dash_extensions-1.0.15-py3-none-any.whl"}:Connection{peer=Client}: h2::codec::framed_read: received frame=Data { stream_id: StreamId(5) }
DEBUG download{total=11}:get_wheel{name=cloud-store==1.2.3 size=None url="https://australia-southeast1-python.pkg.dev/python-artifact-registry-5b23/enea-python-packages/cloud-store/cloud_store-1.2.3-py3-none-any.whl#sha256=3cac92fb4a69dcdb0ef5be1846a3441ae8eaec44fa58d0691cf3dc43f408d5c5"}:get_or_build_wheel{dist=cloud-store==1.2.3}:get_serde:get_cacheable:fresh_request{url="https://australia-southeast1-python.pkg.dev/python-artifact-registry-5b23/enea-python-packages/cloud-store/cloud_store-1.2.3-py3-none-any.whl#sha256=3cac92fb4a69dcdb0ef5be1846a3441ae8eaec44fa58d0691cf3dc43f408d5c5"}:Connection{peer=Client}: h2::codec::framed_read: received frame=Data { stream_id: StreamId(1) }
DEBUG download{total=11}:get_wheel{name=dash-extensions==1.0.15 size=None url="https://files.pythonhosted.org/packages/1e/9c/f35d67e9564678b2e0a93e0b85085362119b84a5b3b915cc4a3cb3a4964a/dash_extensions-1.0.15-py3-none-any.whl"}:get_or_build_wheel{dist=dash-extensions==1.0.15}:get_serde:get_cacheable:fresh_request{url="https://files.pythonhosted.org/packages/1e/9c/f35d67e9564678b2e0a93e0b85085362119b84a5b3b915cc4a3cb3a4964a/dash_extensions-1.0.15-py3-none-any.whl"}:Connection{peer=Client}: h2::codec::framed_read: received frame=Data { stream_id: StreamId(13) }
DEBUG download{total=11}:get_wheel{name=cloud-store==1.2.3 size=None url="https://australia-southeast1-python.pkg.dev/python-artifact-registry-5b23/enea-python-packages/cloud-store/cloud_store-1.2.3-py3-none-any.whl#sha256=3cac92fb4a69dcdb0ef5be1846a3441ae8eaec44fa58d0691cf3dc43f408d5c5"}:get_or_build_wheel{dist=cloud-store==1.2.3}:get_serde:get_cacheable:fresh_request{url="https://australia-southeast1-python.pkg.dev/python-artifact-registry-5b23/enea-python-packages/cloud-store/cloud_store-1.2.3-py3-none-any.whl#sha256=3cac92fb4a69dcdb0ef5be1846a3441ae8eaec44fa58d0691cf3dc43f408d5c5"}:Connection{peer=Client}: h2::codec::framed_read: received frame=Data { stream_id: StreamId(1), flags: (0x1: END_STREAM) }
DEBUG download{total=11}:get_wheel{name=dash-extensions==1.0.15 size=None url="https://files.pythonhosted.org/packages/1e/9c/f35d67e9564678b2e0a93e0b85085362119b84a5b3b915cc4a3cb3a4964a/dash_extensions-1.0.15-py3-none-any.whl"}:get_or_build_wheel{dist=dash-extensions==1.0.15}:get_serde:get_cacheable:fresh_request{url="https://files.pythonhosted.org/packages/1e/9c/f35d67e9564678b2e0a93e0b85085362119b84a5b3b915cc4a3cb3a4964a/dash_extensions-1.0.15-py3-none-any.whl"}:Connection{peer=Client}: h2::codec::framed_read: received frame=Data { stream_id: StreamId(3) }
DEBUG download{total=11}:get_wheel{name=cloud-store==1.2.3 size=None url="https://australia-southeast1-python.pkg.dev/python-artifact-registry-5b23/enea-python-packages/cloud-store/cloud_store-1.2.3-py3-none-any.whl#sha256=3cac92fb4a69dcdb0ef5be1846a3441ae8eaec44fa58d0691cf3dc43f408d5c5"}:get_or_build_wheel{dist=cloud-store==1.2.3}:get_serde:get_cacheable:fresh_request{url="https://australia-southeast1-python.pkg.dev/python-artifact-registry-5b23/enea-python-packages/cloud-store/cloud_store-1.2.3-py3-none-any.whl#sha256=3cac92fb4a69dcdb0ef5be1846a3441ae8eaec44fa58d0691cf3dc43f408d5c5"}:Connection{peer=Client}: h2::codec::framed_read: received frame=Ping { ack: false, payload: [0, 0, 0, 0, 0, 0, 0, 189] }
DEBUG download{total=11}:get_wheel{name=cloud-store==1.2.3 size=None url="https://australia-southeast1-python.pkg.dev/python-artifact-registry-5b23/enea-python-packages/cloud-store/cloud_store-1.2.3-py3-none-any.whl#sha256=3cac92fb4a69dcdb0ef5be1846a3441ae8eaec44fa58d0691cf3dc43f408d5c5"}:get_or_build_wheel{dist=cloud-store==1.2.3}:get_serde:get_cacheable:fresh_request{url="https://australia-southeast1-python.pkg.dev/python-artifact-registry-5b23/enea-python-packages/cloud-store/cloud_store-1.2.3-py3-none-any.whl#sha256=3cac92fb4a69dcdb0ef5be1846a3441ae8eaec44fa58d0691cf3dc43f408d5c5"}:Connection{peer=Client}: h2::codec::framed_write: send frame=Ping { ack: true, payload: [0, 0, 0, 0, 0, 0, 0, 189] }
DEBUG download{total=11}:get_wheel{name=cloud-store==1.2.3 size=None url="https://australia-southeast1-python.pkg.dev/python-artifact-registry-5b23/enea-python-packages/cloud-store/cloud_store-1.2.3-py3-none-any.whl#sha256=3cac92fb4a69dcdb0ef5be1846a3441ae8eaec44fa58d0691cf3dc43f408d5c5"}:get_or_build_wheel{dist=cloud-store==1.2.3}:get_serde:get_cacheable:fresh_request{url="https://australia-southeast1-python.pkg.dev/python-artifact-registry-5b23/enea-python-packages/cloud-store/cloud_store-1.2.3-py3-none-any.whl#sha256=3cac92fb4a69dcdb0ef5be1846a3441ae8eaec44fa58d0691cf3dc43f408d5c5"}:Connection{peer=Client}: h2::codec::framed_read: received frame=Headers { stream_id: StreamId(3), flags: (0x4: END_HEADERS) }
DEBUG download{total=11}:get_wheel{name=cloud-store==1.2.3 size=None url="https://australia-southeast1-python.pkg.dev/python-artifact-registry-5b23/enea-python-packages/cloud-store/cloud_store-1.2.3-py3-none-any.whl#sha256=3cac92fb4a69dcdb0ef5be1846a3441ae8eaec44fa58d0691cf3dc43f408d5c5"}:get_or_build_wheel{dist=cloud-store==1.2.3}:get_serde:get_cacheable:fresh_request{url="https://australia-southeast1-python.pkg.dev/python-artifact-registry-5b23/enea-python-packages/cloud-store/cloud_store-1.2.3-py3-none-any.whl#sha256=3cac92fb4a69dcdb0ef5be1846a3441ae8eaec44fa58d0691cf3dc43f408d5c5"}:Connection{peer=Client}: h2::codec::framed_read: received frame=Data { stream_id: StreamId(3) }
DEBUG download{total=11}:get_wheel{name=cloud-store==1.2.3 size=None url="https://australia-southeast1-python.pkg.dev/python-artifact-registry-5b23/enea-python-packages/cloud-store/cloud_store-1.2.3-py3-none-any.whl#sha256=3cac92fb4a69dcdb0ef5be1846a3441ae8eaec44fa58d0691cf3dc43f408d5c5"}:get_or_build_wheel{dist=cloud-store==1.2.3}:get_serde:get_cacheable:fresh_request{url="https://australia-southeast1-python.pkg.dev/python-artifact-registry-5b23/enea-python-packages/cloud-store/cloud_store-1.2.3-py3-none-any.whl#sha256=3cac92fb4a69dcdb0ef5be1846a3441ae8eaec44fa58d0691cf3dc43f408d5c5"}:Connection{peer=Client}: h2::codec::framed_read: received frame=Data { stream_id: StreamId(3), flags: (0x1: END_STREAM) }
DEBUG download{total=11}:get_wheel{name=cloud-store==1.2.3 size=None url="https://australia-southeast1-python.pkg.dev/python-artifact-registry-5b23/enea-python-packages/cloud-store/cloud_store-1.2.3-py3-none-any.whl#sha256=3cac92fb4a69dcdb0ef5be1846a3441ae8eaec44fa58d0691cf3dc43f408d5c5"}:get_or_build_wheel{dist=cloud-store==1.2.3}:get_serde:get_cacheable:fresh_request{url="https://australia-southeast1-python.pkg.dev/python-artifact-registry-5b23/enea-python-packages/cloud-store/cloud_store-1.2.3-py3-none-any.whl#sha256=3cac92fb4a69dcdb0ef5be1846a3441ae8eaec44fa58d0691cf3dc43f408d5c5"}:Connection{peer=Client}: h2::codec::framed_write: send frame=GoAway { error_code: NO_ERROR, last_stream_id: StreamId(0) }
DEBUG download{total=11}:get_wheel{name=cloud-store==1.2.3 size=None url="https://australia-southeast1-python.pkg.dev/python-artifact-registry-5b23/enea-python-packages/cloud-store/cloud_store-1.2.3-py3-none-any.whl#sha256=3cac92fb4a69dcdb0ef5be1846a3441ae8eaec44fa58d0691cf3dc43f408d5c5"}:get_or_build_wheel{dist=cloud-store==1.2.3}:get_serde:get_cacheable:fresh_request{url="https://australia-southeast1-python.pkg.dev/python-artifact-registry-5b23/enea-python-packages/cloud-store/cloud_store-1.2.3-py3-none-any.whl#sha256=3cac92fb4a69dcdb0ef5be1846a3441ae8eaec44fa58d0691cf3dc43f408d5c5"}:Connection{peer=Client}: h2::proto::connection: Connection::poll; connection error error=GoAway(b"", NO_ERROR, Library)
DEBUG download{total=11}:get_wheel{name=dash-extensions==1.0.15 size=None url="https://files.pythonhosted.org/packages/1e/9c/f35d67e9564678b2e0a93e0b85085362119b84a5b3b915cc4a3cb3a4964a/dash_extensions-1.0.15-py3-none-any.whl"}:get_or_build_wheel{dist=dash-extensions==1.0.15}:get_serde:get_cacheable:fresh_request{url="https://files.pythonhosted.org/packages/1e/9c/f35d67e9564678b2e0a93e0b85085362119b84a5b3b915cc4a3cb3a4964a/dash_extensions-1.0.15-py3-none-any.whl"}:Connection{peer=Client}: h2::codec::framed_read: received frame=Data { stream_id: StreamId(7) }
DEBUG download{total=11}:get_wheel{name=cloud-store==1.2.3 size=None url="https://australia-southeast1-python.pkg.dev/python-artifact-registry-5b23/enea-python-packages/cloud-store/cloud_store-1.2.3-py3-none-any.whl#sha256=3cac92fb4a69dcdb0ef5be1846a3441ae8eaec44fa58d0691cf3dc43f408d5c5"}:get_or_build_wheel{dist=cloud-store==1.2.3}:get_serde:get_cacheable:fresh_request{url="https://australia-southeast1-python.pkg.dev/python-artifact-registry-5b23/enea-python-packages/cloud-store/cloud_store-1.2.3-py3-none-any.whl#sha256=3cac92fb4a69dcdb0ef5be1846a3441ae8eaec44fa58d0691cf3dc43f408d5c5"}:Connection{peer=Client}: rustls::common_state: Sending warning alert CloseNotify

  × Failed to download distributions
  ├─▶ Failed to fetch wheel: cloud-store==1.2.3
  ╰─▶ HTTP status client error (401 Unauthorized) for url (https://australia-southeast1-python.pkg.dev/
      python-artifact-registry-5b23/enea-python-packages/cloud-store/cloud_store-1.2.3-py3-none-
      any.whl#sha256=3cac92fb4a69dcdb0ef5be1846a3441ae8eaec44fa58d0691cf3dc43f408d5c5)

If I remove pixi.lock file and run the same command, it works:
DEBUG resolve_pypi{group=test platform=linux-64}:wheel_metadata{built_dist=cloud-store==1.2.3}:get_serde:get_cacheable:revalidation_request{url="https://australia-southeast1-python.pkg.dev/python-artifact-registry-5b23/enea-python-packages/cloud-store/cloud_store-1.2.3-py3-none-any.whl#sha256=3cac92fb4a69dcdb0ef5be1846a3441ae8eaec44fa58d0691cf3dc43f408d5c5"}: hyper_util::client::legacy::pool: reuse idle connection for ("https", australia-southeast1-python.pkg.dev)
DEBUG resolve_pypi{group=default platform=linux-64}:process_request{request=Versions firestore-aio}:simple_api{package=firestore-aio}:get_cacheable:revalidation_request{url="https://australia-southeast1-python.pkg.dev/python-artifact-registry-5b23/enea-python-packages/simple/firestore-aio/"}:Connection{peer=Client}: h2::codec::framed_write: send frame=Headers { stream_id: StreamId(269), flags: (0x5: END_HEADERS | END_STREAM) }
DEBUG resolve_pypi{group=default platform=linux-64}:process_request{request=Versions firestore-aio}:simple_api{package=firestore-aio}:get_cacheable:revalidation_request{url="https://australia-southeast1-python.pkg.dev/python-artifact-registry-5b23/enea-python-packages/simple/firestore-aio/"}:Connection{peer=Client}: h2::codec::framed_read: received frame=Headers { stream_id: StreamId(267), flags: (0x4: END_HEADERS) }
DEBUG resolve_pypi{group=default platform=linux-64}:wheel_metadata{built_dist=cloud-store==1.2.3}:get_serde:get_cacheable:revalidation_request{url="https://australia-southeast1-python.pkg.dev/python-artifact-registry-5b23/enea-python-packages/cloud-store/cloud_store-1.2.3-py3-none-any.whl#sha256=3cac92fb4a69dcdb0ef5be1846a3441ae8eaec44fa58d0691cf3dc43f408d5c5"}: reqwest::async_impl::client: redirecting 'https://australia-southeast1-python.pkg.dev/python-artifact-registry-5b23/enea-python-packages/cloud-store/cloud_store-1.2.3-py3-none-any.whl#sha256=3cac92fb4a69dcdb0ef5be1846a3441ae8eaec44fa58d0691cf3dc43f408d5c5' to 'https://australia-southeast1-python.pkg.dev/artifacts-downloads/namespaces/python-artifact-registry-5b23/repositories/enea-python-packages/downloads/ALJkh8OnRGy8OdrA3mFEqhECut3dRfXMCoOESo24a6sCrXQmw8Io7jr2nz1uxwdw6ZWdRLKjR8L45vGxfTkg7qPmfMa9QkQnjFqO1Ai6jkHWfdpv6e0x2yM--3G8D0cxxM1wrkKFNYaDu9zjRLJFWqQJIEyFhiTXBdqE-IIU6glJkfvn5_xIsHlf-e815MqEPrg0XirxQvNE6smPonzCsEnR03J9GBdZMt8fH30u-WyB-....._'
DEBUG resolve_pypi{group=default platform=linux-64}:wheel_metadata{built_dist=cloud-store==1.2.3}:get_serde:get_cacheable:revalidation_request{url="https://australia-southeast1-python.pkg.dev/python-artifact-registry-5b23/enea-python-packages/cloud-store/cloud_store-1.2.3-py3-none-any.whl#sha256=3cac92fb4a69dcdb0ef5be1846a3441ae8eaec44fa58d0691cf3dc43f408d5c5"}: hyper_util::client::legacy::pool: reuse idle connection for ("https", australia-southeast1-python.pkg.dev)

So with the pixi.lock when it errors it calls: get_serde:get_cacheable:fresh_request that cannot authenticate to the GAR.
But without pixi.lock, it calls : :get_serde:get_cacheable:revalidation_request that uses reqwest::async_impl::client to get a token and access the GAR and works I think.
You can reproduce this error by copying your pixi.toml and pixi.lock in another folder and running the command from there.
Happy to show you during a call if you want to debug this together!

Sure let's do that, in the call together! I'll first attempt another uv upgrade because they changed quite a bit in the auth and middleware layers.

Okay so I've update the uv version in main, which if you want you could give a go again to see if the problem persists :)

I'll try! So it's not part of the 0.23.0 release?

I'll try! So it's not part of the 0.23.0 release?

Nope, it will be in the next, was quite a big change so hope to get a bit more testing in! :)

It looks like it doesnt work at all for me anymore now.
 INFO solve:solve_tracked: pubgrub::internal::partial_solution: add_decision: root @ 0a0.dev0
DEBUG resolve_pypi{group=test platform=linux-64}:process_request{request=Versions private-package}:simple_api{package=private-package}:get_cacheable: uv_client::cached_client: No cache entry for: https://registry/simple/private-package/
DEBUG resolve_pypi{group=test platform=linux-64}:process_request{request=Versions private-package}:simple_api{package=private-package}:get_cacheable:fresh_request{url="https://registry/simple/private-package/"}: uv_auth::middleware: Checking netrc for credentials for https://registry/simple/private-package/
DEBUG resolve_pypi{group=test platform=linux-64}:process_request{request=Versions private-package}:simple_api{package=private-package}:get_cacheable:fresh_request{url="https://registry/simple/private-package/"}: uv_auth::middleware: Checking keyring for credentials for oauth2accesstoken@https://registry/simple/private-package/
DEBUG resolve_pypi{group=test platform=linux-64}:process_request{request=Versions private-package}:simple_api{package=private-package}:get_cacheable:fresh_request{url="https://pypi.org/simple/private-package/"}: uv_auth::middleware: Checking netrc for credentials for https://pypi.org/simple/private-package/
DEBUG resolve_pypi{group=test platform=linux-64}:process_request{request=Versions private-package}:simple_api{package=private-package}:get_cacheable:fresh_request{url="https://pypi.org/simple/private-package/"}: uv_auth::middleware: Skipping keyring lookup for https://pypi.org/simple/private-package/ with no username
DEBUG solve:solve_tracked:choose_version{package=private-package}: uv_resolver::resolver: Searching for a compatible version of private-package (*)
DEBUG solve:solve_tracked: uv_resolver::resolver: No compatible version found for: private-package
 INFO solve:solve_tracked: pubgrub::internal::core: Start conflict resolution because incompat satisfied:
   private-package * is forbidden
 INFO solve:solve_tracked: pubgrub::internal::core: prior cause: root ==0a0.dev0 is forbidden

 ⠴ default:linux-64     [00:00:23] resolving pypi dependencies                                                                                × failed to solve the pypi requirements of 'test' 'linux-64'
  ├─▶ failed to resolve pypi dependencies
  ╰─▶ Because <private_package> was not found in the package registry and you require enea-appshell, we can conclude that the requirements are unsatisfiable.

I m using pixi main that is using uv: 65b17f6e81125064ea04c5cfef685516ab660cf5

It looks like it doesnt work at all for me anymore now.

 INFO solve:solve_tracked: pubgrub::internal::partial_solution: add_decision: root @ 0a0.dev0

DEBUG resolve_pypi{group=test platform=linux-64}:process_request{request=Versions private-package}:simple_api{package=private-package}:get_cacheable: uv_client::cached_client: No cache entry for: https://registry/simple/private-package/

DEBUG resolve_pypi{group=test platform=linux-64}:process_request{request=Versions private-package}:simple_api{package=private-package}:get_cacheable:fresh_request{url="https://registry/simple/private-package/"}: uv_auth::middleware: Checking netrc for credentials for https://registry/simple/private-package/

DEBUG resolve_pypi{group=test platform=linux-64}:process_request{request=Versions private-package}:simple_api{package=private-package}:get_cacheable:fresh_request{url="https://registry/simple/private-package/"}: uv_auth::middleware: Checking keyring for credentials for oauth2accesstoken@https://registry/simple/private-package/

DEBUG resolve_pypi{group=test platform=linux-64}:process_request{request=Versions private-package}:simple_api{package=private-package}:get_cacheable:fresh_request{url="https://pypi.org/simple/private-package/"}: uv_auth::middleware: Checking netrc for credentials for https://pypi.org/simple/private-package/

DEBUG resolve_pypi{group=test platform=linux-64}:process_request{request=Versions private-package}:simple_api{package=private-package}:get_cacheable:fresh_request{url="https://pypi.org/simple/private-package/"}: uv_auth::middleware: Skipping keyring lookup for https://pypi.org/simple/private-package/ with no username

DEBUG solve:solve_tracked:choose_version{package=private-package}: uv_resolver::resolver: Searching for a compatible version of private-package (*)

DEBUG solve:solve_tracked: uv_resolver::resolver: No compatible version found for: private-package

 INFO solve:solve_tracked: pubgrub::internal::core: Start conflict resolution because incompat satisfied:

   private-package * is forbidden

 INFO solve:solve_tracked: pubgrub::internal::core: prior cause: root ==0a0.dev0 is forbidden

 ⠴ default:linux-64     [00:00:23] resolving pypi dependencies                                                                                × failed to solve the pypi requirements of 'test' 'linux-64'

  ├─▶ failed to resolve pypi dependencies

  ╰─▶ Because <private_package> was not found in the package registry and you require <private_package>, we can conclude that the requirements are unsatisfiable.

I m using pixi main that is using uv: 65b17f6e81125064ea04c5cfef685516ab660cf5

That's a weird registry name can't imagine that being the gcp one, did you change it in the logs?

Oh yeah I changed it in the logs sorry !
It does display properly my private google artifact registry

Are you sure all you details are correct in the toml?
This is working for me:
[project]
name = "gcp"
version = "0.1.0"
description = "Add a short description here"
authors = ["Tim de Jager<EMAIL_ADDRESS>channels = ["conda-forge"]
platforms = ["osx-arm64"]

[pypi-options]
extra-index-urls =<EMAIL_ADDRESS>
[tasks]

[dependencies]
python = "3.12"

[pypi-dependencies]
hi = "==0.1.0" # this is on the private registry

Note two things:

I'm using the extra index url, because otherwise it tries to get everything from the private registry.
I added /simple add the end

Running with install --pypi-keyring-provider subprocess seems to do the trick fro me.

Also running gcloud auth, which I suppose gets me another access token, then adding flask, which triggers a new solve, and new https requests. All seems to authenticate for me now, wondering if it is the same for your

Oh yeah sorry it looks like my local conda environment was broken:

Even after running the inject keyring, logging in with gcloud again and listing the backend, it would not list my Gauth keyring, not sure why.
Anyway it looks ok on another conda environment. I will test try to test the pixi lock error tomorrow.
Thanks for the help!

With a pixi.toml I've aliased pixd to the main debug build of pixi:
╰─ pixd install --pypi-keyring-provider subprocess -v                                                                                ─╯
 INFO pixi::environment: verifying prefix location is unchanged, with prefix file: /private/tmp/gcp/.pixi/envs/default/conda-meta/pixi_env_prefix
 INFO pixi::lock_file::outdated: environment 'default' is out of date because it does not exist in the lock-file.
 INFO pixi::lock_file::resolve::uv_resolution_context: using uv keyring (subprocess) provider
 INFO resolve_conda{group=default platform=osx-arm64}: pixi::lock_file::update: fetched 348 records in 12.759257209s
 INFO pixi::lock_file::update: resolved conda environment for environment 'default' 'osx-arm64' in 13s 211ms 348us 250ns
 INFO pixi::environment: Creating prefix file at: /private/tmp/gcp/.pixi/envs/default/conda-meta/pixi_env_prefix
 INFO pixi::environment: No update needed for the prefix file.
 INFO pixi::environment: Checking if history file exists: /private/tmp/gcp/.pixi/envs/default/conda-meta/history
 INFO pixi::lock_file::update: updated conda packages in the 'default' prefix in 27ms 246us 291ns
 INFO resolve_pypi{group=default platform=osx-arm64}: pixi::lock_file::resolve::pypi: there are no python packages installed by conda
 WARN resolve_pypi{group=default platform=osx-arm64}: uv_client::registry_client: Range requests not supported for hi-0.1.0-py3-none-any.whl; streaming wheel
 WARN resolve_pypi{group=default platform=osx-arm64}: uv_client::registry_client: Range requests not supported for hi-0.1.0-py3-none-any.whl; streaming wheel
 INFO pixi::lock_file::update: resolved pypi packages for environment 'default' 'osx-arm64' in 2s 824ms 306us 375ns
 INFO pixi::install_pypi: Nothing to do - Audited 12 distributions in 43ms
✔ The default environment has been installed.
╭─ I  /tmp/gcp                                                                                  ✔  16s  19:23:19 ─╮
╰─ mkdir ../gcp2                                                                                ─╯
╭─ I  /tmp/gcp                                                                                  ✔  19:23:30 ─╮
╰─ cp pixi.toml pixi.lock ../gcp2                                                                                ─╯
╭─ I  /tmp/gcp                                                                                  ✔  19:23:43 ─╮
╰─ cd ../gcp2/                                                                                ─╯
╭─ I  /tmp/gcp2                                                                                  ✔  19:23:48 ─╮
╰─ pixd install --pypi-keyring-provider subprocess -v                                                                                ─╯
 INFO pixi::environment: verifying prefix location is unchanged, with prefix file: /private/tmp/gcp2/.pixi/envs/default/conda-meta/pixi_env_prefix
 INFO pixi::lock_file::update: the lock-file is up-to-date
 INFO pixi::environment: Creating prefix file at: /private/tmp/gcp2/.pixi/envs/default/conda-meta/pixi_env_prefix
 INFO pixi::environment: Prefix file updated with: '/private/tmp/gcp2/.pixi/envs/default/conda-meta'.
 INFO pixi::environment: Checking if history file exists: /private/tmp/gcp2/.pixi/envs/default/conda-meta/history
 INFO pixi::environment: Creating history file: /private/tmp/gcp2/.pixi/envs/default/conda-meta/history
 INFO pixi::lock_file::resolve::uv_resolution_context: using uv keyring (subprocess) provider
 INFO pixi::install_pypi: resolved install plan: local=12, remote=0, reinstalls=0, extraneous=0
 INFO pixi::install_pypi: Install: ["jinja2", "markupsafe", "pygments", "rich", "werkzeug", "blinker", "mdurl", "click", "hi", "itsdangerous", "markdown-it-py", "flask"]
 INFO pixi::install_pypi: Re-install: []
 INFO pixi::install_pypi: Remove: []
 INFO pixi::install_pypi: Installed 12 packages in 19ms
✔ The default environment has been installed.

That all seems to work, let me try with a pyproject.toml next :)

Ah I see I needed to delete the cache, yes, now I seem to be able to reproduce :)

I'm eager to see what you've found. I'm still trying to figure out how to build pixi from source in the container to test it out, to no avail.

Description
So what is going on is the following.
There are two ways that uv access the index, the first when finding the correct distributions it wants to use and the second when the wheels or sources are actually downloaded.
Because the dist we pass from the locked data into the downloads does not contain the username, uv does not use authentication. So I was wondering then why does it work when resolving!?
Because uv caches credentials in the same process, when it does use the username when resolving it can use it for the download url even though the username is not contained in the url passed to the downloader.
So in the resolve flow:

Resolve certain distributions.
Save authentication.
Lock
Install distributions
No username found, check the url for cached credentials.
Found! Use these.
Success

When installing from just a lock:

Install distribution.
Check the url for username.
None, found do an unauthenticated request.
Failure.

So the thing that threw me off was the part about deleting the lock, that just makes sure you do another resolve and get back into the resolve flow. The package cache also needs to be deleted to reproduce, otherwise it does not hit the network at all.
Solution
I think we can call the uv method store_credentials_for_url prior to downloading. I'll make a PR.

I've made a PR that should have a fix @clement-chaneching, @RaphaelMelanconAtBentley would be great if you could test it before merging if you have that possibility :)

Pixi is also a pixi project you could try using pixi to build :) Don't know if that would help :)

I can confirm that this is fixed for me. Using and azure artifacts feed and I can install, reinstall, launch a shell, pixi run, etc. With or without a pixi.lock available. I'm having other/new issues relating to other packages. I'll investigate to make sure it's not a regression.

Thanks @RaphaelMelanconAtBentley I'll link your comment in the PR as well.

Yep also looks fine to me:

Thanks a lot @tdejager !


Fixes Typecheck bug in preactjs/preact#3934

Added SignalLike as an option for default that fixes /preact/issues/3934 while preserving current functionality.  This is a simple fix but it seems like it would do what's needed.

@marvinhagemeister @rschristian Let me know what you think and if any changes are required.

Thanks for the quick response!  Let me know if I can help more with this or anything else.

We really appreciate the fix! ❤
I'll try to cut a release in a bit, after my dinner.


Some E2E test cases have Kind cluster hardcoded

Is there an existing issue for this?

[X] I have searched the existing issues

Problem Statement
The majority of our E2E test cases use getEnvironmentBuilder helper function to get an environment builder (e.g. like here). It allows running the tests against both GKE and Kind clusters, depending on the passed environment variables.
There are test cases which don't use the helper, but always create a Kind cluster on their own:

TestKongRouterFlavorCompatibility
TestIstioWithKongIngressGateway

Proposed Solution
Use getEnvironmentBuilder in all E2E test cases.
Additional information
No response
Acceptance Criteria

[ ] When E2E tests are run against a GKE cluster (make test.e2e.gke), any of the test cases don't spin up its own Kind cluster, but use the getEnvironmentBuilder helper function

It was fixed by https://github.com/Kong/kubernetes-ingress-controller/pull/3378.


Added 3DMux

The rotation (or orientation) is still not functioning. The width and length parameters are placeholders.

added picoinjector

added picoinjector

On compile, it gets the following errors. This is because the pull request has changes with references from different updates. I'm going to close the pull request. @ryu-bu just do 1 big pull request with all the changes.
npm run watch_compile

><EMAIL_ADDRESS>watch_compile /Users/krishna/Documents/GitHub/3DuF
> watchify ./src/app/appSetup.js -t babelify -v --outfile ./3DuFapp.js -d -t [ babelify ]

Browserslist: caniuse-lite is outdated. Please run next command `npm update caniuse-lite browserslist`
Error: Can't walk dependency graph: Cannot find module '../library/filter' from '/Users/krishna/Documents/GitHub/3DuF/src/app/featureSets/featureSet.js'
    required by /Users/krishna/Documents/GitHub/3DuF/src/app/featureSets/featureSet.js
Error: Can't walk dependency graph: Cannot find module '../library/celltrapS' from '/Users/krishna/Documents/GitHub/3DuF/src/app/featureSets/featureSet.js'
    required by /Users/krishna/Documents/GitHub/3DuF/src/app/featureSets/featureSet.js
Error: Can't walk dependency graph: Cannot find module '../library/chemostatring' from '/Users/krishna/Documents/GitHub/3DuF/src/app/featureSets/featureSet.js'
    required by /Users/krishna/Documents/GitHub/3DuF/src/app/featureSets/featureSet.js
Error: Can't walk dependency graph: Cannot find module '../library/merger' from '/Users/krishna/Documents/GitHub/3DuF/src/app/featureSets/featureSet.js'
    required by /Users/krishna/Documents/GitHub/3DuF/src/app/featureSets/featureSet.js
Error: Can't walk dependency graph: Cannot find module '../library/incubation' from '/Users/krishna/Documents/GitHub/3DuF/src/app/featureSets/featureSet.js'
    required by /Users/krishna/Documents/GitHub/3DuF/src/app/featureSets/featureSet.js
Error: Can't walk dependency graph: Cannot find module '../library/sorter' from '/Users/krishna/Documents/GitHub/3DuF/src/app/featureSets/featureSet.js'
    required by /Users/krishna/Documents/GitHub/3DuF/src/app/featureSets/featureSet.js
Error: Can't walk dependency graph: Cannot find module '../library/splitter' from '/Users/krishna/Documents/GitHub/3DuF/src/app/featureSets/featureSet.js'
    required by /Users/krishna/Documents/GitHub/3DuF/src/app/featureSets/featureSet.js

On compile, it gets the following errors. This is because the pull request has changes with references from different updates. I'm going to close the pull request. @ryu-bu just do 1 big pull request with all the changes.
npm run watch_compile

><EMAIL_ADDRESS>watch_compile /Users/krishna/Documents/GitHub/3DuF
> watchify ./src/app/appSetup.js -t babelify -v --outfile ./3DuFapp.js -d -t [ babelify ]

Browserslist: caniuse-lite is outdated. Please run next command `npm update caniuse-lite browserslist`
Error: Can't walk dependency graph: Cannot find module '../library/filter' from '/Users/krishna/Documents/GitHub/3DuF/src/app/featureSets/featureSet.js'
    required by /Users/krishna/Documents/GitHub/3DuF/src/app/featureSets/featureSet.js
Error: Can't walk dependency graph: Cannot find module '../library/celltrapS' from '/Users/krishna/Documents/GitHub/3DuF/src/app/featureSets/featureSet.js'
    required by /Users/krishna/Documents/GitHub/3DuF/src/app/featureSets/featureSet.js
Error: Can't walk dependency graph: Cannot find module '../library/chemostatring' from '/Users/krishna/Documents/GitHub/3DuF/src/app/featureSets/featureSet.js'
    required by /Users/krishna/Documents/GitHub/3DuF/src/app/featureSets/featureSet.js
Error: Can't walk dependency graph: Cannot find module '../library/merger' from '/Users/krishna/Documents/GitHub/3DuF/src/app/featureSets/featureSet.js'
    required by /Users/krishna/Documents/GitHub/3DuF/src/app/featureSets/featureSet.js
Error: Can't walk dependency graph: Cannot find module '../library/incubation' from '/Users/krishna/Documents/GitHub/3DuF/src/app/featureSets/featureSet.js'
    required by /Users/krishna/Documents/GitHub/3DuF/src/app/featureSets/featureSet.js
Error: Can't walk dependency graph: Cannot find module '../library/sorter' from '/Users/krishna/Documents/GitHub/3DuF/src/app/featureSets/featureSet.js'
    required by /Users/krishna/Documents/GitHub/3DuF/src/app/featureSets/featureSet.js
Error: Can't walk dependency graph: Cannot find module '../library/splitter' from '/Users/krishna/Documents/GitHub/3DuF/src/app/featureSets/featureSet.js'
    required by /Users/krishna/Documents/GitHub/3DuF/src/app/featureSets/featureSet.js


Fix incorrect attack style resetting while meleeing

This double checks that the gorilla is using magic or ranged when the animation for the boulder fires.
I think when they changed demonic gorillas in may, they also made them randomly use the AOE_ATTACK animation, even while attacking with melee. They also added a overhead text to them, which triggers occasionally, but doesn't have anything to do with the attack styles as far as I can tell.

After checking the wiki, when they say "Rhaaaaa", they change attack styles, so i'm adding a check for that when checking pending attacks.


update readme.md

Related Issues or bug

Info about Issue or bug

Fixes: #[issue number that will be closed through this PR]
Proposed Changes

Info about changes Goes here

Additional Info

Anything related Issues

Screenshots

Original
Updated

original screenshot
**updated screenshot **

Which readme you have changed, in issue i asked the awesome face operations readme, the folder

I mentioned the link too

Sorry I thought it was about original readme.md, I will update that till tommorow

No problem it's ok i will review this pr too and will assign point according to the sceme


check for both str and Path when executing a prompt

Could also use os.PathLike, which feels more correct but would require another import

Addresses #157


Gecco-Torch fails on "Sanity Checking Dataloader"

Hi,
Trying to run the torch version I get the following error. Have you ever seen that before? It seems like it's not even on the code-base but rather some pytorch-lightning internals.
I installed by creating a conda environment with python >3.10 and then pip install -e ./
I have changed nothing in the code.
$ python shapenet_airplane_unconditional.py

Using 16bit Automatic Mixed Precision (AMP)
GPU available: True (cuda), used: True
TPU available: False, using: 0 TPU cores
IPU available: False, using: 0 IPUs
HPU available: False, using: 0 HPUs
LOCAL_RANK: 0 - CUDA_VISIBLE_DEVICES: [0]

  | Name        | Type            | Params
------------------------------------------------
0 | backbone    | EDMPrecond      | 13.5 M
1 | conditioner | IdleConditioner | 0
2 | loss        | EDMLoss         | 0
3 | reparam     | GaussianReparam | 0
------------------------------------------------
13.5 M    Trainable params
0         Non-trainable params
13.5 M    Total params
53.924    Total estimated model params size (MB)
Sanity Checking DataLoader 0:   0%|                                                                                | 0/2 [00:00<?, ?it/s]Traceback (most recent call last):
  File "/data/graphdeco/user/gkopanas/point_diffusion/gecco/gecco-torch/example_configs/shapenet_airplane_unconditional.py", line 82, in <module>
    trainer().fit(model, data)
  File "/home/gkopanas/.conda/envs/pvd_gecco/lib/python3.10/site-packages/lightning/pytorch/trainer/trainer.py", line 545, in fit
    call._call_and_handle_interrupt(
  File "/home/gkopanas/.conda/envs/pvd_gecco/lib/python3.10/site-packages/lightning/pytorch/trainer/call.py", line 44, in _call_and_handle_interrupt
    return trainer_fn(*args, **kwargs)
  File "/home/gkopanas/.conda/envs/pvd_gecco/lib/python3.10/site-packages/lightning/pytorch/trainer/trainer.py", line 581, in _fit_impl
    self._run(model, ckpt_path=ckpt_path)
  File "/home/gkopanas/.conda/envs/pvd_gecco/lib/python3.10/site-packages/lightning/pytorch/trainer/trainer.py", line 990, in _run
    results = self._run_stage()
  File "/home/gkopanas/.conda/envs/pvd_gecco/lib/python3.10/site-packages/lightning/pytorch/trainer/trainer.py", line 1034, in _run_stage
    self._run_sanity_check()
  File "/home/gkopanas/.conda/envs/pvd_gecco/lib/python3.10/site-packages/lightning/pytorch/trainer/trainer.py", line 1063, in _run_sanity_check
    val_loop.run()
  File "/home/gkopanas/.conda/envs/pvd_gecco/lib/python3.10/site-packages/lightning/pytorch/loops/utilities.py", line 181, in _decorator
    return loop_run(self, *args, **kwargs)
  File "/home/gkopanas/.conda/envs/pvd_gecco/lib/python3.10/site-packages/lightning/pytorch/loops/evaluation_loop.py", line 134, in run
    self._evaluation_step(batch, batch_idx, dataloader_idx, dataloader_iter)
  File "/home/gkopanas/.conda/envs/pvd_gecco/lib/python3.10/site-packages/lightning/pytorch/loops/evaluation_loop.py", line 391, in _evaluation_step
    output = call._call_strategy_hook(trainer, hook_name, *step_args)
  File "/home/gkopanas/.conda/envs/pvd_gecco/lib/python3.10/site-packages/lightning/pytorch/trainer/call.py", line 309, in _call_strategy_hook
    output = fn(*args, **kwargs)
  File "/home/gkopanas/.conda/envs/pvd_gecco/lib/python3.10/site-packages/lightning/pytorch/strategies/strategy.py", line 403, in validation_step
    return self.lightning_module.validation_step(*args, **kwargs)
  File "/home/gkopanas/.conda/envs/pvd_gecco/lib/python3.10/site-packages/torch/_dynamo/eval_frame.py", line 328, in _fn
    return fn(*args, **kwargs)
  File "/home/gkopanas/.conda/envs/pvd_gecco/lib/python3.10/site-packages/torch/_dynamo/eval_frame.py", line 490, in catch_errors
    return callback(frame, cache_entry, hooks, frame_state)
  File "/home/gkopanas/.conda/envs/pvd_gecco/lib/python3.10/site-packages/torch/_dynamo/convert_frame.py", line 641, in _convert_frame
    result = inner_convert(frame, cache_size, hooks, frame_state)
  File "/home/gkopanas/.conda/envs/pvd_gecco/lib/python3.10/site-packages/torch/_dynamo/convert_frame.py", line 133, in _fn
    return fn(*args, **kwargs)
  File "/home/gkopanas/.conda/envs/pvd_gecco/lib/python3.10/site-packages/torch/_dynamo/convert_frame.py", line 389, in _convert_frame_assert
    return _compile(
  File "/home/gkopanas/.conda/envs/pvd_gecco/lib/python3.10/site-packages/torch/_dynamo/convert_frame.py", line 586, in _compile
    raise InternalTorchDynamoError(str(e)).with_traceback(
  File "/home/gkopanas/.conda/envs/pvd_gecco/lib/python3.10/site-packages/torch/_dynamo/convert_frame.py", line 569, in _compile
    guarded_code = compile_inner(code, one_graph, hooks, transform)
  File "/home/gkopanas/.conda/envs/pvd_gecco/lib/python3.10/site-packages/torch/_dynamo/utils.py", line 189, in time_wrapper
    r = func(*args, **kwargs)
  File "/home/gkopanas/.conda/envs/pvd_gecco/lib/python3.10/site-packages/torch/_dynamo/convert_frame.py", line 549, in compile_inner
    check_fn = CheckFunctionManager(
  File "/home/gkopanas/.conda/envs/pvd_gecco/lib/python3.10/site-packages/torch/_dynamo/guards.py", line 929, in __init__
    guard.create(local_builder, global_builder)
  File "/home/gkopanas/.conda/envs/pvd_gecco/lib/python3.10/site-packages/torch/_guards.py", line 243, in create
    return self.create_fn(self.source.select(local_builder, global_builder), self)
  File "/home/gkopanas/.conda/envs/pvd_gecco/lib/python3.10/site-packages/torch/_dynamo/guards.py", line 404, in CONSTANT_MATCH
    val = self.get(guard.name)
  File "/home/gkopanas/.conda/envs/pvd_gecco/lib/python3.10/site-packages/torch/_dynamo/guards.py", line 234, in get
    return eval(name, self.scope, CLOSURE_VARS)
  File "<string>", line 1, in <module>
torch._dynamo.exc.InternalTorchDynamoError: 'NoneType' object is not subscriptable

You can suppress this exception and fall back to eager by setting:
    import torch._dynamo
    torch._dynamo.config.suppress_errors = True

I tried it in a completely different setup, different cluster/hardware and got the same error.

I see, can you provide the output of pip freeze (with this env activated)? It could be that you're on a differnet version of pytorch and it doesn't work for some reason. I did my development on 2.0.1. I'll dump my pip freeze on Monday so we can look for differences.

Thank you for suggesting this, torch 2.0.1 helped but it also needed to pip install tensorboard - should be added in the env setup.

Does this make the code work overall? I'll try to fix this is an update rather than pinning old dependencies

As far as I can tell the code works fine with 2.0.1


Add ban feature on non-super groups

You can only ban users in supergroups, as of now. It should be emulated in non-super groups, by just kicking the user when it enters.

It looks like this was already fixed sometime. Closing.


Added another Java implementation

Differences to the first Java Implementations:

Added JavaDoc
Only one class
Better code structure
Better testing

@ayan-b Done. Is everything else ok?


Add a development webserver

Use http.server.ThreadingHTTPServer to offer a built-in webserver so something extra like nginx isn't needed for testing.

[x] Directly runnable server with configurable directory and port
[x] Automatic index support
[x] Automatic mime type detection
[x] Option to run from anchovy cli post-build
[x] Automatically detect root directory from anchovy settings
[x] Etag support
[ ] Some sort of way to configure port through anchovy config file?
[ ] Add some tests

Port configuration is deferred to #80.


[docs] Migrating to Sass for stylesheets.

Migrating to Sass for docs as well to unify the workflow.
Related: glfw/website#70
Follow up to : glfw/website#71 and glfw/glfw#1757

Since this seems to be done mostly for variables, may I suggest using CSS custom properties instead? They don’t require any compilation step, and make it easier to change them at runtime (for instance for a dark theme, if we ever get one in the future).

I still rather to keep sass/less in my toolchain for stuff like mixins,
etc; they come in handy 😋
In other words sass/less and css vars can coexist and complement each other.
On Thu, Sep 3, 2020, 5:25 PM linkmauve<EMAIL_ADDRESS>wrote:

Since this seems to be done mostly for variables, may I suggest using CSS
custom properties https://developer.mozilla.org/en-US/docs/Web/CSS/--*
instead? They don’t require any compilation step, and make it easier to
change them at runtime (for instance for a dark theme, if we ever get one
in the future).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/glfw/glfw/pull/1759#issuecomment-686469569, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIGT2SJOUGU3ZL27VLOX43SD6G4DANCNFSM4QUW4PWQ
.

I see no problem with that! :D

Merged, thank you!


PhoneNumberMetadata is out of date

Hi all,
We noticed PhoneNumberMetadata to be out of date for Mexican numbers. We updated a fork with the Mexican metadata, but we'd love to help maintain this library.
Happy to open a PR. Should we update just the mexican data (like we did in our fork) or the entire file? Does the community have a preference?

@josemrb is now working on an update to the last release of the v8.10.x series which makes the metadata up to date https://github.com/socialpaymentsbv/ex_phone_number/pull/33#issuecomment-565619362. Then he plans to release an update to v8.11 and v8.12 are more involved. In light of this I would wait for his work and not do a partial update for the Mexican numbers. Please stay tuned.


Proposal for improvements to releases and image tagging

Here's my proposal for the changes to releases / image tagging.
Release schedule
We should tag a release soon (as v3.2), and come up with a schedule for having a regularly tagged release (I propose every 3 months), we haven't had a tagged release in 6 months.
In concern with this, we'll also update the images/multus-daemonset.yaml to point at the newly tagged release, e.g.
image: nfvpe/multus:v3.2

Improved image tagging
I propose that we tag a :latest image with each merge into master, this will make for a more intuitive use of the :latest tag. Previously, we only tagged :latest with each tagged release, and we would tag :snapshot with each merge into master (e.g. the :snapshot tagged image was equivalent to tip of master)
On the tagging of each release, we'll tag an image with the version, e.g. vX.Y (as we currently do) but, we'll also tag this image as :stable.

@dougbtv it will be nice to have also a Z stream for some important cherry picks like bugs and security issues.


Panick when using relative pathname

Using Anchor v0.5.5 (precompiled binary) on Ubuntu 20.04.
Doing
echo Test > f
ambs -r -- 'Test' f

results in
thread 'finder' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 2, kind: NotFound, message: "No such file or directory" }', src/pipeline_finder.rs:133:42
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

The behaviour is the same with ambr.
Invoking both programs with ./f instead of f works fine.

Thanks! I fixed it, and released v0.5.7.

Great, thanks !


Cu 8697359pc deploy node js project to aws elastic beanstalk dmitry morozov

Added new ci/cd

Task linked: CU-8697359pc Deploy node js project to AWS AWS Elastic Beanstalk


Move target_content_types lookup into its own method

...to prevent a database query being generated on app load
Fixes #1673

This breaks several tests due to target_content_types not being fully eliminated. Closing in favour of #1681


Bump axios from 0.7.0 to 0.19.0

Closes #75
When axios went from version 12 to 13 they changed error handling.
https://github.com/axios/axios/blob/master/UPGRADE_GUIDE.md#error-handling
Axios used to return a response object rather than an Error object. To maintain the test cases and maintain existing request handlers; I'm just pulling the response out of the Error object and passing it on.

Closes #75, finishes #68
Related to https://github.com/StackStorm/hubot-stackstorm/issues/197
This is awesome, thank you very much for the fix! :+1:


Hi  covid-19 website made using your api

Hello, I am made a covid-19  dashboard using covid19india.org
Here is the link  of dashboard made by me
https://web2.eu5.org/

Nice! :) If you want us to include this in our list, please head over to https://github.com/covid19india/api and raise a PR adding your website in the list.


project POD_NAME into the deployments for logging purpose

Fixes #166 .

/lgtm
/approve

/lgtm
/approve


Fix: Support NewTerminal & Detached mode (nerdctl -t -d ...)

Support NewTerminal & Detached mode(nerdctl -t -d ...)
# 1
nerdctal run -t -d ...

# 2
nerdctl create -t ...
nerdctl start

# 3
nerdctl create -t ...
nerdctl start -a ...

Signed-off-by: yaozhenxiu<EMAIL_ADDRESS>

Thanks, but how to test?

Thanks, but how to test?

This requires building a container that only works properly with -t -d modes
I have tested it locally, and I will add some integration test

@AkihiroSuda PTAL

@fahedouch @djdongjin PTAL

Let me merge https://github.com/containerd/nerdctl/pull/1639 before this, sorry


chat notifications when other ppl write and chat is minimized

https://github.com/sopra-fs23-group-13/meme-it-client/pull/94


Changed CSS rules back to English

Also, use back-ticks for code block and added indentation

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@devbysalas Thanks for catching the errors. LGTM!


Cross AZ / Cross Region Deployments

Description
As an operator of validator nodes I want to be able to invite other organizations to join my private cluster so that we can make our resources work together.
For example
Company A wants to build a public BIF deployment to back a paid service where people can transfer assets between 2 different networks.
Business is booming and soon Company A leadership decides that they want to partner with Company B so that they share the cost of running the infrastructure and double the marketing reach through their combined brands.
They issue a fancy press release announcing the partnership, shake hands and then give the problem of figuring out the rest to the engineering department who soon realizes that the data centers of Company B are on a different continent and moving their infrastructure is (of course) not an option.
So, they have to make it so that a cluster of BIF validator nodes are working together in a productive fashion even though the latency between them can be > 200ms at times which is a challenge when you have a leader election algorithm (Etcd/Raft) that is sensitive to latency.
Acceptance Criteria

Verify that we are able to tune Etcd so that cross AZ/R deployments are operational. Start here: https://github.com/etcd-io/etcd/blob/master/Documentation/tuning.md
If Etcd doesn't work, document very thoroughly what tests were done and what were the exact results based on which the conclusions were drawn.
Look into CockroachDB for inspiration on how they solve the exact same challenge in the context of their software. Document the learnings from there and include it in the architectural documentation of BIF regardless of what decision is made in the end of the story.

Fixed by #123 (We no longer use or depend on etcd)


Update to ethereumjs-util@6

This PR updates the direct ethereumjs-util dependency to v6, which includes TypeScript definitions. There are no relevant breaking changes to GABA's direct usage:[1]

[BREAKING] Fixed signature to comply with Geth and Parity in toRpcSig() changing
v from 0/1 to 27/28, this changes the resulting signature buffer, see PR #139
[BREAKING] Remove deprecated sha3-named constants and methods (see v5.2.0 release),
see PR #154

I've changed the places where ethereumjs-util are being require'd to use TypeScript imports where possible (minus BN whose types don't match the usages and #141).

Codecov Report

Merging #142 into develop will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           develop   #142   +/-   ##
======================================
  Coverage      100%   100%
======================================
  Files           21     21
  Lines         1426   1428    +2
  Branches       191    191
======================================
+ Hits          1426   1428    +2

Impacted Files
Coverage Δ

src/user/PreferencesController.ts
100% <100%> (ø)
:arrow_up:

src/transaction/TransactionController.ts
100% <100%> (ø)
:arrow_up:

src/keyring/KeyringController.ts
100% <100%> (ø)
:arrow_up:

src/assets/TokenRatesController.ts
100% <100%> (ø)
:arrow_up:

src/util.ts
100% <100%> (ø)
:arrow_up:

src/assets/AssetsController.ts
100% <100%> (ø)
:arrow_up:

src/assets/AssetsDetectionController.ts
100% <100%> (ø)
:arrow_up:

src/user/AddressBookController.ts
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Published get BadImageFormatException after upgrade to dot net core 1.1

It works fine on my developer machine but not when I published to IIS

Windows Server 2012 R2 x64
I can't find dot net core 1.1 Windows Server Hosting runtime, I install Windows x64 runtime
https://www.microsoft.com/net/download/core
app.UseResponseCaching();
app.UseMvc(routes =>
{

});
app.UseCookieAuthentication(new CookieAuthenticationOptions()
{

}

Between these 3 middle ware is the cause of BadImageFormatException

The problem on UseMvc, is it because I install wrong runtime?

cc @muratg regarding the server hosting installer for Windows.

@andrew-vandenbrink You can install Windows Server Hosting bundle from this link: https://aka.ms/dotnetcore_windowshosting_1_1_0.
(We'll get the downloads page updated with this link as well)

@andrew-vandenbrink once you install the 1.1.0 bundle, can you let us know if you still have the issue? If so, can you upload your project to GitHub so we can take a look? And let us know which version of dotnet you're using? (Run dotnet --version from the command line.)

The stack trace is coming from the ViewsFeatureProvider: https://github.com/aspnet/Mvc/blob/dev/src/Microsoft.AspNetCore.Mvc.Razor/Compilation/ViewsFeatureProvider.cs#L74. Do you have an assembly named AppName.PrecompiledViews.dll in your application graph?
That said, we should possibly ignore more kinds of exceptions here: https://github.com/aspnet/Mvc/blob/dev/src/Microsoft.AspNetCore.Mvc.Razor/Compilation/ViewsFeatureProvider.cs#L76. Clearly FileLoadException isn't sufficient.

@Eilon @muratg I will get back as soon as I have access to my vm... (14 hours++ from now...)
@pranavkm I do have

Are you using Razor view compilation? It's odd that it's 0-byte binary.

I still have same issue after installing Windows Server Hosting.
I delete that 0-byte binary and it works!
I still have issue with razor precompile https://github.com/aspnet/Mvc/issues/5546
If it fails to compile, don't generate x.PrecompiledViews.dll
but the issue still BadImageFormatException? which means even if its successfully compiled, I still get issue.

@andrew-vandenbrink I filed a bug here - https://github.com/aspnet/MvcPrecompilation/issues/35 - to track the issue with 0-byte file.
The tool returns a non-zero exit code, however, https://github.com/dotnet/cli/issues/2836 prevents it from doing anything pertinent with it. Perhaps you could look at wrapping the tool execution and deleting the precompiled file on a non-zero exit code. I admit it's not ideal, but it should prevent you from having to look at the logs to discover a build failure.

Thanks I will close this issue


Consider adding a template for "cover letter for clerk" that works like the Next Steps document

This document would be for printing, not e-filing.
It will mostly just say something like:
Dear clerk of trial_court:
Attached for filing please find the [DEFENDANT]'s [LIST OF FORMS].
Please schedule for hearing at your earliest convenience.
Yours,
[USERS]

Most forms could use a cover letter directed at the recipient. The reason to allow customizing it is for:

Documents that are not court forms but still need a cover letter
Court forms with specialized instructions for the clerk, such as scheduling.

This is a pretty trivial change. But I don't know if a cover page will apply to most forms that can be e-filed.

N/A as email filing isn't a goal of this project anymore.


CDH 5.13.1 release

This will be merged into a new release branch: cdh-513. CDH 5.13.1 is not yet productionised in Omnia and won't be for a few months.
Upgrades libraries to CDH 5.13.1, as per:

https://archive.cloudera.com/cdh5/cdh/5/hadoop/hadoop-project-dist/hadoop-common/dependency-analysis.html
https://www.cloudera.com/documentation/enterprise/release-notes/topics/cm_vd_cdh_package_tarball_513.html

I guess we can make this a release branch by setting $RELEASE_BRANCHES in .travis.yml, right?

@toddmowen The rationale for not merging to master is that anyone following standard practice and bumping to latest version may find that their job doesn't run on CDH 5.3, which is the only version currently on DS and Scoring.
The transition plan is to keep CDH 5.3 as our general production version until CDH 5.13 is added to Scoring.  Note that both 5.3 and 5.13 will be available at this point.  Until then, the 5.13 branch is just for testing.
But, I guess we could just give guidance to not bump versions beyond a particular point until CDH 5.13 is available.  It would avoid the branching through our ecosystem and instead we could just do it where a specific need arises.  Anyone else want to weigh in here?  @andynygard @jdcba

Thinking a bit more about the two options (long-lived branch vs version bump), neither is obviously superior. They both require care to distinguish the two lines of development; in the version bump case it would involve knowing not just the version of uniform which introduced CDH 5.13, but also the versions for all the other core repos in which the change was made (thermometer 1.6, ebenezer 0.24, etc). Though for end users, etl.util should hide all that confusion.
The main difference seems to be that the long-lived branch strategy makes maintaining the CDH 5.3 line more convenient, whereas the version bump strategy makes developing the CDH 5.13 line more convenient (e.g. autowranger would just work) at the cost of extra burden for people using the CDH 5.3 line.
Based on the discussion so far, I think the long-lived branch strategy that @andynygard has adopted is indeed the better choice, since most jobs will still be using the CDH 5.3 line for quite some time.
However asking people to build the whole stack locally if they want to use the CDH 5.13 line seems like it would lead to unnecessary drudgery. Better to get Travis CI to publish the artifacts (with a branch suffix attached).

Yeah it's unfortunate we would have to maintain the branch for so long, as it's so tedious to keep the two branches in sync. It won't be until march some time that we have 5.13 deployed in scoring though, so we thought to branch it in case some new changes are required on the 5.3 environment.
For the local builds, yep definitely want to make them automated through travis. I just don't have github permissions to modify all the builds, nor do I have artifactory permissions to add a new mirror (for some new things that hive-1.1.0 pulls in).
@toddmowen Are you working over the break? Do you happen to have admin rights on those? :)


how the vuejs compiler works

What problem does this feature
Hello i want to know how the vuejs compiler works
Step by step
Thanks

Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the forum, the Discord server or StackOverflow.


RFC: Best Practices re OPENMP - for training, evaluation and recognition

For Tesseract 5 what are the best practices regarding OPENMP.
Is it still true:

OPENMP is needed for training so build tesseract and training tools with --enable-openmp.
For lstmeval (built with --enable-openmp), use OMP_THREAD_LIMIT=1.
For recognition with tesseract (built with --enable-openmp), use OMP_THREAD_LIMIT=1.

OPENMP is not needed for training. It even makes thinks worse for me. Timing results for lstm_squashed_test on AMD EPYC 7502 show that no OPENMP is best, followed by disabled OPENMP. Enabled OPENMP is the last and burns a lot of CPU performance for nothing:
# --disable-openmp
real 28.41
user 28.33
sys 0.08
# --enable-openmp
real 33.16
user 129.41
sys 1.46
# --enable-openmp, OMP_THREAD_LIMIT=1
real 32.89
user 32.61
sys 0.28

The plan is to disable it by default in 5.1.0.

... in autoconf builds. cmake already disables it b default.

Note that even without OPENMP training uses up to two CPU threads, one for training which runs until training is finished and one for evaluation which runs from time to time during the training process.

The reason for disabling OpenMP is that the Tesseract currently use it inefficiently.
For text recognition the speed benefit for using OpenMP wijh fast / tessdata (best->int) traineddata is too small while it consumes too much CPU resources.
For training the OpenMP code is even more problematic than the code used for text recognition. I'm not sure how much speed will be lost here.

Thank you!

no OPENMP is best, followed by disabled OPENMP

Does no OPENMP mean building with --disable-openmp as part of autotools configure?

Yes, currently it is necessary to use configure --disable-openmp. As Amit has written above that should be the default, but I still have no simple code to achieve that.

--disable-openmp disables OpenMP at compile time, while OMP_THREAD_LIMIT=1 disables it in runtime. The first method is more efficient, while the second method is more flexible.

Stefan, for 5.1.0, do you want to keep a way to enable OpenMP with --enable-openmp?

OPENMP is not needed for training. It even makes things worse for me. Timing results for lstm_squashed_test on AMD EPYC 7502 show that no OPENMP (--disable-openmp) is best, followed by disabled OPENMP (OMP_THREAD_LIMIT=1). Enabled OPENMP is the last and burns a lot of CPU performance for nothing:

Ok. I will try to test training from font scenarios in my tess5train-fonts to see if they get similar results.

lstmeval
Which time figures (real, user. sys) are important? Which scenario is preferable?
no OPENMP (--disable-openmp)
time -p lstmeval  \
	--verbosity=0 \
	--model data/engFineTuned/tessdata_fast/engFineTuned_0.631000_121_600.traineddata \
	--eval_listfile data/engFineTuned/list.eval 2>&1 | grep "^BCER eval" > data/engFineTuned/tessdata_fast/engFineTuned_0.631000_121_600.eval.log
real 805.37
user 805.34
sys 0.03
time -p lstmeval  \
	--verbosity=0 \
	--model data/engFineTuned/tessdata_fast/engFineTuned_0.028000_156_2000.traineddata \
	--eval_listfile data/engFineTuned/list.eval 2>&1 | grep "^BCER eval" > data/engFineTuned/tessdata_fast/engFineTuned_0.028000_156_2000.eval.log
real 806.56
user 806.49
sys 0.07
time -p lstmeval  \
	--verbosity=0 \
	--model data/engFineTuned/tessdata_fast/engFineTuned_0.558000_125_700.traineddata \
	--eval_listfile data/engFineTuned/list.eval 2>&1 | grep "^BCER eval" > data/engFineTuned/tessdata_fast/engFineTuned_0.558000_125_700.eval.log
real 806.10
user 806.04
sys 0.07

Enabled OPENMP
time -p lstmeval  \
	--verbosity=0 \
	--model data/engFineTuned/tessdata_fast/engFineTuned_0.645000_119_600.traineddata \
	--eval_listfile data/engFineTuned/list.eval 2>&1 | grep "^BCER eval" > data/engFineTuned/tessdata_fast/engFineTuned_0.645000_119_600.eval.log
real 331.53
user 1041.90
sys 9.02
time -p lstmeval  \
	--verbosity=0 \
	--model data/engFineTuned/tessdata_fast/engFineTuned_0.119000_156_1500.traineddata \
	--eval_listfile data/engFineTuned/list.eval 2>&1 | grep "^BCER eval" > data/engFineTuned/tessdata_fast/engFineTuned_0.119000_156_1500.eval.log
real 331.30
user 1042.38
sys 8.55
time -p lstmeval  \
	--verbosity=0 \
	--model data/engFineTuned/tessdata_fast/engFineTuned_0.014000_165_2500.traineddata \
	--eval_listfile data/engFineTuned/list.eval 2>&1 | grep "^BCER eval" > data/engFineTuned/tessdata_fast/engFineTuned_0.014000_165_2500.eval.log
real 331.70
user 1042.77
sys 8.97

lstmeval - engImpact
No OPENMP
time -p lstmeval  \
	--verbosity=0 \
	--model data/engImpact/tessdata_fast/engImpact_0.489000_152_900.traineddata \
	--eval_listfile data/engImpact/list.eval 2>&1 | grep "^BCER eval" > data/engImpact/tessdata_fast/engImpact_0.489000_152_900.eval.log
real 19.85
user 19.82
sys 0.04

OPENMP
time -p lstmeval  \
	--verbosity=0 \
	--model data/engImpact/tessdata_fast/engImpact_0.489000_152_900.traineddata \
	--eval_listfile data/engImpact/list.eval 2>&1 | grep "^BCER eval" > data/engImpact/tessdata_fast/engImpact_0.489000_152_900.eval.log
real 8.25
user 25.87
sys 0.27

Which time figures (real, user. sys) are important? Which scenario is preferable?

In your test scenario lstmeval was much faster with OPENMP enabled ("real" is 331 s instead of 805 s), so you'd prefer that to get a result fast. The CPU resources where slightly more with OPENMP ("user" 1042 s and "sys" 9 s instead of 805 s / 0.05 s), so the faster execution costs some (acceptable) overhead in this case.

for 5.1.0, do you want to keep a way to enable OpenMP with --enable-openmp?

Yes, I think that's necessary because of compatibility and also because it can be useful as in @Shreeshrii's test case on ARM.

Running Tesseract with several threads seems to work better on ARM than on Intel architectures. I noticed that with Apple M1 (AARCH64), too.

Running Tesseract with several threads seems to work better on ARM than on Intel architectures. I noticed that with Apple M1 (AARCH64), too.

I am running this on AARCH64.

Also, my tests  shows that the enabled OPENMP could make sense in some cases (e.g. for the best data model on Windows & MSVC2019 and Intel processor) It would be great if we found somebody familiar with OpenMP at least for review how tesseract use it...

My timings for OpenMP on Windows MSVC at the end of issue 3044.

Thanks, @tdhintz
It would be good to know if the results still hold.  If possible, please rerun tests with the tesseract 5 released version or latest GitHub version, since there have been many changes since 2020.

@Shreeshrii I'll add that task to our plan for late March.  We build with very specific settings to get best results and I'm sure the build process has changed again, so this will be a heavy lift.

Looks like someone did this already: OpenMP benchmark

Looks like someone did this already: OpenMP benchmark

That test by @zdenop uses one image 15 times. Your tests use many more combinations.

We ran a comparison between a pre-release of 4.0 and the current 5.0 on AVX2 and SSE hardware on Windows that I'll share just for grins. The 4.0 was built with floating point set to fast, COMDAT folding, OpenMP and was PGO optimized. The 5.0 build also used floating point 'fast' and COMDAT folding, but without OpenMP and without PGO optimization.
2,880 combinations of settings and images were tested for each AVX2 and SSE platform. The tests are by no means comprehensive of all possible combinations. For example, only Eng traindata was used, although the Fast, Best and Blended data were all used.

this will be a heavy lift.

I understand.
If possible to do, the results can be added to tessdoc for easy reference. Thanks.


.NET Standard 2.1 Support

Please update the library to support .NET Standard 2.1.
Thank you so much.

.netstandard2.0 libraries can be dependencies of 2.1 libraries and are guaranteed to work on pretty much every conceivable platform & runtime you can imagine - so what would be the point of just adding another target framework?

I encountered a problem before I thought it was related to this problem. Then later I tested and it's working with the 2.1. I will be closing this now thank you for the reply @LordZoltan.


Fixes typo in line chart demo

Description
I noticed a typo on the line chart demo page while playing with the examples, which caused a few seconds of confusion. I just though I might as well fix it 😃.
Motivation and Context
This patch is just to make the examples more consistent and to avoid confusion when new users copy and paste the shown demo code.
How Has This Been Tested?
I didn’t perform any testing, as this is just a typo in an HTML page. I hope this is fine with you.
Screenshots (if appropriate):

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Thanks @pluehne !!


Cherry pick 0.x to main

Fixes #1088.

:warning: please review b35f22cfb7534977a978e63202a4ba0b51c70aa4 in more depth to make sure I didn't do something wrong during conflict resolution.


Support providing top-level elements as symbols

Partially resolves #751
It only provides top-level symbols (datasource, generator, model, enum and type), the main usage is to get sticky scroll working:

All supported symbols and their corresponding icons in Outline view:

This PR also changes "Go To Definition" to highlight only the type name, like what TypeScript language server does.
A simple test was added againest the existing hover.prisma fixture file.
Providing fields requires much more time to do refactoring, which I don't have now.

 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.

The symbols are
     model: SymbolKind.Class,
      enum: SymbolKind.Enum,
      type: SymbolKind.Interface,
      datasource: SymbolKind.Struct,
      generator: SymbolKind.Function,

I assume you picked a different symbol for datasource & generator so they are represented differently, which helps if you have multiple generators for example.

YESSSSSSS

You make my life so much easier, thanks @Jolg42 and @yume-chan


Added Serena Chen

What a lovely idea.  Added you in here c6a66a35eaa8ec49ecdf11f91ab16d2f9e25e740


[Bug]:  Global search on root resources throws exception

What happened?
Using global search on a root resource throws an error.
How to reproduce the bug
Configure a column to be globally searchable on the root resource.  Then search for a record in that resource.
Package Version
1.0.0-alpha.6
PHP Version
^8.1
Laravel Version
^10
Which operating systems does with happen with?
No response
Notes
I'm not sure if this is a user error or not.  When I set up my root resource I didn't override the getAncestors method; it still returns null. So, when the getGlobalSearchResultUrl method is called on the NestedResource and it tries to search through its ancestors for their ids things blow up.

Hi! Thanks a lot, It's fixed in the new release!

@lukas-frey any reason why you default to the edit views instead of the view pages?

@lukas-frey any reason why you default to the edit views instead of the view pages?

Just made more sense to me. When you don't have permission for the edit page, it goes to the view page.
For example, if you have 2 roles: Admin and User, where Admin has permission to view and edit, while user only has permission to view, it made more sense to me that the admin should default to edit (since that's probably what he's most working with) and the user defaulting to view.


RemoteTransform3D applies incorrect rotation when Update Scale is disabled

Tested versions
Reproducible in 4.3.stable, 4.4.dev2
System information
Godot v4.3.stable - Windows 10.0.22631 - GLES3 (Compatibility) - NVIDIA GeForce GTX 1660 SUPER (NVIDIA; <IP_ADDRESS>09) - Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz (16 Threads)
Issue description
RemoteTransform3D applies incorrect rotation to the remote object when Update Scale is disabled and the remote object is under a rotated parent. When Update Scale is enabled, or when the remote object has a parent with neutral transform or no parent at all, everything works as expected.

Steps to reproduce

Open test.tscn in attached project
Rotate the remote_transform_3d object around the X or Z axis
Observe that the green cube does not rotate correctly

Minimal reproduction project (MRP)
bug-report.zip

Do you remember when this last worked?

Do you remember when this last worked?

No idea if it ever did work, but I can confirm it does NOT work in 4.2.stable.

Created a PR to fix this issue.


need a way to retrieve event hub message headers

For eventHubTrigger, is there a way to get the event hub message headers? Currently only the message payload is provided – while there are a lot of useful information from the headers I wish to retrieve.
Also, it'll be very helpful if there is an example of how to properly handle error - for example, if exception happened while trying to process the event, instead of removing the event from the service bus, leave it and have a chance to retry. This would require access to the retry count, lease time, etc.

In the case of C# functions, you can bind to the raw SB messaging EventData Type as described in the wiki here. I assume EventData has all the information on an event you would require.

NodeJS, however I will also be interested to know if there is a C# example.

@reyang -

"if exception happened while trying to process the event, instead of removing the event from the service bus, leave it and have a chance to retry. "  Eventhub is a high throughput system; to keep up with the volume, we receive the events in a batch and checkpoint the entire batch. We don't have support for granular checkpointing. Is this essential for your scenarios?

We can promote some of the properties directly to the "binding data" so that it can be accessible from other languages. We already do this for PartitionContext.
When you refer to "headers", which properties on EventData / PartitionContext exactly are you interested in accessing?

@MikeStall to answer your 2nd question, we want to access EventData.SystemProperties. Property keys we want to access are:

iothub-connection-device-id
iothub-connection-auth-method
iothub-connection-auth-generation-id

And I think people might also would like to access EventData.Properties for custom properties in their event data. Although we don't have such requirement yet, it is giving more flexibility to user when dealing with complicated scenarios.

We also need to add the ability for people to set EventData properties like PartitionKey etc. for output bindings. Currently for languages like Node.js.

Addressed via https://github.com/Azure/azure-webjobs-sdk-script/pull/1337. You can now access all the EventData properties via context.bindingData.

See wiki page here for more info: https://github.com/Azure/azure-webjobs-sdk-script/wiki/Trigger-Binding-Data

Great, thank you! 👍

See wiki page here for more info: https://github.com/Azure/azure-webjobs-sdk-script/wiki/Trigger-Binding-Data

A small improvement proposal to the code in above page. There is line id = input[i].value;, but I believe that should be id = events[i].value; to match the way the argument is named.
Also, should this be already in production? I created a new function, but with a quick look, the bindingData property did not contain propertiesArray and systemPropertiesArray.

Tested again today and now the properties were there - thanks!
@mathewc The small error in the sample code seems to still be there (see my previous comment).


How to start longclaw with docker?

When I docker-compose up I get
docusaurus_1  | LiveReload server started on port 35729
docusaurus_1  | Docusaurus server started on port 3000
But not port 8000?

Hi.
If you want to change the port, it is recommended to check the settings. Here is the file where the ports are specified https://github.com/JamesRamm/longclaw/blob/master/docker-compose.yml
If you just want to start a project in port 8001, take the settings from this file https://github.com/JamesRamm/longclaw/blob/master/Dockerfile.dev

Hi @officerebel the docker-compose file is for the docs only at the moment.
There is a basic docker example here:
https://github.com/JamesRamm/longclaw_demo


Updates to copy on Terms and Conditions page

From @Josh-Rosenblatt-Thesis >

I need to make a few changes on the TBTC Terms and Conditions Page. There are not many, and there in the title and first paragraph. Here's the updated page to replace what is current there.

Updated page: https://drive.google.com/a/thesis.co/file/d/1r4EXmBAPCdWeWDbkV9Rdy_aifl3Turil/view?usp=sharing

Thread in Flowdock: https://www.flowdock.com/app/cardforcoin/keep/threads/E5zcVTMvhIiZKIo5gJdECN_4MA1

Fixed this in #105 .


Fixes #57

Enforce the RFC-15 regular expressions for address prefixes and destination addresses respectively

Signed-off-by: Pascal Avondes<EMAIL_ADDRESS>

Hi, here are some additional comments about the PR:

Mainly, the 2 REGEX for address prefix and destination address got enforced in InterledgerAddress#isValid(java.lang.String), and unit tests got refactored accordingly (i.e. tests that were using invalid 1-segment destination addresses - such as g.foo - are now using valid >=2-segments destination addresses - such as g.foo.bar or g.foo.bar.baz -)
A new unit test was added to ensure a reject of 1-segment destination addresses
Critical modification: InterledgerAddress#getParentPrefix() algorithm was changed, in order to make it possible to call InterledgerAddress.of("g.foo.").getParentPrefix().get().getValue() // expected: "g.". This because a destination address smallest shape is <scheme>.<segment_1>.<segment_2>, and an address prefix smallest shape is <scheme>.. But in the current code base, g.foo. --> g. is walked-up through the g.foo. --> g.foo --> g. path, which breaks on the (in)validated-and-immutable g.foo destination address that is in the middle

About issuing a more precise error message when the address is invalid, I think it would better suit into another evolution ticket, since this refactoring already has a large foot print in the code base. If you're okay with that, I'll open a new ticket, holding a reference on https://github.com/hyperledger/quilt/issues/57 .

I think it would better suit into another evolution ticket

👍

Nice work @pascalav!

You're both welcome :+1:
@sappenin It's ok, I'll write explicit constant names in future contributions.
About more explicit error messages upon an InterledgerAddress#check() reject, I opened https://github.com/hyperledger/quilt/issues/104. Let me know if it's not so good for visitors to open issues: I believe one can't add labels to them when having that role (i.e. tagging as evolution, winter games, foo).


SCT-1243 Add new token command to CLI.

Also add test for deploy arg.

Pull Request Test Coverage Report for Build 156

11 of 11 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.2%) to 93.38%

Totals

Change from base Build 155:
0.2%

Covered Lines:
804

Relevant Lines:
861

💛  - Coveralls


Add touch support

This is actually totally trivial thanks to the touch option in your react-clickdrag component.

I guess it will work, but I'm not sure about the behavior though.. Is it really usable on touch?
I was initially thinking about having a classic number input (or range input) for mobile with touches...

I’d recommend you give it a try. The only change I made was the one shown in the PR. It works really well, I think; however, it’s also pretty much impossible to discover (which is why I added info text to explain it; in fact, the issue of discoverability also exists for users using a cursor). That’s really a UX issue, though, so it may be best handled on a case by case basis by the particular implementation of the control.

Nice use!
Thanks, I'll try it later today

Tested it and it works fine. It's not the best behavior for touch though but it works. And I've noticed to edit the field we have to hold the touch on the input.


[Event Parameter Change] Table 5741 - Transfer Line - procedure TestStatusOpen - event OnBeforeTestStatusOpen

We would like the parameter IncludeSender added to the following event.
Table 5741 - Transfer Line - procedure TestStatusOpen - event OnBeforeTestStatusOpen
Original:
[IntegrationEvent(false, false)]
local procedure OnBeforeTestStatusOpen(var TransferLine: Record "Transfer Line"; TransferHeader: Record "Transfer Header"; var IsHandled: Boolean)
begin
end;

Change: IncludeSender
[IntegrationEvent(true, false)] // <-- we need IncludeSender true
local procedure OnBeforeTestStatusOpen(var TransferLine: Record "Transfer Line"; TransferHeader: Record "Transfer Header"; var IsHandled: Boolean)
begin
end;

You have parameter var TransferLine = Rec = sender.

Thanks for the feedback. I have closed the question.


tweak syllabification script and begin writing tests

This PR adds "ihe" to the list of diphthongs in the syllabify_word function, to better handle words like "ihesus" and "iherusalem". It also adds the beginning of a new test suite - test_functions.py, which has some tests for the functions in latin_syllabification.py. The tests are incomplete, as I found myself spending more time writing them than they were worth.

just commenting that I may have more thoughts on further tweaks/improvements to the syllabification script (it's been on my mind for a long time...)

It would be good have list of words and their desired syllabification results so that any modifications can be tested.


[tool_crash] NoSuchMethodError: NoSuchMethodError: The getter 'printTrace' was called on null.Receiver: nullTried calling: printTrace

Command
flutter driver --driver=test_driver/integration_test.dart --target=integration_test/end_to_end_test.dart --use-existing-app http://<IP_ADDRESS>:53911/uLA7GqY35do=/

Steps to Reproduce

Run flutter driver on an integration_test, with --keep-app-running
Try run the app again using the provided URL from step 1.

Logs
NoSuchMethodError: NoSuchMethodError: The getter 'printTrace' was called on null.
Receiver: null
Tried calling: printTrace
#0      Object.noSuchMethod (dart:core-patch/object_patch.dart:54:5)
#1      _defaultOpenChannel.handleError (package:flutter_tools/src/vmservice.dart:114:54)
#2      _defaultOpenChannel.handleError (package:flutter_tools/src/vmservice.dart:113:27)
#3      _defaultOpenChannel (package:flutter_tools/src/vmservice.dart:155:24)
<asynchronous suspension>
#4      createVmServiceDelegate (package:flutter_tools/src/vmservice.dart:334:32)
<asynchronous suspension>
#5      _connect (package:flutter_tools/src/vmservice.dart:357:48)
<asynchronous suspension>
#6      FlutterDriverService.reuseApplication (package:flutter_tools/src/drive/drive_service.dart:221:18)
<asynchronous suspension>
#7      DriveCommand.runCommand (package:flutter_tools/src/commands/drive.dart:253:7)
<asynchronous suspension>
#8      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1043:27)
<asynchronous suspension>
#9      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#10     CommandRunner.runCommand (package:args/command_runner.dart:196:13)
<asynchronous suspension>
#11     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:284:9)
<asynchronous suspension>
#12     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#13     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:232:5)
<asynchronous suspension>

[✓] Flutter (Channel stable, 2.2.2, on macOS 11.2.3 20D91 darwin-x64, locale en-NZ)
    • Flutter version 2.2.2 at /usr/local/flutter
    • Framework revision d79295af24 (2 weeks ago), 2021-06-11 08:56:01 -0700
    • Engine revision 91c9fc8fe0
    • Dart version 2.13.3

[!] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/benanderson/Library/Android/sdk
    • Platform android-30, build-tools 30.0.3
    • Java binary at: /Applications/Android Studio 4.2 Preview.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.5.1, Build version 12E507
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.2)
    • Android Studio at /Applications/Android Studio 4.2 Preview.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.57.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.23.0

[✓] Connected device (2 available)
    • sdk gphone x86 arm (mobile) • emulator-5554 • android-x86    • Android 11 (API 30) (emulator)
    • Chrome (web)                • chrome        • web-javascript • Google Chrome 91.0.4472.114

! Doctor found issues in 1 category.

Flutter Application Metadata
Type: app
Version: 0.1.5+2
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: stable
Creation framework version: 8af6b2f038c1172e61d418869363a28dffec3cb4
Plugins
flutter_secure_storage-4.0.0
integration_test
location
location_web-3.0.0
package_info-2.0.0
package_info_plus-1.0.0
package_info_plus_macos-1.0.0
package_info_plus_web-1.0.0
path_provider_linux-2.0.0
path_provider_windows-2.0.0
plain_notification_token-1e9dc89f04d51e1feec6834aada8fa1049e5c0db
sentry_flutter-5.0.0
shared_preferences-2.0.3
shared_preferences_linux-2.0.0
shared_preferences_macos-2.0.0
shared_preferences_web-2.0.0
shared_preferences_windows-2.0.0
url_launcher-6.0.2
url_launcher_linux-2.0.0
url_launcher_macos-2.0.0
url_launcher_web-2.0.0
url_launcher_windows-2.0.0

Same issue

The tool has since been migrated to null safety so it is likely that this issue has been fixed. If anyone still experiences this crash on the latest version of flutter stable, kindly file a new issue and provide all the relevant information.
Thank you


Trouble loading weights file

file='epoch=78-step=323584.ckpt'
need to use python 3.10
error
model = FullModel.load_from_checkpoint('Documents/Github/nowcasting_forecast/epoch=78-step=323584.ckpt')
INFO:power_perceiver.pytorch_modules.satellite_predictor:kwargs for XResUNet = {'img_size': (128, 256), 'n_in': 15, 'n_out': 25, 'pretrained': False, 'blur_final': True, 'self_attention': True, 'last_cross': True, 'bottle': False}
Traceback (most recent call last):
  File "<input>", line 1, in <module>
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/pytorch_lightning/core/saving.py", line 161, in load_from_checkpoint
    model = cls._load_model_state(checkpoint, strict=strict, **kwargs)
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/pytorch_lightning/core/saving.py", line 203, in _load_model_state
    model = cls(**_cls_kwargs)
  File "<string>", line 13, in __init__
  File "/Users/peterdudfield/Documents/Github/power_perceiver/power_perceiver/experiments/exp_027_longer_forecasts.py", line 626, in __post_init__
    self.satellite_predictor = SatellitePredictor()
  File "<string>", line 12, in __init__
  File "/Users/peterdudfield/Documents/Github/power_perceiver/power_perceiver/experiments/exp_027_longer_forecasts.py", line 266, in __post_init__
    self.satellite_predictor = XResUNet(
  File "/Users/peterdudfield/Documents/Github/power_perceiver/power_perceiver/pytorch_modules/satellite_predictor.py", line 31, in __init__
    self.model = create_unet_model(arch=arch, **kwargs)
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/fastai/vision/learner.py", line 243, in create_unet_model
    model = arch(pretrained)
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/fastai/vision/models/xresnet.py", line 99, in xse_resnext50
    def xse_resnext50(n_out=1000, pretrained=False, **kwargs):  return XResNet(SEResNeXtBlock, 4, g1, n_out=n_out, **se_kwargs2, **kwargs)
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/fastai/vision/models/xresnet.py", line 47, in __init__
    nn.Linear(block_szs[-1]*expansion, n_out),
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/torch/nn/modules/linear.py", line 96, in __init__
    self.weight = Parameter(torch.empty((out_features, in_features), **factory_kwargs))
TypeError: empty() received an invalid combination of arguments - got (tuple, dtype=NoneType, device=NoneType), but expected one of:
 * (tuple of ints size, *, tuple of names names, torch.memory_format memory_format, torch.dtype dtype, torch.layout layout, torch.device device, bool pin_memory, bool requires_grad)
 * (tuple of ints size, *, torch.memory_format memory_format, Tensor out, torch.dtype dtype, torch.layout layout, torch.device device, bool pin_memory, bool requires_grad)

related to #132

Added a bug report on fastai - https://github.com/fastai/fastai/issues/3745

I can now load it


Unable to Parking

unable to parking even the parking sign already detected.
can you help me?

@Ayensyarah
Can you give us more details about your questions (i.e., which tutorial or error code)
Regards,
Ryan

@RyanJaehyunShim
theres no error when i roslaunch autorace_core and sent data rostopic pub -1 /core/decided_mode std_msgs/UInt8 "data: 2". its follow the line.
then it detect parking sign but not change to parking mode. still following the line

@Ayensyarah
There is a misunderstanding about the mechanism. Once the robot detects a parking sign, it will start to count the number of dots on the line. When the robot finds the dotted line you can see on the racing map (by counting the number of dots), it will move to the parking lot.
Regards,
Ryan

@RyanJaehyunShim
the i should change the dotted value in which file?
detect_parking.py right?

@Ayensyarah
You need the map.

@RyanJaehyunShim
how can i get the mapping? i mean how can i mapping the map.

@Ayensyarah
Refer to 13.6.1 and 13.6.2 if you want to test it on a simulator. If you need a physical map, refer to the following link (https://github.com/ROBOTIS-GIT/autorace_track).

Is this where it counts and check the dotted line? https://github.com/ROBOTIS-GIT/turtlebot3_autorace/blob/master/turtlebot3_autorace_detect/nodes/detect_parking#L220
If yes, then it triggers even if it sees only 1 dot? Or it counts until a few dots, then start to go in?

@arixrobotics
Yes, the latter is correct. You can modify the code and try it again, then you will know it.
Regards,
Ryan

This issue has been closed as there weren't recent activities. Please feel free to reopen this thread if there's any opinion to throw. Thanks.


v0.32.6 no longer shows pod that cannot be scheduled in logs

Description
Observed Behavior:
When a pod cannot be scheduled and karpenter emits the Could not schedule pod, incompatible with ... message, the pod name trying to be scheduled is no longer part of the log.  This makes it more difficult to identify the problematic pod.
Expected Behavior:
v0.28 logs contained the pod name and would expect this to be present.  The pod name used to be contained in the final part of the log in the form
{"commit": "26e2d35-dirty", "pod": "<namespace>/<pod_name>"}

Reproduction Steps (Please include YAML):
Install v0.32 and attempt to schedule a pod that is incompatible with any defined provisioners.
Versions:

Chart Version: v0.32.6
Kubernetes Version (kubectl version): v1.26.11-eks-8cb36c9

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Closing.  The pod name is indeed there.  Our log parsing due to it being moved to the pod field (which is a good change) wasn't identifying it.