
Security News
Open Source Maintainers Demand Ability to Block Copilot-Generated Issues and PRs
Open source maintainers are urging GitHub to let them block Copilot from submitting AI-generated issues and pull requests to their repositories.
server-events
Advanced tools
An asynchronous cross-server eventing. Uses Redis Pub/Sub messaging system for cross-server communication.
Say we have N servers servicing an API for an app and a worker server running some heavy loads. All the servers are connected to a Redis cluster. An action by the app triggers a worker job that produces a result in an unknown time. A result that the app is interested in. ServerEvents allows an API endpoint to respond with the result just as it becomes available. Worker can send a response to an endpoint instance on a particular server right after it has finished running a job. If worker fails to deliver results in time, the event will time out and the API endpoint can respond with a controlled message.
Intialize a ServerEvents instance by providing Redis server options. Optionally you can subscribe to listen 'ready' and 'error' events.
const ServerEvents = require('server-events');
const randomEvents = new ServerEvents({
host: 'localhost',
port: 6379,
db: 0
});
// connect to redis server
await randomEvents.init()
randomEvents.onerror(function(store, error) {
// store can be either 'outputStore' or 'inputStore'
console.log(store, error);
});
Events are referenced by name and id. The name specifies context while id can be used to reference a certain object (i.e. database table index).
randomEvents.emit('not so random', 12);
Additional arguments passed to the emitter will be passed on to the listener.
await randomEvents.emit('pi event', 314, 'arg1', 1, {type: 'object'});
Events returned as promises. Provide a thenable if you wish to get the results as an array.
randomEvents.on('pi event', 314).then(function(result) {
// result ~ ['arg1', 1, {type: 'object'}]
});
Or spreadable to receive them naturally.
randomEvents.on('pi event', 314).then(function([a, b, c]) {
// a ~ 'arg1', b ~ 1, c ~ {type: 'object'}
});
Event timeout will result in an error.
randomEvents.on('wont', 'happen').catch(function(error) {
// event has timed out
});
Custom timeout can be passed.
randomEvents.on('ev', 101, 5000).catch(function(a) {
// event will timeout after 5000 ms unless result is returned
});
The default timeout for all ServerEvents instances is 10000 ms. This can be overriden for each instance:
randomEvents.timeout = 1000; // 1 second
npm test
FAQs
Cross-server eventing
The npm package server-events receives a total of 0 weekly downloads. As such, server-events popularity was classified as not popular.
We found that server-events demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Open source maintainers are urging GitHub to let them block Copilot from submitting AI-generated issues and pull requests to their repositories.
Research
Security News
Malicious Koishi plugin silently exfiltrates messages with hex strings to a hardcoded QQ account, exposing secrets in chatbots across platforms.
Research
Security News
Malicious PyPI checkers validate stolen emails against TikTok and Instagram APIs, enabling targeted account attacks and dark web credential sales.