PHP.wasm – service worker utils
Regroupement des fonctions utiles à tous les modules de la chaîne LoadIstex
Utilities for executing code in Web Workers
Utilities for running tasks on worker threads
Utilities for running tasks on worker threads
No description provided.
Utils for string compression and decompression with multiple strategies for Node.js and browser
Seamless REST/GraphQL API mocking library for browser and Node.js.
Consistent Web Workers in browser and Node.
General utilities for plugins to use
Utility functions for working with TypeScript's API. Successor to the wonderful tsutils. 🛠️️
Utilities for running tasks on worker threads
A fast, efficient Node.js Worker Thread Pool implementation
Utilities for running tasks on worker threads
A little factory function to create a JSON-RPC based Web Worker implementation.
Communicate with a Web Worker using Promises, allowing transferList
webpack Validation Utils
Utilities for ESLint plugins.
The worker which is used by the worker-timers package.
The broker which is used by the worker-timers package.
Type utilities for working with TypeScript + ESLint together
Utils to work with WebWorker
Utilities for working with TypeScript + ESLint together
Utilities for collecting TSConfigs for linting scenarios.
Collect same jobs to single worker, reduce job number and improve thread utilization.
A Sidekiq utility that takes a programmatic approach to starting|stopping Sidekiq workers
A set of common classes and utilities for the ac-summarization workers
Uses Rails HTTP Streaming to render a 'processing request' page that will keep the connection alive during long processes.
Deactive any type of background worker when the cluster is standby. This is useful when deploying apps that utilize timers or queues with a blue/green deploy strategy.
Provides RobotLab::RactorWorkerPool — a pool of Ruby Ractor workers for executing CPU-bound, Ractor-safe tools in parallel. Includes RactorBoundary (deep-freeze utility for crossing Ractor boundaries), RactorJob/RactorJobError/RobotSpec (frozen data carriers), RactorMemoryProxy (shared Memory access from inside Ractors), and RactorNetworkScheduler (dependency-ordered pipeline across Ractors).
Application to gather prometheus style metrics # Usage Install the gem into your gemfile ```gem prometheus-collector``` Install your gemset ```bundle install``` Consume the program. ``` require 'prometheus/collector' class Guage < Prometheus::Collector::Extensions::Base install def run # Do some things that would be collected in Prometheus::Client Objects end end ``` Mount the Prometheus::Collector::Application application, or start it from your app.rb ``` Prometheus::Collector::Application.start ``` # How it works The collector app makes use of the Prometheus client collector and exporter middleware to allow you to write custom applications that export prometheus style metrics. It is designed as a bare-bones scaffold to get you off the ground with a ruby applet to get some statistics. It utilizes rack and its middleware. The interface is fairly straightforward: Your Metric Executing code needs to extend Prometheus::Collector::Extensions::Base for 'repeatedly-runbable' operations and Prometheus::Collector::Extensions::Once for something that should only be executed Once. Your class should implement an instance level `run` function, and may optionally implement a class level `schedule` function: This must return a `cron` style string to tell the application when to invoke your `run` code. By default, `schedule` is set to `* * * * *` which would allow the code to be executed every minute. ### Scheduling Scheduling is implemented via em-cron. Thus the re-scheduling of a task should occur within the parameters of the `schedule` string but is evaluated upon completion. Thus in normal operation, the code should not execute more than one `run` of a given worker definition at a time.
No description provided.
No description provided.
No description provided.