Will Winder

@joe-p do you think supported docker images also solve this proablem? Eventually I'd like to use those in place of the custom docker build the sandbox script is currently using.

Thanks for the feedback everyone. I can honestly say that this use case never occurred to us. I don't know if we'd support this in sandbox, but maybe it's worth...

@jvtrudel yes, it is extremely involved but you can get it working. I documented some of my experiences: [overview of the process](https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!topic/universal-gcode-sender/ILn6ktWBFqc) [this github issue during implementation](https://github.com/winder/Universal-G-Code-Sender/issues/731) [blog post describing...

I guess CI is probably failing because I used a fork. I'll re-open this PR once I have repo permissions.

closing in favor of #527

Copying similar description from #99 ### Subject of the issue The pipeline object is managed using a context with a cancel function and a wait group. This setup is strange....

How about an `allow-backwards-catchup` option in the algod importer? The command line flags are intentionally kept very minimal. A PR for this feature would be appreciated.

I believe this sort of thing may happen if you have multiple Indexer writers running at the same time. Resetting the data directory is the right way to recover.

@scholtz none of these people are working on Algorand anymore. I think the way you'd do this now is to configure your algod follower node to use the custom consensus...

Sorry for the delay. It's definitely improved, it no longer freezes on this machine. The visualizer still stops working if I move it to a new part of the UI....