Repository navigation
Conversation
CyMule
changed the title
|
@cubic-dev-ai review |
@CyMule I have started the AI code review. It will take a few minutes to complete. |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
All reported issues were addressed across 4 files
Shadow auto-approve: would not auto-approve because issues were found.
View guided diff | Re-trigger cubic
|
@cubic-dev-ai review |
@CyMule I have started the AI code review. It will take a few minutes to complete. |
There was a problem hiding this comment.
No issues found across 4 files
Shadow auto-approve: would not auto-approve. This PR does not meet the repository auto-approval settings.
View guided diff | Re-trigger cubic
CyMule
changed the title
There was a problem hiding this comment.
No issues found across 4 files
Shadow auto-approve: would not auto-approve. This PR does not meet the repository auto-approval settings.
View guided diff | Re-trigger cubic
There was a problem hiding this comment.
0 issues found across 2 files (changes from recent commits).
Shadow auto-approve: would not auto-approve. This PR does not meet the repository auto-approval settings.
View guided diff | Re-trigger cubic
|
Closing without merging. These request-scoped identity and scratch-directory helpers won't be added to this package, since its request-scoped helpers are being retired rather than extended. |
The SDK exposes
current_invocation_identity()andinvocation_scratch_dir()for request-scoped plugin identity and scratch paths. This lets a long-lived plugin process serve concurrent invocations while keeping their files and attribution separate.A bound invocation context is authoritative, including fields it leaves absent. Without a context, identity falls back to the process environment and the scratch root is unchanged. With a context, the helper returns a sanitized
job/node/invocationpath.Validation: 211 SDK tests and Ruff, covering concurrent calls, safe paths, batch correlation and streaming context retention.
Package metadata and changelog specify stable
0.1.1. After merge, publish a GitHub release tagged0.1.1from the merged commit;.github/workflows/release.ymlbuilds and publishes the package to PyPI.