So one small wrench that we will want to investigate.
While we were trying to cleanup the database, we found a lot of documents
with transaction ids in txn-queue that references txn documents that were
already in APPLIED (6) state.
Looking at the TXN code, the act of applying the changes to the do
On Tue, May 12, 2015 at 3:50 AM, Eric Snow wrote:
> We've had discussions here a couple of times (since I joined the team)
> about classifying tests in our suite so they could be run more
> flexibly. We've also already added explicit handling for a specific
> kind of test along those same lines:
On 14 May 2015 at 06:41, Gustavo Niemeyer
wrote:
>
> You are right that it's not that simple, but it's not that complex either
> once you understand the background.
>
> Transactions are applied by the txn package by tagging each one of the
> documents that will participate in the transaction with
Hey Menno,
I'm copying the list to ensure we have this documented somewhere for future
reference.
You are right that it's not that simple, but it's not that complex either
once you understand the background.
Transactions are applied by the txn package by tagging each one of the
documents that wi
