Skip to content

Fix arbitrary file write during tarfile extraction in luigi/contrib/lsf_runner.py and luigi/contrib/sge_runner.py #626

Fix arbitrary file write during tarfile extraction in luigi/contrib/lsf_runner.py and luigi/contrib/sge_runner.py

Fix arbitrary file write during tarfile extraction in luigi/contrib/lsf_runner.py and luigi/contrib/sge_runner.py #626

Triggered via pull request September 4, 2024 13:47
Status Failure
Total duration 7m 58s
Artifacts

pythonbuild.yml

on: pull_request
Matrix: base
Matrix: core
Matrix: postgres
Fit to window
Zoom out
Zoom in

Annotations

62 errors and 28 warnings
base (3.9, flake8)
Process completed with exit code 1.
base (3.8, py38-apache)
The job was canceled because "_3_9_flake8" failed.
base (3.8, py38-apache)
The operation was canceled.
base (3.11, py311-aws)
The job was canceled because "_3_9_flake8" failed.
base (3.11, py311-aws)
The operation was canceled.
base (3.9, docs)
The job was canceled because "_3_9_flake8" failed.
base (3.9, docs)
The operation was canceled.
base (3.11, py311-apache)
The job was canceled because "_3_9_flake8" failed.
base (3.11, py311-apache)
The operation was canceled.
base (3.10, py310-aws)
The job was canceled because "_3_9_flake8" failed.
base (3.10, py310-aws)
The operation was canceled.
base (3.7, py37-unixsocket, true)
The job was canceled because "_3_9_flake8" failed.
base (3.7, py37-unixsocket, true)
The operation was canceled.
base (3.8, py38-azureblob)
The job was canceled because "_3_9_flake8" failed.
base (3.8, py38-azureblob)
The operation was canceled.
base (3.9, py39-unixsocket, true)
The job was canceled because "_3_9_flake8" failed.
base (3.9, py39-unixsocket, true)
The operation was canceled.
base (3.12, py312-apache)
The job was canceled because "_3_9_flake8" failed.
base (3.12, py312-apache)
The operation was canceled.
base (3.6, py36-unixsocket, true)
The job was canceled because "_3_9_flake8" failed.
base (3.6, py36-unixsocket, true)
The operation was canceled.
base (3.8, py38-aws)
The job was canceled because "_3_9_flake8" failed.
base (3.8, py38-aws)
The operation was canceled.
base (3.6, py36-apache)
The job was canceled because "_3_9_flake8" failed.
base (3.6, py36-apache)
The operation was canceled.
base (3.10, py310-unixsocket, true)
The job was canceled because "_3_9_flake8" failed.
base (3.10, py310-unixsocket, true)
The operation was canceled.
base (3.8, py38-unixsocket, true)
The job was canceled because "_3_9_flake8" failed.
base (3.8, py38-unixsocket, true)
The operation was canceled.
base (3.7, py37-aws)
The job was canceled because "_3_9_flake8" failed.
base (3.7, py37-aws)
The operation was canceled.
base (3.7, py37-azureblob)
The job was canceled because "_3_9_flake8" failed.
base (3.7, py37-azureblob)
The operation was canceled.
base (3.9, py39-aws)
The job was canceled because "_3_9_flake8" failed.
base (3.9, py39-aws)
The operation was canceled.
base (3.9, py39-apache)
The job was canceled because "_3_9_flake8" failed.
base (3.9, py39-apache)
The operation was canceled.
base (3.12, py312-azureblob)
The job was canceled because "_3_9_flake8" failed.
base (3.6, py36-aws)
The job was canceled because "_3_9_flake8" failed.
base (3.12, py312-azureblob)
The operation was canceled.
base (3.6, py36-aws)
The operation was canceled.
base (3.7, py37-apache)
The job was canceled because "_3_9_flake8" failed.
base (3.7, py37-apache)
The operation was canceled.
base (3.12, py312-aws)
The job was canceled because "_3_9_flake8" failed.
base (3.12, py312-aws)
The operation was canceled.
base (3.9, py39-azureblob)
The job was canceled because "_3_9_flake8" failed.
base (3.9, py39-azureblob)
The operation was canceled.
base (3.6, py36-azureblob)
The job was canceled because "_3_9_flake8" failed.
base (3.6, py36-azureblob)
The operation was canceled.
base (3.11, py311-azureblob)
The job was canceled because "_3_9_flake8" failed.
base (3.10, py310-apache)
The job was canceled because "_3_9_flake8" failed.
base (3.11, py311-azureblob)
The operation was canceled.
base (3.10, py310-apache)
The operation was canceled.
base (3.12, py312-unixsocket, true)
The job was canceled because "_3_9_flake8" failed.
base (3.12, py312-unixsocket, true)
The operation was canceled.
base (3.10, py310-azureblob)
The job was canceled because "_3_9_flake8" failed.
base (3.10, py310-azureblob)
The operation was canceled.
base (3.11, py311-unixsocket, true)
The job was canceled because "_3_9_flake8" failed.
base (3.11, py311-unixsocket, true)
The operation was canceled.
core (3.11, py311-core)
Process completed with exit code 1.
core (3.12, py312-core)
The job was canceled because "_3_11_py311-core" failed.
core (3.12, py312-core)
The operation was canceled.
base (3.9, flake8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
base (3.9, flake8)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
postgres (3.8, py38-postgres)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
postgres (3.8, py38-postgres)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
postgres (3.9, py39-postgres)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
postgres (3.9, py39-postgres)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
postgres (3.10, py310-postgres)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
postgres (3.10, py310-postgres)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
postgres (3.11, py311-postgres)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
postgres (3.11, py311-postgres)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
postgres (3.7, py37-postgres)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
postgres (3.7, py37-postgres)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
postgres (3.6, py36-postgres)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
postgres (3.6, py36-postgres)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
postgres (3.12, py312-postgres)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
postgres (3.12, py312-postgres)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
core (3.8, py38-core)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
core (3.8, py38-core)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
core (3.9, py39-core)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
core (3.9, py39-core)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
core (3.10, py310-core)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
core (3.10, py310-core)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
core (3.7, py37-core)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
core (3.7, py37-core)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
core (3.6, py36-core)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
core (3.6, py36-core)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
core (3.11, py311-core)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
core (3.11, py311-core)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/