event-sourcing

https://github.com/kgrzybek/modular-monolith-with-ddd/blob/54d209639e501301e879aa0d0a84c9ea49e4689e/src/Modules/Meetings/Domain/Meetings/Rules/MeetingAttendeesLimitMustBeGreaterThanGuestsLimitRule.cs#L1-L21

I believe the comparison operator used in the IsBroken method is wrong because the rule is checking that meeting attendees limit must be greater than guests limit.

Describe the bug
When ES is started after it has been stopped while scavenging, it will sometimes throw an exception while trying to mark the scavenge as failed. The error seems to be caused by a boxed long being casted to int.

To Reproduce
Steps to reproduce the behavior:

1. Start scavenging on node
2. Stop node after ChunksCompleted event has been emitted, but before scavenging is

Under the hood, Benthos csv input uses the standard encoding/csv packages's csv.Reader struct.

The current implementation of csv input doesn't allow setting the LazyQuotes field.

We have a use case where we need to set the LazyQuotes field in order to make things work correctly.

This comment says that the message ID is optional,
but for SQL transport it is a mandatory attribute,
in turn it causes misunderstanding?

Is it possible to fix it or did I get something wrong?

https://github.com/ThreeDotsLabs/watermill/blob/b9928e750ba673cf93d442db88efc04706f67388/message/message.go#L20
https://github.com/ThreeDotsLabs/watermill/blob/b9928e750ba673cf93d442db88efc04706f6

Hi I am using NGXS state managment library in my App and I have selector like below and everything is working fine but when I am testing my app I have got error like below. PrintItemsState is lazy loaded and in *.spec.ts NGXS module is imported like NgxsModule.forRoot() . What I noticed problem is that im passing PrintItemsState as argument here:

@Selector([PrintItemsState])

![image](https

Is there a specific app this action is for?
action for ultramsg : https://pipedream.com/apps/ultramsg

Please provide a link to the relevant API docs for the specific service / operation.
https://docs.ultramsg.com/api/post/messages/chat

What is this bug about?

When we bootstrap the chat demo application by npx wolkenkit@4.0.0-internal.108 init, the client uses old API routes, causing a 404 error.

What is the expected result?

When we bootstrap the chat demo application, it works as-is.

What is the actual result?

The chat demo application is not usable, since the client can't fetch from the back-end.

I know it's not a course about RESTful principles but maybe you'll consider in the future extracting resource id from request body to path parameter ?

https://github.com/aspnetrun/run-aspnetcore-microservices/blob/c30712aa099bc335f5613a3b196ea1e943f800a5/src/Services/Catalog/Catalog.API/Controllers/CatalogController.cs#L85

I would like to review the docs and explain also de concepts behind some decisions.
Things needed to explain:

• DDD objectives and reasons why.
• Core concepts like
  • bounded context
  • anti corruption layer
  • domain
  • value objects VS entities
  • aggregates
  • aggregate root
  • layered architecture and each one responsibility
  • reasons for the command and query bus
  • the even