Run only computational experiments a project has attached #115
+252
−88
Conversation
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
Every project showed the registered computation form with all tools, and submitting a run attached its template to the project. Projects attach unit experiments, physical or computational, so: - The catalog (QE installations and the three templates) is registered at API startup, owned by the platform with no owning organization, so projects can attach them before any run exists. - Submitting no longer attaches anything; a tool whose template is not attached to the project is refused with 400. - The project page shows Registered computational experiments only when a computational experiment is attached, offering just those tools. - The help page explains attaching them under Unit Experiments. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QS1dbWTNbwqxXZUMEARjhm
- Catalog upserts return rows written by earlier versions to the platform: no owner, no owning organization, shared visibility. - One advisory lock serializes all catalog writes, so startup registration and submissions cannot deadlock on each other's rows. - Attaching or removing a computational experiment keeps the current tool and its inputs while it stays attached, and re-applies a ?tool= request that was refused before the tool was attached. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QS1dbWTNbwqxXZUMEARjhm
Keying the ?tool= request by the attached tools replayed it after any attachment change, clearing the user's inputs, and broke manual tool selection. Apply each request once, and retry only a request that was refused because its tool was not yet attached. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QS1dbWTNbwqxXZUMEARjhm
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QS1dbWTNbwqxXZUMEARjhm
Sign in
to join this conversation on GitHub.
1 participant
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.
After #111 every project page showed Registered computational experiments with all three tools, and submitting a run attached its template to the project. Projects attach unit experiments, physical or computational, so the attachment must come first.
Changes
ensure_catalog). They're owned by the platform (no owner, no owning organization, shared), so any project can attach them before a run exists. Rows written by earlier versions are returned to the platform on upsert.?tool=request refused because the tool wasn't attached is applied once it is.Review and tests
app/projects/[id]/page.tsx(set-state-in-effectaround line 297) is already on dev.🤖 Generated with Claude Code