Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rely on fedmsg-provided queue. #40

Merged
merged 2 commits into from Sep 13, 2014
Merged

Conversation

ralphbean
Copy link
Contributor

fedbadges implemented this little callLater mechanism a long time ago
before fedmsg and moksha provided a much more sophisticated queueing and
monitoring framework. Inadvertently, this callLater logic actually serves to hide how
many messages are in the fedbadges backlog. By removing it, we can get a
better sense of what the consumer is doing.

fedbadges implemented this little callLater mechanism a long time ago
before fedmsg and moksha provided a much more sophisticated queueing and
monitoring framework.  This callLater logic actually serves to **hide**
how many messages are in the fedbadges backlog.  By removing it, we can
get a better sense of what the consumer is doing.
@pypingou
Copy link
Member

👍 for me

ralphbean added a commit that referenced this pull request Sep 13, 2014
@ralphbean ralphbean merged commit c6a7714 into develop Sep 13, 2014
@ralphbean ralphbean deleted the feature/fedmsg-queueing branch September 13, 2014 12:57
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.

None yet

2 participants