Results for phoenix_testing

Lazy-loading mainnet/testnet fork for Soroban tests. Inspired by Foundry's Anvil.

Rust client for Phoenix channels

Unofficial Rust client for Supabase Realtime (Phoenix Channels)

This is the Rust version of https://gitlab.in2p3.fr/CTA-LAPP/PHOENIX_LIBS2/PhoenixClock project. This project aims to ease the use of clock in complex environments, especially distributed environments where latencies measurement has to be precise and reproductible when running unit tests. **PhoenixClock** provide **PGenericClock**, a template classe which takes two arguments : - The main clock backend (could be **clock**, **PClockNs** for nanoseconds, etc) - A mock of a clock, **PClockMock**, which can play, register and replay a sequence of clock calls These clocks are activated with a mode `PClockMode::PClockMode` which can be : - `PClockMode::NO_MOCK` : for a normal usage - `PClockMode::MOCK` : when the mock the desired clock is played - `PClockMode::MOCK_RECORD` : when the real clock backend is used but the clock mock is recording (could be usefull for debugging or to desing new unit tests quickly)

Process supervisor with automatic restart for the Harmonia agent

Local prover for Dusk Network

A Rust implementation of the Messaging Layer Security (MLS) protocol, as defined in RFC 9420.

A crypto backend for OpenMLS based on libcrux implementing openmls_traits.

This is the Rust version of https://gitlab.in2p3.fr/CTA-LAPP/PHOENIX_LIBS2/PhoenixClock project. This project aims to ease the use of clock in complex environments, especially distributed environments where latencies measurement has to be precise and reproductible when running unit tests. **PhoenixClock** provide **PGenericClock**, a template classe which takes two arguments : - The main clock backend (could be **clock**, **PClockNs** for nanoseconds, etc) - A mock of a clock, **PClockMock**, which can play, register and replay a sequence of clock calls These clocks are activated with a mode `PClockMode::PClockMode` which can be : - `PClockMode::NO_MOCK` : for a normal usage - `PClockMode::MOCK` : when the mock the desired clock is played - `PClockMode::MOCK_RECORD` : when the real clock backend is used but the clock mock is recording (could be usefull for debugging or to desing new unit tests quickly)

This is the Rust version of https://gitlab.in2p3.fr/CTA-LAPP/PHOENIX_LIBS2/PhoenixClock project. This project aims to ease the use of clock in complex environments, especially distributed environments where latencies measurement has to be precise and reproductible when running unit tests. **PhoenixClock** provide **PGenericClock**, a template classe which takes two arguments : - The main clock backend (could be **clock**, **PClockNs** for nanoseconds, etc) - A mock of a clock, **PClockMock**, which can play, register and replay a sequence of clock calls These clocks are activated with a mode `PClockMode::PClockMode` which can be : - `PClockMode::NO_MOCK` : for a normal usage - `PClockMode::MOCK` : when the mock the desired clock is played - `PClockMode::MOCK_RECORD` : when the real clock backend is used but the clock mock is recording (could be usefull for debugging or to desing new unit tests quickly)

This is the Rust version of https://gitlab.in2p3.fr/CTA-LAPP/PHOENIX_LIBS2/network/PhoenixSocket project. This project aims to ease the use of socket in complex environments, especially distributed environments where latencies measurement has to be precise and reproductible when running unit tests. **PhoenixSocket** provide **PGenericSocket**, a template classe which takes two arguments : - The main socket backend (could be **zmq**, **unix socket**, etc) - A mock backend, **PMockBackend**, which can play, register and replay a sequence of socket calls These sockets are activated with a mode `PSocketMode::PSocketMode` which can be : - `PSocketMode::NO_MOCK` : for a normal usage - `PSocketMode::MOCK` : when the mock the desired socket is played - `PSocketMode::MOCK_RECORD` : when the real socket backend is used but the socket mock is recording (could be usefull for debugging or to desing new unit tests quickly)

Zero-knowledge end-to-end encryption with post-quantum hybrid KEM (ML-KEM-768/1024 + X25519)