Justin Turner Arthur

I've started some work on this in [BlackLocus' Pessimistic-Locking branch](https://github.com/blacklocus/JPA-NestedSet/commits/Pessimistic-Locking), but I've only added it for the node-manipulation functions I'm using for our project at the moment. It might be...

The solution might be to have the `NodeInfo` interface to not enforce the id field, instead relying on the JPA API to derive information about the id field—by no means...

There is now a connection close callback that can be used to track when the lib knows the connection has been closed: ```python connect( host='localhost', port=5672, username='guest', password='guest', virtual_host='/', on_connection_close=stop_publishing_things...

@TarasLevelUp I think exposing buffer flow control hints is great—thanks for getting the ball rolling. As for adding it as an option to publish, I don't quite like the idea....

Having a memory leak in one of my aiohttp apps, I've been following this closely. If memory_profiler is to be trusted, this still happens with aiohttp 3.7.x and cpython 3.9.4....

Error or not, we may still want to stop reconnection behavior after we've sent our own goodbye.

@stealthycoin any chance we could get some clarification? Is the plan to drop timeouts as a retrying cause and change the meaning of `AWS_METADATA_SERVICE_NUM_ATTEMPTS`? The lack of retrying combined with...

Thanks, @nyh. I agree, and by not performing the same checks on deserialization, we improve performance. I've adjusted the pull request accordingly. I still remove the `Rounded` check to fix...

> @JustinTArthur Looks like this has ben hanging out for a bit over a year, any issue with merging? The only issue with merging is that no one has merged...

Per a commit comment made by @teward, I've adjusted my pull request to use the same local variable nomenclature conventions employed throughout gribble and the supybot-bitcoin-marketmonitor plugins. My original intention...