Skip to content
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

Unhelpful error when running action #8

Open
daniel-vc opened this issue Mar 11, 2020 · 7 comments
Open

Unhelpful error when running action #8

daniel-vc opened this issue Mar 11, 2020 · 7 comments
Assignees
Labels
bug Something isn't working

Comments

@daniel-vc
Copy link

Hi, I'm trying to use your linting action but even though i've followed your set up steps, and running eslint locally, I get the below message. Any ideas?

Screenshot 2020-03-11 at 16 16 44

@stefanoeb
Copy link
Owner

hey @daniel-vc

Looks like it's a problem with your tests themselves regarding promise chaining.

Just to clarify: does it reproduce locally?

@stefanoeb stefanoeb self-assigned this Mar 19, 2020
@stefanoeb stefanoeb added the bug Something isn't working label Mar 19, 2020
@noftaly
Copy link

noftaly commented Mar 28, 2020

Hi, I have the same issue, and no, it is only in the actions. I don't have those messages locally. For me, it comes from your action!
You can see it right here: https://github.com/Skript-MC/Swan/runs/533285405?check_suite_focus=true

@gslama-akqa
Copy link

Hi there, I can confirm I'm getting the same warning.

@abmusse
Copy link

abmusse commented May 14, 2020

@stefanoeb

I also experienced this issue and found that it is caused by this issue https://npm.community/t/npm-ci-produces-a-tonn-of-excess-warnings-on-install/3261.

This can be fixed by upgrading the nodejs image used in the docker file. I tested using nodejs 12 (current LTS) and this issue went away. I Opened up #10 to help resolve the issue.

@rdzak
Copy link

rdzak commented Jun 2, 2020

I had to remove this action from the workflow due to the same error. I'll be watching this issue to verify it's fixed with proposed solution (node upgrade)

@stefanoeb
Copy link
Owner

I would actually recommend running ESLint without this action, because out of the box the ubuntu runtime of Github Action has everything we need now, like so:

name: CI
on: push
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v2
    - name: Install modules
      run: yarn
    - name: Lint
      run: eslint .

@stefanoeb
Copy link
Owner

Now in the end, all this action is doing is running eslint inside a docker container. I'd say that we would be better off just not using docker at all and run eslint inside the normal runtime (which I hope is regularly updated)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants