Michael P. Jung
Michael P. Jung
I'm a `tracing`-noob so to say. What tracing/logging messages would be needed in deadpool to be more useable?
I'm currently in process of a [`0.10`](https://github.com/bikeshedder/deadpool/milestone/4) release and if replacing `log` by `tracing` solves 90% of the pain I'm more than happy to include it in this release: https://github.com/bikeshedder/deadpool/tree/milestone/v0.10
Sure. Please create a PR against the milestone branch.
I'm no longer convinced that this feature is even worth having. The only use case of it has been replaced by `Pool::retain`, I think. Therefore I'm closing this PR unmerged.
I just released `deadpool-postgres 0.12` to crates.io which does support configuration by URL: - https://crates.io/crates/deadpool-postgres/0.12.0 Unlike the original PR you can specify both `url` and the other connection parameters and...
Sorry for taking so long. I completely forgot about that PR. :see_no_evil: After reviewing it I only found two small details: 1. Every time you use `Available:add` you add 1...
Oh, and please explain this comment to me... - https://github.com/bikeshedder/deadqueue/pull/4/files#r1387924883 How is it borrowed mutably? :thinking:
@overhacked Any updates on this PR?
Thanks a lot. Awesome work! :tada:
Sorry for taking so long. LGTM. Are you going to add the VFS support in this PR, too?