You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At least for me, ChainRules failed to build on Julia v1.7.1 after pulling the latest changes from #597 last night. The error messages (sorry I didn't copy) mentioned that the recently added Base.allequal (julia #43354) is unrecognized. Possibly an issue with Compat controls, related to this comment in the PR? @mcabbott@niklasschmitz@mzgubic
Maybe it's just me, sorry to bother if so. I took this as a sign I should build v1.7.2
Sorry, I just looked a bit and I think I lost the error messages. The error definitely said that ChainRules failed to build and cited not recognizing allequal, but that's about all I remember.
I also incorrectly wrote Base.allequal naively assuming that allequal had been added to Base, adding unnecessary confusion. All around not a helpful post from me!
Maybe I caused ChainRules not to build myself by creating an inconsistent project environment or something like that. I'm happy to close this if it looks okay to you.
Building on @adrhill's comments, I'm beginning to encounter this on Julia v1.7.2 through juno v0.8.4 with julia-client v0.12.6. I presume that juno/julia-client is using the older JuliaFormater? This undefined allequal is frustrating as I now need to precompile zygote v0.6.36 outside of the IDE available to me.
This is really strange. I wonder why it doesn't happen with anything else using Compat -- do any of these packages define their own allequal which clashes somehow?
Does it still occur if with ] dev ChainRules? If so, you could edit the file to have @non_diff Compat.allequal(... instead, maybe that would change something?
Hi, I do have this issue, too, using Julia 1.7.2. Just wanted to add the specific info about when it breaks for me.
The problem seems to be when I load any package before activating an environment, for example
using DrWatson
@quickactivate # or ] activate .
using ChainRules # or Flux
breaks and gives the error with allequal not defined. I also tried it with first using UnicodePlots and then activating environment and using Flux. It is not a huge problem but an inconvenience, since I am using using DrWatson; @quickactivate in most of my scripts.
When first activating environment, then loading Flux/ChainRules, everything works fine. I also not not know which package to update (as for others it was fixed by updating), my packages are updated as much as they can, I do need some lower versions because of dependencies.
Activity
mcabbott commentedon Mar 9, 2022
That's surprising. Did it say
Base.allequal?Details
doddgray commentedon Mar 9, 2022
Sorry, I just looked a bit and I think I lost the error messages. The error definitely said that ChainRules failed to build and cited not recognizing
allequal, but that's about all I remember.I also incorrectly wrote
Base.allequalnaively assuming thatallequalhad been added toBase, adding unnecessary confusion. All around not a helpful post from me!Maybe I caused ChainRules not to build myself by creating an inconsistent project environment or something like that. I'm happy to close this if it looks okay to you.
mcabbott commentedon Mar 9, 2022
CI is 1.7.2, and I tried 1.7.0 and didn't see problems. Glad if it works now!
adrhill commentedon Mar 10, 2022
I can recreate this in 1.7.1:
This currently also breaks Flux.
mzgubic commentedon Mar 10, 2022
Have you tried
] uping your env?I can't reproduce the issue I'm afraid :(
adrhill commentedon Mar 10, 2022
Also happens to me on 1.7.2 on macOS.
updoesn't help.Details
adrhill commentedon Mar 10, 2022
Maybe this is due to my startup.jl?
adrhill commentedon Mar 10, 2022
Ok, this issue can stay closed. Somehow Compat
3.42doesn't exportallequalon my machine. I'll open an issue there.Thanks for the help! :)
Edit: This wasn't an issue with Compat either, but with an older version of JuliaFormatter in my startup.jl!
CiaranOMara commentedon Mar 10, 2022
Building on @adrhill's comments, I'm beginning to encounter this on Julia v1.7.2 through
junov0.8.4 withjulia-clientv0.12.6. I presume thatjuno/julia-clientis using the olderJuliaFormater? This undefinedallequalis frustrating as I now need to precompilezygotev0.6.36 outside of the IDE available to me.mcabbott commentedon Mar 10, 2022
This is really strange. I wonder why it doesn't happen with anything else using Compat -- do any of these packages define their own
allequalwhich clashes somehow?Does it still occur if with
] dev ChainRules? If so, you could edit the file to have@non_diff Compat.allequal(...instead, maybe that would change something?CiaranOMara commentedon Mar 11, 2022
I cannot reproduce the error after successfully precompiling outside of my IDE. So, I can't try your suggestions @mcabbott.
Below is the script of what I've tried within the IDE to reproduce the error.
My more complex projects are now loading
ChainRulesetc through the IDE since a successful precompile.KronosTheLate commentedon May 3, 2022
I also faced this issue. Here is my environment for reproducibility:
masenka31 commentedon Jun 9, 2022
Hi, I do have this issue, too, using Julia 1.7.2. Just wanted to add the specific info about when it breaks for me.
The problem seems to be when I load any package before activating an environment, for example
breaks and gives the error with
allequalnot defined. I also tried it with firstusing UnicodePlotsand then activating environment andusing Flux. It is not a huge problem but an inconvenience, since I am usingusing DrWatson; @quickactivatein most of my scripts.When first activating environment, then loading Flux/ChainRules, everything works fine. I also not not know which package to update (as for others it was fixed by updating), my packages are updated as much as they can, I do need some lower versions because of dependencies.
My
Project.toml:oxinabox commentedon Jun 9, 2022
This feels like a bug in julia itself. Because order of loading shouldn't have an effect on what is defined inside Base...
devmotion commentedon Nov 3, 2026
I'm closing this issue since it seems stale - ChainRules does not use Compat.jl anymore.