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
I found this one issue and just leaving it here as a note for future developers and if someone else stumbles upon this. Please free to close this
When doing waver multi deploy , the entire deployment blocks on the first replica if second replica is on a blocking state due to any error and logs from second replica are not propagated to stdout , making it hard to debug since as a developer I am stuck with a blocked deployment and no logs from my failing replicas.
I am not sure but maybe a potential solution could be to always collect and report logs from all replicas in a polling manner ?
The text was updated successfully, but these errors were encountered:
Hi Maintainers,
I found this one issue and just leaving it here as a note for future developers and if someone else stumbles upon this. Please free to close this
When doing
waver multi deploy
, the entire deployment blocks on the first replica if second replica is on a blocking state due to any error and logs from second replica are not propagated tostdout
, making it hard to debug since as a developer I am stuck with a blocked deployment and no logs from my failingreplicas
.I am not sure but maybe a potential solution could be to always collect and report logs from all replicas in a polling manner ?
The text was updated successfully, but these errors were encountered: