robert

> One thing I noticed is that if a request recipient is dropping requests, the requests keep getting sent out, seemingly perpetually (I haven't dug into whether there's a limit...

Just to chime in on bikeshedding: `catch in { ... }` flows pretty nicely.

The only thing that's lacking IMO is documentation. I'm in agreement that the externalities setup is a little tedious/mysterious for testing of runtime modules. I can also see some level...

> Yes this should only ever change on session boundaries, but we should not put it into SessionInfo directly because of https://github.com/paritytech/polkadot-sdk/issues/734. Implementing session buffering for many storage items is...

what I actually think is happening is probably not an issue with Cumulus, but rather that a) the test somehow ends up building a relay chain where one of the...

cc @ordian

The same behavior is observable, for instance in #7627 ``` ERROR tokio-runtime-worker test_parachain_undying_collator: Unable to build on top of HeadData { number: 3, parent_hash: [184, 32, 130, 93, 163, 77,...

> "Okay. The main thing we can test right now is that the collators work when the zombienet runtime doesn't have asynchronous backing enabled. > Soon we should be able...

One thing I was toying around with locally was having a feature flag for `enable-staging-api` in the Rococo and Westend runtimes. Unfortunately, it won't compile without pretty significant changes to...

> It works if you copy-paste the whole api block: Yeah, that's the simplest brute-force approach. Another option would be to have the main feature branch NOT implement the new...