Skip to content

Releases: wework/grabbit

v1.1.8

02 Dec 10:44
Compare
Choose a tag to compare

Point release containing additional functionality and bug fixes

Improvements

  • Added metric that records the execution time of the entire saga, from it's creation until deletion #224

Fixed Issues

  • Headers get placed on messages even if no value for the header is set #221

v1.1.7

02 Nov 09:21
211f219
Compare
Choose a tag to compare

Point release fixing the following issue

  • Correlation Ids are wrongly set on outgoing commands #219

v1.1.6

20 Oct 11:18
f6ae8c5
Compare
Choose a tag to compare

Point release containing additional functionality and bug fixes

Improvements

  • Transactional outbox configuration #37
  • Transactional outbox metrics #202
  • The ability for producers to specify an idempotency key on the BusMessage. #106

Fixed Issues

  • Messages get re-queued When GlobalRawMessageHandler returns an error #188
  • AMQP channel shuts down when the GlobalRawMessageHandler returns an error #187
  • Wrong started by saga identifier value was set when creating a new saga #194
  • When a saga instance is not found in the saga store do not reject the message #196
  • The target service was not resolved properly in SagaInvocation #195
  • Saga store log entries do not contain the _service field #206
  • Logger is lost at initialization #200
  • Outbox stops trying sending a message after 50 attempts #203
  • Handlers not resolved properly for messages returned from dead lettering #191
  • migration entry with incorrect name #212
  • Not all contextual data was logged when invoking handlers #217

v1.1.5

29 Sep 11:51
0fda748
Compare
Choose a tag to compare

Point release adding documentation and a sample app

Improvements

  • Added sample application #184
  • Improved documentation #38

v1.1.4

28 Sep 11:58
83cea9c
Compare
Choose a tag to compare

point release with some few Improvements and fixies

Improvements

  • Improved documentation #38
  • Support logging of emperror errors #178
  • Provide the ability to create a BusMessage targeting a specific saga instance #134

Fixed Issues

  • Logging via the invocation interface does not log contextual data #175

v1.1.3

25 Sep 09:52
0f43814
Compare
Choose a tag to compare

Point release containing bug fixes and additional functionality

Improvements

  • allow getting the saga id of the current invoked saga #169
  • Improved wording of saga documentation article (#164)

Fixed Issues

  • fixing ReplyToInitiator not working when the initiator sends a message via the RPC interface (#163)
  • fixed logging issues (#167)

v1.1.2

17 Sep 15:24
40a7588
Compare
Choose a tag to compare

Improvements

  • added reply to initiator functionality to sagas #157
  • added generic handler metrics with message type as the label #144

Fixed Issues

  • increased outbox VARCHAR column length to 2048 #155
  • Fix handle empty body #156
  • set the correct Type and Content-Type headers on outgoing messages #160

v1.1.1

31 Aug 13:33
Compare
Choose a tag to compare

Point release rolling up fixes and improvements for the following issues

Improvements

  • Improved observability via opentracing #141
  • Ability to handle raw amqp messages #137

Fixed Issues

  • When a dead letter handler panics grabbit fails to reject the message #135
  • Worker leaks message channels #148
  • Handling incoming messages with an empty body stops consumer #146
  • Migrations table name is not consistent with naming convention #139

v1.1.0

18 Aug 13:33
Compare
Choose a tag to compare

https://github.com/wework/grabbit/projects/1

Improvments

  • Add the ability for handlers to track the number of execution attempts #95
  • Expose the logger in the invocation #87
  • Allow configuring max retries #84
  • Report message handling metrics #103
  • Persistent timeout manager #32
  • Saga timeouts should be reported via a metric #113
  • Improved documentation #38
  • Support database migrations for grabbit mysql persistent store #42
  • Cleanup logs #50
  • Allow Sending Raw Messages #102
  • Separate amqp connection for ingress and egress #46

Fixed Issues

  • Shutting down txoutbox leaves dangling go routines #55
  • Running two separate bus instances for the same service causes high CPU utilization #124
  • A completing saga action may get executed twice #109
  • Dead Letter Handler does not nack/ack after Processing #104
  • Messages that originate from a saga and routed to the same service get rejected #64
  • Closing rows when querying transactional outbox fails #91
  • Saga configuration functions only run when saga created #74
  • Transactions managed incorrectly between retries #81

v1.0.3

25 Jun 06:18
8eb4f85
Compare
Choose a tag to compare

Point release rolling up fixes and improvements for the following issues

Improvements

Fixed issues