Skip to content
This repository was archived by the owner on Dec 18, 2018. It is now read-only.

Debug MaxInputBufferLength failures on Travis OSX #926

Closed
wants to merge 34 commits into from

Conversation

mikeharder
Copy link
Contributor

@mikeharder mikeharder commented Jun 13, 2016

PR to debug MaxInputBufferLength failures on Travis OSX. Fixes will be rolled into #912.

mikeharder added 30 commits June 9, 2016 14:44
- Tests currently fail sometimes, caused by server reading more bytes than sent by client.
…sending the full number of requested bytes when a SocketException is thrown, which is not guaranteed to be true on all platforms.
- Send bytes in a background task
- Block test thread until send task has gone a while without writing bytes, rather than using timeout and SocketException.
- Refactor to use mostly the same code for both pause and no-pause scenarios.
- Required for connection filters, which use use two instances of SocketInput.  We need to ensure the combined buffers do not exceed the limit, and to coordinate the calls to `IConnectionControl` between the two instances of SocketInput.
- Prevents breaking tests which call SocketInput.ctor()
- Add Moq to KestrelTests
Add comments explaining why each size is tested.
- HTTP requires "\r\n", and WriteLine() uses "\n" on Mac/Linux
… paused until around 10MB after the server sends backpressure.
@mikeharder mikeharder changed the title Debug MaxInputBufferLength failures on OSX Debug MaxInputBufferLength failures on Travis OSX Jun 13, 2016
@cesarblum
Copy link
Contributor

Delete? Or still investigating?

@mikeharder mikeharder closed this Jun 14, 2016
@mikeharder mikeharder deleted the mikeharder/max-input-buffer-length-travis-osx branch June 14, 2016 01:34
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.

3 participants