Ian Terrell

We are observing similar symptoms on Google App Engine. It works fine for a while, and then crashes on `get_nns_by_vector`. Nothing in the logs, just nginx reporting that upstream crashed.

I'm doing a project using a variant of ReSwift and have added routing to it. For the case of the back button (and, in theory, the `popToRootView` case, although we...

@bensheldon It looks like it is `ActiveRecord::StatementInvalid` wrapping `PG::ReadOnlySqlTransaction`: > `ActiveRecord::StatementInvalid: PG::ReadOnlySqlTransaction: ERROR: cannot execute LISTEN during recovery` Here's the backtrace: [backtrace.log](https://github.com/bensheldon/good_job/files/12717716/backtrace.log) & thanks!

For alerts you can use the handler for each button to update the state. So in addition to taking the action that might be confirmed, you would also use `store.setRoute`...

There are two things I notice in this repro. 1. The store is managing the UI, and should only be accessed on the main thread. Dispatching from a non-main thread...

To further emphasize the above and explain some of what you're seeing, dispatching to the store from a non-main thread is not supported because actions _must_ be serialized. Since the...

Yes — that is it. That is so that scene coordinators can "reuse" coordinators without having `start` called multiple times. I definitely need to update the sample app... it is...

Yes — fundamentally I think it's the scene coordinator's responsibility to know whether or not to start each scene's coordinator.

Thanks — it is helpful to see how other people interpret the code without better documentation. 1. I don't think there is any need to store `childCoordinatorsPresented`. You only need...

Recommended object graph: ``` coordinator | v view controller | v handler ``` or ``` coordinator --> handler | ^ v / view controller ``` if the coordinator needs access...