This PR aims to address problem we either encountered during the 2023 convention or before but didn't have time to fix:
Fix a time precision problem that would cause what looked like a race condition after creating a reservation. When creating a reservation and immediately querying all stations, the timestamp used in the second query would be truncated to the closest second, causing the timestamp for finding reservations to occur earlier in time than the actual creation timestamp of the reservation by a few ms, therefore causing the query to return no reservations for the station.
Thanks to the previous fix, a lot of state management pubsub logic for station lifecycle was removed. Instead, the entire stations map is passed around via pubsub and assigned to the socket directly and phoenix takes care of updating the relevant pieces of pages, as intended by the framework.
Removed noisy debug statements that should not have been committed
This PR aims to address problem we either encountered during the 2023 convention or before but didn't have time to fix:
Fix a time precision problem that would cause what looked like a race condition after creating a reservation. When creating a reservation and immediately querying all stations, the timestamp used in the second query would be truncated to the closest second, causing the timestamp for finding reservations to occur earlier in time than the actual creation timestamp of the reservation by a few ms, therefore causing the query to return no reservations for the station.
Thanks to the previous fix, a lot of state management pubsub logic for station lifecycle was removed. Instead, the entire stations map is passed around via pubsub and assigned to the socket directly and phoenix takes care of updating the relevant pieces of pages, as intended by the framework.
Removed noisy debug statements that should not have been committed