Failing build

[cer]

See https://github.com/eventuate-examples/eventuate-tram-golang-examples-customers-and-orders/runs/2334547181?check_suite_focus=true

Only io.eventuate.examples.tram.ordersandcustomers.customers.domain.events.CustomerCreatedEvent is published - no events related to order creations.

[dartartem]

@cer I read messages and found that order service does not have eventuate.outbox.id property set. Fixed. Tested locally (just in case). Now I will create PR.

[dartartem]

PR: #4

[cer]

@cer I read messages and found that order service does not have eventuate.outbox.id property set. Fixed. Tested locally (just in case). Now I will create PR.

How did it work locally for you?

[dartartem]

I am trying to understand

[dartartem]

So, it did not help. It worked for me locally because db schema is compatible between application id and db id versions. Cdc just checks the id header and case if it is missed it generates it depending on database generated id, otherwise just process the message (in case if service that sent message does not have eventuate outbox id specified).

[cer]

It worked for me locally because db schema is compatible between application id and db id versions. Cdc just checks the id header and case if it is missed it generates it depending on database generated id, otherwise just process the message (in case if service that sent message does not have eventuate outbox id specified).

I am not sure what you are trying to say. Please explain more including why your environment's db schema is different than Github's?

Also, is the different due to differing snapshots versions? incorrect local copies of libraries? Please pull the images to make sure your environment has the latest.

Also, please analyze the results of the build:

• The container logs including the HTTP proxy.
• The messages that are printed including those in the received_message table

[dartartem]

I am not sure what you are trying to say. Please explain more including why your environment's db schema is different than Github's?`

it is not different. I just saying that if one service uses db id and other is not they can work together.
The reason why builds fail is still unclear for me.

Also, is the different due to differing snapshots versions? incorrect local copies of libraries? Please pull the images to make sure your environment has the latest.

I will check

Also, please analyze the results of the build:
The container logs including the HTTP proxy.
The messages that are printed including those in the received_message table

Will do

[dartartem]

tried to remove all docker images and gralde/maven local repositories. Tests pass.

[dartartem]

@cer I think this image is not up to date: eventuateexamples/eventuate-tram-examples-customers-and-orders-order-service

Looks like It does not support db ids. I think it is published from master, not from development.

[cer]

@cer I think this image is not up to date: eventuateexamples/eventuate-tram-examples-customers-and-orders-order-service

Looks like It does not support db ids. I think it is published from master, not from development.

Why 'think'? Please be specific:

$ docker images | grep eventuateexamples/eventuate-tram-examples-customers-and-orders-order-service
eventuateexamples/eventuate-tram-examples-customers-and-orders-order-service           latest                            7230f71ad32a        7 weeks ago         357MB

The build should probably publish separately tagged images from master and development.

But would this cause the tests to fail? And why do they pass locally for you?

[dartartem]

But would this cause the tests to fail? And why do they pass locally for you?

it is not a global answer, it just a clue :) . Image has no tags, so it's version is not clear.
However, I see that some printed messages have ids (not dbid, just ids), but they should not have them if eventuate.outbox.id specified.

[dartartem]

@cer

I checked messages carefully. There are only CustomerCreatedEvent and OrderCreatedEvent.
It means that OrderCreatedEvent is not handled. Because after order creation, when OrderCreatedEvent handled,
there should be one of: CustomerCreditReservedEvent, CustomerCreditReservationFailedEvent, CustomerValidationEvent.
Unfortunately there are errors at all. In case if cdc processing failed cdc should print errors. When proxy cannot send http request there are errors too. Go customer-service also has error handlers. But there is nothing.

I extended customer-service logging.
Extended logging of proxy.

But after extending customer logs tests become passing:

https://github.com/dartartem/eventuate-tram-golang-examples-customers-and-orders/runs/2341692790
https://github.com/dartartem/eventuate-tram-golang-examples-customers-and-orders/runs/2342824978
https://github.com/dartartem/eventuate-tram-golang-examples-customers-and-orders/runs/2344556738

I have no idea what is happening. But if it repeats, we will have more logged info.