4 ms·
> Every so often, an order total changed between the time that the user saw the total on the confirmation screen and when they actually hit the button to place
by dmurray 5y ago
> Every so often, an order total changed between the time that the user saw the total on the confirmation screen and when they actually hit the button to place the order (which seems to be what happened here).
I don't see any reason from the post to believe this kind of race condition is what happened here.
Uber's CS says the promotional code used was not valid for this restaurant, but presumably the app accepted it anyway. That's also likely a validation error, but of a different class.
- dboshardy 5y ago> I'm kind of surprised that UberEats doesn't seem to have a similar validation step. That's what OP was saying.
- teeray 5y ago> an order total changed between the time that the user saw the total on the confirmation screen and when they actually hit the button to place the order > …but presumably the app accepted it anyway… Not a lawyer, but I’m pretty sure things like this would constitute a contract. Of course, whether there’s squirrelly language in the Terms of Service is another question… EDIT: formatting
- brodock 5y agoIf I have to guess, something something microservices/event-system. One separate team handles code consumption which is not he same who handles the validation, and because its a distributed mess, it is eternally broken.