Partially completed txn has mysterious state: 'complete'
See original GitHub issueI have a transaction which has state : 'complete'
It has many items. Some of the items are state : 'done'
and some of them are state : 'pending'
It appears as if the transaction failed to fully complete the first time around, and there may have been an attempt to recover it with _repairAllIncomplete
However - I can’t find any situation where the library will set state : 'complete'
for a transaction. That’s the name of a selfRepairMode
not a transaction state, as I understand it.
Does this ring any bells? In the meantime, I’ll keep looking.
Issue Analytics
- State:
- Created 6 years ago
- Comments:12 (12 by maintainers)
Top Results From Across the Web
Transaction comes back after finishTransaction - Stack Overflow
When you get notified of a successful purchase via paymentQueue:updatedTransactions: check the state variable. If it has not been set, it means you...
Read more >Intro Into Transaction Management and Error Handling
The transaction will remain active and needs to be completed with explicit COMMIT or ROLLBACK statement later.
Read more >Re: [HACKERS] Strange transaction-id behaviour ... - PostgreSQL
> I'm cc:ing this to the hackers list so they can take a look at it. It is intentional. A given command can...
Read more >8. Transactions - Percona
In Percona TokuMX, all operations are transparently wrapped in an atomic transaction on the server. The operation either completely succeeds or completely fails ......
Read more >Living the Mysteries: A Guide for Unfinished Christians
Living the Mysteries: A Guide for Unfinished Christians [Hahn PH D, Scott, Aquilina, Mike] on Amazon.com. *FREE* shipping on qualifying offers.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Cool. Thanks for that. I’ve just published a new version with the PR merged.
I had a look at your latest changes - they look great, thank you so much!
One small little thing… perhaps when calling retryFailedRepairs, it could also retry txns that crashed the process the first time around? I’ve submitted a PR with this change.