cursor.decoder.released logs Attr.OPERATION (hyp_operation) while its cursor.decoder.started counterpart logs a literal operation key
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 48/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
- Domain
- observability
Research direction
Read hypaware-core/plugins-workspace/cursor/src/listener.js:76 and hypaware-core/plugins-workspace/cursor/src/native_decoder.js:110, then compare the event attributes with listener.js:134 and :143. Done means the started/released pair uses the same operation-key convention and released carries component and status; the issue says this is backlog work and needs explicit delegation.
Written by the indexing model from the issue text.
Description
Source: #2097 at cd0d42d4ff03dc3c4e6439f8cef9dc6f43d76212
Location: hypaware-core/plugins-workspace/cursor/src/listener.js:76; hypaware-core/plugins-workspace/cursor/src/native_decoder.js:110
Severity: cosmetic
Evidence
Verified at head: listener.js:76 emits cursor.decoder.released with { [Attr.OPERATION]: 'recovery.read' } and Attr.OPERATION is 'hyp_operation' (src/core/observability/attrs.js:102), while native_decoder.js:110 emits cursor.decoder.started with the literal { component: 'plugin.cursor', operation: 'recovery.read' }. The spawn/release pair cannot be filtered or correlated on one attribute key, and released carries no component and no status unlike its neighbours at listener.js:134 and :143.
Why deferral is safe
Cosmetic observability inconsistency on the isolated deflake commit; no behavior is wrong and the test that consumes the line matches on the event name, not the attributes. Each file follows its own local convention, so either side could be called the odd one out; aligning them is cleanup, not a fix this PR owes.
Acceptance condition
The cursor.decoder.started / cursor.decoder.released pair shares one attribute-key convention (both Attr.* or both literal), and released carries component and status like its neighbours; a grep of the two lines shows the same operation key.
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)
- 297
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
- 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 hyparam/hypaware
-
docs: ollama.md says --source ollama adds to an existing install, but without --force it refusesOpen
Difficulty 2/5 Under an hour Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
report_commands.js runtime output still says 'server' in four places; one names the destinationOpen
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
Maintainers usually reply within 1 day
All issues in hyparam/hypaware
Similar issues
-
Handle HTTP errors when downloading release binariesPossibly taken @mugenkyou claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
neutralinojs/neutralinojs-cli#468 ·
Maintainers usually reply within 1 day
-
area:ci priority:p0 type:chore
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
lucacasanova/homedeck#2 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
terser/html-minifier-terser#242 ·
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
MustacheCase/zanadir#516 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
stylelint-scss/stylelint-config-standard-scss#297 · 1 comment ·