Aaltronav/dougal-software
1
0
Fork 0
mirror of https://gitlab.com/wgp/dougal/software.git synced 2025-12-06 10:47:07 +00:00
Code Issues Packages Projects Releases Activity
Files
6a21ddd1cd2a633bae999973a1d040b5d663abe1
dougal-software/lib/www/server/events/index.js

30 lines
699 B
JavaScript
Raw Normal View History

Replace ad-hoc notifier with pg-listen based version
2023-09-29 15:44:12 +02:00
const { listen } = require('../lib/db/notify');
Refactor SOL/EOL real-time detection handler. This also implements a generic handler mechanism that can be reused for other purposes, such as sending email / XMPP notifications, doing real-time QC checks and so on. Fixes #113.
2021-05-24 13:48:53 +02:00
const channels = require('../lib/db/channels');
Rewrite events listener and handlers. The events listener now uses a proper self-consuming queue and the event handlers have been rewritten accordingly. The way this works is that running init() on the handlers library instantiates the handlers and returns two higher-order functions, prepare() and despatch(). A call to the latter of these is appended to the queue with each new incoming event. The handlers have access to a context object (ctx) which may be used to persist data between calls and/or exchange data between handlers. This is used notably to give the handlers access to project configurations, which are themselves refreshed by a project configuration change handler (DetectProjectConfigurationChange).
2023-10-14 20:53:42 +02:00
const handlers = require('./handlers');
const { ActionsQueue } = require('../lib/queue');
Replace console output by debug functions
2022-05-15 13:37:24 +02:00
const { ERROR, INFO, DEBUG } = require('DOUGAL_ROOT/debug')(__filename);
Auto-create FSP/LSP events from nav header. If the nav header is being received, this will try to detect the start and end of line and create an entry in the log. It doesn't check whether FSP/FGSP LSP/LGSP entries already do exist for that sequence. Closes # 28.
2020-09-28 21:36:32 +02:00
function start () {
Rewrite events listener and handlers. The events listener now uses a proper self-consuming queue and the event handlers have been rewritten accordingly. The way this works is that running init() on the handlers library instantiates the handlers and returns two higher-order functions, prepare() and despatch(). A call to the latter of these is appended to the queue with each new incoming event. The handlers have access to a context object (ctx) which may be used to persist data between calls and/or exchange data between handlers. This is used notably to give the handlers access to project configurations, which are themselves refreshed by a project configuration change handler (DetectProjectConfigurationChange).
2023-10-14 20:53:42 +02:00
const queue = new ActionsQueue();
const ctx = {}; // Context object
const { prepare, despatch } = handlers.init(ctx);
listen(channels, function (data) {
Replace console output by debug functions
2022-05-15 13:37:24 +02:00
DEBUG("Incoming data", data);
Rewrite events listener and handlers. The events listener now uses a proper self-consuming queue and the event handlers have been rewritten accordingly. The way this works is that running init() on the handlers library instantiates the handlers and returns two higher-order functions, prepare() and despatch(). A call to the latter of these is appended to the queue with each new incoming event. The handlers have access to a context object (ctx) which may be used to persist data between calls and/or exchange data between handlers. This is used notably to give the handlers access to project configurations, which are themselves refreshed by a project configuration change handler (DetectProjectConfigurationChange).
2023-10-14 20:53:42 +02:00
// We don't bother awaiting
queue.enqueue(() => despatch(data, ctx));
DEBUG("Queue size", queue.length());
Auto-create FSP/LSP events from nav header. If the nav header is being received, this will try to detect the start and end of line and create an entry in the log. It doesn't check whether FSP/FGSP LSP/LGSP entries already do exist for that sequence. Closes # 28.
2020-09-28 21:36:32 +02:00
});
Clean up whitespace. Commands used: find . -type f -name '*.js'| while read FILE; do if echo $FILE |grep -qv node_modules; then sed -ri 's/^\s+$//' "$FILE"; fi; done find . -type f -name '*.vue'| while read FILE; do if echo $FILE |grep -qv node_modules; then sed -ri 's/^\s+$//' "$FILE"; fi; done find . -type f -name '*.py'| while read FILE; do if echo $FILE |grep -qv node_modules; then sed -ri 's/^\s+$//' "$FILE"; fi; done
2022-04-29 14:48:21 +02:00
Rewrite events listener and handlers. The events listener now uses a proper self-consuming queue and the event handlers have been rewritten accordingly. The way this works is that running init() on the handlers library instantiates the handlers and returns two higher-order functions, prepare() and despatch(). A call to the latter of these is appended to the queue with each new incoming event. The handlers have access to a context object (ctx) which may be used to persist data between calls and/or exchange data between handlers. This is used notably to give the handlers access to project configurations, which are themselves refreshed by a project configuration change handler (DetectProjectConfigurationChange).
2023-10-14 20:53:42 +02:00
INFO("Events manager started");
Auto-create FSP/LSP events from nav header. If the nav header is being received, this will try to detect the start and end of line and create an entry in the log. It doesn't check whether FSP/FGSP LSP/LGSP entries already do exist for that sequence. Closes # 28.
2020-09-28 21:36:32 +02:00
}
module.exports = { start }
Run events manager in a separate process. Not sure if this is going to do anything in terms of improving the handling of and reacting to events, but it doesn't seem to hurt terribly. Eventually, all this will probably need to be refactored to use EventEmitter.
2020-10-02 01:34:49 +02:00
if (require.main === module) {
start();
}
Reference in New Issue Copy Permalink