[axe-linter] v4.8.1 - Couldn't start client axe Linter
Product
axe Linter
Product Version
4.8.1
Latest Version
- [X] I have tested the issue with the latest version of the product
Issue Description
Expectation
Extension loads and successfully starts client.
Actual
I receive an error stating Couldn't start client axe Linter.
Output reads as follows:
[Error - 08:32:56] Starting client failed
Error: spawn Unknown system error -86
at ChildProcess.spawn (node:internal/child_process:413:11)
at Object.spawn (node:child_process:806:9)
at /Users/davidjourneaux/.vscode/extensions/deque-systems.vscode-axe-linter-4.8.1/dist/src/extension.js:1:251603
How to Reproduce
Install axe Accessibility Linter v4.1.8.1 in VS Code and wait for it to load. I assume that if you use a similar environment to mine, you should see the error appear. Otherwise, I'm not sure how to reproduce.
Additional context
Using Mac OS Sonoma 14.3 VS Code 1.86.2
I've read through related issues, but they seem to be for older extension versions, and the advice given has not helped.
Happy to provide any additional context upon request.
Hey @dvdjrnx do you mind uninstalling the extension and reinstall it?
I'm experiencing the same issue with a comparable setup to the description. Uninstalling and reinstalling didn't help anything unfortunately.
Hey @michael-siek, thanks for getting back. I uninstalled the extension once I realised it wasn't working. Just installed it again now, and it still doesn't work.
@dvdjrnx during the installation, the extension contacts S3 to download some additional components. Do you have S3 blocked or restricted?
@dylanb Not that I'm aware of, no. I checked with my team to verify, and there has been no efforts to block or restrict S3 on our network or machines.
Same issue here. Not sure if S3 is blocked or restricted. what is the URL it is trying to reach?
@dvdjrnx @roadking do you mind trying this on the latest version of the vscode extension v4.10.3?
@dylanb VS Code (1.96) and Axe (4.10.3) are on the newest version. Is there a url or port to S3, that could be blocked?
Hey @Lucas-Feichtinger do you mind reaching out to me in the deque accessibility slack channel and I should be able to help resolve this with you.