"Thread context" emulation for Node.js based on continuation local storage
Debug namespace structure helper coupled with thread-context
Properly hijack require, i.e., properly define require hooks and customizations
A streaming way to send data to a Node.js Worker Thread
Runs the following loaders in a worker pool
A native Node.js module that can capture JavaScript stack traces from main and worker threads, even with blocked event loops.
A continuation-local storage module compatible with NestJS's dependency injection.
Use Rollup with workers and ES6 modules today.
Library with base interfaces for LangGraph checkpoint savers.
A mutex for guarding async workflows
Request-scoped storage support, based on Asynchronous Local Storage, with fallback to cls-hooked for older Node versions
A transport for pino that sends messages to Loki
Client library for interacting with the LangGraph API
Thread comment integration for Univer Sheets.
Shared thread comment UI components and services for Univer.
Use Rollup with workers and ES6 modules today.
Thread comment UI integration for Univer Docs.
Thread comment UI integration for Univer Sheets.
Remote data source integration for Univer thread comments.
Shared thread comment models, commands, and services for Univer.
Preset for thread comments in Univer Sheets.
Preset for thread comments in Univer Docs.
This is an internal utility, not intended for public usage.
Helpers for communicating between JavaScript environments using message passing.
Thread-local key-value state bag with scoped overrides via blocks, automatic restoration, and thread isolation for implicit context propagation.
Allows Thread to carry context from ancestors.
Logging framework storing context id in thread local
This gem helps track user journey storing X-Request-Id in the thread context and passing it to Sidekiq jobs
Simple lib to reset thread local context on demand. Includes a rack middleware plugin.
Passes thread variables to child spawned threads. Main use case is enabling logging in child thread to keep context of a request.
Sashiko is a small Ruby gem that adds a declarative span DSL on top of OpenTelemetry, plus helpers for keeping trace context attached as work crosses Thread, Fiber, queue, HTTP, and Ractor boundaries. Includes a span-replay mechanism for emitting spans from Ractor workers, optional Faraday and Anthropic adapters, RBS signatures, and a Ruby::Box-aware `tracer:` injection path for multi-tenant observability.
Dynamic scope implementation for Method Overriding: override methods by specified context, only in current thread
bbv.Common is a library of .NET components and functionality including: * (a)synchronous notification component with thread switching using publisher-subscriber pattern, * hierarchical state machine with fluent definition syntax, * programmatic, loosely coupled, context based rule engine, * support for active objects to build multi-threaded applications
Concurrently is a concurrency framework for Ruby and mruby based on fibers. With it code can be evaluated independently in its own execution context similar to a thread: hello = concurrently do wait 0.2 # seconds "hello" end world = concurrently do wait 0.1 # seconds "world" end puts "#{hello.await_result} #{world.await_result}"
Ephemeron improves the performance of your app. It takes on itself the persistence of the ActiveRecord objects. It protects you from saving the same object many times. It checks whether a fetched from a database object was used. It allows you to eliminate the controller's before_actions that are unnecessarily called. Ephemeron works in the context of the thread and does the bulk of its job (i.a. persistence) at the end of the thread's lifecycle. Although, you can trigger the finalization at any given moment. You don't have to make a distinction in the code for the part that is responsible for the domain logic and the other responsible for the application layers.
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.
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.
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.