Jeremiah Senkpiel
Jeremiah Senkpiel
Hmm. Maybe we _should_ have a default client-error-handling middleware feature. It's hard to know what users will want though - raw text? Json? Maybe based on `Accepts`? However if you...
> We recently bumped our Tide version from 0.8.1 to 0.14.0 which caused our response payloads/bodies for errors to be empty. Ah I did not notice that. Yes this is...
See also for reference https://github.com/eaze/preroll/blob/latest/src/middleware/json_error.rs
I can't seem to load that discord link FWIW.
Err... this isn't solving the issue that #642 and #644 solve... this is just general ergonomics, imo? Likewise see https://github.com/http-rs/tide/issues/643#issuecomment-657621351
I would have thought that too, but that's [not what the std lib examples shows](https://doc.rust-lang.org/std/sync/struct.Arc.html#examples-19): ```rust use std::sync::Arc; let mut data = Arc::new(5); *Arc::make_mut(&mut data) += 1; // Won't clone...
I think that would be a feature though? Inserting a middleware when a request is potentially on the way out is a good way to cause indecipherable timing errors. This...
Could also do both a soft and hard cap.
``` error: component 'rustfmt' for target 'x86_64-unknown-linux-gnu' is unavailable for download for channel nightly Sometimes not all components are available in any given nightly. Error: Process completed with exit code...
https://github.com/http-rs/http-types/pull/179 should fix this for you when `http-types` is updated. This looks like it was an oversight from there. Thought I do think the train of thought is that folks...