Silver drops Phoenix DeviceEnable (string in bronze)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 77/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- python
- Domain
- data-engineering
Research direction
Start with src/flashpoint/semantics/silver.py and the P4 spike table in p4-views-and-reports design.md; trace how DeviceEnable values become silver value and are filtered. Add the stated Enabled/Disabled mapping, a Q7 corpus test, and a DERIVE_VERSION bump. Done means the test confirms enabled and disabled states are retained as 1 and 0.
Written by the indexing model from the issue text.
Description
Found during the P4 spike (openspec change p4-views-and-reports, design.md spike table).
Problem: Phoenix 6 DeviceEnable is a string in bronze (v_str), but the silver query builds value as COALESCE(v_f64, CAST(v_bool AS DOUBLE), CAST(v_i64 AS DOUBLE)) (src/flashpoint/semantics/silver.py). Every device_enable row is NULL and gets dropped by WHERE d.value IS NOT NULL, so silver has no per-device enable state even though METRICS maps it.
Impact: per-device enabled time can't be measured; gold/unit_usage.enabled_s uses the robot's enable intervals from framing instead.
Fix sketch: map the known DeviceEnable strings (e.g. Enabled/Disabled) to 1/0 in the silver query, with a corpus test on Q7; bump DERIVE_VERSION.
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- Avg merge
- 18h 37m
- Merged PRs (30d)
- 15
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 IgniteRobotics/flashpoint
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
IgniteRobotics/flashpoint#45 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
IgniteRobotics/flashpoint#44 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
IgniteRobotics/flashpoint#43 ·
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 1/5 Under an hour Newbie friendliness 85/100
IgniteRobotics/flashpoint#12 ·
Maintainers usually reply within 1 day
-
tools/update-owlet-manifest.py ignores --help and starts downloadingMay be free again @yoveneim claimed this 11 days ago, and no pull request is open. Openbug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
IgniteRobotics/flashpoint#11 · 1 comment ·
Maintainers usually reply within 1 day
All issues in IgniteRobotics/flashpoint
Similar issues
-
Backend issue lists report in-patch warnings and out-of-patch errors as not publishablePossibly taken @RaphaelFakhri claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
mozilla/code-review#3794 ·
Maintainers usually reply within 1 day
-
[oblt-aw][autodoc] Update docs that still describe the security registry as emptyPossibly taken @github-actions claimed this today. Open
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
[Bug] adb backup script reports "Done" & exits 0 when the backup failsPossibly taken @bhattmanthan claimed this today. Openrequest-issue-assignment
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
OWASP/mastg#4034 · 5 comments ·
Maintainers usually reply within 1 day
-
agent-ui bug p2
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
correction metadata
Difficulty 1/5 Under an hour Newbie friendliness 72/100
acl-org/acl-anthology#10768 · 1 comment ·
Maintainers usually reply within 1 day