-
-
Notifications
You must be signed in to change notification settings - Fork 287
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
SharpZipLib 1.4.0 dependency may cause deadlocks #650
Comments
I assume you call something like |
No, SpecFlow is all async, the BeforeFeature bindings are async too. The They use an isAsync flag which was set incorrectly (this is the change where they fixed it). This change has not yet been released. With the isAsync flag set to true, like in 1.4.0, it will write out to the outputStream asynchronously. This is then awaited in the TarOutputStream: |
Yep, that looks not right. I think you can override the version with |
When I reference SharpZipLib 1.3.3 I get a package version downgrade detected error from dotnet restore because the Testcontainers v2.2.0 NuGet package has a SharpZipLib >= 1.4.0 dependency. I downgraded Testcontainers to v2.1.0 which also works for now! 👍 |
…in the Docker container image build
…in the Docker container image build (#671)
Describe the bug
SharpZipLib has found a regression in its codebase (icsharpcode/SharpZipLib#786) between 1.3.3 and 1.4.0 which can cause deadlocks when writing tarballs
v2.2.0 references SharpZipLib 1.4.0 which may cause deadlocks.
To Reproduce
In my case I was running Testcontainers in a BeforeFeature binding in Specflow.
Expected behavior
No deadlocks. I don't see any preview versions where this fix is included. However, rolling back to 1.3.3 should also work.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
icsharpcode/SharpZipLib#788
icsharpcode/SharpZipLib#791
The text was updated successfully, but these errors were encountered: