Runner throws abort errors into the pwsh script, which terminates excavator
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- github-actions, powershell
- Domain
- ci-cd
Research direction
Begin with the linked GitHub Actions run and the PowerShell script path shown in the issue image; reproduce the runner behavior and trace where abort errors enter the script. Done means the excavator job no longer terminates when the runner emits those errors, with the workflow behavior verified.
Written by the indexing model from the issue text.
Description
- Dominant language
- PowerShell
- Stars
- 32
- Forks
- 30
- 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 ScoopInstaller/GithubActions
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
ScoopInstaller/GithubActions#98 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 70/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
ScoopInstaller/GithubActions#89 · 2 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
All issues in ScoopInstaller/GithubActions
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
code-yeongyu/senpi#3573 ·
Maintainers usually reply within 1 day
-
ci good first issue priorité: moyenne
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
area/ci bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
bug follow-up lane:backlog
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Sanne/incus-spawn#1495 · 1 comment ·
Maintainers usually reply within 1 day
-
Container fails to start when a mounted neo4j.conf uses spaces around `=`Possibly taken @RaphaelFakhri claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
neo4j/docker-neo4j#596 ·