Paul Colomiets

Wow, that worked like a charm! Thanks. [Here is the code](https://github.com/tailhook/verwalter/commit/82d16ad9b86a1cdf8b7018c1f084f142cc09d902) that catches panics and logs payload and location for anyone trying to figure it out. However, I think this...

> This also concers https://github.com/nrc/graphql and @nrc. > We've already talked about sharing fundamental infrastructure like the parser. Sure, here is the issue: https://github.com/nrc/graphql/issues/36 > it's important to have great...

> Would you be interested in moving the parser into the graphql-rust organization? I'm fine with that. Should it be done now?

SDL is implemented and pushed to crates.io as v0.2.0

Well, AST in graphql-parser is currently owned, so works fine for async code right now. Then we can try to benchmark and optimize things. Usually, rust/jemalloc is very good, so...

> Execution of the futures can be batched quite easily, but the creation of the futures much less so, and those futures will need to know the query. I expect...

What do you think about using [`compat`](https://docs.rs/failure/0.1.1/failure/trait.Fail.html#method.compat) method?

> Globals are pretty much an anti-pattern. It's nice that IED does not support it. Unless you're using containers. In that case, local installations are pretty much anti-pattern.

Thank you for reporting! Fixed in v0.8.0-127-gefc0bc0 for bionic. I'm not sure if all non-LTS releases work, but I hope so.

@roman901 what ubuntu distribution do you use?