-
Notifications
You must be signed in to change notification settings - Fork 115
Data race warning #111
Comments
@Perlence can you update goreq and run the race detector again?. Seems like is something else https://github.com/franela/goreq/blob/master/goreq.go#L314 |
I've updated goreq so the master is 8f5efc2. Unfortunately warning's still there:
|
@Perlence We found the issue. We'll be fixing this shorty. It won't affect your code unless you are specifying different maxRedirects per request. |
Hi, I'm seeing the same issue - would love a fix just to clean up the warning. |
@rhd we'll fix it shortly. |
I have independently rediscovered this race condition in my application. I'm at head, eg 72c51a5 Note also that changing the Makefile to run go test --race finds other race conditions as well. |
Yes, there are some race conditions they all come from using DefaultClient and allowing functionallity that should require a new client. |
any progress on this over the weekend? |
@rrh I haven't had time to check this, but those races are hard to tackle without breaking backwards compatibility, that's a bummer. |
I use goreq to send concurrent requests:
But when I checked the program for races, I got this:
So race detector warns me that goroutines write unsafely into
CheckRedirect
ofDefaultClient
.The text was updated successfully, but these errors were encountered: