Stanislav Jakuschevskij 06c7445e91 Replace panic with error handling ... Starting from the processor.Block.Process all methods now return errors if something goes wrong with unpacking of the blocks and reading the transactions. In each function where the error is being propagated back to client it is wrapped in a message with the function name. This makes it easier to track down the error and see the propagation chain. Finally the error is logged to the terminal and the go routine shuts down gracefully. The graceful shutdown executes all deferred functions which close the context, the checkpointer and the gateway. Before panics were used everywhere which was an issue because the unpacking of the blocks happened in a go routine. When a panic happens in a go routine only the deferred functions of the go routine are called but not those of the client which lead to unexpected behavior. The transact function is also executed in a go routine therefore the same typo of error handling was implemented there. Signed-off-by: Stanislav Jakuschevskij <stas@two-giants.com>		2025-02-24 13:14:48 +01:00
..
contract	Replace panic with error handling	2025-02-24 13:14:48 +01:00
parser	Replace panic with error handling	2025-02-24 13:14:48 +01:00
processor	Replace panic with error handling	2025-02-24 13:14:48 +01:00
store	Replace panic with error handling	2025-02-24 13:14:48 +01:00
utils	Replace panic with error handling	2025-02-24 13:14:48 +01:00
app.go	Implement caching	2025-02-24 13:14:47 +01:00
connect.go	Extract block processor and store from listener	2025-02-24 13:14:47 +01:00
getAllAssets.go	Replace panic with error handling	2025-02-24 13:14:48 +01:00
go.mod	Encapsulate block parser in a package	2025-02-24 13:14:47 +01:00
go.sum	Encapsulate block parser in a package	2025-02-24 13:14:47 +01:00
listen.go	Replace panic with error handling	2025-02-24 13:14:48 +01:00
transact.go	Replace panic with error handling	2025-02-24 13:14:48 +01:00