-
Notifications
You must be signed in to change notification settings - Fork 887
Document flow for adding a database query #131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hey team! Please add your planning poker estimate with ZenHub @f0ssel @kylecarbs @johnstcn |
What is meant by "documentation" in this case? A README in the source code? A wiki page? |
I think this can be closed tbh, we seem to do fine without it |
Agreed |
spikecurtis
added a commit
that referenced
this issue
Dec 3, 2024
Upgrades yamux to 0.1.2, which includes a couple bug fixes. > Significant Changes > * Fixed a case where Streams may continue to exist and block operations even after their Session has been closed. #127 ensures when a Session closes that blocking Stream operations exit as well. > * Allow Reads on locally closed streams. Prior to #131 calling Close() and then Read() on a Stream would fail. Close should only indicate the Stream is done writing. The peer must call Close before Read considers the stream closed. See #131 for details. > * Tests have been improved significantly. See below for details. https://github.com/hashicorp/yamux/releases/tag/v0.1.2
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: