temporalio / temporalio/features
SDKs should expose Nexus request deadline
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
Describe the solution you'd like
All SDKs should make the "request deadline" available in the Nexus context. Note, this is intentionally deadline and not timeout (even though it's derived from request timeout header) because deadline is more useful. Ideally this is called "request deadline" and not just "deadline" which can ambiguously mean operation deadline or fetch result deadline.
Per-SDK Tickets
Nexus SDK
- Go - Already in context
- Java - Already exists
- TypeScript - https://github.com/nexus-rpc/sdk-typescript/issues/27
- Python - https://github.com/nexus-rpc/sdk-python/issues/29
- .NET - https://github.com/nexus-rpc/sdk-dotnet/issues/13
Temporal SDK
- Go - Already in context
- Java - TODO
- Core - TODO - needs to expose deadline to langs (already has request-timeout parser logic)
- TypeScript - TODO - after Core
- Python - TODO - after Core
- .NET - TODO - after Core
- Ruby - TODO - no Nexus yet
-
PHP - TODO - no Nexus yet - Temporal CLI - N/A
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Core request-timeout parser logic mentioned in the issue, then review the unchecked Temporal SDK entries, beginning with Java and Core. The linked per-SDK tickets show completed Nexus SDK work and remaining language-specific scope. Done means exposing a clearly named request deadline in the Nexus context for each applicable Temporal SDK.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, go, java, python, ruby, typescript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100