update sheepdog for postgresql ssl support #349
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New Features
Breaking Changes
Bug Fixes
isolation_levelREAD_COMMITTED. This error occurs when there's competing transactions in thesheepdogdatabase, for example, when using multiple workers inuwsgiwhich are trying to reach a shared resource insheepdog_db.The conflict occurs after submitting multiple requests to
sheepdogusing the gen3sdk for python (see https://github.com/uc-cdis/gen3sdk-python/blob/master/gen3/submission.py#L187) as part of populating the data dictionary with metadata. In this case, it looks like the race condition mentioned here https://github.com/uc-cdis/cloud-automation/blob/1f9cbb52cecf449a5ad76f984fe0dda449d924d3/kube/services/jobs/gdcdb-create-job.yaml#L48 is occurring. This is a workaround to useisolation_levelofREAD_COMMITTEDwithinsheepdog.Improvements
uwsgi.iniandDockerfileto supportpythondependency installsDependency updates
pythondependency updates inrequirements.txtfordatamodelutils==1.0.0,dictionaryutils==3.2.0,gen3authz==0.4.0,six>=1.15.0, andpy2neo.pythondependency updates indev-requirements.txtforcoverage==5.3.0andcodacy-coverage==1.3.11Deployment changes