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
Additional details:
The build seems to fail on the xcb dependency version 0.8.2, however this build has succeeded in the past and is currently available on docs.rs. This leads me to wonder if the cause is a bug in the latest rustdoc nightly. Is it possible to get the documentation re-built with stable?
Your build error doesn't seem to be related to the version of rust, though. cc @pietroalbini, do you intentionally make /opt/rustwide/cargo-home read-only?
It looks like xcb is a new dependency in nannou 0.12, I wonder if it's trying to write to part of the filesystem it's not supposed to. I know we changed the sandboxing pretty significantly about a month ago in the switch to rustwide: #407, xcb hasn't been rebuilt since 2018: https://docs.rs/crate/xcb/0.8.2/builds/87332
Your build error doesn't seem to be related to the version of rust, though. cc @pietroalbini, do you intentionally make /opt/rustwide/cargo-home read-only?
Yeah, otherwise a malicious crate could've messed up the state for other crates.
It looks like xcb is a new dependency in nannou 0.12, I wonder if it's trying to write to part of the filesystem it's not supposed to. I know we changed the sandboxing pretty significantly about a month ago in the switch to rustwide: #407, xcb hasn't been rebuilt since 2018: https://docs.rs/crate/xcb/0.8.2/builds/87332
I just tried building xcb 0.8.2 myself using docker-compose run web build crate xcb 0.8.2, and this appears to be what caused the problem.
The crate has a python script rs_client.py which it uses to create some FFI files. The exact line it fails at is rs_client.py:114.
The good news is, xcb 0.9.0 works fine, so I think if x11-clipboard (the dependency of copypasta, the dependency of conrod_core, the dependency of nannou) upgrades to 0.9.0, this should be fixed.
We tracked down the dependency (x11-clipboard) that caused the error and sent a PR quininer/x11-clipboard#17 through, which has been bubbled up to the other dependency copypasta in a minor patch alacritty/alacritty#3024. conrod_core (the dependency which pulls in copypasta) just requests 0.6, so I would think building with copypasta 0.6.1 would get rid of this issue, although admittedly I can't seem to figure out how to tell the docker container to do that on my own machine.
Oh hold on I think I misunderstood your comment. You're asking us to build with a different version of a minor dependency? We don't control dependency management, that's done by cargo. If you've fixed the bug you can publish a new version and docs.rs will build that version.
Oh hold on I think I misunderstood your comment. You're asking us to build with a different version of a minor dependency? We don't control dependency management, that's done by cargo. If you've fixed the bug you can publish a new version and docs.rs will build that version.
Gotcha, that's what I was asking. Thanks for your help!
Activity
jyn514 commentedon Nov 8, 2019
Related: #229, #228
jyn514 commentedon Nov 8, 2019
Your build error doesn't seem to be related to the version of rust, though. cc @pietroalbini, do you intentionally make
/opt/rustwide/cargo-homeread-only?jyn514 commentedon Nov 8, 2019
It looks like
xcbis a new dependency innannou 0.12, I wonder if it's trying to write to part of the filesystem it's not supposed to. I know we changed the sandboxing pretty significantly about a month ago in the switch to rustwide: #407,xcbhasn't been rebuilt since 2018: https://docs.rs/crate/xcb/0.8.2/builds/87332emilyalbini commentedon Nov 10, 2019
Yeah, otherwise a malicious crate could've messed up the state for other crates.
alberdingk-thijm commentedon Nov 21, 2019
I just tried building
xcb 0.8.2myself usingdocker-compose run web build crate xcb 0.8.2, and this appears to be what caused the problem.The crate has a python script
rs_client.pywhich it uses to create some FFI files. The exact line it fails at isrs_client.py:114.The good news is,
xcb 0.9.0works fine, so I think ifx11-clipboard(the dependency ofcopypasta, the dependency ofconrod_core, the dependency ofnannou) upgrades to0.9.0, this should be fixed.jyn514 commentedon Nov 21, 2019
Looks like this isn't a bug in docs.rs, going to close this.
mitchmindtree commentedon Nov 23, 2019
Thanks for digging into this @alberdingk-thijm!
alberdingk-thijm commentedon Dec 4, 2019
@jyn514, do you happen to know when docs.rs will try to build
nannou(and the other crates related to this error inxcb) again?jyn514 commentedon Dec 5, 2019
Rebuilding automagically is #464 . Currently someone has to schedule a manual build.
jyn514 commentedon Dec 5, 2019
This particular crate won't be helped by rebuilding however because it tries to write to a read only filesystem.
alberdingk-thijm commentedon Dec 5, 2019
We tracked down the dependency (
x11-clipboard) that caused the error and sent a PR quininer/x11-clipboard#17 through, which has been bubbled up to the other dependencycopypastain a minor patch alacritty/alacritty#3024.conrod_core(the dependency which pulls incopypasta) just requests0.6, so I would think building withcopypasta 0.6.1would get rid of this issue, although admittedly I can't seem to figure out how to tell the docker container to do that on my own machine.jyn514 commentedon Dec 5, 2019
@alberdingk-thijm Could you make these updates in a different repo, such as nannou-org/nannou#429? This is not a docs.rs bug.
jyn514 commentedon Dec 5, 2019
Oh hold on I think I misunderstood your comment. You're asking us to build with a different version of a minor dependency? We don't control dependency management, that's done by cargo. If you've fixed the bug you can publish a new version and docs.rs will build that version.
alberdingk-thijm commentedon Dec 5, 2019
Gotcha, that's what I was asking. Thanks for your help!