"Error: EAGAIN: resource temporarily unavailable, read" when using --standard-json flag
- Dominant language
- TypeScript
- Stars
- 1.5k
- Forks
- 349
- Avg merge
- 8m
- Merged PRs (30d)
- 1
Description
When trying to use the command line with the flag **--standard-json**, the following error is thrown
```
solcjs --standard-json Example.json
```
```
internal/fs/utils.js:230
throw err;
^
Error: EAGAIN: resource temporarily unavailable, read
at Object.readSync (fs.js:537:3)
at tryReadSync (fs.js:352:20)
at Object.readFileSync (fs.js:389:19)
at Object. (/usr/lib/node_modules/solc/solcjs:37:18)
at Module._compile (internal/modules/cjs/loader.js:1151:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1171:10)
at Module.load (internal/modules/cjs/loader.js:1000:32)
at Function.Module._load (internal/modules/cjs/loader.js:899:14)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:71:12)
at internal/main/run_main_module.js:17:47 {
errno: -11,
syscall: 'read',
code: 'EAGAIN'
}
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing `solcjs --standard-json Example.json` and read the stack trace through `/usr/lib/node_modules/solc/solcjs`, especially the `fs.readFileSync` call. Trace how the `--standard-json` argument is handled and verify that the command completes without the reported EAGAIN read error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js, solidity
- Domain
- cli, compilers
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100