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
shell> julia --project=.
julia> @time using Stipple
1.721656 seconds (958.61 k allocations: 70.250 MiB, 9.36% gc time, 13.36% compilation time)
While on 1.11:
Precompiling StippleMarkdown...
62 dependencies successfully precompiled in 123 seconds. 38 already precompiled.
1 dependency had output during precompilation:
┌ Stipple
│ ┌ Info:
│ └ Web Server starting at http://127.0.0.1:8883
│ [ Info: Listening on: 127.0.0.1:8883, thread id: 1
│ [ Info: GET / 200
│ [ Info: Server on 127.0.0.1:8883 closing
└
ERROR: InitError: MethodError: no method matching dirname(::Nothing)
The function `dirname` exists, but no method is defined for this combination of argument types.
Closest candidates are:
dirname(::FilePathsBase.AbstractPath)
@ FilePathsBase ~/.julia/packages/FilePathsBase/Laclt/src/aliases.jl:12
dirname(::AbstractString)
@ Base path.jl:183
Stacktrace:
[1] __init__()
@ StippleMarkdown ~/.julia/packages/StippleMarkdown/yPAaL/src/StippleMarkdown.jl:34
..
That seems like an actual bug in your package.
For 1.11 possibly self-inflicted, though I'm not sure how, or how to fix... I tend to CTRL-C when precompiling, usually without any bad effect, and in 1.10 I didn't manage to start with my dirty environment, then trying to fix got the strange error...
The text was updated successfully, but these errors were encountered:
Could this be due to a conflict with the Manifest file? See the warning when you import the package:
julia> using StippleMarkdown
┌ Warning: The active manifest file has dependencies that were resolved with a different julia version (1.11.0-rc4). Unexpected behavior may occur.
[Yes it is, I see now how it happened... it's the one in the current directory, I thought the global env used/messed up by Julia, I'm not used to using --project=. ]
I trimmed out the original first ("strange") [non]bug, and left in the relevant other error.
PallHaraldsson
changed the title
FYI;: strange bug on 1.10.5 (NOT 1.11, despite the error message)
Bug on 1.11.0?
Oct 8, 2024
While on 1.11:
That seems like an actual bug in your package.
For 1.11 possibly self-inflicted, though I'm not sure how, or how to fix... I tend to CTRL-C when precompiling, usually without any bad effect, and in 1.10 I didn't manage to start with my dirty environment, then trying to fix got the strange error...
The text was updated successfully, but these errors were encountered: