-
Notifications
You must be signed in to change notification settings - Fork 47
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
Request of updating the rust toolchain version #1000
Comments
Btw, I'm not saying 0.9.28 parachain-node + 0.9.26 worker will work, in fact, I still get some crate version conflict in between, but that's another story |
Yeyy. Issue number 1000 🥳 The rust version is currently blocked by apache/incubator-teaclave-sgx-sdk#386 (comment), but usually they keep to their promise. So we can expect an update there soon. Regarding your issue: I believe we've seen that before. Is it not fixable by manually downgrading the |
I deleted the above comments; v0.9.28 is |
Thanks both 👍
I don't think it will help, as it's not about the crate version (in fact, we don't have such crate in parachain or substrate), it's about the compiler features, and I just noticed you did similar stuff here, and I had to patch Anyways 0.9.28 parachain-node + 0.9.26 worker doesn't seem to compile together due to conflict crate versions, something like:
Never mind I saw the 0.9.28 PR is round the corner, we'll go v0.9.28 |
They have not yet updated... I did a follow-up comment. apache/incubator-teaclave-sgx-sdk#386 (comment) Let's hope for the best. |
Finally teaclave has published an update, see #1074. |
Problem:
the current toolchain (
nightly-2022-03-10
) seems a bit old to compilepolkadot-v0.9.28
cumulus dependencies. It complains about "unstable library feature" when compiling the worker withmy-node-runtime
pointing tolitentry-parachain-runtime
, which is sitting atpolkadot-v0.9.28
:I double-checked the crate
sc-transaction-pool
: it comes from our parachain only (fromcumulus-relay-chain-interface
), not in integritee-node, so you probably won't have such a problem.For now I can work around this by forking substrate and patching it in worker TOML, but still as polkadot evolves it could grow to some point where patching is too much and we'd need a newer toolchain.
However, this might not be so easy though: it would require newer toolchain support from sgx-* crates. As far as I tested, simply changing the TC to a newer version wouldn't work out of the box.
If you have better ideas, please let me know!
Edit: oops I accidentally took away the 1000th issue, sorry 😂
The text was updated successfully, but these errors were encountered: