Wrong handling of RabbitMQ messages about pitstop HOT 4 CLOSED

Thanks for your interest in my sample solution!

I will look into this. I haven't heard anyone having this issue before, so I will try to reproduce it with the latest version of the RabbitMQ Docker image.

from pitstop.

@dmitriifilonenko I've updated the messagehandler class based on your version.

I've also split the infrastructure package into 2 separate packages (Messaging and Service Discovery) and updated all NuGet references in all projects. Make sure to update the dotnet docker images to the latest version and rebuild all docker images (updated to dotnet core 2.1.6).

Thanks again for finding this and creating an issue!

from pitstop.

About not being able to do a PR: you're not a contributor on this repo so you're not able to push changes directly to it. So if you want to do a pull request, make sure you fork the repo first to your own Github account and clone it on your machine. Apply your changes and push them to the forked repo. You then will be able to create a pull request on the original Pitstop repo.

from pitstop.

Thank you Edwin!

from pitstop.