Skip to content

[CI]: eslint failure #25251

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
scottshambaugh opened this issue Feb 18, 2023 · 1 comment · Fixed by #25262
Closed

[CI]: eslint failure #25251

scottshambaugh opened this issue Feb 18, 2023 · 1 comment · Fixed by #25262
Labels
CI: testing CI configuration and testing
Milestone

Comments

@scottshambaugh
Copy link
Contributor

scottshambaugh commented Feb 18, 2023

Summary

Recent PRs are failing eslint linter checks with the following:

Run reviewdog/action-eslint@v1
Run $GITHUB_ACTION_PATH/script.sh
🐶 Installing reviewdog ... https://github.com/reviewdog/reviewdog
 Running `npm install` to install eslint ...
eslint version:
/home/runner/work/_actions/reviewdog/action-eslint/v1/script.sh: 20: Unknown: not found
 Running eslint with reviewdog 🐶 ...
  /home/runner/work/_actions/reviewdog/action-eslint/v1/script.sh: 23: Unknown: not found
reviewdog: failed to unmarshal rdjson (DiagnosticResult): proto: syntax error (line 1:1): unexpected token 
Error: Process completed with exit code 1.

Looks related to this: reviewdog/action-eslint#152

Proposed fix

The above issues proposes a workaround with:

      - uses: actions/setup-node@v3
         with:
           node-version: '18.13'
           cache: 'yarn'

However I’m unclear if pinning that version is best practice.

@scottshambaugh scottshambaugh added Maintenance CI: testing CI configuration and testing and removed Maintenance labels Feb 18, 2023
@robrighter
Copy link
Contributor

robrighter commented Feb 19, 2023

I feel like it would be reasonable to apply this workaround for now and also create a separate issue to remove the workaround when v9 support is added.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI: testing CI configuration and testing
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants