Bump prefix-dev/setup-pixi from 0.10.0 to 0.10.1 - #196
Merged
chrisburr merged 2 commits intoAug 28, 2026
Conversation
Bumps [prefix-dev/setup-pixi](https://github.com/prefix-dev/setup-pixi) from 0.10.0 to 0.10.1. - [Release notes](https://github.com/prefix-dev/setup-pixi/releases) - [Commits](prefix-dev/setup-pixi@v0.10.0...v0.10.1) --- updated-dependencies: - dependency-name: prefix-dev/setup-pixi dependency-version: 0.10.1 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Temporarily clone chrisburr/DIRAC fix/plot-tests-numpy-bins-{v8r0,v9r0,
integration} instead of DIRACGrid/DIRAC, to check that they fix the
Test_Plots.py::test_histogram failure that is blocking this PR.
Revert this commit before merging.
dependabot
Bot
deleted the
dependabot/github_actions/prefix-dev/setup-pixi-0.10.1
branch
August 28, 2026 08:17
chrisburr
added a commit
that referenced
this pull request
Aug 31, 2026
* fix: Clone DIRACGrid/DIRAC in the integration tests again ccf6911 ("Bump prefix-dev/setup-pixi from 0.10.0 to 0.10.1 (#196)") accidentally merged a temporary hack that pointed the integration tests at chrisburr/DIRAC fix/plot-tests-numpy-bins-{v8r0,v9r0,integration} instead of DIRACGrid/DIRAC, so main has not been testing against the real DIRAC branches since then. The plot test fixes those branches carried have been merged upstream (DIRACGrid/DIRAC#8753, #8754 and #8755) and are present in rel-v8r0, rel-v9r0 and integration, so the hack is no longer needed. * fix: Pin m2crypto <0.46 to avoid a broken ssl_read() conda-forge published m2crypto 0.46.0 through 0.49.0 on 2026-08-28, which broke every integration test with: SystemError: <built-in function ssl_read> returned a result with an exception set 0.46.0 rewrote ssl_read() in src/SWIG/_ssl.i and inverted the handling of ssl_sleep_with_timeout()'s return value: that helper returns 0 when poll() reports the fd is ready and -1 on timeout, but the new code treats 0 as a failure and falls through to retry on -1. It also dropped the gettimeofday() that initialised the deadline, so the timeout is computed from an uninitialised struct timeval. The result is that any read() on a connection with a timeout set spins on SSL_read() until data arrives and then returns a value with a stale SSLTimeoutError still set, which breaks all DIRAC DISET/dips traffic. ssl_connect(), ssl_write() and ssl_accept() are unaffected. Reproduced against the conda-forge builds of 0.46.0 and 0.49.0; 0.45.1 is the last working release and the bug is still present upstream.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps prefix-dev/setup-pixi from 0.10.0 to 0.10.1.
Release notes
Sourced from prefix-dev/setup-pixi's releases.
Commits
f00437fUpdate dependencies and add pnpm workspace configuration (#279)d0c199dchore(deps): bump the gh-actions group with 3 updates (#276)2253d9cchore(deps): bump the gh-actions group with 3 updates (#273)c5359a3chore(deps): bump the nodejs group with 6 updates (#274)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)