Repository navigation
🐛 [BUG] - Solc versions list 403 #422
Description
Description
I run the command wake up --example counter --force
After that, I run the wake up command, during which I receive a 403 error from the server when trying to request the list of solc versions.
In the browser, the link opens without a 403 error. After adding the header \"User-Agent\": \"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36\" to svm.py, it starts working correctly.
Tested with eth-wake version 4.22.0
Reproduction steps
1. Open PowerShell in any empty git directory (with README and .gitignore)
2. Do not edit anything
3. Run 'wake up --example counter --force` and after that `wake up`
4. See error in log:
2026-02-05 17:27:22,704 wake.svm.svm: Failed to download solc list from https://binaries.soliditylang.org/windows-amd64/list.json: svm.py:308 HTTP Error 403: ForbiddenReproduction URL
Screenshots
Logs
wake up
[17:27:22] Found 12 *.sol files in 0.01 s init.py:680
Loaded previous build in 0.44 s compiler.py:869WARNING 2026-02-05 17:27:22,704 wake.svm.svm: Failed to download solc list from https://binaries.soliditylang.org/windows-amd64/list.json: svm.py:308 HTTP Error 403: Forbidden
Compiled 1 files using 1 solc runs in 0.12 s compiler.py:1249 Processed compilation results in 0.01 s compiler.py:1502
[17:27:23] Wrote build artifacts in 0.39 sOS
Windows
Reacted by pg-bouncer
Activity
0xInnominatus commentedon Mar 3, 2026
I have tested this with new version 4.22.1 and the bug has gone. Thank you!
0xInnominatus commentedon Jun 2, 2026
Just FYI: it seems that this bug exists in the pre-release version 5.0.0rc2. I noticed it while using https://github.com/Ackee-Blockchain/wake-detect-action, which relies on the latest release version of Wake (see details in this issue).
In the latest stable version (4.22.1), the same problem does not occur.
michprev commentedon Jun 3, 2026
Hey, thanks for the investigation! Yes, you're right that the bugfix has to be ported to the 5.0 branch.
At the same time, the Github action should be using the latest stable version of Wake, not the release candidate. Looking into that