discussion: start_block parameter in decorator [SBK-360] about silverback

[fubuloubu]

In general, guidance should be that it only supports streaming new data events.

The historical handling is useful for restarts, but I think when we finally utilize the task queue correctly it will just start collecting unhandled items in the queue that a restarted worker would start processing on a restart, and we wouldn't need to backtrack anything

[mikeshultz]

In general, guidance should be that it only supports streaming new data events.

The historical handling is useful for restarts, but I think when we finally utilize the task queue correctly it will just start collecting unhandled items in the queue that a restarted worker would start processing on a restart, and we wouldn't need to backtrack anything

Unhandled jobs aren't really the same thing as missed blocks/events though. start_block causes the runner to queue up jobs for historical blocks/events during startup when polling.