HTTP graceful shutdown, needed to achieve zero-downtime doing restarts.
Helper library for implementing Kubernetes heath checks and graceful HTTP shutdown in Node applications
gracefully shuts downs http server
A drop-in replacement for fs, making various improvements.
TypeScript definitions for graceful-fs
Promisified graceful-fs
graceful fs.readlink
The time-based use-recency-unaware cousin of [`lru-cache`](http://npm.im/lru-cache)
fs-extra contains methods that aren't included in the vanilla Node.js fs package. Such as recursive mkdir, copy, and remove.
Gracefully terminates HTTP servers in Node.js
graceful exit process even parent exit on SIGKILL.
Executes git commands gracefully. Retries them on errors
A powerful package for gracefully shutting down NestJS applications
Graceful exit when `uncaughtException` emit, base on `process.on('uncaughtException')`.
Gracefully shutdown your modular NodeJS application
Gracefully exit HTTP servers (Express/Koa/Fastify/etc), databases (Mongo/Mongoose), Bree job schedulers, and custom handlers.
This package provides an Axios-based HTTP client adapter that integrates seamlessly with the @apimatic/core package, enabling efficient HTTP request execution with extended capabilities.
Tiny (~5k), dependency-free Node.JS library to make your API more graceful
fs (file system package) extensions
Gracefully terminates HTTP(S) server.
Gracefully shutdown fastify
Close DDP connections gradually on server shutdown
Graceful process exit manager. allows waiting on multiple async services.
Check license info for a package
Minimal HTTP server with graceful shutdown & value passing
Stīpa is a lightweight, zero-dependency HTTP/1.1 framework built entirely on Ruby stdlib. Features: - Pure stdlib (socket, thread, erb, json, securerandom) - HTTP/1.1 with keep-alive, SO_REUSEPORT, and TCP_NODELAY - Thread pool with bounded queue and graceful shutdown - Pre-compiled middleware stack with zero per-request overhead - ERB templates with layouts, partials, and Vue 3 island helpers - CLI generator for MVC and API-only applications - Structured logging in logfmt format - Named route parameters via regex captures
A patched version of Resque that interprets Heroku's TERM as a graceful shutdown. Visit http://quickleft.com/blog/heroku-s-cedar-stack-will-kill-your-resque-workers for more information. 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.
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.