change way of reading csv file with analysis.py
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- build-system, data
Research direction
Start with analysis.py and inspect how its first and second arguments are parsed and how the CSV file is opened; then review how Bazel currently invokes it. Define a clearer input interface that works with Bazel, and verify that the analysis still reads the intended CSV file.
Written by the indexing model from the issue text.
Description
The way now is to have something as a first argument and the file to read as a second. There needs to be a more meaningful way and a good use with bazel
- Dominant language
- C
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. 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 es-ude/ElasticNodeMonitoring
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
es-ude/ElasticNodeMonitoring#5 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
All issues in es-ude/ElasticNodeMonitoring
Similar issues
-
feature request
Difficulty 1/5 Under an hour Newbie friendliness 86/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
FujiNetWIFI/fujinet-firmware#1730 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
category:port-update
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 2 days