You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: