Permalink
Commits on Mar 9, 2016
  1. Merge pull request #48 from fedora-infra/feature/a-picture-is-worth-a…

    …-thousand-words
    
    A diagram for how fedbadges relates to the other badges.fp.o pieces.
    ralphbean committed Mar 9, 2016
Commits on Mar 8, 2016
Commits on Oct 13, 2015
  1. Merge pull request #47 from fedora-infra/feature/force-lowercase

    Force lowercase when comparing package names with pkgdb.
    ralphbean committed Oct 13, 2015
Commits on Aug 28, 2015
  1. 0.5.2

    ralphbean committed Aug 28, 2015
  2. Don't award badges to bodhi or taskotron..

    ..to spare @kparal's inbox.
    ralphbean committed Aug 28, 2015
Commits on May 5, 2015
  1. Merge pull request #45 from fedora-infra/feature/liberal-topic

    Set the consumer to consume all topics.
    ralphbean committed May 5, 2015
  2. Set the consumer to consume all topics.

    Previously, this didn't matter since everything was under the fedoraproject namespace.. but *now* we want to award badges for anitya activity, and they're under the ``org.release-monitoring....`` namespace.
    ralphbean committed May 5, 2015
  3. 0.5.1

    ralphbean committed May 5, 2015
Commits on May 4, 2015
  1. Merge pull request #44 from fedora-infra/feature/email2fas

    Add a new email2fas flag modeled off the existing nick2fas flag.
    ralphbean committed May 4, 2015
Commits on Nov 4, 2014
  1. Turbo Mode

    When we first receive a message, we put ourselves to sleep to wait for a
    moment.  The reason for this is that, when things are 'calm' on the bus, we
    receive messages "too fast".  A message that arrives to the badge awarder
    triggers (usually) a check against datanommer to count messages.  But if we try
    to count them before this message arrives at datanommer, we'll get skewed
    results!  Race condition.  We go to sleep to allow ample time for datanommer to
    consume this one before we go and start doing checks on it.  When fedbadges was
    first released, this was absolutely necessary.
    
    Since that time, the fedmsg bus has become much more congested.  So, to improve
    our average speed at handling messages, we only do that sleep statement if
    we're not already backlogged.  If we know we have a huge workload ahead of us,
    then go ahead and start handling messages as fast as we can.
    ralphbean committed Nov 4, 2014
  2. Remove unused imports.

    ralphbean committed Nov 4, 2014
Commits on Oct 8, 2014
  1. Merge pull request #42 from fedora-infra/feature/suppress-integrity-e…

    …rrors
    
    Suppress integrity errors.
    ralphbean committed Oct 8, 2014
  2. Suppress integrity errors.

    ralphbean committed Oct 8, 2014
Commits on Oct 7, 2014
  1. Icky.

    ralphbean committed Oct 7, 2014
Commits on Oct 3, 2014
  1. Merge pull request #41 from fedora-infra/feature/race-conditions

    Use threading.local to separate sessions.
    ralphbean committed Oct 3, 2014
  2. PEP8.

    ralphbean committed Oct 3, 2014
  3. PEP8.

    ralphbean committed Oct 3, 2014
  4. Use threading.local to separate sessions.

    The fedbadges backend was designed to only have one thread.
    
    This past week we gave it many threads (so that it could keep up with
    its increasingly demanding workload), but this has started to generate
    crashes from race conditions (mostly inside sqlalchemy).
    
    This patch will not solve all of those problems, but it will solve some.
    This will make it so that *each* thread will get its very own database
    session so that they don't stomp on each other quite so much.
    ralphbean committed Oct 3, 2014
Commits on Oct 1, 2014
  1. Demote this log statement.

    ralphbean committed Oct 1, 2014
Commits on Sep 30, 2014
  1. Add missing import.

    ralphbean committed Sep 30, 2014
Commits on Sep 29, 2014
  1. 0.5.0

    ralphbean committed Sep 29, 2014
Commits on Sep 13, 2014
  1. Merge pull request #40 from fedora-infra/feature/fedmsg-queueing

    Rely on fedmsg-provided queue.
    ralphbean committed Sep 13, 2014
Commits on Sep 11, 2014
  1. Rely on fedmsg-provided queue.

    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.
    ralphbean committed Sep 11, 2014