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 Nov 5, 2019. It is now read-only.
I'm not entirely sure this is what causes the bug, but the filename I was trying to use was
~/import/3ffd2e08ab2741ba9faeab1f1c6c4c894004c048.jpg. Absolute paths didn't work, either, so I think it's the length of the filename which causes the bug.
It might be worth nothing that the normal "File not found!" response doesn't appear if you enter an invalid filename of about the same length.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm not entirely sure this is what causes the bug, but the filename I was trying to use was
~/import/3ffd2e08ab2741ba9faeab1f1c6c4c894004c048.jpg. Absolute paths didn't work, either, so I think it's the length of the filename which causes the bug.
It might be worth nothing that the normal "File not found!" response doesn't appear if you enter an invalid filename of about the same length.
The text was updated successfully, but these errors were encountered: