Ecosystem/serai
Ecosystem/serai
1
0
Fork 0
mirror of https://github.com/serai-dex/serai.git synced 2024-12-26 21:50:26 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1
serai/message-queue
History
Luke Parker 7eb388e546
PR to track down CI failures (#501) 
* Use an extended timeout for DKGs specifically

* Add a log statement when message-queue connection fails

* Add a 60 second keep-alive to connections

* Use zalloc for processor/message-queue/coordinator

An additional layer which protects us against edge cases with Zeroizing
(objects which don't support it or don't miss it).

* Add further logs to message-queue

* Further increase re-attempt timeouts in CI

* Remove misplaced continue inmessage-queue client

Fixes observed CI failures.

* Revert "Further increase re-attempt timeouts in CI"

This reverts commit 3723530cf6.
2024-01-04 01:08:13 -05:00
..
src PR to track down CI failures (#501) 2024-01-04 01:08:13 -05:00
Cargo.toml PR to track down CI failures (#501) 2024-01-04 01:08:13 -05:00
LICENSE Add a message queue 2023-07-01 08:53:46 -04:00
README.md Add a message queue 2023-07-01 08:53:46 -04:00

README.md

Message Log

A message log for various services to communicate over.

Each message is checked to be of the claimed origin. Then, it's added to the recipient's message queue. This queue is sequentially handled, FIFO, only dropping messages once the recipient acknowledges it's been handled.

A client which publishes an event specifies its own ID for the publication. If multiple publications with the same ID occur, they are assumed repeats and dropped.

This library always panics as its error-cases should be unreachable, given its intranet status.