anybody else get this with Dave?
1 Like
Have you uploaded any files yet ?
I did a test today and uploaded a file then loaded the vault without problems.
If you haven’t uploaded a file to your vault it does not exist and can not be loaded.
1 Like
I gather the box is being rebuilt.
It looked like there was a stale caching issue after the upgrade to 0.6.0 libs, so the box was torn down and I don’t think it has been stood up again yet.
1 Like
I have no idea what you just said, but thanks for the reply.
4 Likes
In short, it’s known and temporary. Antsnest will be back again soon! 
3 Likes
well I hope so 
Compiling alloy-consensus v0.15.11
211.3 error[E0433]: failed to resolve: could not find `__private` in `serde`
211.3 --> /usr/local/cargo/registry/src/index.crates.io-1949cf8c6b5b557f/alloy-consensus-0.15.11/src/transaction/envelope.rs:916:34
211.3 |
211.3 916 | let content = serde::__private::de::Content::deserialize(deserializer)?;
211.3 | ^^^^^^^^^ could not find `__private` in `serde`
211.3
something bad happened to poor serde
2 Likes
Ah, is that what is killing it? I saw github build had that error, but I didn’t get it locally.
I’ll do some digging tomorrow!
3 Likes
can you jump onto a chat with me and safemedia please?
210.5 Compiling alloy-consensus v0.15.11
211.3 error[E0433]: failed to resolve: could not find `__private` in `serde`
211.3 --> /usr/local/cargo/registry/src/index.crates.io-1949cf8c6b5b557f/alloy-consensus-0.15.11/src/transaction/envelope.rs:916:34
211.3 |
211.3 916 | let content = serde::__private::de::Content::deserialize(deserializer)?;
211.3 | ^^^^^^^^^ could not find `__private` in `serde`
211.3
211.3 error[E0433]: failed to resolve: could not find `__private` in `serde`
211.3 --> /usr/local/cargo/registry/src/index.crates.io-1949cf8c6b5b557f/alloy-consensus-0.15.11/src/transaction/envelope.rs:918:24
211.3 |
211.3 918 | serde::__private::de::ContentRefDeserializer::<D::Error>::new(&content);
211.3 | ^^^^^^^^^ could not find `__private` in `serde`
211.3
215.8 For more information about this error, try `rustc --explain E0433`.
215.8 error: could not compile `alloy-consensus` (lib) due to 2 previous errors
215.8 warning: build failed, waiting for other jobs to finish...
------
Dockerfile:25
--------------------
23 | # Build AntTP in release mode
24 | WORKDIR /build/anttp
25 | >>> RUN cargo build --release
26 |
27 | # Stage 2: Node.js + WebSocket server
--------------------
target anttp_server: failed to solve: process "/bin/sh -c cargo build --release" did not complete successfully: exit code: 101
1 Like
About to find my bed and I don’t know why that dependency is playing up, without digging deeply. Iirc, it is a dependency of a dependency, so something odd going on. Will look into it tomorrow.
The binaries on github work, it that helps.
3 Likes
I’ve seen the same serde error so I don’t think there’s much we can do except revert and wait for it to be fixed.
3 Likes
I had it trying to build dweb earlier today.
4 Likes
Did You try --locked?
1 Like
Yes. Same result.
2 Likes
I have it in a state where it builds and pushed that today, so it may be ok now.
4 Likes
Cool, will try tomorrow. 
4 Likes
We have anntp and dweb building OK from @traktions github.
Its Cloudflare SSL problems that are bugging us now.
1 Like
We’re just bypassing building the image ourself now, we are just getting the official docker image from @Traktion docker account.
The pro is that it avoids all our long building time. The con is that we are just avoiding this above error in lieu of this caddy cert issue that we are seeing. The other error above might still be in the docker image or not, won’t know till we get that far.
2 Likes
I’ve pushed my cargo.toml, which may help folks get the same build experience as me. It has fixed the build issue on GitHub, so hopefully it will for the above too.
I’ve also pushed a few other minor changes I was working on at the time (why not?).
4 Likes