Skip to content

Keep LogExpFunctions 0.3 extra for SparseConnectivityTracer - #1200

Closed
ChrisRackauckas-Claude wants to merge 1 commit into
SciML:masterfrom
ChrisRackauckas-Claude:compat-fix-downgrade-floors-20260826
Closed

ChrisRackauckas-Claude wants to merge 1 commit into
SciML:masterfrom
ChrisRackauckas-Claude:compat-fix-downgrade-floors-20260826

Conversation

@ChrisRackauckas-Claude

Copy link
Copy Markdown
Member

Keep LogExpFunctions 0.3 extra so docs can resolve with SparseConnectivityTracer.

Follow-up to #1198 (merged). Downgrade Core on that PR already passed. Docs failed: NonlinearSolveBase LogExpFunctions = "1" vs SparseConnectivityTracer WeakCompat LogExpFunctions = "0.3" (CI: https://github.com/SciML/NonlinearSolve.jl/actions/runs/32945709491/job/98105852988). Downstream IntegrationTest is master-same.

Local Julia 1.10 docs instantiate:

  • after (0.3.29, 1): RESOLVE_OK + INSTANTIATE_OK, LogExpFunctions 0.3.29 (NonlinearSolve-docs.log)
file dep before after
lib/NonlinearSolveBase/Project.toml LogExpFunctions 1 0.3.29, 1

Bound-only. NLsolve 5 / ForwardDiff 1 / TimerOutputs 1 stay. No yanked-only majors.

This PR should be ignored until reviewed by @ChrisRackauckas.

🤖 Generated with Claude Code

NonlinearSolveBase LogExpFunctions 1 is unsatisfiable in docs with
SparseConnectivityTracer WeakCompat LogExpFunctions 0.3. Restore
0.3.29, 1. Downgrade Core already passed.

Co-Authored-By: Chris Rackauckas <accounts@chrisrackauckas.com>
Co-Authored-By: Claude <noreply@anthropic.com>
@ChrisRackauckas-Claude

Copy link
Copy Markdown
Member Author

Closing extras workaround. Real fix is SCT allowing LogExpFunctions 1: JuliaDiff/SparseConnectivityTracer.jl#327

@adrhill

adrhill commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

SpaseConnectivityTracer.jl v1.2.3 with the fix has been tagged.

@ChrisRackauckas-Claude

Copy link
Copy Markdown
Member Author

The upstream fix is now released as SparseConnectivityTracer v1.2.3 and registered in General. Plan: raise the SparseConnectivityTracer test/docs floors to 1.2.3, reproduce the FirstOrder alldeps downgrade failure on the unmodified branch, rerun the same downgrade path plus FirstOrder Core and the docs build after the bound change, then open a focused draft PR.

@ChrisRackauckas-Claude

Copy link
Copy Markdown
Member Author

Resolved by the upstream release; no NonlinearSolve diff is needed.

SparseConnectivityTracer v1.2.3 was registered by JuliaRegistries/General#166124. Current master at 90aeffc7952b22cab7c558fba06c4d80b08aac47 now resolves the existing SparseConnectivityTracer = "1" bound to the first jointly compatible release.

Local Julia 1.10.11, isolated depots:

  • Workflow-equivalent docs instantiate: exit 0; SCT 1.2.3, LogExpFunctions 1.0.1, ForwardDiff 1.4.5.
  • julia --project=docs docs/make.jl: exit 0.
  • Exact FirstOrder alldeps downgrade action: exit 0; SCT 1.2.3, LogExpFunctions 1.0.0, ForwardDiff 1.4.0.
  • Locked SCT-backed sparsity tests: Brusselator 2D | 5/5; Structured Jacobians | 16/16.

The authoritative current-master docs run is green: https://github.com/SciML/NonlinearSolve.jl/actions/runs/33001644905.

Not claimed: the full locked FirstOrder Core suite. I stopped it after one hour in the unrelated TrustRegion allocation benchmark (rootfind_tests__item8.jl); 1,061 TrustRegion assertions had passed before interruption. The FirstOrder downgrade CI job is queued at https://github.com/SciML/NonlinearSolve.jl/actions/runs/33001644941/job/98313758956.

This closes the LogExpFunctions/SparseConnectivityTracer follow-up to #1198.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants