Ecosystem/serai
Ecosystem/serai
1
0
Fork 0
mirror of https://github.com/serai-dex/serai.git synced 2024-12-23 12:09:37 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1
serai/message-queue/Cargo.toml

54 lines
1.8 KiB
TOML
Raw Normal View History

Add a message queue This is intended to be a reliable transport between the processors and coordinator. Since it'll be intranet only, it's written as never fail. Primarily needs testing and a proper ID.
2023-07-01 12:53:46 +00:00
[package]
name = "serai-message-queue"
version = "0.1.0"
Add a Docker-based test for the message-queue service
2023-07-20 22:53:03 +00:00
description = "A message queue for Serai focused on consistency"
Add a message queue This is intended to be a reliable transport between the processors and coordinator. Since it'll be intranet only, it's written as never fail. Primarily needs testing and a proper ID.
2023-07-01 12:53:46 +00:00
license = "AGPL-3.0-only"
Add a Docker-based test for the message-queue service
2023-07-20 22:53:03 +00:00
repository = "https://github.com/serai-dex/serai/tree/develop/message-queue"
Add a message queue This is intended to be a reliable transport between the processors and coordinator. Since it'll be intranet only, it's written as never fail. Primarily needs testing and a proper ID.
2023-07-01 12:53:46 +00:00
authors = ["Luke Parker <lukeparker5132@gmail.com>"]
keywords = []
edition = "2021"
publish = false
Add/correct msrv labels
2024-12-08 23:27:01 +00:00
rust-version = "1.80"
Add a message queue This is intended to be a reliable transport between the processors and coordinator. Since it'll be intranet only, it's written as never fail. Primarily needs testing and a proper ID.
2023-07-01 12:53:46 +00:00
[package.metadata.docs.rs]
all-features = true
rustdoc-args = ["--cfg", "docsrs"]
Add workspace lints
2023-12-17 01:54:24 +00:00
[lints]
workspace = true
Add a message queue This is intended to be a reliable transport between the processors and coordinator. Since it'll be intranet only, it's written as never fail. Primarily needs testing and a proper ID.
2023-07-01 12:53:46 +00:00
[dependencies]
# Macros
replace `lazy_static!` with `once_cell::sync::Lazy`
2023-11-05 14:43:40 +00:00
once_cell = { version = "1", default-features = false }
Add a message queue This is intended to be a reliable transport between the processors and coordinator. Since it'll be intranet only, it's written as never fail. Primarily needs testing and a proper ID.
2023-07-01 12:53:46 +00:00
# Encoders
Correct std feature-flagging If a crate has std set, it should enable std for all dependencies in order to let them properly select which algorithms to use. Some crates fallback to slower/worse algorithms on no-std. Also more aggressively sets default-features = false leading to a *10%* reduction in the amount of crates coordinator builds.
2023-10-31 11:41:23 +00:00
hex = { version = "0.4", default-features = false, features = ["std"] }
Replace bincode with borsh (#452) * Add SignalsConfig to chain_spec * Correct multiexp feature flagging for rand_core std * Remove bincode for borsh Replaces a non-canonical encoding with a canonical encoding which additionally should be faster. Also fixes an issue where we used bincode in transcripts where it cannot be trusted. This ended up fixing a myriad of other bugs observed, unfortunately. Accordingly, it either has to be merged or the bug fixes from it must be ported to a new PR. * Make serde optional, minimize usage * Make borsh an optional dependency of substrate/ crates * Remove unused dependencies * Use [u8; 64] where possible in the processor messages * Correct borsh feature flagging
2023-11-25 09:01:11 +00:00
borsh = { version = "1", default-features = false, features = ["std", "derive", "de_strict_order"] }
Add a message queue This is intended to be a reliable transport between the processors and coordinator. Since it'll be intranet only, it's written as never fail. Primarily needs testing and a proper ID.
2023-07-01 12:53:46 +00:00
Integrate coordinator with MessageQueue and RocksDB Also resolves a couple TODOs.
2023-07-18 05:53:51 +00:00
# Libs
Correct std feature-flagging If a crate has std set, it should enable std for all dependencies in order to let them properly select which algorithms to use. Some crates fallback to slower/worse algorithms on no-std. Also more aggressively sets default-features = false leading to a *10%* reduction in the amount of crates coordinator builds.
2023-10-31 11:41:23 +00:00
zeroize = { version = "1", default-features = false, features = ["std"] }
rand_core = { version = "0.6", default-features = false, features = ["std"] }
Integrate coordinator with MessageQueue and RocksDB Also resolves a couple TODOs.
2023-07-18 05:53:51 +00:00
Add a message queue This is intended to be a reliable transport between the processors and coordinator. Since it'll be intranet only, it's written as never fail. Primarily needs testing and a proper ID.
2023-07-01 12:53:46 +00:00
# Cryptography
Correct std feature-flagging If a crate has std set, it should enable std for all dependencies in order to let them properly select which algorithms to use. Some crates fallback to slower/worse algorithms on no-std. Also more aggressively sets default-features = false leading to a *10%* reduction in the amount of crates coordinator builds.
2023-10-31 11:41:23 +00:00
transcript = { package = "flexible-transcript", path = "../crypto/transcript", default-features = false, features = ["std", "recommended"] }
ciphersuite = { path = "../crypto/ciphersuite", default-features = false, features = ["std", "ristretto"] }
schnorr-signatures = { path = "../crypto/schnorr", default-features = false, features = ["std"] }
Add a message queue This is intended to be a reliable transport between the processors and coordinator. Since it'll be intranet only, it's written as never fail. Primarily needs testing and a proper ID.
2023-07-01 12:53:46 +00:00
# Application
Correct std feature-flagging If a crate has std set, it should enable std for all dependencies in order to let them properly select which algorithms to use. Some crates fallback to slower/worse algorithms on no-std. Also more aggressively sets default-features = false leading to a *10%* reduction in the amount of crates coordinator builds.
2023-10-31 11:41:23 +00:00
log = { version = "0.4", default-features = false, features = ["std"] }
env_logger = { version = "0.10", default-features = false, features = ["humantime"] }
Add a Docker-based test for the message-queue service
2023-07-20 22:53:03 +00:00
Correct std feature-flagging If a crate has std set, it should enable std for all dependencies in order to let them properly select which algorithms to use. Some crates fallback to slower/worse algorithms on no-std. Also more aggressively sets default-features = false leading to a *10%* reduction in the amount of crates coordinator builds.
2023-10-31 11:41:23 +00:00
# Uses a single threaded runtime since this shouldn't ever be CPU-bound
Move message-queue to a fully binary representation (#454) * Move message-queue to a fully binary representation Additionally adds a timeout to the message queue test. * coordinator clippy * Remove contention for the message-queue socket by using per-request sockets * clippy
2023-11-26 16:22:18 +00:00
tokio = { version = "1", default-features = false, features = ["rt", "time", "io-util", "net", "macros"] }
Add a message queue This is intended to be a reliable transport between the processors and coordinator. Since it'll be intranet only, it's written as never fail. Primarily needs testing and a proper ID.
2023-07-01 12:53:46 +00:00
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 3723530cf610e784adf5c94ec1c723b58ce7b193.
2024-01-04 06:08:13 +00:00
zalloc = { path = "../common/zalloc" }
Use parity-db in current Dockerfiles (#455) * Use redb and in Dockerfiles The motivation for redb was to remove the multiple rocksdb compile times from CI. * Correct feature flagging of coordinator and message-queue in Dockerfiles * Correct message-queue DB type alias * Use consistent table typing in redb * Correct rebase artifacts * Correct removal of binaries feature from message-queue * Correct processor feature flagging * Replace redb with parity-db It still has much better compile times yet doesn't block when creating multiple transactions. It also is actively maintained and doesn't grow our tree. The MPT aspects are irrelevant. * Correct stray Redb * clippy warning * Correct txn get
2023-11-30 09:22:37 +00:00
serai-db = { path = "../common/db", optional = true }
Add a message queue This is intended to be a reliable transport between the processors and coordinator. Since it'll be intranet only, it's written as never fail. Primarily needs testing and a proper ID.
2023-07-01 12:53:46 +00:00
Add common crate to access env variables In the future, we should use a proper secret store (not just env variables). This lets us update one block of code and not n in the future.
2023-07-17 04:50:46 +00:00
serai-env = { path = "../common/env" }
Move message-queue to a fully binary representation (#454) * Move message-queue to a fully binary representation Additionally adds a timeout to the message queue test. * coordinator clippy * Remove contention for the message-queue socket by using per-request sockets * clippy
2023-11-26 16:22:18 +00:00
serai-primitives = { path = "../substrate/primitives", features = ["borsh"] }
Add a Docker-based test for the message-queue service
2023-07-20 22:53:03 +00:00
[features]
Use parity-db in current Dockerfiles (#455) * Use redb and in Dockerfiles The motivation for redb was to remove the multiple rocksdb compile times from CI. * Correct feature flagging of coordinator and message-queue in Dockerfiles * Correct message-queue DB type alias * Use consistent table typing in redb * Correct rebase artifacts * Correct removal of binaries feature from message-queue * Correct processor feature flagging * Replace redb with parity-db It still has much better compile times yet doesn't block when creating multiple transactions. It also is actively maintained and doesn't grow our tree. The MPT aspects are irrelevant. * Correct stray Redb * clippy warning * Correct txn get
2023-11-30 09:22:37 +00:00
parity-db = ["serai-db/parity-db"]
rocksdb = ["serai-db/rocksdb"]
Reference in a new issue Copy permalink