UI init/wait logs overwritten with "no artifact logs are available" after pod deleted

[tooptoop4]

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

[shuangkun]

Is it too resource-intensive to store it in memory? Can we fetch the log of init/wait from the server and display it in the UI? We currently achieve this by taking logs from cloud provider log systems, such as Alibaba Cloud SLS, when a pod has been deleted, and displaying them on the UI.