Skip to content

Conversation

@avigailberger
Copy link
Contributor

retries

Provide a way to externally configure the maximum amount of retries handlers get executed before declaring the message as poison and rejecting it

Closes #35

Guy Baron and others added 28 commits May 7, 2019 14:12
the test now validates that messages get rejected when handlers return
an error and all rety attempts did not sccueed
increased test coverage
added tests for protobuf serlializer
fixing a bug where saga configuration functions were run only when saga was created
fix wrong timeout interface method in documentation
increasing test timeouts of ci build to 60s
Timeouts now are not passed as bus messages to avoid the need to deal
with serialization.
Timeout interface changed so that handling a timeout now accepts a
transaction and a bus instance instead of an invocation and a bus
message
This allows saga instances ifthey choose to continue react to messages after they
timeout
otherwise updating it

In addition fixing some linting errors
first commit towards supporting persistent timeouts
update documentation after changes of timeout interface : https://github.com/wework/grabbit/pull/78/files
Update SAGA.md - timeout interface doc fix
transaction

When a handler fails and gets retried each retry should be run in a new
transaction
fixing a bug in which all handler retires executed within the same
@coveralls
Copy link

Coverage Status

Coverage increased (+3.05%) to 73.469% when pulling 4d54fc7 on allow-configuring-max-retries into 4d48803 on master.

@rhinof
Copy link
Contributor

rhinof commented Jun 5, 2019

@avigailberger I am closing this PR. please create a new one that merges from your branch into the v1.x branch and not to master.

@rhinof rhinof closed this Jun 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Allow configuring max retries

5 participants