It looks like a failed link-check is causing nightly CI builds to fail, since July 31. See:
At a quick glance, I'm seeing the error ModuleNotFoundError: No module named 'uxarray.RemapWeights' related to /uxarray/docs/api.rst line 474. Pinging @rajeeja who last touched that line in api.rst according to git blame. Though, I'm not sure if that line is the actual issue or if the issue is something else.
This is the second recent nightly CI failure related to link check (see #1580). Would it make sense to enable link-check in PRs, to reduce the chances of repeated failures like this in the future? When it passes, it only takes roughly 3 mins to run.
EDIT: actually, the real issue is probably the following: ( contributing: line 117) broken https://stackoverflow.com/ - 403 Client Error: Forbidden for url: https://stackoverflow.com/. I suspect that enabling link-check in PRs probably would not actually help this issue.
It looks like a failed link-check is causing nightly CI builds to fail, since July 31. See:
At a quick glance, I'm seeing the error
ModuleNotFoundError: No module named 'uxarray.RemapWeights'related to/uxarray/docs/api.rstline 474. Pinging @rajeeja who last touched that line inapi.rstaccording to git blame. Though, I'm not sure if that line is the actual issue or if the issue is something else.This is the second recent nightly CI failure related to link check (see #1580).
Would it make sense to enable link-check in PRs, to reduce the chances of repeated failures like this in the future? When it passes, it only takes roughly 3 mins to run.EDIT: actually, the real issue is probably the following:
( contributing: line 117) broken https://stackoverflow.com/ - 403 Client Error: Forbidden for url: https://stackoverflow.com/. I suspect that enabling link-check in PRs probably would not actually help this issue.