Skip to content

chore(core): Optimize stack update scheduling by predicting upcoming state changes #1295

chore(core): Optimize stack update scheduling by predicting upcoming state changes

chore(core): Optimize stack update scheduling by predicting upcoming state changes #1295

Triggered via pull request January 12, 2026 03:38
Status Failure
Total duration 1m 18s
Artifacts

integration.yml

on: pull_request
Check whether the written test passes normally
1m 12s
Check whether the written test passes normally
Check the TypeScript typings
1m 2s
Check the TypeScript typings
Check the status of Changesets
1m 16s
Check the status of Changesets
Fit to window
Zoom out
Zoom in

Annotations

10 errors
Check the TypeScript typings
Process completed with exit code 1.
Check the TypeScript typings
Argument of type 'Mutex' is not assignable to parameter of type '{ scheduler: Scheduler; }'.
Check the TypeScript typings
Expected 0 arguments, but got 1.
Check the TypeScript typings
Argument of type '{ initialEvents: DomainEvent[]; changePublisher: ScheduledPublisher<{ effects: Effect[]; stack: Stack; }>; updateScheduler: SwitchScheduler; }' is not assignable to parameter of type '{ changePublisher: Publisher<{ effects: Effect[]; stack: Stack; }>; updateScheduler: SwitchScheduler; updateErrorReporter: (error: unknown) => void; initialEvents: DomainEvent[]; }'.
Check the TypeScript typings
Property 'estimatedTransitionEnd' does not exist on type '{}'.
Check the TypeScript typings
Parameter 'b' implicitly has an 'any' type.
Check the TypeScript typings
Parameter 'a' implicitly has an 'any' type.
Check the TypeScript typings
Cannot find module '../projectToOngoingTransitions' or its corresponding type declarations.
Check whether the written test passes normally
Process completed with exit code 1.
Check the status of Changesets
Process completed with exit code 1.