Skip to content
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

ToxicStub allow to unblocking write to Output #436

Merged
merged 1 commit into from
Sep 10, 2022
Merged

Conversation

miry
Copy link
Contributor

@miry miry commented Sep 6, 2022

It could happen when Link has no reciever and there is some packets in buffer.
It produces deadlock.

@miry miry self-assigned this Sep 6, 2022
@miry miry added the Toxiproxy label Sep 6, 2022
@miry miry force-pushed the locking-problem branch 2 times, most recently from 53a7f78 to 7387396 Compare September 7, 2022 12:22
@miry miry added this to the 2.5.0 milestone Sep 7, 2022
@miry miry marked this pull request as ready for review September 7, 2022 16:51
@miry miry force-pushed the locking-problem branch 4 times, most recently from 960d5fe to 15eb362 Compare September 7, 2022 20:07
@kwart
Copy link

kwart commented Sep 8, 2022

This PR seems to cause incorrect HTTP responses on the DELETE command:

curl -v -X DELETE http://localhost:49266/proxies/tc-okJxHciQ:5701/toxics/CUT_CONNECTION_DOWNSTREAM
*   Trying 127.0.0.1:49266...
* Connected to localhost (127.0.0.1) port 49266 (#0)
> DELETE /proxies/tc-okJxHciQ:5701/toxics/CUT_CONNECTION_DOWNSTREAM HTTP/1.1
> Host: localhost:49266
> User-Agent: curl/7.81.0
> Accept: */*
> 
* Empty reply from server
* Closing connection 0
curl: (52) Empty reply from server

@miry
Copy link
Contributor Author

miry commented Sep 8, 2022

Yep, I am working on correcting timeouts to finish Delete toxic in window of WriteTimeout.

@miry miry force-pushed the locking-problem branch 3 times, most recently from 6f3fdcd to 6e4fd5f Compare September 9, 2022 18:05
@miry miry requested review from a team, frightenedmonkey, yuseinishiyama and dabealu and removed request for a team September 9, 2022 18:14
It could happen when Link has no reciever and there is some packets in buffer.
It produces deadlock.

Dynamic test with latest version of toxiproxy
@miry miry merged commit 524143c into master Sep 10, 2022
@miry miry deleted the locking-problem branch September 10, 2022 10:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants