Robert Kawecki
Robert Kawecki
Apparently, this module only allows one to pass a custom table name, but not a schema name. As a result, it is impossible to use a schema other than the...
We have a process that writes a value to a file which is then required by the actual build process like this: ```sh git describe --tags HEAD >.app-version || date...
Hi, I'm trying to create a consumer that uses a non-durable subscription, as described here: https://pulsar.apache.org/docs/2.7.0/concepts-messaging/#what-is-a-subscription-mode However, I cannot find how to set the subscription mode in the Node.js. Am...
Hi, I have a use case where I expose a Pulsar topic over HTTP via Server-Sent Events. Basically, when a client connects over HTTP, I do this: ```js const reader...
There are currently two issues surrounding the use of `$HOME` and `$PM2_HOME`, and both originate from lib/PM2Tracker.js:165 : * `process.env.HOME` is used, instead of `os.homedir()`. * The user's home is...
If generating an EventSourcedAggregate snapshot in `#commit()` throws an error, the Promise returned from the method never settles. This is because: * We return a deferred's `.promise` * We never...
Currently, `ResourceQueueManager` only supports the dreaded `console.log` method of logging errors. For serious logging, an injected logger object / logger function should be used instead.
Currently, the scope of `esdf` is that it defines an `EventSourcedAggregate` class, the Event and Commit data transfer objects, several utilities and a loading mechanism (tryWith). Thus, a few unused...
Currently, ESDF assumes that event (commit) dispatch to a Publisher only occurs via a Streamer - a component which reads (tails) the database and pushes new commits out. Event Sinks...
event.eventPayload and event.eventType do not make much sense, as they are already located in the event object. "event.payload" and "event.type" would be much better. The codebase should be inspected throughout...