getting filename NaN,NaN. when content-type is application/octet-stream
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 267
- Forks
- 60
- PR merge metrics
- No merged PRs in 30d
Description
I'm downloading images from an external website, saving it locally and afterwards uploading it via node-imager to amazon. Sometimes it happens that an image has content-type "application/octet-stream" instead of a supported type. imager doesn't throw an error in this case but uploads the file with filename NaN,NaN,NaN,.. this file is not reachable afterwards.
Contributor 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.
Research direction
Reproduce the external download and Amazon upload path with content-type application/octet-stream, then trace where the filename is derived before the upload. There are no files or tests identified in the issue; done means unsupported content no longer produces an unusable NaN filename and the behavior is covered by a regression check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript, node.js
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100