d3049eb97b
## What Add `TaskQueueKind` to the `NexusTask` token proto so the frontend can pass the correct kind to matching on `RespondNexusTaskCompleted`/`Failed`, instead of hardcoding `TASK_QUEUE_KIND_NORMAL`. ## Why To distinguish internal nexus invocations from user facing ones. [#10141](https://github.com/temporalio/temporal/pull/10141) switched `nexus_task_requests` `is_internal` detection from task queue name prefix to `TaskQueueKind`, but the frontend hardcodes `NORMAL` when constructing the matching request for Respond operations because the token didn't carry the kind. This means `is_internal` is always `false` for Respond on worker-commands queues. ## How did you test it? Unit tests: - Frontend handler: `RespondNexusTaskCompleted` and `RespondNexusTaskFailed` preserve `TaskQueueKind` from token (WORKER_COMMANDS preserved, NORMAL preserved, UNSPECIFIED defaults to NORMAL) - Matching engine: `PollNexusTaskQueue` sets the correct `TaskQueueKind` in the serialized task token for both NORMAL and WORKER_COMMANDS partitions - Backwards compatible: old tokens without the field default to `TASK_QUEUE_KIND_UNSPECIFIED`, treated as `NORMAL` 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Temporal—durable execution platform
Introduction • Getting Started • Contributing • Temporal Docs • Temporal 101
Introduction
Temporal is a durable execution platform that enables developers to build scalable applications without sacrificing productivity or reliability. The Temporal server executes units of application logic called Workflows in a resilient manner that automatically handles intermittent failures, and retries failed operations.
Temporal is a mature technology that originated as a fork of Uber's Cadence. It is developed by Temporal Technologies, a startup by the creators of Cadence.
Getting Started
Download and Start Temporal Server Locally
Execute the following commands to start a pre-built image along with all the dependencies.
brew install temporal
temporal server start-dev
Refer to Temporal CLI documentation for more installation options.
Run the Samples
Clone or download samples for Go or Java and run them with the local Temporal server. We have a number of HelloWorld type scenarios available, as well as more advanced ones. Note that the sets of samples are currently different between Go and Java.
Use CLI
Use Temporal CLI to interact with the running Temporal server.
temporal operator namespace list
temporal workflow list
Use Temporal Web UI
Try Temporal Web UI by opening http://localhost:8233 for viewing your sample workflows executing on Temporal.
Repository
This repository contains the source code of the Temporal server. To implement Workflows, Activities and Workers, use one of the supported languages.
Contributing
We'd love your help in making Temporal great.
Helpful links to get started:
- work on or propose a new feature
- learn about the Temporal Server architecture
- learn how to build and run the Temporal Server locally
- learn about Temporal Server testing tools and best practices
- join the Temporal community forum and Slack