export.py missing --progress
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 48/100
Research direction
Start with python/export.py and inspect the comment block that lists --progress alongside the argument-handling code. Compare the documented option with the options currently implemented. Done means the example's --progress behavior matches its documentation, or the documentation no longer advertises an unavailable option.
Written by the indexing model from the issue text.
Description
In the Python Examples , export.py, is showing --progress argument in comment block as an available option but it is not implemented
https://github.com/splunk/splunk-app-examples/blob/master/python/export.py
- Dominant language
- JavaScript
- Stars
- 155
- Forks
- 84
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
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 splunk/splunk-app-examples
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
splunk/splunk-app-examples#67 · 1 comment · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
splunk/splunk-app-examples#65 · 1 comment · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 32/100
splunk/splunk-app-examples#48 · 2 comments ·
All issues in splunk/splunk-app-examples
Similar issues
-
area: bazaar bug complexity: medium
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
accensa/x402-facilitator-stellar#779 ·
Maintainers usually reply within 1 day
-
could-have reliability
Difficulty 1/5 Under an hour Newbie friendliness 88/100