Sam Saffron 34ede90927 FIX: under rare conditions saving a new draft could error temporarily ...

Under rare conditions due to bad HTTP timing and so on a draft could be
set at the exact same time from 2 unicorn workers.

When this happened and all the stars aligned, one of the sets would win
and the other would raise an error.

This transparently handles the situation without adding any cost to the
draft system.

The alternative is to add a distributed mutex, tricky DB transaction or handle
the error in the controller. However this seems like a reasonable way to
work around a pretty big edge case.

2020-01-02 11:38:14 +11:00

..

assets

FIX: Only show admin wrench when there are actions on mobile

2019-12-31 12:35:44 +00:00

controllers

API endpoints should return a response, not nil

2019-12-30 10:14:29 -05:00

helpers

FIX: Replace deprecated URI.encode, URI.escape, URI.unescape and URI.unencode (#8528)

2019-12-12 12:49:21 +10:00

jobs

FIX: Replace deprecated URI.encode, URI.escape, URI.unescape and URI.unencode (#8528)

2019-12-12 12:49:21 +10:00

mailers

FIX: Replace deprecated URI.encode, URI.escape, URI.unescape and URI.unencode (#8528)

2019-12-12 12:49:21 +10:00

models

FIX: under rare conditions saving a new draft could error temporarily

2020-01-02 11:38:14 +11:00

serializers

DEV: Improve support for extending flags. (#8619)

2019-12-27 08:41:50 -03:00

services

FIX: parallel spec system needs a dedicated upload folder for each worker. (#8547)

2019-12-18 11:21:57 +05:30

views

FEATURE: improve email change workflow

2019-11-21 16:28:35 +11:00