Repository navigation
feat(seed): make every seeded demo experiment public - #99
Merged
Merged
Conversation
Only the hotter-target safety experiment was public, so a public deployment (the HF Space) showed one demo without sign-in and hid the rest. - demo_audit_results.json: "Health vs RAG scenarios" is public too (the decision-model experiment already was). - seed_agentic_demo: the recorded agentic run goes into its own public experiment, "Agentic: auditing the Support Refund Assistant (recorded)"; a run loaded before this is grouped on the next seed. - audits 0013: a one-time data migration makes the seeded demo experiments public in workspaces seeded earlier. It only touches an experiment with a seeded name whose runs are all seeded demo runs; an experiment someone makes private afterwards stays private.
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
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.
Summary
Only one seeded demo experiment ("Safety: does a hotter target change the verdicts?") was public, so a public deployment such as the HF Space showed that one without sign-in and hid the rest. Now every seeded demo is public:
audits 0013) makes the seeded demo experiments public. It only touches an experiment with a seeded name whose runs are all seeded demo runs, so a user's own experiment, or a demo experiment someone added their own run to, stays private; and because it runs once, an experiment made private again later stays private.docs/deployment.mdnotes demo runs are viewable without sign-in.Testing
infra/tests/test_seed_demo.py: all 3 demo experiments public; the migration publishes earlier demo experiments and leaves a mixed one and a user's same-named one private.infra/tests/test_seed_agentic_demo.py: the agentic run is in a public experiment and its page loads anonymously; a run loaded before grouping is grouped once on the next seed.test_visualizer.py::test_time_budget_truncates) fails under-n autoand passes alone.makemigrations --checkclean,ruff check .clean.