Francesco Guardiani
Francesco Guardiani
@tillrohrmann this is roughly the spec for the ad-hoc UI endpoint ```rust pub struct BatchOperationRequest { pub invocations: Vec } pub struct BatchOperationResult { pub succeeded: Vec, pub failed: Vec...
Good part of this was fixed in schemars 1.0, see #3766
@tillrohrmann shall i address the comment you made in my pr here directly? Or i do it on my pr and then you rebase here?
This is ready for an initial pass. The test is failing because i still didn't figure out how to do the exclusion properly :shaking_face: but the exclusion is legit
~~TODO: in the state machine `init_journal`, better to also init there the journal using journal v2. this sorts out the situation where users update with scheduled invocations.~~
Fixed the problem with exclusions!
did some manual testing locally, primarily around scheduled invocations, first disabling then enabling, and viceversa. So far everything seems to work as expected.
The fundamental issue here is that the PinnedDEploument doesn't take part of the retry shield logic of the invoker, so it needs to be sent atomically together with the first...
> Aren't we only sending a EffectKind::PinnedDeployment message to the partition processor if there is a JournalEntry to be sent to the partition processor Yes but those are sent with...