Mathieu Leplatre
Mathieu Leplatre
What's the status of this ? Does the built-in plugin `kinto.plugins.quotas` covers this already? BTW created date was later reported in issue #679
Note: the problem only exists for buckets, since it's (currently) the only object that has two types of children. The chain of implicit permissions would then have two steps: _create...
The only way to get of this is to rely on a SEQUENCE to build timestamps. I suggest that we get rid of the fact that timestamps are based on...
The `records_pkey` error that we can see in the mentioned Sentry error is indeed easy to catch, since it's a conflict on `(id, parent_id, collection_id)`, and not on timestamp unicity...
Yes, there are mainly two scenarios: * two overlapping requests trying to create the same object (`records_pkey`) * two overlapping requests (*same millisec*) creating/updating/deleting objects within the same parent (`idx_records_parent_id_collection_id_last_modified`)...
Please add the underscores to the keywords ;) What you describe might come from this: https://github.com/Kinto/kinto/blob/0ebe2f3aaaefe41db58d8fc51aae46fd00aff773/kinto/core/resource/schema.py#L230-L231 And indeed, we should probably only allow it for fields related to timestamps (I...
I guess this could be achieve using #600. It would require some manipulation by the client, but would keep things simple.
It's kind of tricky to fix, because we register a route with the explicit name `default`: https://github.com/Kinto/kinto/blob/cd6bb4f0416265ca05fe52a7a05a42cdf46bad8f/kinto/plugins/default_bucket/__init__.py#L202-L203
We iterate on the settings defined in the .ini + the defaults: https://github.com/Kinto/kinto/blob/86a9943b428b8e7fab53190bf840222f5c833225/kinto/core/initialization.py#L480-L497 What would we be your suggestion? Note that the plugin include happens after the initialization phase: https://github.com/Kinto/kinto/blob/86a9943b428b8e7fab53190bf840222f5c833225/kinto/core/__init__.py#L202-L205