-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
DemoCards.jl broken builds #187
Comments
Strictly speaking, this isn't really JuliaHub specific. You can repro the issue with just I'm happy to just make the whole package dir writable, but arguably your package should handle that case on its own.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am here because the JuliaHub documentation generation says that it is done by this package, and the "contact support" button does not appear to work for me.
In projects using
DemoCards.jl
, the docs builds on JuliaHub appear to fail due to a bad writing permission (which is necessary for creating the demo cards during the build process). I have two projects depending on it, and it appears that theDemoCards.jl
docs fail for the same reason. The logs for these projects are:Other packages that I see that depend on it, such as the great
Plots.jl
package, appear to circumvent the problem by redirecting the "read on JuliaHub" button to their own hosted docs, which I cannot for the life of me figure out where the setting for this is.Regardless, the logs for each project share the write permission error within the docs directory with a similar error:
The line in question is 471: "SystemError: opening file "/juliateam/.julia/packages/ClusterValidityIndices/UT9rS/docs/src/examples/basic-examples/cvi-example.jl": Permission denied"
Is the write permission and subsequent error on the side of
DocumentationGenerator.jl
or a setting in JuliaHub? If it is on the JuliaHub side, is there documentation to show how to change some permissions setting, or is it out of our hands? Thanks for your time.The text was updated successfully, but these errors were encountered: