In case of visibility record not consistent with workflow execution, it's good to have a CLI cmd to update doc, similar to delete doc.

Hi @lucabriguglia

I just updated the project I made a couple of years ago when your project was named Weapsy.CQRS. Now I'm using the latest version of Kledex and .Net Core 3.1.

I let you the links in case you wanna include them in the documentation:

• http://elvanydev.com/Microservices-part3/
• https://github.com/vany0114/microservices-dotnetcore-docker-servicefabric

Thanks for k

Provide better explanation and examples of async message routing.

See chat discussion for the why?

Guy Radford @guyradford 22:08
...
I have managed to get the router to put the ActionEvent out through Bernard... but the router then try to route the message internally... I have trued to get$actionEvent->stopPropagation(true); and $actionEvent->setParam(MessageBus::EVENT_PARAM_MESSAGE_HANDLED, tru

Currently, there's no documentation about mixing management and messaging operations in a transaction. The only documentation about transactional processing refers to messaging operations.

I can't seem to figure out how to pass it the proper options to get the Delayed Message Plugin to work properly when using servicebus.

My current attempt is as follows:

Consumer:

  const options = {
      ack: true,
      queueOptions: {
        exchangeOptions: {
          type: 'x-delayed-message',
          'x

The current codebase requires ElasticSearch 6 (we currently test with 6.8.8). Please document this requirement (and maybe provide for clear error handling in the code when this requirement is not met,
to provide for better user experience).

( related: #313 )

From @alprema on March 15, 2016 10:20

Since the IStorage.Write() method returns a Task, it should be waited by InMemoryMessageMatcher in order to catch exceptions.

Copied from original issue: Abc-Arbitrage/Zebus.Persistence#3

In the QuickInstall section of the ReadMe, is the following:

You can also build these files from source: https://github.com/nsqio/nsq (official), or https://github.com/judwhite/nsq (fork) to add the ability to run as a Windows Service.

Is the separate Fork still necessary for the Windows Service Build? It looks as though [A PR in NSQ]

node-ts/bus#56 indicates that the documentation is lacking around how to integrate all the components into a solution, especially around how to create a message-driven set of distributed services.

NServiceBus has a set of examples/tutorials that demonstrate some messaging core concepts and how to implem

prooph/proophessor-do-symfony#30

But please note issue with examples. Maybe docs update? And video with example seems to be outdated. ALso, message_detection does not work for me. "QueryBus was not able to identify a Finder for query "

Currently a warning is logged when publishing a message and there are no subscribers for that message type. The warning should only be logged once per message type.

i am trying to register my message Hander for azure servicebus and i see the following description about one of the constructors of messageHandlerOptions class:-
maxConcurrentCalls maximum number of concurrent calls to the onMessage handler
autoComplete true if the pump should automatically complete message after onMessageHandler action is completed. false otherwise.
**maxAutoRenewDurat

We need a linter to check for common mistakes that violate SDK imposed restrictions in workflow and activity implementations.
We can base it on the contributed one: https://github.com/sagikazarmark/cadencelint

Currently, it's only applied on the keyvault.
The way dotnet text works makes it hard as it can only accept a single test project a time.

/cc @jtaubensee @vinaysurya @nemakam