Sean Pianka

Should we mark this for 1.0?

Any updates or plans on merging this?

> @seanpianka @akatechis Sorry for my lack of responses! > I guess there is never a good time to do this review so I guess I'll try to do this...

@bnayagrawal Confirmed that the updated changes to slack have broken this modification (applying changes to either index.js or ssb-interop.js still ends up w/ the chat background being white on white...

@laurencee Applying the original changes to the "new version folder"/index.js and/or ssb-interop.js does not seem to function properly (the background of the chat is still white w/ white text).

I've been using `--virtual` for my build deps, but version pinning an edge package. Then, trying to `apk del` the virtual was throwing this unsatisfiable constraints error. @kaniini Your advice...

I'm seeing the same issues with the same development environment: ``` $ rustup target add x86_unknown-linux-musl error: toolchain 'nightly-x86_64-apple-darwin' does not contain component 'rust-std' for target 'x86_unknown-linux-musl'; did you mean...

This issue prompted me to try the above command due to an issue with the Rust version used by the compiler: ``` $ node_modules/serverless/bin/serverless.js deploy Serverless: Building Rust app.cmd.lambda func......

I added something similar to #93 in #75, perhaps you can build a new router with a shared reference to the builder, rather than cloning the router explicitly? I can...

Have you tried using the `RequestService` instead of the `RouterService`? It strictly handles processing of the hyper::Request instance, rather than involving Routerify in the serving of the UDS or TCP-specific...