cloudfoundry / cloudfoundry/stratos
Unable to deploy an application via folder upload that relies on an executable file
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 267
- Forks
- 137
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 77
Description
- Files uploaded by frontend lose their permissions (set to 0644 server side).
- Apps that rely on an executable file therefore fail to start up
- Ideally we should retain these permissions
What we have in the front end...
- Reference to a list of https://developer.mozilla.org/en-US/docs/Web/API/File
- What we do (ish) during the upload process
new FileReader().readAsArrayBuffer(file)
It doesn't look like file permissions are readily available via exposed properties. I know you can determine file mine type using the raw bits (https://stackoverflow.com/questions/18299806/how-to-check-file-mime-type-with-javascript-before-upload), however can't find a way to determine the file permissions the same way.
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
No source file or test is named. Start by tracing the frontend upload flow around FileReader and then identify the server-side handling that changes permissions; determine whether executable permissions can be retained, and verify that an application uploaded through the folder flow starts successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- cloud, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100