fs_store_log date_reference to pickup time is 2 hours "off"
Summary
the date_reference is saved with an offset of 2 hours when referring to pickups. references to deleted wall posts are fine.
other effects are to the engagement statistic since it references the store_log table During "winter time" the intervall is 1 hour to get the correct join - during summer time it would probably be 2 hours again.
Steps to reproduce
Sign up for a slot, confirm a user in a slot or remove a user from a slot
What is the current bug behavior?
check the date_reference value in the fs_store_log table it is 2 hours "behind" when referring to pickups.
What is the expected correct behavior?
The time should be saved in the correct timezone in the tables.
Relevant error messages and/or screenshots
There seems to be a different time handling time values coming from pickups in Carbon and time values being read from the "getSingleStorepost".
https://foodsharing.freshdesk.com/a/tickets/621 -> has a screenshot of 'two hours in the future'
Possible fixes
Unify all time handling to Carbon time.