Peter Bengtsson

Nope. No progress. And I have up. On Wed, Apr 13, 2022 at 6:03 PM corey34 ***@***.***> wrote: > @peterbe did you ever find out how to do > this?...

I quite like the simplicity and "natural feel" of using `rg foo | rg bar` to do the equivalent of `git grep -e foo --and -e bar`. The only significant...

I don't even know if it's possible with pipes but if you could know that that the next pipe is another `rg` the `--color always` could be on by default....

> `sw-debug.js` is (more than likely) due to it being installed by Preact-CLI, but never removed. Disconnect it from your browser's dev tools. > > Also fill in the issue...

Pardon my kinto-juniorness but... Feels like this issue is crossing paths with https://github.com/Kinto/kinto/pull/1598 which is about doing inserts. It feels like the bestest way would be to use row-level locking....

By the way, the `delete` case is solvable without a lock using @Natim 's idea of either using `WHERE last_modified = 'previous_last_modified'` or something like this: ```python cur.execute(""" DELETE FROM...

I have prototypes for insert, upsert, update and delete all as python scripts that are pure psycopg2 based. I use a threadpool and some `time.sleep()` to trigger the race conditions...

I'm trying to collect my thoughts. https://github.com/Kinto/kinto/issues/1525 is all about the `create()` method. This issue has escalated into a discussion about leveraging proper row-level locks. Hopefully we can break this...

This is my attempt to file a followup to [this comment](https://github.com/Kinto/kinto/pull/1615#issuecomment-386329257) where I found that selecting 10,000 records at a time from 709,000 records caused it to miss two records...

> I though we were precise at the milliseconds so as_epoch should be unique No `as_epoch` rounds to what looks like the nearest second or something. From my database: ```...