zaproxy / zaproxy/actions-common
Unable to debug error in readPreviousReport
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 18
- Avg merge
- 4h 12m
- Merged PRs (30d)
- 5
Description
Everytime My Zap actions run, even though there's an Issue open and the action can find such Issue, they create new issues due to an error in processing.
Ongoing open issue has been identified #1234
Error occurred while downloading the artifacts!
Alerts present in the current report: true
Process completed successfully and a new issue #1235 has been created for the ZAP Scan.
Unfortunately, the error handling code does not print the error, so it's very hard to figure out what's going on.
Could we change that error catching to print the error?
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 at packages/scans/src/action-helper.js around line 230, where the readPreviousReport error handling is located. Trace the artifact-processing failure path and confirm that the caught error is printed in the action output when the failure occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript, typescript
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 52/100