serai/orchestration/processor/monero/Dockerfile.processor.monero

  cargo build --features "binaries parity-db monero" -p serai-processor && \
  mv /serai/target/debug/serai-processor /serai/bin
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			`cargo build --features "binaries parity-db monero" -p serai-processor && \`
Use debug builds in our Dockerfiles to reduce CI times (#462) * Use debug builds in our Dockerfiles to reduce CI times Also enables only spawning the mdns service when debug in the coordinator. * Correct underflow in processor Prior undetected due to relase builds not having bounds checks enabled. * Restore Serai release due to CI/RPC failures caused by compiling it in debug mode This is probably worth an issue filed upstream, if it can be tracked down. * Correct failing debug asserts in Monero These debug asserts assumed there was a change address to take the remainder. If there's no change address, the remainder is shunted to the fee, causing the fee to be distinct from the estimate. We presumably need to modify monero-serai such that change: None isn't valid, and users must use Change::Fingerprintable(None). 2023-11-29 05:24:37 +00:00			`mv /serai/target/debug/serai-processor /serai/bin`