Ben
Ben
**Describe the bug** As mentioned [here](https://github.com/massalabs/massa/pull/3364#issuecomment-1380268069), it would seem that running `cargo test` or `cargo test --doc` misses checks that are called behind `#[cfg(any(test, feature = "testing"))]` (Same behavior if...
**Is your feature request related to a problem? Please describe.** The current context to a failure when the bounds are broken is "Failed u32 deserialization". Something like "Deserialized u32 out...
**Is your feature request related to a problem? Please describe.** Signature verification is opted into, as the best time to test is context dependant. E.g. a node can receive the...
**Is your feature request related to a problem? Please describe.** Right now, the `SecureSend` wrapper does not communicate which step of the process is current. - Signed data for sending...
Normally I would have just included it in #3384 but this is security related, and want to make sure I understand it right, and doc-it well
There is currently no utilities being used to guard against mismanagement of secrets within the source code. Maintaining confidentiality is highly fragile, requiring all code dealing with secrets to not...
**Is your feature request related to a problem? Please describe.** When looking to contribute, I decided to run a `cargo clippy -- -W clippy::pedantic`, and see what cropped up. A...
* [ ] document all added functions * [ ] try in sandbox /simulation/labnet * [ ] unit tests on the added/changed features * [ ] make tests compile *...
We are building an SPA in the frontend. Our design at this point involves navigating to the third party, and in the redirect, setting things up to then pass to...
The Project I am working on doesn't conform to the assumptions in keyberon about input/output pins being rows/columns. This PR does two things: - In the matrix file, renames variables...