Files
mgmt/engine
James Shubin b808592fb3 engine: Work around bad timestamp panic
Occasionally when a back poke happens downstream of an upstream vertex
which has already exited, it could get back poked, which would cause a
panic. This moves the deletion of the state struct until the entire
graph has completed so that it won't panic. It doesn't matter if a back
poke is lost, we're shutting down or pausing, and in this scenario it
can be lost.
2019-01-17 20:05:49 -05:00
..
2018-04-19 01:10:58 -04:00
2018-04-19 01:10:58 -04:00
2018-12-21 06:22:12 -05:00
2018-04-19 01:10:58 -04:00
2018-04-19 01:10:58 -04:00
2018-04-19 01:10:58 -04:00
2018-04-19 01:10:58 -04:00