Open connoroday opened 4 years ago
Code handles this situation ! The cron job hadn't run yet which is why it hadn't reflected. Closing this out
we should maybe expose a button that syncs bounties, from the blockchain, to the DB, in the admin for our CS team :)
I ran into this issue twice in the last two weeks and had to open support tickets to get the updated TX reflected in the bounty.
Initially, It looks like the gas fee is getting set to 5 GWEI on the bounties payout TX. It seems likely that this super low fee is being set by the Gitcoin web app but I'm not sure.
Either way, once the 5 GWEI tx payout is sent, it's stuck in the pending tx queue indefinitely until the user handles it manually. I'll poke around the bounties web app and see if I can spot the fee being set low there as if that is the case, a fix there would be especially nice.
Describe the bug
When paying out a bounty, if the transaction gets stuck has to be resubmitted with a higher gas price, it will be stuck shown as “pending” on the Gitcoin bounty page
To Reproduce
Pay out with very low few, then increase fee
Expected behavior
Once a dropped and replaced transaction goes through, Gitcoin should reflect a successful payout
Screenshots
See: https://gitcoin.co/issue/nucypher/hackathon/8/100023187 https://etherscan.io/tx/0xe9460ebc40f9708c5948297806c45a19b3f537e5c2df73c13097a3eb13b3aff7
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context