LivelyKernel / LivelyKernel/lively4-core
Dropbox access does not support files names that have to be url-encoded
Open
Nobody has claimed this yet.
comp: service worker
effort1: easy (hours)
P2: required
type: bug
- Dominant language
- JavaScript
- Stars
- 89
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
E.g. https://lively4/dropbox/Softwaremodularit%C3%A4t.md throws a FileNotFoundError: path/not_found/..
Contributor guide
No contributing guide indexed for this repository
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
Use the example Dropbox URL to reproduce the FileNotFoundError, then trace how the Dropbox access path handles the encoded filename. Confirm that the URL-encoded name resolves to the existing file and verify the behavior with a comparable filename containing non-ASCII characters.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100