Skip to content

[Snyk] Security upgrade python from 3.13.2-slim-bookworm to 3.14.0rc1-slim-bookworm - #14

Open
jcschaff wants to merge 1 commit into
mainfrom
snyk-fix-9d6f7310e6f6828f46bdd69bf22b829d
Open

[Snyk] Security upgrade python from 3.13.2-slim-bookworm to 3.14.0rc1-slim-bookworm#14
jcschaff wants to merge 1 commit into
mainfrom
snyk-fix-9d6f7310e6f6828f46bdd69bf22b829d

Conversation

@jcschaff

Copy link
Copy Markdown
Contributor

snyk-top-banner

Snyk has created this PR to fix 5 vulnerabilities in the dockerfile dependencies of this project.

Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.

Snyk changed the following file(s):

  • Dockerfile-worker

We recommend upgrading to python:3.14.0rc1-slim-bookworm, as this image has only 44 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
medium severity Heap-based Buffer Overflow
SNYK-DEBIAN12-GNUTLS28-10690985
  586  
medium severity Double Free
SNYK-DEBIAN12-GNUTLS28-10690987
  586  
medium severity NULL Pointer Dereference
SNYK-DEBIAN12-GNUTLS28-10690990
  586  
medium severity Improper Certificate Validation
SNYK-DEBIAN12-GNUTLS28-10690993
  586  
medium severity Race Condition
SNYK-DEBIAN12-SYSTEMD-10264074
  514  

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Double Free
🦉 NULL Pointer Dereference

NovrusShehaj pushed a commit to NovrusShehaj/platform that referenced this pull request Aug 3, 2026
…eview

biosimulations#14 (worker pod disk leak) -- wrap biosim_service.run_biosim_sim in
    try/finally inside submit_biosim_run_activity so local_omex_path is
    always removed, even when submit raises (HTTP 5xx, network, auth).
    The os.remove is itself wrapped in try/except OSError so a missing-file
    race during cleanup is non-fatal.

biosimulations#5 (FAILED-row cache pollution) -- gate insert_biosimulator_workflow_run
    in poll_biosim_run_activity on `simulation_run.status == SUCCEEDED`.
    Non-SUCCEEDED runs still return a fully-populated (un-saved)
    BiosimulatorWorkflowRun so OmexSimWorkflow can surface the FAILED
    state -- the workflow does not consult database_id. Eliminates
    unbounded BiosimSims growth on failing inputs and removes the
    cache-lookup ordering hazard (cached_runs[0] could otherwise be a
    FAILED row hiding a later SUCCEEDED one).

biosimulations#10 (missing Mongo indexes) -- add an ensure_indexes() method to all
    three Mongo DB services (default no-op on the abstract base; Mongo
    impls override). Called from init_standalone() and from each test
    fixture so production and tests share the same shape. Indexes:
      BiosimSimulationRuns: processing_id, run_id (unique)
      BiosimSims: (file_hash_md5, image_digest, cache_buster) compound +
        biosim_run.id
      BiosimOmex: file_hash_md5 (non-unique; the check-then-insert
        callers don't handle DuplicateKeyError, so uniqueness stays
        logical).

#2 (status 404 after workflow history eviction) -- restructure
    GET /simulations/{processing_id}: don't 404 when the workflow query
    raises. Try the SimulationRunRecord DB fallback; only 404 if both
    sources are empty. A new _conglomerate_status_from_records helper
    builds ConglomerateStatus from persisted records when the workflow
    is gone (mapping CREATED/SUCCEEDED/FAILED back to
    processing/success/failure).

Tests: 3 new router tests cover the workflow-not-found-with-DB-fallback
path, the both-empty 404, and the hybrid enrichment-from-DB path. Existing
test_get_simulation_status_not_found still passes (no records -> 404).

Full -m "not integration" gate: 83 passed, 1 failed (the pre-existing
test_slurm_service env failure, unchanged).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.

2 participants