Orders SDK Progress Bar not Wrapped in Jupyter Notebook
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- jupyter-notebook, python
- Domain
- developer-experience
Research direction
Reproduce the Orders SDK download in a Jupyter notebook with a long output path and inspect the progress-bar behavior. Done means the full progress information remains visible regardless of filename length; the payload names no source file or test, so those would need to be located.
Written by the indexing model from the issue text.
Description
Expected behavior
When I download an order using the Orders SDK in a jupyter notebook, I should be able to see the download progress bar (regardless of the filename lengths, especially since this is not something we can specify) to check how far my download has progressed.
Actual behavior (describe the problem)
With the current behavior, I'm not able to see the progress due to the filename length, and it is cut off. This is a problem because I can't tell how far my download has progressed or how much time might be remaining. This is specifically an issue within jupyter notebooks. I've included a screenshot of what this currently looks like on my machine
Workaround
One workaround is not specifying the output directory (as this lengthens the path name), but I need the images ina specific directory so this is not really a workaround.
- Dominant language
- Python
- Stars
- 300
- Forks
- 100
- Avg merge
- 9d 22h
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the 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 planetlabs/planet-client-python
-
better-testing
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
planetlabs/planet-client-python#1110 ·
-
FeaturesClient list_items does not support filteringPossibly taken A pull request linked to this issue is open or already merged. Openproposal
Difficulty 3/5 1-2 days Newbie friendliness 65/100
planetlabs/planet-client-python#1221 ·
-
FeaturesClient does not implement Update FeaturePossibly taken A pull request linked to this issue is open or already merged. Openproposal
Difficulty 3/5 1-2 days Newbie friendliness 57/100
planetlabs/planet-client-python#1214 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 48/100
planetlabs/planet-client-python#1197 · 1 comment · 1 reaction ·
-
Quota APIMay be free again @asonnenschein claimed this 417 days ago, and no pull request is open. Openai-claude
planetlabs/planet-client-python#1191 · 1 comment · 1 assignee ·
All issues in planetlabs/planet-client-python
Similar issues
-
json_params_matcher fails on falsy top-level JSON primitives (0, False, "")Possibly taken @mayureshsonawane17 claimed this today. OpenWaiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
bojieli/ai-agent-book#1169 ·
Maintainers usually reply within 1 day
-
priority:low ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
OpenHands/extensions#738 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
micronaut-projects/micronaut-core#13677 ·
Maintainers usually reply within 1 day