Neptune-Crypto/neptune-core - CodSpeed

neptune-core

Blog Docs Changelog

Performance History

Latest Results

docs: Improve docs wrt. Triton programs Co-authored-by: skaunov <skaunov@disroot.org>

master

3 days ago

WIP: Precheck incoming connections before upgrade to peer_loop

precheck-new-connections

6 days ago

ci: Ensure panic without debug assertions A number of tests must panic, also when debug assertions are not activated. This should act as a tripwire test against the bad logic I reference here: https://github.com/Neptune-Crypto/neptune-core/issues/816#issuecomment-4170429369

add-release-tests-to-ci

6 days ago

devops: Fix weird dev profile settings In a previous commit by me, some weird dev profile settings were set, disabling debug assertions. That's problematic because we rely on those for some internal testing and state consistency checks. Cf. 85e6799c116f1f9082720e6d250c45620a0f6b78 Luckily, no tests failed when I activated debug assertions and overflow checks again. Notice that the test profile inherits these settings from the dev profile, so this commit reenables debug assertions in tests.

master

6 days ago

test(DbtVec): Verify out-of-bounds panic on `get` and `set` Following the discussion in #816 I came to the wrong conclusion that an `assert` could be changed to a `debug_assert`. This test shows why that's not the case. An out-of-bounds for these async getters and setters should panic. If the assert is not there, then instead of panicking, the method will in the scenario outlined in the test return a wrong value -- a value that's no longer an element in the list.

master

6 days ago

log: Throttle some network logs and specify bounce reason (#896) 1. When logging a bounce event, specify the reason. This change fixes #839. 2. Throttle log messages with this effect. One bounce message per 20 seconds per bouncee. 3. Degrade bounce log messages due to max num peers reached from `warn!` to `trace!`. Bounce due to max num peers reached is as benign as it gets. 4. Degrade abrupt closure messages from `warn!` to `trace!` and throttle to 1 message per 20 s. 5. Add and use new dependency, `tracing-throttle`, which allows fine-grained configuration of log message in the tracing framework.

master

6 days ago

feat: visibility

skaunov:sentoutput_by_indicies

7 days ago

log: Reduce logging severity In case of bounce due to max num peers, use trace. And for all abrupt closures, use trace.

asz/softer-bounce-logs

7 days ago

Latest Branches

0%

WIP: Precheck incoming connections before upgrade to peer_loop#899

6 days ago

f94fae6

precheck-new-connections

0%

ci: Ensure panic without debug assertions#898

6 days ago

81ad3c1

add-release-tests-to-ci

-1%

feat: add sent tx getter for a wallet#895

7 days ago

e9ef8e3

skaunov:sentoutput_by_indicies

© 2026 CodSpeed Technology

Home Terms Privacy Docs