Bigna Härdi

Any idea what this errors means? https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2842595 ``` error: failed to run custom build command for `substrate-test-runtime v2.0.0 (/builds/parity/mirrors/substrate/test-utils/runtime)` [2023-05-16 09:02:26] note: To improve backtraces for build dependencies, set the...

> Seems that we need one more origin/master merge due to little bug that was fixed in github flows: https://github.com/paritytech/substrate/pull/14161 Finally passed 👍

@bkchr thanks a lot for the tip! Honestly, didn't expect that 🥳

When we change to `is_final` instead of the current expected one, we shouldn't forget about the future status. So it probably makes sense to do https://github.com/scs/substrate-api-client/issues/295 in the same swoop.

I've looked into that some - and I have to agree with [#551](https://github.com/paritytech/subxt/issues/551) about the problem with the subscription. ### Scenario: Let's say the client has subscribed for runtime upgrades...

Yes, I saw that. But as far as I understood, that's for the cli version. For the GitHub Action one, I didn't find that option. Ofc, one could build the...

I see. Didn't look too deeply into that. Nonetheless, something like https://github.com/integritee-network/worker/issues/970#issue-1360604404 was possible. Not sure if that's verifiable with the metadata, but I think it should be worth it...

I suggest timeboxing this task to 8h. If there's a promising lead after investigation, it should be done in a different task.

I agree in general, but before doing all this work, we should probably make sure that a local nonce cache does make sense. At least theoretically. E.g. find out if...

Yes. I was just thinking about the separation of creating and sending extriniscs. The creation is done without the api, while the sending is done with it. For a cache,...