Expose Function invocation deadlines - #306
Merged
Merged
Conversation
Narrow the get_deadline() accessor so only two expected states return None: vercel_runtime absent, or an older runtime without the accessor. Broken installs and runtime bugs now surface instead of reading as a missing deadline.
nsidnev
approved these changes
Aug 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
vercel.functions.get_deadline()as the public api for vercel/vercel-internal#509.Python parity with Node's:
Python
Node's runtime bridge reads
x-vercel-internal-deadlineinto request context, thengetDeadline()parses it. Python mirrors this with a runtimeContextVarand a lazy SDK accessor. Older runtimes and non-Vercel environments returnNone.Rusty derives the RFC 3339 header from
maxDuration. Header delivery is implemented in vercel/functions#3533