GitHub
10/03/2023, 1:53 AMimage▾
GitHub
10/03/2023, 1:53 AMimage▾
GitHub
10/03/2023, 1:53 AMdask cuda worker
i.e. that dask-cuda is present on the specified image.
Type
☑︎ Feature
☑︎ Plugin
Are all requirements met?
☐ Code completed
☐ Smoke tested
☑︎ Unit tests added
☐ Code documentation added
☐ Any pending items have an associated Issue
Complete description
Currently we build an arg to submit to the container and inject values such as threads and memory from the limits specified in the resources object in the dask plugin object. Dask cuda gives us many built in gpu tools and all that is required is to ensure dask cuda is installed and then to start out workers with dask-cuda-worker
. So, in order to accomodate, we simply check for gpu limits in the dask plugin resources and overwrite the first arg to dask-cuda-worker
.
flyteorg/flyte
GitHub Actions: Build & Push Image
GitHub Actions: Bump git tags
GitHub Actions: Integration Test
GitHub Actions: Unit Tests (flyteplugins) / Run Unit Test
GitHub Actions: Lint (flyteplugins) / Run Lint
GitHub Actions: Docker Build Images (flytepropeller) / build_docker
✅ 24 other checks have passed
24/30 successful checksGitHub
10/03/2023, 1:53 AMdask cuda worker
i.e. that dask-cuda is present on the specified image.
Type
☑︎ Feature
☑︎ Plugin
Are all requirements met?
☐ Code completed
☐ Smoke tested
☑︎ Unit tests added
☐ Code documentation added
☐ Any pending items have an associated Issue
Complete description
Currently we build an arg to submit to the container and inject values such as threads and memory from the limits specified in the resources object in the dask plugin object. Dask cuda gives us many built in gpu tools and all that is required is to ensure dask cuda is installed and then to start out workers with dask-cuda-worker
. So, in order to accomodate, we simply check for gpu limits in the dask plugin resources and overwrite the first arg to dask-cuda-worker
.
flyteorg/flyteplugins
✅ All checks have passed
6/6 successful checksGitHub
10/03/2023, 1:57 AMGitHub
10/03/2023, 1:57 AMGitHub
10/03/2023, 1:58 AM*ResourceWrapper
cache (*Resource) -> cast to (*Resource) // it works
s3 (Resource) -> cast to (*Resource) // Failed to do type casting since we unmarshall the resource to Resource
here.
We read the resource from s3 bucket after restarting the propeller (cache becomes empty).
Type
☑︎ Bug Fix
☐ Feature
☐ Plugin
Are all requirements met?
☑︎ Code completed
☑︎ Smoke tested
☑︎ Unit tests added
☐ Code documentation added
☐ Any pending items have an associated Issue
Complete description
^^^
Tracking Issue
NA
Follow-up issue
NA
flyteorg/flyte
GitHub Actions: Build & Push Image
GitHub Actions: Bump git tags
Codecov: 58.97% (-0.01%) compared to d9586b0
GitHub Actions: generate_kustomize
GitHub Actions: docs
✅ 25 other checks have passed
25/30 successful checksGitHub
10/03/2023, 1:58 AMimage▾
GitHub
10/03/2023, 1:58 AMGitHub
10/03/2023, 1:58 AM- name: FLYTE_INTERNAL_NODE_ID
value: n0/dn0/dn0/dn0/dn0/dn0/dn0/dn0/dn0/dn0
Type
☐ Bug Fix
☑︎ Feature
☐ Plugin
Are all requirements met?
☑︎ Code completed
☑︎ Smoke tested
☐ Unit tests added
☐ Code documentation added
☐ Any pending items have an associated Issue
Complete description
Currently the environment variables do not provide enough information to know the exact task being executed.
For example we intended to create a unique ID for all retries of a task. Without the nodeID this is not possible as tasks might be reused.
One can retrieve this information also from the hostname but this fails for long names due to k8s pod name length limits.
flyteorg/flyte
Codecov: 58.97% (-0.01%) compared to d9586b0
Codecov: 0.00% of diff hit (target 58.98%)
GitHub Actions: Build & Push Image
GitHub Actions: Bump git tags
GitHub Actions: Integration Test
GitHub Actions: Docker Build Images (datacatalog) / build_docker
GitHub Actions: generate_helm
✅ 23 other checks have passed
23/30 successful checksGitHub
10/03/2023, 1:59 AMGitHub
10/03/2023, 1:59 AMGitHub
10/03/2023, 2:05 AMitemID
to it. The workers won't process the item again after the task is done.
Before:
After:
100 workflows, each has 100 tasks.
Before:
image▾
image▾
GitHub
10/03/2023, 2:05 AM@dependabot rebase
.
* * *
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
• @dependabot rebase
will rebase this PR
• @dependabot recreate
will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge
will merge this PR after your CI passes on it
• @dependabot squash and merge
will squash and merge this PR after your CI passes on it
• @dependabot cancel merge
will cancel a previously requested merge and block automerging
• @dependabot reopen
will reopen this PR if it is closed
• @dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels
will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers
will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees
will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone
will set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the Security Alerts page.
flyteorg/flytestdlib
✅ All checks have passed
7/7 successful checksGitHub
10/03/2023, 2:05 AM@dependabot rebase
.
* * *
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
• @dependabot rebase
will rebase this PR
• @dependabot recreate
will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge
will merge this PR after your CI passes on it
• @dependabot squash and merge
will squash and merge this PR after your CI passes on it
• @dependabot cancel merge
will cancel a previously requested merge and block automerging
• @dependabot reopen
will reopen this PR if it is closed
• @dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels
will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers
will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees
will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone
will set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the Security Alerts page.
flyteorg/flytestdlib
✅ All checks have passed
7/7 successful checksGitHub
10/03/2023, 2:05 AM@dependabot rebase
.
* * *
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
• @dependabot rebase
will rebase this PR
• @dependabot recreate
will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge
will merge this PR after your CI passes on it
• @dependabot squash and merge
will squash and merge this PR after your CI passes on it
• @dependabot cancel merge
will cancel a previously requested merge and block automerging
• @dependabot reopen
will reopen this PR if it is closed
• @dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels
will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers
will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees
will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone
will set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the Security Alerts page.
flyteorg/flytestdlib
✅ All checks have passed
5/5 successful checksGitHub
10/03/2023, 2:05 AM@dependabot rebase
.
* * *
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
• @dependabot rebase
will rebase this PR
• @dependabot recreate
will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge
will merge this PR after your CI passes on it
• @dependabot squash and merge
will squash and merge this PR after your CI passes on it
• @dependabot cancel merge
will cancel a previously requested merge and block automerging
• @dependabot reopen
will reopen this PR if it is closed
• @dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels
will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers
will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees
will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone
will set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the Security Alerts page.
flyteorg/flytestdlib
Codecov: 68.14% (-0.03%) compared to 0dbe3c2
✅ 6 other checks have passed
6/7 successful checksGitHub
10/03/2023, 2:05 AM@dependabot rebase
.
* * *
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
• @dependabot rebase
will rebase this PR
• @dependabot recreate
will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge
will merge this PR after your CI passes on it
• @dependabot squash and merge
will squash and merge this PR after your CI passes on it
• @dependabot cancel merge
will cancel a previously requested merge and block automerging
• @dependabot reopen
will reopen this PR if it is closed
• @dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels
will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers
will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees
will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone
will set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the Security Alerts page.
flyteorg/flytestdlib
✅ All checks have passed
7/7 successful checksGitHub
10/03/2023, 2:07 AMGitHub
10/03/2023, 2:07 AMbase_exec_id
label with the value of current execution or a previous base_exec_id
if it exists.
Reasons:
1. Make it possible to retrieve all executions launched by the same base execution id (even recursively)
2. users could group executions using their own base exec id
3. flytectl get executions or remote list executions can use this label as a filter to retrieve high level progress of all subworkflows
Type
☐ Bug Fix
☑︎ Feature
☐ Plugin
Are all requirements met?
☑︎ Code completed
☐ Smoke tested
☑︎ Unit tests added
☑︎ Code documentation added
☑︎ Any pending items have an associated Issue
flyteorg/flyte
GitHub Actions: Integration Test (flyteadmin) / Integration tests
GitHub Actions: Unit Tests (flytestdlib) / Run Unit Test
GitHub Actions: Unit Tests (flytepropeller) / Run Unit Test
GitHub Actions: Unit Tests (flyteplugins) / Run Unit Test
GitHub Actions: Unit Tests (flytecopilot) / Run Unit Test
GitHub Actions: Unit Tests (flyteadmin) / Run Unit Test
GitHub Actions: Unit Tests (datacatalog) / Run Unit Test
GitHub Actions: Lint (flytestdlib) / Run Lint
GitHub Actions: Lint (flytepropeller) / Run Lint
GitHub Actions: Lint (flyteplugins) / Run Lint
GitHub Actions: Lint (flyteidl) / Run Lint
GitHub Actions: Lint (flyteadmin) / Run Lint
GitHub Actions: Lint (datacatalog) / Run Lint
GitHub Actions: Check Go Generate (flytepropeller) / Go Generate
GitHub Actions: Check Go Generate (flytecopilot) / Go Generate
GitHub Actions: Check Go Generate (flyteadmin) / Go Generate
GitHub Actions: Check Go Generate (datacatalog) / Go Generate
GitHub Actions: compile
✅ 12 other checks have passed
12/30 successful checksGitHub
10/03/2023, 2:08 AMGitHub
10/03/2023, 2:08 AMGitHub
10/03/2023, 2:08 AMGitHub
10/03/2023, 2:08 AMGitHub
10/03/2023, 2:08 AMalpine:3.16.7
, as this image has only 0 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Some of the most important vulnerabilities in your base image include:
* * *
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: https://camo.githubusercontent.com/c93ecbc4eafcf2a7f4f9ed6fc23e85c2dc09edee72b1c6c86f4dfb66ecd1e3c8/68747470733a2f2f6170692e7365676d656e742e696f2f76312f706978656c2f747261636b3f646174613d65794a33636d6c305a55746c65534936496e4a79576d785a634564485932527954485a7362306c596430645563566734576b4652546e4e434f5545774969776959573576626e6c746233567a535751694f6949355a6a566c4e5749324e53316a4f4467304c545269595449744f4449774d4330304d546b324d6d4a6c593259355a6d4d694c434a6c646d567564434936496c425349485a705a58646c5a434973496e42796233426c636e52705a584d694f6e736963484a4a5a434936496a6c6d4e575531596a59314c574d344f4451744e474a684d6930344d6a41774c5451784f545979596d566a5a6a6c6d59794a3966513d3d
🧐 View latest project report
🛠️ Adjust project settings
* * *
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Use After Free
flyteorg/flyte
GitHub Actions: Build & Push Image
GitHub Actions: Bump git tags
GitHub Actions: Integration Test
GitHub Actions: Check Go Generate
GitHub Actions: Lint
GitHub Actions: Unit Tests
GitHub Actions: Docker Build Images (flytepropeller) / build_docker
GitHub Actions: Docker Build Images (flytecopilot) / build_docker
GitHub Actions: generate_kustomize
GitHub Actions: Docker Build Images (flyteadmin) / build_docker
GitHub Actions: publish-development-helm-chart (flyteagent)
GitHub Actions: docs
GitHub Actions: Docker Build Images (datacatalog) / build_docker
GitHub Actions: publish-development-helm-chart (flyte-core)
GitHub Actions: generate_helm
GitHub Actions: publish-development-helm-chart (flyte-binary)
GitHub Actions: compile
GitHub Actions: Check for spelling errors
GitHub Actions: unpack-envvars
DCO: DCO
✅ 1 other check has passed
1/21 successful checksGitHub
10/03/2023, 2:08 AMalpine:3.16.7
, as this image has only 0 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Some of the most important vulnerabilities in your base image include:
* * *
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: https://camo.githubusercontent.com/c93ecbc4eafcf2a7f4f9ed6fc23e85c2dc09edee72b1c6c86f4dfb66ecd1e3c8/68747470733a2f2f6170692e7365676d656e742e696f2f76312f706978656c2f747261636b3f646174613d65794a33636d6c305a55746c65534936496e4a79576d785a634564485932527954485a7362306c596430645563566734576b4652546e4e434f5545774969776959573576626e6c746233567a535751694f6949355a6a566c4e5749324e53316a4f4467304c545269595449744f4449774d4330304d546b324d6d4a6c593259355a6d4d694c434a6c646d567564434936496c425349485a705a58646c5a434973496e42796233426c636e52705a584d694f6e736963484a4a5a434936496a6c6d4e575531596a59314c574d344f4451744e474a684d6930344d6a41774c5451784f545979596d566a5a6a6c6d59794a3966513d3d
🧐 View latest project report
🛠️ Adjust project settings
* * *
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Use After Free
flyteorg/flyteadmin
GitHub Actions: Build & Push Flyteadmin Image
GitHub Actions: Build & Push Flytescheduler Image
GitHub Actions: Goreleaser
GitHub Actions: Bump Version
DCO: DCO
✅ 9 other checks have passed
9/14 successful checksGitHub
10/03/2023, 2:08 AMalpine:3.18.3
, as this image has only 0 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Some of the most important vulnerabilities in your base image include:
* * *
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: https://camo.githubusercontent.com/f34c15b682f973979690863beb90eb9ec81f2da51e438b24a5b9ccea74de7f89/68747470733a2f2f6170692e7365676d656e742e696f2f76312f706978656c2f747261636b3f646174613d65794a33636d6c305a55746c65534936496e4a79576d785a634564485932527954485a7362306c596430645563566734576b4652546e4e434f5545774969776959573576626e6c746233567a535751694f694a69595467774d6d5978595330775954646c4c54517a4d32457459544d335979307a5a445a6d4d5745324e6a4a684d4459694c434a6c646d567564434936496c425349485a705a58646c5a434973496e42796233426c636e52705a584d694f6e736963484a4a5a434936496d4a684f4441795a6a46684c5442684e3255744e444d7a595331684d7a646a4c544e6b4e6d5978595459324d6d45774e694a3966513d3d
🧐 View latest project report
🛠️ Adjust project settings
* * *
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Use After Free
flyteorg/flyte
GitHub Actions: Build & Push Image
GitHub Actions: Bump git tags
GitHub Actions: Integration Test
GitHub Actions: Lint
GitHub Actions: Check Go Generate
GitHub Actions: Unit Tests
GitHub Actions: Docker Build Images (flytepropeller) / build_docker
GitHub Actions: Docker Build Images (flytecopilot) / build_docker
GitHub Actions: Docker Build Images (flyteadmin) / build_docker
GitHub Actions: docs
GitHub Actions: Docker Build Images (datacatalog) / build_docker
GitHub Actions: generate_kustomize
GitHub Actions: publish-development-helm-chart (flyteagent)
GitHub Actions: unpack-envvars
GitHub Actions: publish-development-helm-chart (flyte-core)
GitHub Actions: generate_helm
GitHub Actions: publish-development-helm-chart (flyte-binary)
GitHub Actions: Check for spelling errors
GitHub Actions: compile
DCO: DCO
✅ 1 other check has passed
1/21 successful checksGitHub
10/03/2023, 2:08 AMalpine:3.18.3
, as this image has only 0 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Some of the most important vulnerabilities in your base image include:
* * *
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: https://camo.githubusercontent.com/f34c15b682f973979690863beb90eb9ec81f2da51e438b24a5b9ccea74de7f89/68747470733a2f2f6170692e7365676d656e742e696f2f76312f706978656c2f747261636b3f646174613d65794a33636d6c305a55746c65534936496e4a79576d785a634564485932527954485a7362306c596430645563566734576b4652546e4e434f5545774969776959573576626e6c746233567a535751694f694a69595467774d6d5978595330775954646c4c54517a4d32457459544d335979307a5a445a6d4d5745324e6a4a684d4459694c434a6c646d567564434936496c425349485a705a58646c5a434973496e42796233426c636e52705a584d694f6e736963484a4a5a434936496d4a684f4441795a6a46684c5442684e3255744e444d7a595331684d7a646a4c544e6b4e6d5978595459324d6d45774e694a3966513d3d
🧐 View latest project report
🛠️ Adjust project settings
* * *
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Use After Free
flyteorg/flyteadmin
GitHub Actions: Build & Push Flyteadmin Image
GitHub Actions: Build & Push Flytescheduler Image
GitHub Actions: Goreleaser
GitHub Actions: Bump Version
DCO: DCO
✅ 9 other checks have passed
9/14 successful checksGitHub
10/03/2023, 2:09 AMalpine:3.14
, as this image has only 0 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Some of the most important vulnerabilities in your base image include:
* * *
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: https://camo.githubusercontent.com/d1ff4db20480b90549a49be4825621c6e6368eaab60913b604911dfd8104477f/68747470733a2f2f6170692e7365676d656e742e696f2f76312f706978656c2f747261636b3f646174613d65794a33636d6c305a55746c65534936496e4a79576d785a634564485932527954485a7362306c596430645563566734576b4652546e4e434f5545774969776959573576626e6c746233567a535751694f694a6c5a6d51794d6d49334e6930354d446b304c5451784f545974595441795a4330345a444d774e7a51305a6a68684e6a55694c434a6c646d567564434936496c425349485a705a58646c5a434973496e42796233426c636e52705a584d694f6e736963484a4a5a434936496d566d5a444979596a63324c546b774f5451744e4445354e6931684d444a6b4c54686b4d7a41334e44526d4f4745324e534a3966513d3d
🧐 View latest project report
🛠️ Adjust project settings
* * *
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Use After Free
flyteorg/flyte
GitHub Actions: Build & Push Image
GitHub Actions: Bump git tags
GitHub Actions: Integration Test
GitHub Actions: Check Go Generate
GitHub Actions: Unit Tests
GitHub Actions: Lint
GitHub Actions: Docker Build Images (flytepropeller) / build_docker
GitHub Actions: Docker Build Images (flyteadmin) / build_docker
GitHub Actions: Docker Build Images (flytecopilot) / build_docker
GitHub Actions: generate_helm
GitHub Actions: publish-development-helm-chart (flyteagent)
GitHub Actions: Docker Build Images (datacatalog) / build_docker
GitHub Actions: generate_kustomize
GitHub Actions: publish-development-helm-chart (flyte-core)
GitHub Actions: unpack-envvars
GitHub Actions: docs
GitHub Actions: publish-development-helm-chart (flyte-binary)
GitHub Actions: Check for spelling errors
GitHub Actions: compile
DCO: DCO
✅ 1 other check has passed
1/21 successful checksGitHub
10/03/2023, 2:09 AMalpine:3.14
, as this image has only 0 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Some of the most important vulnerabilities in your base image include:
* * *
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: https://camo.githubusercontent.com/d1ff4db20480b90549a49be4825621c6e6368eaab60913b604911dfd8104477f/68747470733a2f2f6170692e7365676d656e742e696f2f76312f706978656c2f747261636b3f646174613d65794a33636d6c305a55746c65534936496e4a79576d785a634564485932527954485a7362306c596430645563566734576b4652546e4e434f5545774969776959573576626e6c746233567a535751694f694a6c5a6d51794d6d49334e6930354d446b304c5451784f545974595441795a4330345a444d774e7a51305a6a68684e6a55694c434a6c646d567564434936496c425349485a705a58646c5a434973496e42796233426c636e52705a584d694f6e736963484a4a5a434936496d566d5a444979596a63324c546b774f5451744e4445354e6931684d444a6b4c54686b4d7a41334e44526d4f4745324e534a3966513d3d
🧐 View latest project report
🛠️ Adjust project settings
* * *
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Use After Free
flyteorg/flyteadmin
GitHub Actions: Goreleaser
GitHub Actions: Build & Push Flytescheduler Image
GitHub Actions: Build & Push Flyteadmin Image
GitHub Actions: Bump Version
DCO: DCO
✅ 7 other checks have passed
7/12 successful checks