A streaming way to send data to a Node.js Worker Thread
Runs the following loaders in a worker pool
Properly hijack require, i.e., properly define require hooks and customizations
Use Rollup with workers and ES6 modules today.
Library with base interfaces for LangGraph checkpoint savers.
A mutex for guarding async workflows
Client library for interacting with the LangGraph API
Thread comment integration for Univer Sheets.
Shared thread comment UI components and services for Univer.
Thread comment UI integration for Univer Sheets.
Use Rollup with workers and ES6 modules today.
Thread comment UI integration for Univer Docs.
Shared thread comment models, commands, and services for Univer.
Preset for thread comments in Univer Sheets.
Preset for thread comments in Univer Docs.
Helpers for communicating between JavaScript environments using message passing.
Remote data source integration for Univer thread comments.
A native Node.js module that can capture JavaScript stack traces from main and worker threads, even with blocked event loops.
Jazzer.js libfuzzer-based fuzzer for Node.js
A minimal and tiny Node.js Worker Thread Pool implementation, a fork of piscina, but with fewer features
Utilities for executing code in Web Workers
Work with IANA language tags.
No description provided.
Full BCP 47 language subtag data from the official IANA repository, in JSON format with multiple indices.
Language definitions and parsers for Thread
Thread dataflow integration for data processing pipelines, using CocoIndex.
A safe, fast, flexible code analysis and parsing library built in Rust. High-level entry point for the Thread ecosystem.
A lightweight, thread-safe Ruby library for parsing the Accept-Language HTTP header as defined in RFC 2616, with full support for BCP 47 language tags.
Yet another ImageMagick hardcore gui-frontend with multi-threading. Only Russian language is supported.
An implementation of the thread-local variable provided in many programming languages like Java.
Eventbox is a model of concurrent computation that is used to build thread-safe objects with arbitrary interfaces. It is [kind of advancement](#comparison-threading-abstractions) of the well known [actor model](https://en.wikipedia.org/wiki/Actor_model) leveraging the possibilities of the ruby language. It is a small, consistent but powerful threading abstraction which **integrates well into existing environments**.
Sup is a console-based email client for people with a lot of email. * GMail-like thread-centered archiving, tagging and muting * Handling mail from multiple mbox and Maildir sources * Blazing fast full-text search with a rich query language * Multiple accounts - pick the right one when sending mail * Ruby-programmable hooks * Automatically tracking recent contacts
A thread-safe two dimensional sparse matrix data structure with C, Java and Ruby bindings. It was created to make loading and accessing medium sized (10GB+) matrices in boxed languages like Java/Scala or Ruby easier.
A thread-safe two dimensional sparse matrix data structure with C, Java and Ruby bindings. It was created to make loading and accessing medium sized (10GB+) matrices in boxed languages like Java/Scala or Ruby easier.
TCB gives Rails applications a clean domain language for DDD. Thread-safe event bus, command routing, aggregate pattern, and opt-in event persistence.
Language server implementation that provides Steep-equivalent type checking features using ruby-lsp's single-process multi-threaded architecture
This is the official Ruby client for the Zizq job queue server. Zizq is a simple, single binary, zero dependency, language agnostic job queue. Features: - Enqueue and process jobs across programming languages - Persistent/journalled - Multi-thread and/or multi-fiber - Scheduled jobs - Prioritized queues - Optional ActiveJob integration - Unique jobs - Cron scheduling (recurring jobs) - Job introspection and management, including `jq` filters This client supports multi-threaded and/or multi-fiber concurrency and is very fast. The Zizq server provides everything needed. There are no separate external storage dependencies to configure such as Redis or a RDBMS. See https://zizq.io for full details and documentation.
Provides RobotLab::DocumentStore — a thread-safe, in-memory semantic search store backed by fastembed (BAAI/bge-small-en-v1.5). Store text documents by key and retrieve the closest matches to a natural-language query using cosine similarity. Works standalone or as a drop-in extension for robot_lab agents and networks.
CommandSet is a user interface framework. Its focus is a DSL for defining commands, much like Rake or RSpec. A default readline based terminal interpreter (complete with context sensitive tab completion, and the amenities of readline: history editing, etc) is included. It could very well be adapted to interact with CGI or a GUI - both are planned. CommandSet has a lot of very nice features. First is the domain-specific language for defining commands and sets of commands. Those sets can further be neatly composed into larger interfaces, so that useful or standard commands can be resued. Optional application modes, much like Cisco's IOS, with a little bit more flexibility. Arguments have their own sub-language, that allows them to provide interface hints (like tab completion) as well as input validation. On the output side of things, CommandSet has a very flexible output capturing mechanism, which generates a tree of data as it's generated, even capturing writes to multiple places at once (even from multiple threads) and keeping everything straight. Methods that normally write to stdout are interposed and fed into the tree, so you can hack in existing scripts with minimal adjustment. The final output can be presented to the user in a number of formats, including contextual coloring and indentation, or even progress hashes. XML is also provided, although it needs some work. Templates are on the way. While you're developing your application, you might find the record and playback utilities useful. cmdset-record will start up with your defaults for your command set, and spit out an interaction script. Then you can replay the script against the live set with cmdset-playback. Great for ad hoc testing, usability surveys and general demos.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.