Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More β†’
Socket
Sign inDemoInstall
Socket

tigerbeetle-node

Package Overview
Dependencies
Maintainers
3
Versions
321
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

tigerbeetle-node - npm Package Versions

23
…
33

0.16.17

Diff

Changelog

Source

TigerBeetle 0.16.17

Released: 2024-12-09

This release includes a correctness fix for the preview API get_account_balances, get_account_transfers, query_accounts, and query_transfers. If your application uses these features it might be affected.

Safety And Performance

  • #2544

    Fix correctness bug which affected the preview get_account_balances, get_account_transfers, query_accounts, and query_transfers queries. Specifically, if several filters are used (that is, several fields in QueryFilter or AccountFilter are set), then some objects might be missing from the result set.

    The underlying data is safely stored in the database, so re-running these queries using the new version of TigerBeetle will give correct results.

  • #2550

    Fix panic in the node client which occurred on eviction.

  • #2534

    Fix incorrect ABI used on aarch64 for the client library. To prevent such issues from cropping up in the future, add aarch64 testing to CI.

  • #2520

    Add extra assertions to verify object cache consistency.

  • #2485

    Implement network fault injection in VΓΆrtex, our non-deterministic whole system simulator.

Features

  • #2539

    Log level can now be specified at runtime.

  • #2538

    Log messages now include UTC timestamp (formatted as per RFC 3339).

Internals

  • #2543

    Relax compiler requirements for building TigerBeetle. While we only support building using one specific version of Zig, the one downloaded via ./zig/download.sh, you can try using other versions.

  • #2533

    Document how to handle errors during release. TigerBeetle's release process is complicated, as we need to release, in lockstep, both the tigerbeetle binary and all the related client libraries. The release process is intentionally designed to be "highly-available", such that a failure of any aspect of a release can be safely detected, isolated, and repaired. But, so far, this wasn't clearly spelled out in the documentation!

TigerTracks 🎧

sentientwaffle
published 0.16.16 β€’

Changelog

Source

TigerBeetle 0.16.16

Released: 2024-12-02

The highlight of today's release is the new official Python client, implemented in #2527, and #2487. Please kick the tires!

Safety And Performance

  • #2517

    Require that all replicas in a cluster have the latest TigerBeetle binary as a precondition for an upgrade.

  • #2506

    Fix several bugs when handling misdirected writes. That is, situations when the disk reports a write as successful, despite the write ending up in the wrong place on the disk!

  • #2478

    Make sure that TigerBeetle memory is not swappable, otherwise a storage fault can occur in a currently swapped-out page, circumventing TigerBeetle guarantees.

  • #2522

    REPL correctly emits errors when several objects are used as an argument of an operation that only works for a single object, like get_account_transfers.

  • #2502

    Add randomized integration tests for the Java client.

Features

Internals

  • #2526

    Ignore OOM failures during fuzzing. Fuzzers normally don't use that much memory, but, depending on random parameters selected by swarm testing, there are big outliers. If all concurrent fuzzers hit a seed that requires a lot of memory, a fuzzing machine runs out of physical RAM. Handle such errors and don't treat them as fuzzing failures.

  • #2510

    Track the number of untriaged issues on DevHub.

TigerTracks 🎧

sentientwaffle
published 0.16.15 β€’

sentientwaffle
published 0.16.14 β€’

Changelog

Source

TigerBeetle 0.16.14

Released: 2024-11-25

Safety And Performance

  • #2501

    Call DetachCurrentThread when the Java client is closed. The underlying Zig TigerBeetle client runs in a separate thread internally, and a handler to this thread was being leaked.

    This is not noticeable in normal operation, but could impact long running processes that create and close clients frequently.

  • #2492

    Document that it's not possible to currently look up or query more than a full batch of accounts atomically without using the history flag and querying balances.

  • #2434

    Add the ability to check timestamp order - and verify they are monotonically increasing - for accounts and transfers inside Vortex.

Internals

  • #2455

    Recently the VOPR has gotten too good, and it's very tempting to switch to an empirical mode of coding: write some code and let the VOPR figure out whether it is correct or not.

    This is suboptimal - silence of the VOPR doesn't guarantee total absence of bugs and safety comes in layers and cross checks. Just formal or informal reasoning is not enough, we need both.

    Document this in TigerStyle.

  • #2472

    Previously, the Zig part of languages clients logged directly to stderr using Zig's std.log, but since directly outputting to stderr is considered rude for a library, logging was disabled.

    This PR adds in scaffolding for sending these logs to the client language to be handled there, tying in with native log libraries (eg, Log4j). No languages use it yet, however.

    Additionally, log warn and err directly to stderr, if there's no handler.

TigerTracks 🎧

sentientwaffle
published 0.16.13 β€’

Changelog

Source

TigerBeetle 0.16.13

Released: 2024-11-18

Safety And Performance

  • #2461

    Fix a broken assert when a recently-state-synced replica that has not completed journal repair receives an old commit message.

  • #2474

    Retry EAGAIN on (disk) reads. This is essential for running TigerBeetle on XFS, since XFS returns EAGAIN unexpectedly.

  • #2476

    Fix a message bus crash when a client reconnects to a replica without the replica receiving a disconnect for the first connection.

  • #2475

    Save 256KiB of RAM by not having a prefetch cache for historical balances. (Historical balances are never prefetched, so this cache was unused.)

  • #2482

    Update hardware requirements in the documentation to include the recommended network bandwidth, advice for very large data files, and farther emphasis on the importance of ECC RAM.

  • #2484

    Don't panic the client when the client's session is evicted. Instead, report an error any time a new batch is submitted to the evicted client. (How the error is reported depends on the client language – e.g. Java throws an exception, whereas Node.js rejects the Promise).

    Note that if running clients are evicted, that typically indicates that there are too many clients running – check out the suggested system architecture.

Features

  • #2464

    Add REPL interactivity. Also change the REPL from dynamic to static allocation. Thanks @wpaulino!

Internals

  • #2481

    Expose the VSR timestamp to the client. (This is an experimental feature which will be removed soon – don't use this!)

TigerTracks 🎧

sentientwaffle
published 0.16.12 β€’

Changelog

Source

TigerBeetle 0.16.12

Released: 2024-11-11

Safety And Performance

  • #2435

    Fix an attempt to access uninitialized fields of tb_packet_t when tb_client_deinit aborts pending requests. Also add Java unit tests to reproduce the problem and validate the fix.

  • #2437

    Fix a liveness issue where the cluster gets stuck despite sufficient durability, caused by buggy logic for cycling through faulty blocks during repair. Now, we divide the request buffer between the read_global_queue and faulty_blocks, ensuring that we always request blocks from both.

Features

  • #2462

    Update DevHub styling.

  • #2424

    Vortex can now not only crash replicas (by killing and restarting the process) but also stop and resume them.

Internals

  • #2458

    Fix the Dotnet walkthrough example that misused length instead of the final index when slicing an array. Thanks @tenatus for reporting it!

  • #2453

    Fix a CI failure caused by concurrent processes trying to create the fs_supports_direct_io probe file in the same path.

  • #2441

    Replace curl shell invocation with Zig's http client. 😎

  • #2454

    Properly handle "host unreachable" (EHOSTUNREACH) on Linux, instead of returning unexpected error.

  • #2443, #2451, #2459, #2460, #2465

    Various code refactorings to improve naming conventions, readability, and organization.

TigerTracks 🎧

TigerBeetle (unreleased)

Released: 2024-11-04

Safety And Performance

  • #2356

    Add "Vortex" – a full-system integration test. Notably, unlike the VOPR this test suite covers the language clients.

  • #2430

    Cancel in-flight async (Linux) IO before freeing memory. This was not an issue on the replica side, as replicas only stop when their process stops. However, clients may be closed without the process also ending. If IO is still in flight when this occurs, we must ensure that all IO is cancelled before the client's buffers are freed, to guard against a use-after-free.

    This PR also fixes an unrelated assertion failure that triggered when closing a client that had already closed its socket.

  • #2432

    On startup and after checkpoint, assert that number of blocks acquired by the free set is consistent with the number of blocks we see acquired via the manifest and checkpoint trailers.

  • #2436

    Reject connections from unknown replicas.

  • #2438

    Fix multiversion builds on MacOS.

  • #2442

    On an unrecognized error code from the OS, print that error before we panic. (This was already the policy in Debug builds, but now it includes ReleaseSafe as well.)

  • #2444

    Fix a panic involving an in-flight write to an old reply after state sync.

Internals

  • #2440

    Expose reply timestamp from vsr.Client. (Note that this is not yet surfaced by language clients).

TigerTracks 🎧

sentientwaffle
published 0.16.11 β€’

Changelog

Source

TigerBeetle 0.16.11

Released: 2024-10-28

Safety And Performance

  • #2428

    Make Grid.reserve() abort rather than returning null. When Grid.reserve() aborts, that indicates that the data file size limit would be exceeded by the reservation. We were already panicking in this case by unwrapping the result, but now it has a useful error message.

  • #2416

    Improve availability and performance by sending start_view message earlier in the new-primary recovery – as soon as the journal headers are repaired.

  • #2360

    Refactor compaction to clarify the scheduling logic, schedule more aggressively, and make it easier to run multiple compactions concurrently. This also improved the benchmark performance.

Features

  • #2425

    Support multiversion (non-automatic) upgrades when the replica is started with --development or --experimental.

Internals

  • #2427

    Allow a release's Git tag and config.process.release to differ. This simplifies the release process for hotfixes, when the Git tag is bumped but the config.process.release is unchanged.

TigerTracks 🎧

sentientwaffle
published 0.16.10 β€’

Changelog

Source

TigerBeetle 0.16.10

Released: 2024-10-21

Safety And Performance

  • #2414

    Improve performance & availability during view change by ensuring a replica only repairs the portion of the WAL that is required to become primary, instead of repairing it in its entirety.

  • #2412

    Add a unit test for Zig's stdlib sort.

    Stable sort is critical for compaction correctness. Zig stdlib does have a sort fuzz test, but it doesn't cover the presorted subarray case, and doesn't check arrays much larger than the sort algorithm's on-stack cache.

  • #2413

    Fix a bug in the MessageBus wherein connections weren't being terminated during client teardown.

Internals

  • #2405

    Fix a bug in the benchmark wherein the usage of --account-count-hot was broken when used in conjunction with the uniform distribution.

  • #2409

    Revamp the core_missing_prepares liveness-mode check to correctly check for the prepares that a replica should repair (after #2414).

TigerTracks 🎧

sentientwaffle
published 0.16.9 β€’

Changelog

Source

TigerBeetle 0.16.9

Released: 2024-10-15

Safety And Performance

  • #2394, #2401

    TigerBeetle clients internally batch operations for improved performance. Fix a bug where an unclosed link chain could be batched before another linked chain, causing them to be treated as one long linked chain. Additionally, prevent non-batchable requests from sharing packets entirely.

  • #2398

    AMOUNT_MAX is used as a sentinel value for things like balancing transfers to specify moving as much as possible. Correct and fix its value in the Java client. Thanks @tKe!

Features

  • #2274

    Improve the benchmark by adding Zipfian distributed random numbers, to better simulate realistic conditions and as a precursor to approximating YCSB.

  • #2393

    Previously, TigerBeetle's clients disallowed empty batches locally, before the request was even sent to the cluster. However, this is actually a valid protocol message - even if it's not used by the current state machine - so allow empty batches to be sent from clients.

  • #2384

    Revamp client documentation so that each snippet is self-contained, and standardize it across all languages.

Internals

TigerTracks 🎧

sentientwaffle
published 0.16.8 β€’

Changelog

Source

TigerBeetle 0.16.8

Released: 2024-10-07

Safety And Performance

  • #2359

    Significantly reduced P100 latency by incrementally spreading the mutable table's sort during compaction. This leverages the optimization of sort algorithms for processing sequences of already sorted sub-arrays.

  • #2367

    Improve the workload generator to support concurrent tests with different ledgers.

  • #2382, #2363

    Fix VOPR seeds. For more awesome details about the backstory and solutions to these issues, please refer to the PR.

Features

  • #2358

    Update the REPL to support representing the maximum integer value as -0, serving as the AMOUNT_MAX sentinel. Additionally, other negative values such as -1 can be used to represent maxInt - 1.

    Also, include support for hexadecimal numbers for more convenient inputting of GUID/UUID literals (e.g. 0xa1a2a3a4_b1b2_c1c2_d1d2_e1e2e3e4e5e6).

    Allow the timestamp field to be set, enabling the REPL to be used for imported events.

Internals

  • #2376

    Use zig fetch as a replacement for downloading files, removing dependence on external tools.

  • #2383

    Port of Rust's dbg! macro to Zig, and the corresponding CI validation to prevent code using it from being merged into main! 😎

  • #2370, #2373

    Verify the release versions included in the multiversion binary pack at build time (not only during runtime) and improve the tigerbeetle version --verbose command's multiversion output.

  • #2369

    Fix a multiversioning issue where the binary size exceeded the read buffer, failing to parse the executable header.

  • #2380

    Consistently use transient_error instead of transient_failure and cleanup the StateMachine code.

  • #2379

    Add missing links to the operations query_accounts and query_transfers in the documentation and include the declaration for QueryFilter and QueryFilterFlags in the tb_client.h header.

  • #2333

    Clearer error message when the replica crashes due to a data file being too large, instructing the operator to increase the memory allocated for the manifest log.

TigerTracks 🎧

23
…
33
SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚑️ by Socket Inc