Walther Chen

Playing around with this a bit, I'm not sure it makes sense to have users implement their own `Err` -> `Rejection` if `Cause`s are going to be the main way...

Ok, I'll look at the new rejection system.

I've rebased on master. In this implementation, the user just has to implement `reject::Reject` for their error, then they can use it in `param_with_err` (formerly `param2`). Let me know if...

And it seems like you no longer need to implement `std::error::Error` to work with the custom rejection system, just `reject::Reject`.

It's been a while since this PR was submitted, I've updated it to better reflect the latest `Rejection` system. Quick summary: `path::param` will always return `reject::not_found()` if there's an error...

Oops, doesn't fix. Increasing the threads and the NilClass behavior returns.

Ok, so some modifications and it looks like nilClass has not returned. Changing the reference from `olap` to `@@olap` in `get_cubes_or_404` appeared to get rid of the last NilClass.

Hello, Would the proposed features allow me to use ring for [this](https://standards.freedesktop.org/secret-service/ch07s03.html)? I'm currently using rust-crypto, and am hoping to move away. Some issues: - https://github.com/DaGenix/rust-crypto/issues/410 (I think I found...

More background, which I had written in another issue: ``` Puma caught this error: undefined method `[]' for nil:NilClass (NoMethodError) /home/deploy/.rvm/gems/jruby-9.1.13.0/gems/mondrian-rest-1.0.0-java/lib/mondrian_rest/api_formatters.rb:104:in `block in pluck' org/jruby/RubyArray.java:2486:in `map' /home/deploy/.rvm/gems/jruby-9.1.13.0/gems/mondrian-rest-1.0.0-java/lib/mondrian_rest/api_formatters.rb:104:in `pluck' /home/deploy/.rvm/gems/jruby-9.1.13.0/gems/mondrian-rest-1.0.0-java/lib/mondrian_rest/api_formatters.rb:63:in `block...

pinging @jspeis on this issue