Skip to content

feat!: standardize remote execution on JSON - #677

Closed
KAJdev wants to merge 1 commit into
mainfrom
zeke/json-remote-contract
Closed

KAJdev wants to merge 1 commit into
mainfrom
zeke/json-remote-contract

Conversation

@KAJdev

@KAJdev KAJdev commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

Queues and tasks share a JSON-only contract for arguments, results, and stream chunks. Shared validation rejects Python-only values, non-string keys, and non-finite numbers consistently across live, deployed, and same-worker calls.

Remote responses use explicit JSON decoding, and serialization failures reach callers as errors. Null and empty results retain their values through local HTTP and worker execution.

The companion runtime requires this SDK’s shared protocol helpers. Publish the compatible SDK before deploying that runtime.

@KAJdev
KAJdev marked this pull request as draft November 3, 2026 00:14
@KAJdev KAJdev closed this Nov 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant