TritonDataCenter / TritonDataCenter/node-triton
EPIPE from `triton account get | head -2`
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 60
- Forks
- 36
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 1
Description
$ triton -a bob account get | head -2
id: fb2c3efc-46ef-11e7-bc2c-d342fb695bb6
login: bob
events.js:141
throw er; // Unhandled 'error' event
^
Error: write EPIPE
at exports._errnoException (util.js:907:11)
at WriteWrap.afterWrite (net.js:787:14)
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
Start by reproducing triton -a bob account get | head -2 and inspect the CLI entry point and output/error handling reached by triton account get. Done means the command no longer emits an unhandled EPIPE error when its output is piped through head.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100