Dashboard status

[Bisaloo]

This is an issue that will be automatically re-opened whenever dashboard updates fail. If this issue is currently open, our team has been notified and someone will try to fix it as soon as possible.

[Bisaloo]

Temporary failure due to unreachable internet resource during system dependency installation. Re-running the workflow fixed the issues.

[Bisaloo]

Error: getaddrinfo EAI_AGAIN api.r-hub.io

in setup-r step.

Details here: epiforecasts/epiforecasts.github.io#29

Latest runs are working fine.

[Bisaloo]

remote: fatal error in commit_refs
To https://github.com/r-hub/cransays
! [remote rejected] history -> history (failure)

while trying to save history. It is probably a temporary GitHub outage since more recent runs work fine but I'll investigate if this keeps happening.

[Bisaloo]

apt-get install was trying to install a package that has been removed from the repos. This is solved by running apt-get update before attempting to run apt-get install.

I've added a step to run apt-get update manually for now (9e7de77) but I've opened an issue in r-lib/actions to do it automatically: r-lib/actions#554

[Bisaloo]

There was an error when attempting to execute the process '/usr/bin/git'. This may indicate the process failed to start. Error: spawn /usr/bin/git ENOENT

Re-run worked fine.

[Bisaloo]

Error: Can't use 'tar -xzf' extract archive file: /home/runner/work/_actions/_temp_51cb7f5e-8fa6-4b7f-8b21-4c9528aa60ab/a80e75d6-0dfb-40d5-bd83-dd0b5323a144.tar.gz. return code: 2.

In "Set up job" step. More recent runs work fine.

[Bisaloo]

Error: Failed to install pandoc: The process 'sudo' failed with exit code 1

Latest runs are fine.

[Bisaloo]

We get:

Failed to connect to cran.r-project.org port 21: Connection refused

I can reproduce locally with various methods. I'm not sure if it's down or if they made it private 🤔.

[Bisaloo]

It might be related to the maintenance announced on https://cran.r-project.org/:

CRAN submissions is offline from Jul 22, 2022 to Aug 5, 2022 (CRAN team vacation and maintenance work).

[Bisaloo]

nothing to commit, working tree clean

in save history job.

I suspect #86 wasn't the right fix since artifacts will always overwrite the previous ones. If jobs timings make it so that jobs from two different runs pull the same artifact, there will be nothing to commit.

[maelle]

   Quitting from lines at lines 30-54 [get-data] (dashboard.Rmd)
Caused by error:
! Failed to connect to cran.r-project.org port 21 after 574 ms: Connection refused

[Bisaloo]

I can reproduce locally. Let's wait to see if it's temporary or if they're shutting down the ftp access.

[Bisaloo]

It seems to be resolved now.

[Bisaloo]

GitHub Actions has encountered an internal error when running your job.

🤷 seems fine now

[Bisaloo]

Error: Error: Request timeout: /rversions/resolve/release/linux-ubuntu-22.04/x86_64

In setup-r

[Bisaloo]

GitHub Actions has encountered an internal error when running your job.

Transient issue from GitHub's end where save-history didn't start. Nothing we can do here.

[Bisaloo]

From https://cran.r-project.org/:

Submissions are closed: This year's CRAN submission summer break (CRAN team vacation and maintenance work) is from Aug 1, 2024 to Aug 16, 2024.

I have disabled the workflow for now to avoid unnecessary use of resources.

[Bisaloo]

CRAN is back from holidays since last week and the dashboard is back on its regular update schedule.

[Bisaloo]

Two workflows tried to push the same file name, because they happened to snapshot at the same time. A potential solution for this rare edge case may be to include seconds in the saved file name. @maelle, any thoughts?

In all cases, all is back to normal now.

[maelle]

such bad luck 😮 including seconds sounds fine

[maelle]

It has now worked again a few times. The error was:

Render-dashboard
The hosted runner: GitHub Actions 3 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

🤨