Report destination guard: the 'report publish' anti-vacuity half is satisfiable by interface spellings of remote such as <remote>

Open
  • Is something wrong?
#2,206 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
52/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript
Domain
testing

Research direction

Read test/core/cli-consistency-gate.test.js around lines 693-699 and inspect how report-publish text is blanked before the vacuity check. Run the relevant consistency-gate test; done means probe N7 fails, A5 still fails, and the shipped tree stays green. The issue says this is backlog-only unless a human delegates it.

Written by the indexing model from the issue text.

Description

Source: #2195 at ffc56a5d71f5cc51dd32fb9da5b3fa85f8787665
Location: test/core/cli-consistency-gate.test.js:693-699
Severity: low

Evidence

Probe N7 from PR #2195 round 2: delete every real destination word from the report publish summary and body but leave '--to ' and the guard stays green (28/28), at bcaca550 too, so pre-existing. Only the exact spellings '--remote' and 'hyp remote ...' are blanked; '', '--no-remote', 'hypaware remote list', and 'Hyp remote list' survive blanking (the blanking is case-sensitive and anchored on the literal 'hyp ') and spuriously supply the remote family to the vacuity check.

Why deferral is safe

Same class as finding 4: the vacuity assertion is the guard's own hardening beyond #2189's contradiction requirement, and round 1's vouching that the publish half 'does still bite' was conditional on prose shape, not unconditional. The contradiction class the issue names is caught regardless. Recording it keeps finding 4's deferral scope complete.

Acceptance condition

The blanking covers the interface spellings ('', '--no-remote', 'hypaware remote ...', case-insensitive command prefix) before the vacuity check, so probe N7 goes red while A5 stays red and the shipped tree stays green.

Review preference; backlog only. A human may explicitly delegate it with neutral:fix.

Dominant language
JavaScript
Stars
11
Forks
0
Avg merge
2h 49m
Merged PRs (30d)
302

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from hyparam/hypaware

All issues in hyparam/hypaware

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.