Repository navigation
Document separate workflow and activity worker processes - #162
Merged
Merged
Conversation
This was referenced Oct 19, 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
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.



Delivered
Merged as
0ed44b85467dd4ff7989e158ffd2f834fdd08485, with the same treeb23aad832cdca6843df43f5043725424b4e95feaas reviewed candidate2310f1d.All 15 candidate checks and all 15 fresh-main checks passed.
The guide is
published. Its deployment audit identifies this merge and SDK 2.6.0. Website
#271 adds the shared English/Ukrainian links. All four canonical pages were
read back after deployment. Issue #161 is delivered.
Changes
Adds a runnable example with workflow-only and activity-only processes, distinct
worker IDs, independent slots, explicit activity queues, a deliberate retry and
signal-driven shutdown. The portal guide covers routing observations, downstream
budgets, async blocking, local activities, sessions and sticky history.
No SDK runtime, version or dependency constraint changed.
Verification
Normally installed PyPI SDK 2.6.0, Python 3.12 and published Server 2.9.5
at immutable image index
sha256:f5771101fc55a3e1e8f8bd572beb1d57f593c05db5e5760f0773f75a96fe7ebb:retried shared queue and retried distinct activity queue. They check exact
results, handler types, queues, attempt numbers, worker identity and clean
SIGTERM exits with registrations removed.
CLI, four workflow slots/two activity slots and
hello, world. The finalworker roster was empty. The start process executes neither handler.
reports 42 passed and 49 skipped. Its log explicitly shows all three new
cases passed. This is separate from the normally installed wheel checks.
Python versions passed. The Sonar PR gate passed with zero open/confirmed
findings and 0% new duplication under unchanged settings.
Shutdown qualification covers completed examples and idle polls. The first
local setup selected an absent database-cache table and failed readiness before
workflow admission; the corrected setup uses Redis. Successful SQLite cases
include transient HTTP 503 responses recovered by the SDK's existing transport
policy. No lock cause is established.
All local test resources, dependencies, database and raw output were removed at
20:35:26 UTC. Merged worktrees, branches and posting scratch were retired at
20:45 UTC. Both remote heads return 404. Borrowed images and foreign resources
were preserved.