GianIac/numax

If you'd like to help with Numax, this is a great place to start, thank you so much for taking a look ! Add tests that explicitly validate bounded JSON page behavior near the 1 MiB response limit. Why The API intentionally bounds page responses and updates next_cursor when truncating. This is important behavior that deserves dedicated regression coverage. Scope in crates/nx-api/src/routes.rs tests: add/extend scenarios for large keys pages add/extend scenarios for large peers pages verify response stays within limit and pagination remains contract-safe no endpoint contract changes Done when tests confirm bounded responses do not exceed limit truncation still returns coherent items and next_cursor all nx-api tests pass Notes Please prioritize deterministic tests over huge random payloads. Thanks again for considering contributing to Numax.

If you'd like to help with Numax, this is a great place to start, thank you so much for taking a look ! Strengthen boundary coverage for scan_prefix_page_after_bounded in nx-store. Why This function is sensitive to both record and byte limits. Boundary tests help prevent off-by-one regressions in pagination and byte accounting. Scope in crates/nx-store/src/lib.rs tests: add case with max_records = 0 add case where a record exactly matches remaining byte budget add case that exceeds budget by 1 byte keep function behavior unchanged Done when all new boundary tests pass behavior at limits is explicit and documented by test names no unrelated store logic changes Notes Please keep test fixtures small and readable. Thanks again for considering contributing to Numax.

If you'd like to help with Numax, this is a great place to start, thank you so much for taking a look ! Add tests for remote-op duration histogram bucket mapping in observability metrics. Why DurationHistogram uses fixed manual buckets. Boundary tests reduce the chance of silent regressions in latency bucket accounting. Scope in crates/nx-core/src/observability.rs tests: verify bucket placement at exact upper bounds verify placement just above a bound verify sum and count accumulation consistency no metric naming/contract changes Done when histogram boundary tests pass bucket, sum, and count behavior is explicitly asserted existing observability tests remain green Notes Please keep tests deterministic and narrowly scoped. Thanks again for considering contributing to Numax.

If you'd like to help with Numax, this is a great place to start, thank you so much for taking a look ! Add focused tests for --color parsing behavior in nx-cli. Why parse_requested_color supports multiple forms (--color=... and --color ...) and custom validation paths. Dedicated tests improve confidence in CLI UX and error quality. Scope in crates/nx-cli/src/main.rs tests: cover --color=auto|always|never cover --color <value> cover missing value after --color cover invalid value handling no CLI behavior changes unless needed to match intended current contract Done when tests pass under cargo test -p nx-cli valid values parse correctly invalid/missing values return expected clap errors Notes Please keep this issue limited to color argument parsing tests. Thanks again for considering contributing to Numax.

If you'd like to help with Numax, this is a great place to start, thank you so much for taking a look ! Extend CI build-wasm job to run ABI smoke tests for non-Rust guest examples (where tests exist). Why CI currently validates only part of non-Rust guest coverage automated checks prevent drift in guest ABI contracts this improves trust in examples used for onboarding Scope update .github/workflows/ci.yml build-wasm job execute available smoke tests for guest language examples (C/C++/TinyGo as applicable) keep runtime and existing checks unchanged Done when CI runs non-Rust ABI smoke tests and reports failures clearly current successful paths remain intact workflow remains maintainable and readable Notes If a language toolchain is not available by default, document/justify the step clearly. Thanks again for considering contributing to Numax.