Hi!
Thanks for your work on the Scalingo CLI, it's been very useful to the team i'm part of!
I'm using the cli to get a database backup doing scalingo --app my-app --addon postgresql backups-download
It triggers the download of the ~20GB database backup
and it fails at some point with the error
An error occurred:
download file: stream error: stream ID 1; INTERNAL_ERROR; received from peer
It can be after 3% or 95% (which is quite frustrating 😆 ) or anywhere in between
I'm fairly certain the root problem is one my end because of my internet connection
Error happens, that ok. Neither you or I have control over my internet connection
However, i notice that the 20GB download is always started over from scratch. And this is where i feel the Scalingo CLI could see an improvement.
Such large downloads are prone to errors, but it could be possible to resume the download from where it stopped with chunk encoding or other techniques
Would it be something the Scalingo CLI could consider?
Thanks!
Hi!
Thanks for your work on the Scalingo CLI, it's been very useful to the team i'm part of!
I'm using the cli to get a database backup doing
scalingo --app my-app --addon postgresql backups-downloadIt triggers the download of the ~20GB database backup
and it fails at some point with the error
It can be after 3% or 95% (which is quite frustrating 😆 ) or anywhere in between
I'm fairly certain the root problem is one my end because of my internet connection
Error happens, that ok. Neither you or I have control over my internet connection
However, i notice that the 20GB download is always started over from scratch. And this is where i feel the Scalingo CLI could see an improvement.
Such large downloads are prone to errors, but it could be possible to resume the download from where it stopped with chunk encoding or other techniques
Would it be something the Scalingo CLI could consider?
Thanks!