wait-on is a cross platform command line utility and Node.js API which will wait for files, ports, sockets, and http(s) resources to become available
Timeout HTTP/HTTPS requests
A simple Node.js module to check if a TCP port is already bound.
Emit `ETIMEDOUT` or `ESOCKETTIMEDOUT` when ClientRequest is hanged
Missing keepalive http.Agent
The safe way to handle the `connect` socket event
Utility to wait for a TCP port to open.
A socket implementation for PGlite enabling remote connections
Gracefully shutdown a running HTTP server.
Client for the realtime Engine
Detects the ALPN protocol
Official library for using the Slack Platform's Socket Mode API
Make low-level DNS requests with retry and timeout support.
Schema validation for the mutation server protocol (MSP).
Standards-compliant WebSocket server and client
Wait for a condition to be true
TypeScript definitions for wait-on
Unix datagram socket
Throttle a function to limit its execution rate
Debounce a function
Wait for multiple callback
CLI for Socket.dev
a library of conditions that are useful for end-to-end tests
Detect the appearance of an element in the browser DOM
A script that waits for a TCP socket to be available at a given address
Companion gem for the Hyperion HTTP server. Patches PG::Connection so exec_params and friends cooperate with Async::Scheduler. Fibers serve other requests while one fiber waits on Postgres. Pure Ruby, drop-in.
by is a library preloader for ruby designed to speed up process startup. It uses a client/server approach, where the server loads the libraries and listens on a UNIX socket, and the client connects to that socket to run processes. For each client connection, the server forks a worker process, which uses the current directory, stdin, stdout, stderr, and environment of the client process. The worker process then processes the arguments provided by the client. The client process waits until the worker process closes the socket, which the worker process attempts to do right before it exits.
Monitor `clamd` from the luxury of your existing OkComputer setup! This check will make noise when the daemon does not respond to messages. It makes a socket connection, sends a PING and waits for a PONG. If any of that does not occur, you'll know it.