-
Notifications
You must be signed in to change notification settings - Fork 230
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Errors delegating to Traces #2556
Comments
@RamRamez cam you please investigate? |
This issue is somehow complicated. Basically DApp prepares transactions (here delegation) based on pledges data stored in backend. On @Danibelle first delegation, she couldn't send updated data to feathers so the pledges data were obsolete. No easy fix comes to my mind at this moment, the only working solution I would recommend is that after delegating on project money (Here the campaign), user should wait for about 10 blocks of rinkeby to be mined before next attempt to delegating from the same project. |
OK Thank you Amin. I understand this from subsequent delegations - the difference between the first delegation (yours) and subsequent delegations is that there were TWO "Oh No" messages instead of just one. But the bigger issue is that instantly upon signing the MetaMask transaction - all the errors popped up instantly. Seems like there should be a delay after signing that says WAIT ... and the Delegation Window should either close when I select Delegate, or stay in a waiting stage until the blocks are mined. |
I do get a 'Transaction Successful' once the blocks are mined. |
In DM also @Danibelle mentioned an important clue! The first delegation was not complete! |
Receiving errors when delegating funds to Traces - this one on paying Amins Trace on Giveth 2 Campaign.
Issue type: Error
Unable to update the donation in feathers
Name:
Error
LineNumber:
undefined
FileName:
undefined
Stack
"NotAuthenticated: Error\n at new c (https://d33wubrfki0l68.cloudfront.net/bundles/0a08adf3c01a13e5279cc943c2ec2023df978ba3.js:2:2531672)\n at convert (https://d33wubrfki0l68.cloudfront.net/bundles/0a08adf3c01a13e5279cc943c2ec2023df978ba3.js:2:2533700)\n at p. (https://d33wubrfki0l68.cloudfront.net/bundles/0a08adf3c01a13e5279cc943c2ec2023df978ba3.js:2:2524987)\n at p.onack (https://d33wubrfki0l68.cloudfront.net/bundles/0a08adf3c01a13e5279cc943c2ec2023df978ba3.js:2:1337452)\n at p.onpacket (https://d33wubrfki0l68.cloudfront.net/bundles/0a08adf3c01a13e5279cc943c2ec2023df978ba3.js:2:1336857)\n at p. (https://d33wubrfki0l68.cloudfront.net/bundles/0a08adf3c01a13e5279cc943c2ec2023df978ba3.js:2:1338793)\n at p.r.emit (https://d33wubrfki0l68.cloudfront.net/bundles/0a08adf3c01a13e5279cc943c2ec2023df978ba3.js:2:624669)\n at p.ondecoded (https://d33wubrfki0l68.cloudfront.net/bundles/0a08adf3c01a13e5279cc943c2ec2023df978ba3.js:2:1328330)\n at l. (https://d33wubrfki0l68.cloudfront.net/bundles/0a08adf3c01a13e5279cc943c2ec2023df978ba3.js:2:1338793)\n at l.r.emit (https://d33wubrfki0l68.cloudfront.net/bundles/0a08adf3c01a13e5279cc943c2ec2023df978ba3.js:2:624669)"
The text was updated successfully, but these errors were encountered: