Jackson Utsch

I followed the [yew guide](https://yew.rs/docs/getting-started/introduction#install-trunk). It doesn't use the `--locked` flag, so I assume no. I can try using it. `cargo metadata` works and spits loads of text about the...

Utilizing `--locked` gave me two warnings while installing ``` warning: package `cpufeatures v0.2.2` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked warning: package `tracing-subscriber v0.3.12` in Cargo.lock...

Sounds like a different error if it is talking about traits not found. Believe these are just from the standard prelude though. @etch1000

This sets in stone no evolution to add support of failure cases in reducers (which is the current direction anyhow 😕). Is TCA going to use the `Effect` type long...

@stephencelis That is fair. It is quite an extensive change. It is a breaking change unless you can assume a generic type unless explicitly specified. I have the strong preference...

I'm good with the `typealias` , taking another direction for error handling. Don't believe any changes are needed for such.

This only happens on my linux machine (not on my macbook), seems to be platform specific.

I seem to getting the same port issue sometimes. Oddly enough also on macOS 14.1. but mongodb-memory-server v8.13.0. Will try newer version.

Well, it seems I have interesting results. Updating to `v9.0.1` seems to made this issue much less frequent.

``` Port "50113" already in use at MongoInstance.checkErrorInLine (node_modules/mongodb-memory-server-core/src/util/MongoInstance.ts:611:9) at MongoInstance.stdoutHandler (node_modules/mongodb-memory-server-core/src/util/MongoInstance.ts:585:10) ``` In the code referenced I think we need a lock of sorts for `PORTS_CACHE`. If we could...