Herman J. Radtke III

@episodeyang this repo pins to the master branch on mio. Try removing the existing mio dependency and replace it with `mio = "0.5.0"` in `Cargo.toml` file.

Thank you, I missed that issue! Installing globally does not change the fact that these vulnerabilities still exist though. The solution given by @YJPL is hiding the issue away. If...

`npm audit` does not check globally installed packages. See [How to npm audit global packages](https://stackoverflow.com/questions/52538773/how-to-npm-audit-global-packages) for instructions on how to do so.

I am happy to add this in if we accept https://github.com/zircote/Hal/issues/18

This is def a bug. I am not sure it is even possible not to provide a self link given the API though.

Agreed. That is what my comment > This should probably be configurable on a per-origin basis is implying. As I think about this, maybe per origin configuration is less important...

@manpreeeeeet you can give it a go!

i have the full origin resource basically functional. some things i want to explore: - proper styling - safe updates (using something like if-unmodified-since)

Related: https://github.com/hjr3/soldr/pull/51 i switched to using react-admin

Things to show on the dashboard: - total requests - failed requests - 10 most recent with link to all failed - requests over last 30 days We may want...