New build failure
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
Research direction
Start with the failure output from make test, especially Makefile:27 and the ff [command] --help path in the cmd package. Run the command to reproduce the coverage-report broken pipe, then trace which command exits early. Done means make test completes without the broken-pipe error and the command tests pass.
Written by the indexing model from the issue text.
Description
Use "ff [command] --help" for more information about a command.
error generating coverage report: write |1: broken pipe
FAIL github.com/hyperledger/firefly-cli/cmd 0.032s
FAIL
make: *** [Makefile:27: test] Error 1
- Dominant language
- Go
- Stars
- 66
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from hyperledger-firefly/cli
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
hyperledger-firefly/cli#357 ·
-
bug good first issue
Difficulty 3/5 1-2 days Newbie friendliness 45/100
hyperledger-firefly/cli#343 · 1 comment ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
hyperledger-firefly/cli#339 · 7 comments ·
-
bug Windows WSL
Difficulty 3/5 1-2 days Newbie friendliness 25/100
hyperledger-firefly/cli#335 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
hyperledger-firefly/cli#334 · 2 comments ·
All issues in hyperledger-firefly/cli
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day
-
[Bug]: APIGW request ID headers are inconsistent between server and clientPossibly taken @zouxingyuks claimed this today. Openproduct/backlog
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
TencentBlueKing/bk-nodemgr#3782 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 91/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
praetorianer777/Dynamo#53 ·
Maintainers usually reply within 1 day
-
internal test setup
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
SAP/terraform-provider-scc#430 ·