BUG : Command '['/usr/bin/npm', 'bin', '--global']' returned non-zero exit status 1.

[icepick4]

I don't know why but when I run my workflow, I got this error :

Here is my .yml file :

name: Waka Readme

on:
  schedule:
    # Runs at 12am IST
    - cron: '0 0 * * *'
  workflow_dispatch:
jobs:
  update-readme:
    name: Update Readme with Metrics
    runs-on: ubuntu-latest
    steps:
      - uses: anmol098/waka-readme-stats@master
        with:
          WAKATIME_API_KEY: ${{ secrets.WAKATIME_API_KEY }}
          GH_TOKEN: ${{ secrets.GH_TOKEN }}
          SHOW_PROFILE_VIEWS: false
          SHOW_OS: TRUE
          SHOW_PROJECTS: TRUE
          SHOW_LANGUAGE: TRUE
          SHOW_TIMEZONE: false
          SHOW_EDITORS: false

I looked to see if other people had this problem, but I didn't find anything.
Maybe I missed something about the process.
Thank's for your help

[aravindvnair99]

@icepick4 I'm having same issue since last 12 days as seen here - https://github.com/aravindvnair99/AravindVNair99/commits/main

So you're not the only one. Looks like something has changed in the dependencies.

As per the error message, something is going wrong when we try to save the bar graph here:

waka-readme-stats/make_bar_graph.py

Line 105 in 34f9ec1

chart.save('bar_graph.png')

[icepick4]

Thank's for your answer !
Okay okay, I thought I did something wrong I am relieved, then I will wait for an update.

[unownone]

Hey @icepick4 @aravindvnair99 you guys can have a quick fix , in your config set SHOW_LOC_CHART="False" , this should make sure that loc.py isn't invoked not causing the problem .

[aravindvnair99]

@unownone Yes that's correct. I wanted to find the issue and the solution for the same however. Unfortunately, I haven't had time to look at what's causing the issue. If anyone wants to submit a PR, feel free.

[icepick4]

@unownone Thank you it works !

[unownone]

@aravindvnair99 I think the issue most probably is coming from altair or the data that is coming from outside , as it breaks at a subprocess level , so you have to dig pretty down ig? I sat down for a while but gave up :,,,) , generating github personal access tokens are a pain .

Do you think there's a good way to test things ( like printing in a test.md for testing @anmol098 )

[aravindvnair99]

@unownone generally what I do to test is fork this repository, makes changes in my fork. Set my profile to use my fork to validate and test instead of pointing to this repository and once things look good, I create a pull request.

Unfortunately we don't have a CI system in this repository to test every incoming PR.

[pseusys]

@aravindvnair99, I've submitted a PR that should solve the issue (however I still get http error 104 localy), could you please check it out?

[aravindvnair99]

Thanks for the PR @pseusys!

@unownone / @icepick4 I've merged the PR. You can test it out.

[jschaef]

stumbled over same error: Command '['/usr/bin/npm', 'bin', '--global']' returned non-zero exit status 1 with npm 9.3.1 (openSUSE Tumbleweed). It turned out that from `altair_saver/savers/_node.py +15:

@functools.lru_cache(2)
def npm_bin(global_: bool) -> str:
    """Locate the npm binary directory."""
    npm = shutil.which("npm")
    if not npm:
        raise ExecutableNotFound("npm")
    cmd = [npm, "bin"]
    if global_:
        cmd.append("--global")
    return check_output_with_stderr(cmd).decode().strip()

We get an error because npm --global returns some help and echo $? shows 1.

I changed above code to just:

@functools.lru_cache(2)
def npm_bin(global_: bool) -> str:
    """Locate the npm binary directory."""
    npm = shutil.which("npm")
    if not npm:
        raise ExecutableNotFound("npm")
    cmd = [npm, "bin"]
    if global_:
        cmd.append("--global")
    cmd.append("--version")
    ^^^^^^^^^^^^^^^^^^^^^^^
    return check_output_with_stderr(cmd).decode().strip()

So npm --global --version is a valid command returning 0. I don't know if this
applies for other distributions also. npm has been installed via:

npm install -g npm@latest
which npm: /usr/local/bin/npm

works also with os specific package installed via:

zypper in npm
which npm: /usr/bin/npm

[mollenhauer]

My solution is to install all node depencies in my python project directory:

npm init
npm install vega-lite vega-cli canvas
npm install npm@8

And since .venv/bin is already in the PATH i will link npm into it:

ln -sf ../../node_modules/.bin/npm .venv/bin/npm

[pseusys]

@mollenhauer the issue was resolved a while ago...