Hans Baker

Flaky tests? Only change in my branch was a comment and failing tests are in unrelated parts of the codebase. Unable to rerun failed checks on my end, btw.

> @BakerNet Thanks for the PR. I can confirm that this resolved the direct issue. If I try to install a package it will now call keyring with the correct...

> This is on my to-do list, it's been slow because of all the cfg changes for testing — we've generally avoided doing something like this so far. Without an...

@jenshnielsen would you mind testing this again to check if my fix works on your end when you have time?

> Okay thanks I can take a look into this unless @BakerNet is interested I know why this is happening and can work on it. It's because of the early...

The PR for this has been ready for a few days (#2570 ) I don't mean to rush, just an FYI in case it wasn't clear it's ready for review.

As of #2254 `--keyring-provider subprocess` is available. It has been tested on at least two Google artifact registry projects (using [keyrings.google-artifactregistry-auth](https://cloud.google.com/artifact-registry/docs/python/authentication#keyring) plugin) as working.

> Maybe like they implemented that wrong? cc @BakerNet > > You can use `python -c 'import keyring; keyring.get_credential("", username=None)'` instead > Looks like a typo in keyring @jaraco `AttributeError:...

> thanks, I assume v0.23 has the same issue? I am getting same error, also Docker on WSL2 (Ubuntu 22.04). I get error on `0.22.0` and `0.23.0` but not `0.21.0`

I found that because I am mounting my root folder to the docker container, having a virtual environment in my local root will break `watchfiles` in the container. The workaround...