...
- I've run `make stop`, which stopped all the containers
- postgres-oms-statutory and postgres-oms-discounts both tried to write something to WAL simultaneously on shutdown (probably dumping to disk the data that wasn't on disk, but on memory instead), corrupting it
- other DBs weren't affected because they didn't use the postgres volume
- I've deployed everything and ran `make start`
- two DBs started to complain about WAL being corrupted (edited)
...
Author: serge1peshcoff
Date/time: 23rd August 2019
Result: wrong event deleted due to the bug in the events module
Summary:
Okay, so this was quite fun.
In events module, there is 'id' and 'url' fields. You can find the event either by ID (if it's numeric) or by URL. So, when you query the /events/:id - like endpoint, if the ID is numeric, it searches the event by ID and URL (since url can also be numeric), if not, it searches by url only.
We had two of the following events:
id | url | name
----+----------------------------------------------------------------------------------------------------------+----------------------------------------------------------
44 | | NWM Chisinau: Welcome Back to Casa Mare
22 | 44 | RTC London - "London, mind the RTC!"
Someone smart set the event URL of RTC London to 44. That resulted in the funny bug:
1) when you go to the listing of the events, you click on the RTC London and then (the link to this event is /events/44) you are redirected to the NWM Chisinau page.
2) one girl managed to delete the wrong event (RTC London instead of NWM Chisinau).