Disable sensors that send results quicker than 30s/minute
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
Research direction
The issue provides no files, tests, or entry points. Start by locating where the REST API receives sensor results and how sensor reporting intervals are tracked; clarify the intended behavior for sensors reporting more often than every 30 seconds or once per minute. Done means the agreed behavior is implemented and covered by tests.
Written by the indexing model from the issue text.
Description
This issue has no description.
- Dominant language
- Python
- Stars
- 6
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 developmentseed/dustduino-server
-
Heroku build Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
developmentseed/dustduino-server#19 · 1 comment ·
-
Captcha Open
Difficulty 5/5 Over a week Newbie friendliness 20/100
developmentseed/dustduino-server#11 · 1 comment ·
-
add tests Open
Difficulty 5/5 Over a week Newbie friendliness 15/100
All issues in developmentseed/dustduino-server
Similar issues
-
essnmx good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
[Feature] 奇物选择添加优先级 Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
syfoud/Simulated_Scepter#174 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Giskard-AI/giskard-oss#2840 · 1 comment ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Openarea: repo bug perceived difficulty: 2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yeti-platform/yeti#1380 ·