Closed bruceadams closed 10 years ago
Thankfully, it doesn't appear that we transferred money to deactivated-jashkenas this week. Why is that? My hunch is that we include claimed_time in the query for participants during payday. Yup. So that's good. :-)
It's still a bug that andyet was able to tip deactivated-jashkenas after he was deactivated. Looks like it's time for another self-check, @zwn. :-)
I'm dropping this to ★★☆ since we don't actually move money in this case.
It's still a bug that andyet was able to tip deactivated-jashkenas after he was deactivated. Looks like it's time for another self-check,@zwnhttps://github.com/zwn. :-)
I don't think this is a bug. There is actually no code that prevents it :astonished:. Cf. #1705
How can we tell that a user is deactivated? Unsetting claimed_time
without deleting appropriate elsewhere
returns 500. See
https://www.gittip.com/deactivated-jashkenas/. What it is we should forbid
when fixing tipping to deactivated accounts? Because I was able to
tip 6a2ab9485317 just fine. We need a definition of deactivated account.
deactivated-jashkenas
is showing up as a top receiver on the Ruby community page, which is especially unfortunate since it's a user-facing link that results in a 500. (@zwn and I discussed this a bit on IRC)
deactivated-jashkenas
is showing up as a top receiver on the Ruby community page
Blech. Gross. :-(
Bumping back up to ★★★.
:+1: Just got a 500 error as a result of this issue.
This was fixed by #2507.
After deactivating jashkenas, they sent an email to support saying:
I asked @whit537 to take a look, he says: