Error: couldn't install and enable argus: exit status 1

[zohairhadi]

Describe the bug

After creating the workflow and running listen on a PR after a commit, I'm getting the following error Error: couldn't install and enable argus: exit status 1

This is my workflow file

name: Lstn Test

on: push

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
        - uses: listendev/action@v0.10
          with:
            token: "..."
            jwt: ${{ secrets.LSTN_API_KEY }}
            ci: "only"
            # reporter: "gh-pull-comment"

Expected vs actual behavior

Expected for listen to start generating a report of the packages, but I'm getting the following error Error: couldn't install and enable argus: exit status 1

Logs

Error: couldn't install and enable argus: exit status 1

[leodido]

Hello @zohairhadi, thank you for reporting it!

Could you please try it with argus_version: v0.0 option for now?

[danielpacak]

I took listen.dev GitHub action v0.11.0 for a spin and bumped into a similar issue:

• PR to reproduce: https://github.com/UNIT-7124/listen.dev-seed/pull/1
• Logs output from a workflow run (might have expired): https://github.com/UNIT-7124/listen.dev-seed/actions/runs/11362331969/job/31603961094
• Fails with and without the argus_version option.

[leodido]

Hello Daniel,

thanks for reporting it!

I reproduced your CI workflow and I confirm it breaks. It's because of ci: true. Please switch it to ci: only and try again. 🙏

With the changes above, it should work.

[danielpacak]

Thanks for checking and a prompt reply @leodido . I have changed to the ci: only option, but apparently the problem persists in the subsequent workflow run: https://github.com/UNIT-7124/listen.dev-seed/actions/runs/11364169951/job/31609642292

[leodido]

Oh, this is funny!

I can't reproduce the problem with ci: only.

See the screenshots below.

---

To continue my investigation, it would help me if you could regenerate the LSTN_API_KEY token.

From your project at https://dashboard.listen.dev create a new one...

Then, update the LSTN_API_KEY action secret in your GitHub repository, and try again ...

Thank you

[danielpacak]

I know it can be tricky troubleshooting GitHub actions runners. I tried with regenerated API token and the problem still persists: https://github.com/UNIT-7124/listen.dev-seed/actions/runs/11364169951