DOM trap for a focus
It is a trap! (for a focus)
A set of utils for faster development of GraphQL tools
Simple async batch with concurrency control and progress reporting.
A mutex for guarding async workflows
provides locking mechanism to sync across browser tabs
A inter-process and inter-machine lockfile utility that works on a local or network file system
Lock on asynchronous code
Mutex locks for async functions
TypeScript definitions for async-lock
React focus lock for all Chakra components
Simple lock class
Enables body scroll locking (for iOS Mobile and Tablet, Android, desktop Safari/Chrome/Firefox) without breaking scrolling of a target element (eg. modal/lightbox/flyouts/nav-menus)
Batch processing in JS
lock asynchronous resources.
mutex lock for javascript
AWS SDK for JavaScript Batch Client for Node.js, Browser and React Native
Throttle the parallelism of an asynchronous (promise returning) function / functions
🔐Body scroll locking that just works with everything
A set of utils for faster development of GraphQL tools
It is a trap! (for a focus)
Manage a cluster of child processes
The Screen Orientation API provides methods to lock and unlock the screen orientation.
TypeScript definitions for dom-screen-wake-lock
This is a weak deduper to make things like bulk email run safer. It is not a lock safe for financial/security needs because it uses a weak redis locking pattern that can have race conditions. However, imagine a bulk email job that loops over 100 users, and enqueues a background email for each user. If the job fails at iteration 50, a retry would enqueue all the users again and many will receive dupes. This would continue multiple times as the parent job continued to rerun. By marking that a subjob has been enqueued, we can let that isolated job handle its own failures, and the batch enqueue job can run multiple times without re-enqueueing the same subjobs.
Define retention policies on ActiveRecord models to automatically destroy, delete, or archive expired records. Includes batch limiting, advisory locking, transactional archiving, and background job support.
Instead of making ActiveRecord calls to change a counter field, write them to capacitor. They'll get summarized in a redis hash, with a separate process batch-retrieving and writing to ActiveRecord. Being single-threaded, the writing process avoids row lock collisions, and absorbs traffic spikes by coalescing changes to the same row into one DB write.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.