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
{{ message }}
This repository has been archived by the owner on Aug 12, 2024. It is now read-only.
Some pictures (in my experience it has only happened on profile pictures) https://image.production.journal-api.lapse.app/image/upload/q_100//xxxx/xxxx.jpg will throw a error 500, this can be remedied by adjusting the parameters of the API call, for example using: https://image.production.journal-api.lapse.app/image/upload/,//xxxx/xxxx.jpg doesn't throw an error. I think the best fix would be to default throws parameters to a simple , and then if the user specifies specific parameters adjust it then. It also might be possible to default it to q_65 which is what the Lapse app uses.
Specifically I found issues with the q parameter, with an image I was testing with I was getting issues when using q_100 but when I bumped it down to q_50 I didn't seem to get any errors.
Before fixing this I want to perform more tests to try to determine the cause of the issue,
The text was updated successfully, but these errors were encountered:
Some pictures (in my experience it has only happened on profile pictures)
https://image.production.journal-api.lapse.app/image/upload/q_100//xxxx/xxxx.jpg
will throw a error 500, this can be remedied by adjusting the parameters of the API call, for example using:https://image.production.journal-api.lapse.app/image/upload/,//xxxx/xxxx.jpg
doesn't throw an error. I think the best fix would be to default throws parameters to a simple,
and then if the user specifies specific parameters adjust it then. It also might be possible to default it toq_65
which is what the Lapse app uses.Specifically I found issues with the
q
parameter, with an image I was testing with I was getting issues when usingq_100
but when I bumped it down toq_50
I didn't seem to get any errors.Before fixing this I want to perform more tests to try to determine the cause of the issue,
The text was updated successfully, but these errors were encountered: