-
Notifications
You must be signed in to change notification settings - Fork 481
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
Multiple data race issues #1192
Comments
See tus#1192 This adds a mock slog Logger to create a data race issue. Run go test -race to trigger
Unfortunately this uncovers quite a few more data race issues, which go beyond the scope of this issue:
and
|
Updated the issue. This requires a rework of the context implementation. |
Thank you for bringing this up! I haven't used the data race detector before, so tusd hasn't been vetted by it so far, but we should change this. Running the race detector during tests also shows a few issues ( I'll have a look at them soon. |
Opened #1199. |
I addressed the data races in handler and s3store in #1199, but not the logger-related one yet. |
We don't seem to be able to reproduce this specific data race anymore (see #1193 (comment)). Since the other races have been fixed, I will close this issue for now. Feel free to reopen it if the problem appears again. |
Describe the bug
tusd.Config{}
Logger is set. When performing an upload a data race is reported:To Reproduce
Steps to reproduce the behavior:
-race
Currently still investigating which other circumstances lead to this.
But
writing to a context without creating a copy is probably not correct.
Expected behavior
No data race should happen
Setup details
Please provide following details, if applicable to your situation:
The text was updated successfully, but these errors were encountered: