There is a series of projects I’m developing for work in Rust, but I’ve run into a bit of a complex problem.
(skip to the last paragraph if you want to skip the context)
The dependency chain looks like this:
Customer Facing Project ←
NPM module ←
xquery interpreter ←
Each of these projects has other dependencies, but this chain is the important part for this post.
The NPM module is based on
neon, which provides Node.JS bindings for Rust code.
The interpreter and parser are written in Rust.
On the build server, when the slave is trying to builld the CFP, all goes well throughout the chain until
neon needs to update its dependency on the interpreter, which is stored on a separate git server that uses a certificate.
For this updating, neon uses
cargo, as indicated by these lines of the log:
neon info running cargo neon info cargo build --release Updating git repository `https://[redacted]/sbr-xquery-interpreter-api` error: failed to load source for a dependency on `sbr-xquery-interpreter-api`
It’s because neon uses cargo that I’m posting here rather than creating an issue on the neon github page, so all of the above is just for context.
My question is, given that
cargo has an issue with actually pulling in the
sbr-xquery-interpreter-api dependency, could it be that cargo has a problem with accessing the certificate? And if so, what can I do about it?