mini CLR rounds on newsfeed - READY FOR REVIEW

[owocki]

Description

This is what this looks like:

The bones are done done:

• mechanisms to create /schedule match rounds
• mechanisms to continually refresh match rankings
• mechanism to automatically make a CLR payout
• mechanism to follow users straight on newsfeed

Still gotta put the finishing touches on here:

• show CLR estimates on newsfeed items (not just leaderboard)
• make estimates refresh when new tip is made (either ajax or fresh)
• make tips non alpha
• a TLDR how it works module (need help from design)
• what do we do with the follow data? do we highlight it into the various tab types?
• follow buttons everywhere on newsfeed
• create Earnings, newsfeed items, email when payout happys. celebrate it!

Refers/Fixes

#5941

Testing

tested locally

should be merged along with #5916

[codecov]

Codecov Report

Merging #5942 into stable will increase coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           stable    #5942      +/-   ##
==========================================
+ Coverage   28.79%   28.84%   +0.05%     
==========================================
  Files         270      271       +1     
  Lines       23742    23933     +191     
  Branches     3454     3487      +33     
==========================================
+ Hits         6837     6904      +67     
- Misses      16636    16752     +116     
- Partials      269      277       +8     

Impacted Files	Coverage Δ
app/dashboard/views.py	11.58% <0.00%> (ø)	⬆️
...rketing/management/commands/no_applicants_email.py	0.00% <0.00%> (ø)	⬆️
...eting/management/commands/assemble_leaderboards.py	42.20% <0.00%> (ø)	⬆️
app/townsquare/clr.py	12.64% <0.00%> (ø)
app/dashboard/utils.py	40.81% <0.00%> (+3.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 8b1d85d...53ea785. Read the comment docs.

[owocki]

build is failing bc of some rinkeby issue

   
        if http_error_msg:
>           raise HTTPError(http_error_msg, response=self)
E           requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: https://rinkeby.infura.io/

[danlipert]

build is failing bc of some rinkeby issue

   
        if http_error_msg:
>           raise HTTPError(http_error_msg, response=self)
E           requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: https://rinkeby.infura.io/

@owocki You need to use a real infura account now with the app id and such https://community.infura.io/t/legacy-key-deprecation/443

[danlipert]

Looking good so far - seems to just need the typical cleanup and also you accidentally mvd the clr.py file instead of cp

[danlipert]

Probably worth generating a throwaway keypair here for defaults

[owocki]

@owocki You need to use a real infura account now with the app id and such https://community.infura.io/t/legacy-key-deprecation/443

sure; is there a .TRAVIS_ENV somewhere we can update? app/travis.env looks like

[owocki]

61987bc handles rinkeby key