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

fix: potential memory corruption caused by Google storage objects accessed from different threads #1174

Merged
merged 4 commits into from Sep 24, 2021

Conversation

johanneskoester
Copy link
Contributor

@johanneskoester johanneskoester commented Sep 14, 2021

Description

Hopefully fixes issue #1006.

QC

  • The PR contains a test case for the changes or the changes are already covered by an existing test case.
  • The documentation (docs/) is updated to reflect the changes or this is not necessary (e.g. if the change does neither modify the language nor the behavior or functionalities of Snakemake).

@sonarcloud
Copy link

sonarcloud bot commented Sep 24, 2021

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 1 Code Smell

No Coverage information No Coverage information
0.0% 0.0% Duplication

@johanneskoester johanneskoester merged commit 41a5071 into main Sep 24, 2021
6 checks passed
@johanneskoester johanneskoester deleted the fix-issue-1006 branch Sep 24, 2021
iamh2o added a commit to iamh2o/snakemake that referenced this pull request Nov 17, 2021
…ects accessed from different threads (snakemake#1174)"

This reverts commit 41a5071.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant