abandon claim fails

tzarebczan commented

2018-11-13 17:43:30 +01:00

(Migrated from github.com)

When trying to abandon: https://spee.ch/@NorVegan:3/THEUNMASKING-Part5-TheSexualAssaults-Thumbnail, it gets stuck on "Your claim is being abandond". the abandon call returns:

{"success":false,"message":"That channel does not exist"}

abandon params: {"claimId":"4b13b27a62e4b416161fa4cd4607120598d2fc8d"}

Internal Use

Acceptance Criteria

Definition of Done

Tested against acceptance criteria
Tested against the assumptions of the user story
The project builds without errors
Unit tests are written and passing
Tests on devices/browsers listed in the issue have passed
QA performed & issues resolved
Refactoring completed
Any configuration or build changes documented
Documentation updated
Peer Code Review performed

When trying to abandon: https://spee.ch/@NorVegan:3/THEUNMASKING-Part5-TheSexualAssaults-Thumbnail, it gets stuck on "Your claim is being abandond". the abandon call returns: ```{"success":false,"message":"That channel does not exist"}``` abandon params: ```{"claimId":"4b13b27a62e4b416161fa4cd4607120598d2fc8d"}``` ## Internal Use ### Acceptance Criteria 1. 2. 3. ### Definition of Done - [ ] Tested against acceptance criteria - [ ] Tested against the assumptions of the user story - [ ] The project builds without errors - [ ] Unit tests are written and passing - [ ] Tests on devices/browsers listed in the issue have passed - [ ] QA performed & issues resolved - [ ] Refactoring completed - [ ] Any configuration or build changes documented - [ ] Documentation updated - [ ] Peer Code Review performed

tzarebczan commented

2018-11-13 21:04:01 +01:00

(Migrated from github.com)

I abandoned the above manually, but this looks like it happens if it can't find the claim in it's DB (not sure how it gets into this state - maybe an abandon failure ?)

Edit: Looks like this is a case where the abandon fails on the daemon, and can no longer be re-tried on spee.ch due to the channel error. Still trying to figure out why the claim did not abandon properly on the daemon/blockchain side - https://github.com/lbryio/lbry/issues/1646

I abandoned the above manually, but this looks like it happens if it can't find the claim in it's DB (not sure how it gets into this state - maybe an abandon failure ?) Edit: Looks like this is a case where the abandon fails on the daemon, and can no longer be re-tried on spee.ch due to the channel error. Still trying to figure out why the claim did not abandon properly on the daemon/blockchain side - https://github.com/lbryio/lbry/issues/1646

tzarebczan commented

2018-12-04 18:44:28 +01:00

(Migrated from github.com)

Looks like this is also related to https://github.com/lbryio/lbrycrd/issues/186 - we need to handle this edge case better in our wallet. A user also ran into this on 0.21.2

2018-12-04 12:08:15,722 WARNING  torba.client.basenetwork:28: Wallet server returned an error. Code: -1 Message: the transaction was rejected by network rules.

64: non-mandatory-script-verify-flag (Data push larger than necessary)
[0100000001a7bfdb31abc9ca5eed68fc7da260476cd1e1d5216186d142ff8c150c1014fd36000000006a47304402206df8764da78d06d2c721b788803e0114539408e171280655c783bc7e861b693a02204f563d71754ce7fe648f35a2baa951d2afb7e868880ac0d3b819b3dd10f27366012103d07fe8a0deb7423f552bd1c182251c8a926951f688801e3b2ba681148783a506ffffffff0174180f00000000001976a914322ab934ea45bde72d3f9c8bb0dc00eb0b031f0188ac00000000]

Looks like this is also related to https://github.com/lbryio/lbrycrd/issues/186 - we need to handle this edge case better in our wallet. A user also ran into this on 0.21.2 ``` 2018-12-04 12:08:15,722 WARNING torba.client.basenetwork:28: Wallet server returned an error. Code: -1 Message: the transaction was rejected by network rules. 64: non-mandatory-script-verify-flag (Data push larger than necessary) [0100000001a7bfdb31abc9ca5eed68fc7da260476cd1e1d5216186d142ff8c150c1014fd36000000006a47304402206df8764da78d06d2c721b788803e0114539408e171280655c783bc7e861b693a02204f563d71754ce7fe648f35a2baa951d2afb7e868880ac0d3b819b3dd10f27366012103d07fe8a0deb7423f552bd1c182251c8a926951f688801e3b2ba681148783a506ffffffff0174180f00000000001976a914322ab934ea45bde72d3f9c8bb0dc00eb0b031f0188ac00000000] ```

This discussion has been locked. Commenting is limited to contributors.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/spee.ch#740

Rows
Columns

abandon claim fails #740

Internal Use

Acceptance Criteria

Definition of Done