Skip to content

spec 019: CLUSTER UPDATE EXTENSION keeps what it does not name - #20

Merged
VGSML merged 3 commits into
mainfrom
019-cluster-update-keeps
Oct 22, 2026
Merged

VGSML merged 3 commits into
mainfrom
019-cluster-update-keeps

Conversation

@VGSML

@VGSML VGSML commented Oct 22, 2026

Copy link
Copy Markdown
Contributor

Found by hugr-platform spec 010's review: the console's update form inherits this. Fixed at the owner's request.

Before: an update rewrote two things it did not name.

  • The repository. It was resolved again with no FROM, and the update's grammar took none. On a node trusting one repository the item silently moved to it. On a node trusting several, every update was refused.
  • The comment. It was written empty.

Now:

  • An update without FROM keeps the item's repository. That repository must still be trusted; otherwise the refusal names it and asks for FROM.
  • An update without COMMENT keeps the comment.
  • FROM on an update moves the item to another trusted repository.
  • An install is unchanged.

Test (test/cpp/test_acl_cluster_install.cpp):

  • with a second trusted repository, an update keeps the item's repository and its comment;
  • FROM an untrusted repository is refused and writes nothing;
  • FROM a trusted one moves the item;
  • an install still names its repository among several.

The test now takes postgres_scanner as DuckDB publishes it for this build's version and platform: DuckDB v2.0.0 is released, at extensions.duckdb.org/v2.0.0/<platform>. So every build runs the test, not only one that makes the scanner. It is skipped only when the extension cannot be fetched.

Locally: make test-cpp and test/sql/* all pass. docs/cluster.md gives the update's grammar.

🤖 Generated with Claude Code

https://claude.ai/code/session_01LdLs2iBQygBKtsApdH9Sxi

VGSML and others added 3 commits October 22, 2026 23:11
An update rewrote the item's repository (resolved again with no FROM, which its grammar did not take: moved on a node
trusting one repository, refused on one trusting several) and its comment (written empty). Now an update without FROM
keeps the item's repository (still one the node trusts), without COMMENT its comment; FROM moves it. Found by
hugr-platform spec 010's review (the console's update form).

The install test takes postgres_scanner as DuckDB publishes it for this build's version and platform (DuckDB v2.0.0 is
released): every build runs it, not only one that makes the scanner.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LdLs2iBQygBKtsApdH9Sxi
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LdLs2iBQygBKtsApdH9Sxi
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LdLs2iBQygBKtsApdH9Sxi
@VGSML
VGSML merged commit 93dfc34 into main Oct 22, 2026
5 checks passed
@VGSML
VGSML deleted the 019-cluster-update-keeps branch October 22, 2026 21:34
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