We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
See https://github.com/litentry/litentry-parachain/actions/runs/5373385699/jobs/9747713246
Is it because of two low polkadot version, combined with the fact that upstream has been using stable rustc?
See paritytech/substrate#13580
Or is it because srtool is using a too new rustc version? (1.70) Maybe we can solve it by downgrading the srtool image version.
1.70
It needs a bit of research. The goal is we can successfully build wasm with srtools and the built wasm can be used for runtime ugprade.
✔️ Please set appropriate labels and assignees if applicable.
The text was updated successfully, but these errors were encountered:
Updates?
Sorry, something went wrong.
https://github.com/litentry/litentry-parachain/actions/runs/5373385699/jobs/9747713246
Unable to run the srtools locally on my machine, I will be forking and testing the GHA
felixfaisal
Successfully merging a pull request may close this issue.
Context
See https://github.com/litentry/litentry-parachain/actions/runs/5373385699/jobs/9747713246
Is it because of two low polkadot version, combined with the fact that upstream has been using stable rustc?
See paritytech/substrate#13580
Or is it because srtool is using a too new rustc version? (
1.70
) Maybe we can solve it by downgrading the srtool image version.It needs a bit of research.
The goal is we can successfully build wasm with srtools and the built wasm can be used for runtime ugprade.
✔️ Please set appropriate labels and assignees if applicable.
The text was updated successfully, but these errors were encountered: