Looking more closely at where concurrency bugs lurk
Details
SOMEONE DISCOVERED A CONCURRENCY ISSUE IN OUR DESIGN!
After we start retrieving a clip from a device, an operation that takes a while, other requests for that clip could come in. And when they did, they messed up the stream version that we were relying on.
This would lead to a version mismatch error, causing the component to crash and restart, after which it would usually do things correctly. Unless another request for the same clip came in after we started fetching it again.
So we’re going to fix it!
And in fixing it, we’ll see a pattern to watch out for, and we’ll make the design a lot simpler.
We’ll walk through several options for fixing it and discuss their pros and cons.
A big thanks to LiveView Technologies, for once again hosting us!
See you on the 19th! This is a week earlier than normal so that we accommodate a scheduling conflict our host would have.
Please RSVP if you can make it in person so that we can get a good food count!
To participate remotely, we’ll be on Zoom: https://aumni-fund.zoom.us/j/81089216912?pwd=YW5BUW13Z3JPT3ZwRE9zUlVJWFU3QT09
(If you want to attend via Zoom, RSVP to this event, and make sure your Zoom name matches your name here on Meetup.)