Nick Vatamaniuc

@joaohf very interesting, I don't know much about Yocto project, so may not be able to help much with the diff. I did however apply this patch to make it...

> That is why I had also to patch the build_js.escript in order to remove the hardcoded quickjs path. In yocto build the quickjs will be available in PATH for...

As discussed in one of the CouchDB dev meetings, the last two required features for https://github.com/apache/couchdb/pull/4627 support were: 1) Windows support 2) A way to scan and find compatibility issues...

I had tried it in 2.3.1 and I see the same negative pending value behavior. Not clear if it was meant to do that (there is a plausible semantic explanation...

Returning some of the same start sequence numbers comes as a side-effect of having individual shards. Each shard has an integer sequence number that's incrementing. 0 is a special "start"...

I guess a plausible interpretation of the pending number is that it reflects both the direction and offset from the *end* of the changes feed, regardless in which direction we're...

Let's try to fix the pending value to actually return something useful: https://github.com/apache/couchdb/pull/4715

> Just fixing the pending count but not addressing the encoded sequences doesn't seem useful. It is potentially misleading even. Hmm, I don't see how the pending count fix in...

> "pending" means "this is how many newer changes there are yet to be received" Exactly. That's what https://github.com/apache/couchdb/pull/4715 fixes it to be. Our [docs](https://docs.couchdb.org/en/stable/api/database/changes.html) state that: > pending (number)...

Good idea, Jan. There is a uuid7, too: * https://www.ietf.org/archive/id/draft-peabody-dispatch-new-uuid-format-03.html#name-uuid-version-7 * https://pypi.org/project/uuid7/