OpenZeppelin / OpenZeppelin/openzeppelin-upgrades
Support read-only file systems
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 658
- Forks
- 286
- PR merge metrics
- No merged PRs in 30d
Description
I believe the error is caused by the above function.
I am using Google App Engine to host my deploy function (which will deploy an upgradable contract to Matic). It works fine with I tested in in my local Mac environment. However, when I trigger the login in Google App Engine, I see this error. I would like to ask if there is any solution for this?
[Error: EROFS: read-only file system, mkdir '/workspace/cache/validations.json.lock'] {
errno: -30,
code: 'EROFS',
syscall: 'mkdir',
path: '/workspace/cache/validations.json.lock'
}
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
Start with packages/plugin-hardhat/src/utils/validations.ts at line 14 and reproduce the deployment in Google App Engine, where the filesystem is read-only. Trace how cache/validations.json.lock is created and define the expected behavior for that environment; the issue is done when the deployment no longer fails with EROFS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- google-cloud, typescript
- Domain
- cloud, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100