WASI threads proposal implementation in JavaScript
A fast, efficient Node.js Worker Thread Pool implementation
Helpers for communicating between JavaScript environments using message passing.
UnRS Resolver Node API
Web workers & worker threads as simple as a function call
A simple isomorphic library for executing functions inside WebWorkers or Node Threads pools.
This is the **wasm32-wasip1-threads** binary for `@tailwindcss/oxide`
Web workers & worker threads as simple as a function call
Simple worker threads pool using Node's worker_threads module. Compatible with ES6+ Promise, Async/Await.
Fast JavaScript/TypeScript bundler in Rust with Rollup-compatible API.
Oxc Parser Node API
A native Node.js module that can capture JavaScript stack traces from main and worker threads, even with blocked event loops.
Oxc Resolver Node API
Read all directory recursively 列出（遍历）目录下的所有文件，包括子目录
Simple, efficient, scalable data store wrapper for LMDB
Serialize JavaScript to a superset of JSON that includes regular expressions and functions.
Oxc Transformer Node API
A mutex for guarding async workflows
Bare compatibility wrapper for the Node.js builtin `worker_threads` module
Lightweight Web Worker API implementation with native threads
Google OAuth 2.0, OpenID Connect, and mutable Google Workspace-style surfaces for local Gmail, Calendar, and Drive flows.
Utilities for type-safe Web Worker communication with RPC.
Oxc Minifier Node API
A agent component for Convex.
Emulates Python threading API paradigm. Creating threads by giving some block to constructor is sometime slightly unpractical way of running threads. This library allows encapsulating threads to classes, so class can define itself as thread which can be run by plain method call.
A generic thread-safe object pool for Ruby with configurable size, checkout timeouts, idle timeout eviction, health checks, and lazy resource creation.
Sometimes you have an object that is not thread-safe, but you need to make sure each of its methods is thread-safe, because they deal with some resources, like files or databases and you want them to manage those resources sequentially. This small gem will help you achieve exactly that without any re-design of the objects you already have. Just decorate them with SyncEm decorator and that is it.
Provides an object or module to use safely by more than one thread
Use the threadlock method in your class definition to automatically run instance methods inside of an instance-wide re-entrant lock (Monitor). All locked methods in an instance are protected by a single lock, unless a specific lock is specified. You can protect all or some of your methods from being run concurrently. In Ruby>=2.1, threadlock can also be used as a syntactic decorator. Enjoy.
Synchronizable is a generic way to provide per-object thread safety
Provides an object-placeholder for lazy and threaded calculations.
Setup signal handler which dumps backtrace of running threads and number of allocated objects per class. Require 'sigdump/setup', send SIGCONT, and see /tmp/sigdump-<pid>.log.
Thread-safe immutable objects that provide delegation and basic validation to hashes.
This is an experimental branch that implements a connection pool of Net::HTTP objects instead of a connection/thread. C/T is fine if you're only using your http threads to make connections but if you use them in child threads then I suspect you will have a thread memory leak. Also, I want to see if I get less connection resets if the most recently used connection is always returned. Also added a :force_retry option that if set to true will retry POST requests as well as idempotent requests. This branch is currently incompatible with the master branch in the following ways: * It doesn't allow you to recreate the Net::HTTP::Persistent object on the fly. This is possible in the master version since all the data is kept in thread local storage. For this version, you should probably create a class instance of the object and use that in your instance methods. * It uses a hash in the initialize method. This was easier for me as I use a HashWithIndifferentAccess created from a YAML file to define my options. This should probably be modified to check the arguments to achieve backwards compatibility. * The method shutdown is unimplemented as I wasn't sure how I should implement it and I don't need it as I do a graceful shutdown from nginx to finish up my connections. For connection issues, I completely recreate a new Net::HTTP instance. I was running into an issue which I suspect is a JRuby bug where an SSL connection that times out would leave the ssl context in a frozen state which would then make that connection unusable so each time that thread handled a connection a 500 error with the exception "TypeError: can't modify frozen". I think Joseph West's fork resolves this issue but I'm paranoid so I recreate the object. Compatibility with the master version could probably be achieved by creating a Strategy wrapper class for GenePool and a separate strategy class with the connection/thread implementation.
A simple, non-threaded, local-object pub-sub/observer with the ability to pub-sub on topics. Topics can be any Ruby object.
The win32-event library provides an interface to Windows event objects. An event object is a synchronization object whose state can be explicitly set to a signaled state. Event objects are useful in sending a signal to a thread indicating that a particular event has occurred.
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.