Acknowledgements not being recorded

rishi.rk · July 22, 2021, 8:41am

Hi,

I have a persistent subscription on a $by_category stream, with the ResolvedLinkedTos = true. I’m consuming events and immediately acknowledging the messages

for {
event, err := readConnectionClient.Read()
readConnectionClient.Ack(event.EventID)
…
}

The events are being read, but these events are being sent to the parked messages bucket. How do I ack ResolvedLinkedTos events using the go client?

Thanks

steven.blair · July 22, 2021, 8:56am

Could you show me the EventAppeared code?
You should have access to EventStore.Client.PersistentSubscription.

Then you simply do:

await persistentSubscription.Ack(resolvedEvent);

rishi.rk · July 22, 2021, 9:02am

My implementation is using the EventStore-Client-Go implementation, Ack() expects the UUID. Here’s a reference that I followed

github.com

EventStore/EventStore-Client-Go/blob/master/client/persistent_subscription_read_test.go#L58


	firstReadEvent, err := readConnectionClient.Read()
	require.NoError(t, err)
	require.NotNil(t, firstReadEvent)

	secondReadEvent, err := readConnectionClient.Read()
	require.NoError(t, err)
	require.NotNil(t, secondReadEvent)

	// since buffer size is two, after reading two outstanding messages
	// we must acknowledge a message in order to receive third one
	err = readConnectionClient.Ack(firstReadEvent.EventID)
	require.NoError(t, err)

	thirdReadEvent, err := readConnectionClient.Read()
	require.NoError(t, err)
	require.NotNil(t, thirdReadEvent)
}

func Test_PersistentSubscription_ToExistingStream_StartFromBeginning_AndEventsInIt(t *testing.T) {
	containerInstance, clientInstance := initializeContainerAndClient(t)
	defer func() {

steven.blair · July 22, 2021, 9:08am

Not sure sorry.
I have only used the C# library.
If you Nak it, and add indicate not to park, does it do anything different?

rishi.rk · July 22, 2021, 9:59am

I tried that as well, no difference

steven.blair · July 22, 2021, 10:21am

Out iof ideas, sorry.

yorick.laupa · July 22, 2021, 4:34pm

Hi @rishi.rk and thanks for reporting the issue.

It’s a client bug. Because you set ResolveToS to true and how the Go client is currently written, it does the acknowledgement on the resolved event instead of the link event in this case ($by_category is only comprised of links). The ack is just ignored by the server because the event-id doesn’t belong to the persistent subscription.

I’m currently working on the Go client and will address that issue as soon as possible.