Skip to content
This repository was archived by the owner on Jan 13, 2021. It is now read-only.

removing stream from recent_recv_streams on clean close #270

Merged

Conversation

nateprewitt
Copy link
Member

This addresses #265. Not sure if the test is overkill for such a minor change, but I figured I'd err on the side of 101% coverage :) I'll strip it out if it's unneeded.

@Lukasa
Copy link
Member

Lukasa commented Aug 16, 2016

Thanks for this!

I'm happy with the change, and have no objection to that test, but I'd also like a more specific test. Can we write a test that cleanly closes one stream? That is, that uses a stream through its lifetime, such that it gets a complete response, and then confirms that it has been removed from everything?

@nateprewitt
Copy link
Member Author

Were you looking for something more along the lines of this? This is what I originally wrote but felt it might exercise unnecessary code.

@Lukasa
Copy link
Member

Lukasa commented Aug 16, 2016

Yup @nateprewitt, that looks right.

@nateprewitt nateprewitt force-pushed the 265_remove_stream_on_close branch 2 times, most recently from e15eeb1 to 9620d4f Compare August 16, 2016 16:07
@nateprewitt nateprewitt force-pushed the 265_remove_stream_on_close branch from 9620d4f to 90b43a3 Compare August 16, 2016 16:18
@nateprewitt
Copy link
Member Author

Replaced old test with lifecycle test. The former felt redundant with this one.

@Lukasa
Copy link
Member

Lukasa commented Aug 16, 2016

Fab, thanks @nateprewitt! ✨ 🍰 ✨

@Lukasa Lukasa merged commit 689e4ce into python-hyper:development Aug 16, 2016
Lukasa added a commit that referenced this pull request Aug 16, 2016
@nateprewitt nateprewitt deleted the 265_remove_stream_on_close branch August 26, 2016 00:52
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants