Skip to content

Conversation

@kirkbaly
Copy link

@kirkbaly kirkbaly commented Aug 9, 2018

Added the ability to set a timeout_wait flag for consumers. This ensures the consumer appropriately terminates when its connection is lost, rather than waiting for an idle timeout or a max execution timeout.

kirkbaly and others added 2 commits August 9, 2018 07:28
Added the ability to set a timeout_wait flag for consumers. This ensures the consumer appropriately terminates when its connection is lost, rather than waiting for an idle timeout or a max execution timeout.
} else {
throw $e;
if ($this->gracefulMaxExecutionDateTime
&& $this->gracefulMaxExecutionDateTime <= new \DateTime("@$now")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not just use timestamps everywhere? I mean there is no point to use \DateTime here.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, agreed that timestamps would be preferred. I introduced $lastActivityDateTime as \DateTime to match $gracefulMaxExecutionDateTime which was already in place.

@ramunasd
Copy link
Member

ramunasd commented Apr 9, 2021

I see there is too much conflicts since last update. Please rebase and reopen as new PR.

@ramunasd ramunasd closed this Apr 9, 2021
@kirkbaly
Copy link
Author

kirkbaly commented Apr 9, 2021

This PR was opened about 3 years ago back when the repo was not being maintained, so it is perhaps just a little out of date 😄

However, it does appear that my changes were introduced by @constantable in 5542098. It looks like they are already in master, so there is no need for this PR or a new one.

Thanks!

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.

2 participants