Felix Ruess

FYI @eapolinario @neilisaur

Thanks @eapolinario !

This is basically a duplicate of https://github.com/flyteorg/flyte/issues/3574 as this happens for all limits.

Looks like we are seeing the same problem and react crashes when opening some timelines...

Also in the timeline view RUNNING should be further differentiated between waiting (due to resource quota, not submitted to k8s yet), queued in k8s and actually running...

This actually annoyed us so much that a colleague made his own simple status UI that will properly show the running vs queued status!

This is super annoying and regularly results in CI failures here and we have to manually publish the repo again so that the last packages are actually available. Any updates...

This is not an issue with the exporter... Memory per thread does not make sense, as all threads in the same process share the memory (virtual address space).