You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(init): reset timed-out init synchronously and fail provisioning on extended-init timeout
Two fixes to the init-timeout case in the init-await switch:
1. The reset of a timed-out init now runs synchronously BEFORE signaling
ready. Reset's cleanup (Clear/Release in rapidcore.Server.Reset) releases
the current reservation, so running it concurrently with the first
invoke's Reserve() raced that invoke's reservation and could cancel it
mid-flight, returning an empty result while the suppressed init was
still running. The reset cannot deadlock on the unconsumed init failure:
awaitInitCompletion acks rapid before the (still pending) initFailures
channel send, which the invoke path consumes later.
2. The suppressed-init retry model only applies to on-demand functions.
Provisioned concurrency / Managed Instances environments that exceed
their extended init window now fail provisioning via /status/error
(AWS fails the provisioning operation) instead of signaling ready and
inevitably re-running the long init into the shorter invoke timeout.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
0 commit comments