No progress during "Streaming the extraction of the CodeQL bundle"
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 32/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- github-actions, typescript
Research direction
The issue names no source files or tests; start by tracing the CodeQL bundle download and the tar -x --zstd extraction step shown in the logs. Reproduce or instrument the extraction path to determine why it can stop progressing for hours, and consider the issue done when the cause and a validated fix or diagnostic are documented.
Written by the indexing model from the issue text.
Description
Every now and then, we see this error in our CodeQL scans. Both default and "advanced" ones:
Written by John Gilmore and Jay Fenlason.
Found gnu tar version 1.34.
Did not find CodeQL tools version 2.20.5 in the toolcache.
Looked for CodeQL bundle codeql-bundle-linux64.tar.zst in github/codeql-action on https://git.xxxxxxx.com but got error HttpError: Not Found.
Using CodeQL CLI version 2.20.5 sourced from https://github.com/github/codeql-action/releases/download/codeql-bundle-v2.20.5/codeql-bundle-linux64.tar.zst .
Downloading CodeQL tools from https://github.com/github/codeql-action/releases/download/codeql-bundle-v2.20.5/codeql-bundle-linux64.tar.zst . This may take a while.
Streaming the extraction of the CodeQL bundle.
tar -x --zstd --ignore-zeros --warning=no-unknown-keyword --overwrite -f - -C /_work/_temp/82a785df-7d7a-4843-a891-ff0b9e40xxxx
Error: The operation was canceled.
The above message is from the latest time we saw this error (01/03/25), which is post v3.28.10 as the usage of "--ignore-zeros" seems to confirm for the tar command.
The operation being cancelled, is due to a time out after a few hours of apparently, nothing happening.
The error happens from way back and we are unable to see any transcient problem in our compute/network resources that helps us understand.
- Dominant language
- TypeScript
- Stars
- 1.6k
- Forks
- 493
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 44
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.
More from github/codeql-action
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/codeql-action#4052 · 4 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
github/codeql-action#4078 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
github/codeql-action#4008 · 9 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
github/codeql-action#3978 · 4 comments · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
github/codeql-action#3915 · 6 comments · 3 reactions ·
All issues in github/codeql-action
Similar issues
-
clawsweeper:linked-pr-open clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:message-loss issue-rating: 🦞 diamond lobster maturity:stable P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#616 ·
-
ZCode 3.14.3 に対応する Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
supermomonga/zcode-acp#24 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
growthbook/growthbook#7100 ·
-
triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100