Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix any #393

Merged
merged 2 commits into from
Jun 28, 2024
Merged

fix any #393

merged 2 commits into from
Jun 28, 2024

Conversation

bvdmitri
Copy link
Contributor

@bvdmitri bvdmitri commented Jun 27, 2024

This PR fixes #196

Checklist

  • Appropriate tests were added
  • Any code changes were done in a way that does not break public API
  • All documentation related to code changes were updated
  • The new code follows the
    contributor guidelines, in particular the SciML Style Guide and
    COLPRAC.
  • Any new documentation only uses public API

Additional context

Add any other context about the problem here.

@ChrisRackauckas
Copy link
Member

 SymbolicIndexingInterface [2efcf032] log:
 ├─possible versions are: 0.1.0-0.3.22 or uninstalled
 └─restricted to versions 0.3.23 by RecursiveArrayTools [731186ca] — no versions left
   └─RecursiveArrayTools [731186ca] log:
     ├─possible versions are: 3.24.0 or uninstalled
     └─RecursiveArrayTools [731186ca] is fixed to version 3.24.0

@AayushSabharwal is this due to the recent yanks? We need to clean master here.

@AayushSabharwal
Copy link
Member

Yes

@AayushSabharwal
Copy link
Member

I'll revert the SII changes and PR

@bvdmitri
Copy link
Contributor Author

Yeah, I needed to dev the SymbolicIndexingInterface in order to run tests locally (it passed)

@ChrisRackauckas
Copy link
Member

Rebase onto the fixed master and you should be good.

@ChrisRackauckas ChrisRackauckas merged commit 3d46884 into SciML:master Jun 28, 2024
17 of 23 checks passed
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.

Possible bug in any(f::Function,A::ArrayPartition)
3 participants