Mostafa Moradian
Mostafa Moradian
After some investigation and the fact that Gossip protocol libraries are old and unmaintained, I think the go to approach is to use Raft, considering that [Kafka](https://developer.confluent.io/learn/kraft/) also used it...
@eabasir This only shows half the traces, namely those that happened between GatewayD and postgres (DB), and not the ones between the client (e.g. psql) and GatewayD.
Basically you should trace when the client connects until it disconnects and observe and compare the changes before it. This way you can see what is important to an E2E...
I guess this can be moved back to the backlog until one has time to do it.
@eabasir I couldn't reproduce it on my machine. It just works.
@eabasir `git` was recently updated by @sinadarbouy and is available on the `main` branch.
@eabasir @sinadarbouy Can you test this again with the latest version to see if it is still reproducible? I couldn't reproduce this again.
@sinadarbouy How about adding [`pull_policy: always`](https://docs.docker.com/reference/compose-file/services/#pull_policy) to the GatewayD image, so every time you run it, it'll pull the _actual_ latest version, rather than the existing one?
Hey @ChrisDev83, Thanks for reporting this. It's gonna be fixed in #372. Please test it and provide feedback.
@ChrisDev83 Interesting! I'll see if this is a configuration option in kafka-go, and I'll make it configurable via JS. I just saw this: https://github.com/segmentio/kafka-go/discussions/1415