bregctl package: refuse an empty successor at build time
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 70/100
Research direction
Look at the bregctl package command's code, likely in a src/cli/package.rs or similar module. Find where it builds and signs a successor package. Check the change plan against the predecessor for emptiness, and integrate the same error message used by apply.package.empty_plan. Run existing tests for the package command to ensure the new check works.
Written by the indexing model from the issue text.
Description
Gap
After #1353, bregctl apply reports a successor package with an empty change plan as apply.package.empty_plan instead of a binding refusal. bregctl package still builds and signs such a successor, so the operator only finds out when they apply it.
Request
Have bregctl package refuse, or at least warn about, a successor whose change plan against its predecessor is empty, using the same wording as apply.package.empty_plan. Check first whether any legitimate workflow needs an empty successor (for example, re-signing or re-keying only) before making this a hard refusal.
Follow-up from #1353.
- Dominant language
- Rust
- Stars
- 2
- Forks
- 0
- Avg merge
- 4h 26m
- Merged PRs (30d)
- 152
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from registrystack/registry-stack
-
bug github_actions
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
registrystack/registry-stack#1393 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
registrystack/registry-stack#1383 ·
-
area:breg enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
registrystack/registry-stack#1379 ·
-
area:casework documentation
Difficulty 1/5 Under an hour Newbie friendliness 90/100
registrystack/registry-stack#1369 ·
-
area:casework bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
registrystack/registry-stack#1368 ·
All issues in registrystack/registry-stack
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
longbridge/gpui-kit#3223 ·
-
bug engine
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
rocky-data/rocky#2181 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
oasisprotocol/oasis-sdk#2523 ·
-
[indexer] [QA] Add a focused test for the new NonRetryableError / assertSocketAlive() behavior. Openbot:ai-assisted component:indexer QA-roadmap status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
midnightntwrk/midnight-indexer#1557 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Luminous-Dynamics/mycelix#3069 ·