question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Bad credentials error on POST

See original GitHub issue

I can’t get the test coverage results to POST back to GitHub. Every time I get a 401 bad credentials error.

  • using v0.2.21
  • the entire job run takes less than 5 minutes
  • I’m using the default GITHUB_TOKEN
  • repository settings allow both read and write permissions for workflows
  • the job YAML is not further restricting permissions
  • self-hosted macOS runner

I could use some advice on how to continue troubleshooting this.

Issue Analytics

  • State:open
  • Created 2 years ago
  • Comments:7

github_iconTop GitHub Comments

2reactions
natecheadlecommented, Oct 11, 2021

to clarify @scttl comment. place github-token under with: for the task. This appears to resolve the issue.

- name: Publish Code Coverage Results
        uses: romeovs/lcov-reporter-action@v0.2.21
        with:
          lcov-file: ${{Code_Coverage_File}}
          github-token: ${{ secrets.GITHUB_TOKEN }}
1reaction
and3rsoncommented, May 13, 2022

I was able to make it work with default GITHUB_TOKEN by adding pull-requests: write permission to my workflow:

# ...
permissions:
  contents: read  # Required when overriding permissions
  pull-requests: write  # <== Add this to allow action to modify your PR
# ...
jobs:
  # ...
  backend:
    # ...
    steps:
      # ...
      - uses: romeovs/lcov-reporter-action@v0.2.16
        with:
          lcov-file: ./back-end/coverage.lcov
          github-token: ${{ secrets.GITHUB_TOKEN }}

https://docs.github.com/en/actions/security-guides/automatic-token-authentication#example-1-passing-the-github_token-as-an-input

image

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to fix "Bad credentials" error using authentication manager?
AuthRequest is username and password. But the error is when I try to authenticate the user using the AuthenticationManager.
Read more >
Bad Credentials: The Email Server is Saying Exactly What it ...
We have yet to encounter a case other than this meaning exactly what is says. It's a bad username/password error returned from email...
Read more >
bad credentials using gmail smtp - Google Support
SMTP ERROR: Password command failed: 535-5.7.8 Username and Password not accepted. Learn more at535 5.7.8 https://support.google.com/mail/?p=BadCredentials ...
Read more >
I get a message that says I have “bad credentials.” What ...
A “bad credentials” error occurs when the username or password that you have entered cannot be found in the user database.
Read more >
Error "Username and Password not accepted" when send email
Learn more at 535 5.7.8 https://support.google.com/mail/?p=BadCredentials j12sm1633120qtq.59 - gsmtp". I sure that my gmail and password that I config in ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found