A queue for limited process fork
A simple tool to keep requests to be executed in order.
Runs typescript type checker and linter on separate process.
Tiny queue data structure
fast, tiny `queueMicrotask` shim for modern engines
High-priority task queue for Node.js and browsers
A shim for the setImmediate efficient script yielding API
Detect Node.JS (as opposite to browser environment). ESM modification
Promise queue with concurrency control
Microsoft Azure Storage SDK for JavaScript - Queue
The smallest and simplest JavaScript priority queue
queue-lit is a tiny queue data structure in case you `Array#push()` or `Array#shift()` on large arrays very often
Next tick shim that prefers process.nextTick over queueMicrotask for compat
Coding agent CLI with read, bash, edit, write tools and session management
An implementation of the Unicode Line Breaking Algorithm (UAX #14)
High-priority task queue for Node.js and browsers
A simple, fast, robust job/task queue, backed by Redis.
Promise queue with concurrency control. This is a fork of sindresorhus/p-queue, but with CommonJS support.
Runs typescript type checker and linter on separate process.
seriously like the best async child process library
Simple JS queue with auto run for node and browsers
In memory queue system prioritizing tasks
Promise-based queue
The fastest javascript implementation of a double-ended queue. Used by the official Redis, MongoDB, MariaDB & MySQL libraries for Node.js and many other libraries. Maintains compatability with deque.
Library to maintain a forking queue of Cucumber processes, with optional VNC displays.
Library to maintain a forking queue of Cucumber processes, with optional VNC displays. Designed for JRuby and Windows.
Forks X children, processes all jobs in the queue and all processes quit when there are no more jobs to complete
Resque-mongo is a fork of resque that uses mongo as a queue backend. Resque is a Redis-backed Ruby library for creating background jobs, placing those jobs on multiple queues, and processing them later. Background jobs can be any Ruby class or module that responds to perform. Your existing classes can easily be converted to background jobs or you can create new classes specifically to do work. Or, you can do both. Resque is heavily inspired by DelayedJob (which rocks) and is comprised of three parts: * A Ruby library for creating, querying, and processing jobs * A Rake task for starting a worker which processes jobs * A Sinatra app for monitoring queues, jobs, and workers.
NOTE: This is a fork of puma-plugin-telemetry, modified to: - Support Puma 7 - Add LogTarget, with custom formatter: and transform: options - Warn about socket telemetry on unsupported platforms Puma plugin which should be able to handle all your metric needs regarding your webserver: - ability to publish basic puma statistics (like queue backlog) to both logs and datadog - ability to add custom target whenever you need it - ability to monitor puma socket listen queue (!) - ability to report requests queue time via custom rack middleware - the time request spent between being accepted by Load Balancer and start of its processing by Puma worker
Verity is a Ruby test framework built around a core principle: tests are executable data structures, not a nested DSL. Each test carries structured metadata (tags, timeout, resource declarations) used for CI filtering, parallel grouping, and scheduling. Execution uses process-level forking with a SQLite manifest as the work queue and result store.
= Ungulate According to Wikipedia, this can mean "hoofed animal". Camels have hooves. This is a gem for uploading and processing images using an Amazon Web Services stack. It comes with a few goodies: * ungulate_server.rb - simple queue runner that expects a YAML-encoded job description for RMagick * Ungulate::FileUpload - a model for e.g. Rails that does some cryptography stuff - example to follow * A view helper for Rails: "ungulate_upload_form_for" == Installation gem install ungulate == Documentation http://wiki.github.com/camelpunch/ungulate/ == Note on Patches/Pull Requests * Fork the project. * Make your feature addition or bug fix. * Add tests for it. This is important so I don't break it in a future version unintentionally. * Commit, do not mess with rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull) * Send me a pull request. Bonus points for topic branches. == Copyright Copyright (c) 2011 Camel Punch Limited. See LICENSE for details.