locking mechanism to handle dupe gitcoinbot comments

[owocki]

Description

locking mechanism to handle dupe gitcoinbot submission

Checklist

• linter status: 100% pass
• changes don't break existing behavior
• commit message follows commit guidelines

Affected core subsystem(s)

bounties

Testing

tested it by adding a time.sleep() to the sync_geth method

Refers/Fixes

#2488

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (master@0275e2b). Click here to learn what that means.
The diff coverage is 16.66%.

@@            Coverage Diff            @@
##             master    #2674   +/-   ##
=========================================
  Coverage          ?   29.86%           
=========================================
  Files             ?      162           
  Lines             ?    13017           
  Branches          ?     1741           
=========================================
  Hits              ?     3888           
  Misses            ?     9005           
  Partials          ?      124

Impacted Files	Coverage Δ
app/dashboard/utils.py	35.55% <10%> (ø)
app/app/settings.py	80.16% <100%> (ø)
app/app/utils.py	22.42% <14.28%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0275e2b...72d2860. Read the comment docs.

[mbeacom]

@owocki This LGTM - Does this seem to work fine with Python 3.7?

My main hangup is that redis-semaphore was last updated in December 2016 and doesn't seem to have a whole lot of traction as far as stars/forks go.

I'm not saying we shouldn't merge this - just an ongoing support question. Did you happen to check out https://github.com/vaidik/sherlock ?

[owocki]

yes i tested with python 3.7 and it worked fine.

i agree sherlock looks more fully featured, but it also hasn't had an update in ~ 7 months

[owocki]

#2695