Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
The bounty program web site has poor error handling.
It gives the same "technical difficulties" diagnostic in all of the constraints checked with triggers:
Your reward votes on this issue would exceed 100%.
No votes on issues created after the current pay period
- other internal errors.
When you get the "oops" message, check to see if your vote actually worked. If so, the problem is harmless.
Otherwise, report the problem in the #bounties channel in discord. Note that the error message itself isn't all that helpful. We need to know exactly what you were trying to do such as log in or cast a specific vote.
Everybody is more than welcome to pitch in and fix these usability paper cuts in bounty issue #491.
July 31 Database Problems
We (Dan, David, Jim) think we fixed it:
- 26891c4 2018-08-04 09:30:44 -0500 trust_cert: use utf8 to match github_users
If you see Uncaught exception was thrown while processing this request. or cannot prepare sql statement you are not alone. Report the problem in the #bounties channel in discord. Note that the error message itself isn't all that helpful. We need to know exactly what you were trying to do such as log in or cast a specific vote.
Diagnosis and treatment
The mysql database started reporting
Table 'xataface.trust_cert' doesn't exist Jul 31 16:08:33.
This coincides with some work on converting some of the tables to unicode as part of
the following commits:
- 3934d16 2018-07-30 14:35:13 +0000 Hide weight field when entering votes
- d62bad1 2018-07-27 12:32:44 -0500 budget, reward: don't retrospectively drop votes
- ddc1abe 2018-07-27 12:25:19 -0500 budget_wt: use frozen weights where available
- e146005 2018-07-27 12:22:06 -0500 utf8 charset fixes
- 2b6d579 2018-07-27 11:37:16 -0500 rewards: use reward_vote.weight where available
One of the more useful diagnostics,
Turn off 'foreign_key_checks' and try again. started showing
up 2018-08-03T06:25:24.265059Z after some flailing around with
service mysqld restart and
InnoDB Troubleshooting and such.
set foreign_key_checks=0 and then
set foreign_key_checks=1 seems to make the symptoms go away
for a while. Currently, only a very limited number of people can login an issue SQL commands to
the database. Ask around in
#bounties to contact them.