Downgrade: raise DiffEqGPU compat floor to 3.10#103
Merged
ChrisRackauckas merged 1 commit intoJun 23, 2026
Merged
Conversation
DiffEqGPU v3.9.0 references DiffEqBase.determine_event_occurrence, a
symbol that was removed from DiffEqBase. With a current DiffEqBase
(v6.218.0) the downgrade resolution pins DiffEqGPU to its 3.9.0 floor,
which then fails to precompile:
UndefVarError: `determine_event_occurrence` not defined
@ DiffEqGPU .../ensemblegpukernel/integrators/integrator_utils.jl:373
DiffEqGPU v3.10.0 removed that reference and raised its own DiffEqBase
floor to 6.205.1, so it precompiles cleanly. Raising the lower bound
here resolves the downgrade conflict without restricting upgrades.
Co-Authored-By: Chris Rackauckas <accounts@chrisrackauckas.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
2 participants
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.
Summary
Raises the
DiffEqGPUcompat lower bound from3.9to3.10to fix the failingDowngrade / Downgrade Testsjob onmain.Root cause
The downgrade-compat resolution pins
DiffEqGPUto its floor,v3.9.0. That version'ssrc/ensemblegpukernel/integrators/integrator_utils.jl:373referencesDiffEqBase.determine_event_occurrence, a symbol that has since been removed from DiffEqBase. With a current DiffEqBase (v6.218.0, whichv3.9.0's looseDiffEqBase = "6.122"compat happily allows) the symbol is gone, so DiffEqGPU — and therefore ParallelParticleSwarms — fails to precompile:DiffEqGPU v3.10.0removed that reference (commit removingdetermine_event_occurrencefor the refactored DiffEqBase event API) and raised its ownDiffEqBasefloor to6.205.1, so it precompiles cleanly against current DiffEqBase. Raising the lower bound here is a safe lower-bound raise: it never restricts upgrades, only excludes the broken3.9.xfloor.Local verification (Julia 1.10 / lts, the downgrade channel)
Pkg.add(DiffEqGPU@3.9.0)→ precompile fails with the exactUndefVarError: determine_event_occurrenceatintegrator_utils.jl:373.Pkg.add(DiffEqGPU@3.10.0)→ precompiles and loads cleanly.downgrade.jlover the patchedProject.toml: resolver now picksDiffEqGPU v3.10.0withDiffEqBase v6.218.0and produces a valid manifest.Not addressed here (separate failures on
main)could not lock config file /home/.../.gitconfig: File exists), not a code issue.Rosenbrock N=4PSO regression test diverges only on the Julia 1.13.0-rc1 prerelease (objective3.70vs2.98e-13on 1.12) — a Julia-version RNG-stream change in the stochastic optimizer, not a package bug. Left for separate handling (not a tolerance loosening).Please ignore until reviewed by @ChrisRackauckas.