Skip to content

feat: give log requests their own warning - #9630

Draft
atlaie wants to merge 1 commit into
devfrom
atlaie/enclave-msg-log-request-warning
Draft

atlaie wants to merge 1 commit into
devfrom
atlaie/enclave-msg-log-request-warning

Conversation

@atlaie

@atlaie atlaie commented Nov 13, 2026

Copy link
Copy Markdown
Collaborator

A log request no longer reuses the approval warning, which called it an approval and said to approve only reviewed code although the job had already run. It now has its own warning, which names the readers:

This request lets ds@x.com read stderr.txt, as the job wrote it. The job code can print private data into it. To read it first, request it with no readers: the enclave then releases it to the data owners only.

With no readers (the data owners), the last sentence is left out. Message only; no behaviour change.

One of five small PRs from the 13 Nov enclave test; each merges cleanly with the others and with #9576.

Asana: https://app.asana.com/0/0/1220519894181017/f

🤖 Generated with Claude Code

No rush: after the release.

A log request no longer reuses the approval warning. Its warning names
who will read the log and, when the readers are named, says to request
it with no readers first to read it before them.

Messages, display and docstrings only; no behaviour change.
Asana: https://app.asana.com/0/0/1220519894181017/f

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant