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]

unable to access 'https://github.com/r-hub/cransays/': The requested URL returned error: 500

while trying to commit historical data

githubstatus.com says:

We are experiencing an elevated rate of 5xx errors on the order of 1-5% being returned from numerous APIs across the site. The issue has been isolated to one datacenter. We will continue to keep users updated on progress towards mitigation.

[Bisaloo]

Error: Can't find 'action.yml', 'action.yaml' or 'Dockerfile' for action 'r-lib/actions/setup-pandoc@v2'.

In "Set up job" preliminary step. That's a new one 🤷 but following runs are fine.

[maelle]

Very informative error message: "This job failed" 😂 https://github.com/r-hub/cransays/actions/runs/8282109436/job/22662185459

[maelle]

Pandoc download error

Run r-lib/actions/setup-pandoc@v2
Download pandoc
  Unexpected HTTP response: 503
  Waiting 20 seconds before trying again
  Unexpected HTTP response: 502
  Waiting 20 seconds before trying again
  Error: Failed to download Pandoc 3.1.11: Error: Unexpected HTTP response: 502

Can't close now, as the new run isn't done.

[Bisaloo]

For some reason, this specific run was super slow: 1h 34m 42s, which means the next run finished before, and committing historical data failed with the following message:

error: failed to push some refs to 'https://github.com/r-hub/cransays'
hint: Updates were rejected because the remote contains work that you do not
hint: have locally. This is usually caused by another repository pushing to
hint: the same ref. If you want to integrate the remote changes, use
hint: 'git pull' before pushing again.

This is something to consider if we increase the refresh rate, and the historical data snapshot rate in the same movement, as suggested in #76.

[Bisaloo]

Same issue as the previous comment. I'll submit a PR to make it more robust.

[Bisaloo]

Same issue as the previous two times. Should be fixed by #86.

[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.