[question] clarification on exclude rules

[Borda]

Hello, I'm hitting a strange (for me as a user) unexpected behaviour. I have a problematic URL that often returns 500, so I placed it in the exlide list in my toml file, but it's still showing up in the report as an error...

verbose = "info"
no_progress = true
include_verbatim = true
retry_wait_time = 3
max_concurrency = 10

exclude = [
    "https://github.com/YOUR_USERNAME/supervision.git",  # hint for forking contributors
    "http://127.0.0.1:8000",  # hint for local docs server
    "https://sam2.metademolab.com/",  # returns 403 Forbidden
    "https://snyk.io/advisor/python/supervision/badge.svg",
]

and GH actions:

      - name: 🔗 Link Checker
        uses: lycheeverse/lychee-action@v2
        with:
          lycheeVersion: v0.22.0
          args: |
            --config .github/lychee.toml
            ${{ secrets.UNIVERSE_RATELIMIT_BYPASS_KEY != '' && format('--header "x-ratelimit-bypass: {0}"', secrets.UNIVERSE_RATELIMIT_BYPASS_KEY) || '--exclude "https://universe.roboflow.com/.*"' }}
            README.md
          fail: true

and the report states

# Summary

| Status         | Count |
|----------------|-------|
| 🔍 Total       | 60    |
| ✅ Successful  | 46    |
| ⏳ Timeouts    | 0     |
| 🔀 Redirected  | 13    |
| 👻 Excluded    | 0     |
| ❓ Unknown     | 0     |
| 🚫 Errors      | 1     |
| ⛔ Unsupported | 0     |

## Errors per input

### Errors in README.md

* [500] <https://snyk.io/advisor/python/supervision/badge.svg> | Rejected status code (this depends on your "accept" configuration): Internal Server Error

[katrinafyi]

When the 500 is encountered, is UNIVERSE_RATELIMIT_BYPASS_KEY set or unset? Does doing the opposite (unsetting or setting) affect the 500 exclude?

Edit: my hypothesis is that if exclude is specified both in the CLI and the TOML, then the CLI value will fully override the TOML one.

[Borda]

Edit: my hypothesis is that if exclude is specified both in the CLI and the TOML, then the CLI value will fully override the TOML one.

Yes, I had the same, but in the open PR, have a branch within the repo, not, so secrets are available, so no other exclude is used, and still this one site has 500 errors...
Could be due to error number ot has a different treatment?

[katrinafyi]

500 is a very normal error and doesn't have any special treatment.

In your PR, the first thing that stands out is the standalone link checking job passes, but the link checking inside build prereleases does not. This means it's likely not a lychee problem.

Looking further, I think the jobs that fail are the ones using workflow_call, because the secrets haven't been set up to propagate to the called workflow. Something like this should work: https://docs.github.com/en/actions/how-tos/reuse-automations/reuse-workflows#using-inputs-and-secrets-in-a-reusable-workflow. You can also see that for the lychee runs that fail, their arguments have the --exclude on the command line.