trixi-framework / trixi-framework/Trixi.jl

Timeout error for GitHub action CacheNotebooks

Open
#1,112 1 comment 0 reactions 0 assignees View on GitHub
documentation
Dominant language
Julia
Stars
731
Forks
167
Avg merge
2d 18h
Merged PRs (30d)
25

Description

The GitHub action [repo2docker-action](https://github.com/jupyterhub/repo2docker-action) seems to have a maximum time allowed of 900s to trigger mybinder (implemented [here](https://github.com/jupyterhub/repo2docker-action/blob/86cbba650927d185d7cee256eb48d0a7eeb38906/trigger_binder.sh#L8)).
So, our action fails with the timeout error `curl: (28) Operation timed out after 900000 milliseconds with 423286 bytes received`.

A question about the possibility of adjusting the time limit can be found in this [issue](https://github.com/jupyterhub/repo2docker-action/issues/88).

Contributor guide

Open the contributing guide

Research direction

Start by reading trigger_binder.sh in repo2docker-action at the linked line and the referenced repo2docker-action issue 88. Confirm whether the 900-second limit can be configured or changed upstream, then determine whether Trixi.jl needs an actionable workflow change. Done means the timeout cause and a supported resolution are established.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.