madkom / event-store-client Goto Github PK

Great library.

Found an issue in a specific case when GES is retrying a message to the client.

1. run 1 persistentSubscription.php, but comment out the ack part.
2. add a message
3. See the message come in, then Ctrl-C the persistentSubscription.php
4. restart 1 persistentSubscription (with ack part back in), it shows Subscription confirmed:, at the exact time the GetEventStore is retrying the un-acked message, the persistentSubscription stops and exits. The message isn't handled.
5. try restarting the persistentSubscription it will keep doing the same thing.
6. If I start 2 persistentSubscriptions, 1 will stop and exit, the other will handle the message and keep waiting for additional messages. If I restart the stopped one it will now work.

Thanks.

Hey there, awesome library! Is it possible to disable output described below? I can't find where it comes from though:

consumer_1 | Madkom\EventStore\Client\Domain\Socket\Data\ReadStreamEventsCompleted {
consumer_1 | 1: events(1) =>
consumer_1 | [0] =>
consumer_1 | Madkom\EventStore\Client\Domain\Socket\Data\ResolvedIndexedEvent {
consumer_1 | 1: event =>
consumer_1 | Madkom\EventStore\Client\Domain\Socket\Data\EventRecord {
consumer_1 | 1: event_stream_id => 'someteststream'
consumer_1 | 2: event_number => 1431
consumer_1 | 3: event_id => '�=?��o�і��N�'
consumer_1 | 4: event_type => 'testType'
consumer_1 | 5: data_content_type => 1
consumer_1 | 6: metadata_content_type => 1
consumer_1 | 7: data => '{"test":"bla"}'
consumer_1 | 8: metadata => ''
consumer_1 | 9: created => 635841737138180630
consumer_1 | 10: created_epoch => 1448576913818
consumer_1 | }
consumer_1 | }
consumer_1 | 2: result => 0
consumer_1 | 3: next_event_number => 1432
consumer_1 | 4: last_event_number => 1431
consumer_1 | 5: is_end_of_stream => true
consumer_1 | 6: last_commit_position => 10572603
consumer_1 | 7: error => ''
consumer_1 | }