argoproj / argoproj/argo-workflows
UI init/wait logs overwritten with "no artifact logs are available" after pod deleted
- Dominant language
- Go
- Stars
- 17k
- Forks
- 3.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 138
Description
you run any workflow, click on the logs button in the ui, select init container, it shows those logs, but then once pod dies the logs are no longer visible and "no artifact logs are available" error appears. i think the react ui could be made to not overwrite the log display if you already had it open (i understand anyone clicking the links for the first time after pod died, should still see the error)
pseudocode:
before fetching next set of logs, preserve current logs in memory
if next set of logs is unavailable then display what is in memory
Contributor guide
Research direction
Reproduce the issue by opening init-container logs in the React UI, then wait for the pod to be deleted and observe the log display. Trace the UI log-fetching and display flow; done means previously visible logs remain when a later fetch reports that artifact logs are unavailable, while a first-time request still shows that error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, react
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100