Closed mentics closed 2 years ago
Thank you for reporting - I can recreate this on my own hardware. I'll have a look into this, but I will be out travelling until the end of september, so there might be some time until this is fixed. My personal working configuration on Julia 1.7 uses the following package versions, in case you want to pin them:
Status `~/Uni/Code/FluxArchitectures/Project.toml`
[fbb218c0] BSON v0.3.5
⌃ [587475ba] Flux v0.13.3
⌅ [5cadff95] JuliennedArrays v0.3.0
[189a3867] Reexport v1.2.2
⌃ [295af30f] Revise v3.3.3
⌃ [82cb661a] SliceMap v0.2.6
[bd369af6] Tables v1.7.0
⌃ [e88e6eb3] Zygote v0.6.40
[4af54fe1] LazyArtifacts
[9a3f8284] Random
I think this is likely an issue in Zygote's compiler. The stack trace points at the call to Flux.reset! in the loss function. If I remove that, the error goes away. I'll close this issue and open one on Zygote.
I created a simple test case that didn't involve FluxArchitectures, so it's certainly not related to this project. Here's the ticket I created for Zygote: https://github.com/FluxML/Zygote.jl/issues/1297
Thanks! I am currently also having some issues where my tests break, and I could isolate that to be caused by going from Zygote 0.6.43 to 0.6.44. Apparently there is something wrong with how structs are handled by Zygote, but it doesn't show up in all cases...
Running Julia 1.8.0 on Windows 11, I copy-pasted the example code at the top of the examples page into a new Julia environment after adding FluxArchitectures and Plots packages. When it reached the line
Flux.train!
, it gave the following stack trace: