You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I've discovered this problem with my colleague when we ran ottoopensource/gitactionboard docker image in our k8s cluster. The default resources allocation was with a single CPU. But it is easy to reproduce it with docker/podman.
Additional context
We've spend with my colleague a few hours to understand what was the problem of not loading the data started with debugging k8s cluster and ended up reading source code of otto-de/gitactionboard where we found CompletableFuture usage in GithubWorkflowService. Handling this situation with timeout or at least documenting resources requirements would save us some time and I hope it will save time for people in a future who might face the same problem. Thank you.
The text was updated successfully, but these errors were encountered:
Describe the bug
I've discovered this problem with my colleague when we ran
ottoopensource/gitactionboard
docker image in our k8s cluster. The default resources allocation was with a single CPU. But it is easy to reproduce it withdocker
/podman
.To Reproduce
Steps to reproduce the behavior:
Run the command below.
Go to localhost:8008 in your web browser
Be sure that it is loading forever
Look at logs and be sure that it hangs
Stop the process
Run the command below.
Go to localhost:8008 in your web browser
Be sure that all workflows have been loaded successfully
Look at logs and be sure that nothing hangs
Expected behavior
I think one of the options is fine:
Screenshots
Step 3:
Step 8:
Logs
Step 4:
logs-1.txt
Step 9:
logs-2.txt
Additional context
We've spend with my colleague a few hours to understand what was the problem of not loading the data started with debugging k8s cluster and ended up reading source code of
otto-de/gitactionboard
where we foundCompletableFuture
usage in GithubWorkflowService. Handling this situation with timeout or at least documenting resources requirements would save us some time and I hope it will save time for people in a future who might face the same problem. Thank you.The text was updated successfully, but these errors were encountered: