Release - flytesnacks v0.3.171 New release published by flyte-bot Changelog • cbf9b21 Correction in Code snippets (#904) flyteorg/flytesnacks

Release - v1.1.74 New release published by flyte-bot Changelog • 8596a56 Truncate execution error message in list execution calls (#523) flyteorg/flyteadmin

#3348 [Core feature] Enhance task logging template utils for start/finish time Issue created by andrewwdye Motivation: Why do you think this is important? Flyteplugins provides default task logging support for Cloudwatch and Stackdriver; however, the links don't include start/finish times. Depending when the links are followed, the user may need to adjust time filters in the log viewer, leading to initial confusion over missing logs and adding an unnecessary step. Template params for

{{ .podUnixStartTime }}

and

{{ .podUnixFinishTime }}

are provided; however. they are incompatible with at least Cloudwatch and Stackdriver. Cloudwatch expects time queries in unix timestamp using millisecond granularity and Stackdriver expects time queries in RFC3339 or ISO 8601 formats. Goal: What should the final outcome look like, ideally? Flyte task log links should contain time specific references based on the task's start time (and end time if available). Describe alternatives you've considered Require the user to manually filter to the task timeframe Propose: Link/Inline OR Additional context One option is to introduce new template params for

PodUnixMsecStartTime

and

PodTimestampStartTime

(and their Finish counterparts), corresponding to unix milliseconds and RFC 3339, respectively. As part of this change we should update the log link to use the container end time if available. Today it is hardcoded to

now()

. Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

1 new commit pushed to

<https://github.com/flyteorg/flytesnacks/tree/master|master>

by samhita-alla

<https://github.com/flyteorg/flytesnacks/commit/1d6ae681476f4f367d2c17888bdd4f74d8734f61|1d6ae681>

- Fix bioinformatics example (#957) flyteorg/flytesnacks

#765 Bump pillow from 9.1.0 to 9.1.1 in /cookbook/case_studies/bioinformatics/blast Pull request opened by dependabot[bot] Bumps pillow from 9.1.0 to 9.1.1. Release notes Sourced from pillow's releases.

9.1.1

This release addresses several security problems.

CVE-2022-30595: When reading a TGA file with RLE packets that cross scan lines, Pillow reads the information past the end of the first line without deducting that from the length of the remaining file data. This vulnerability was introduced in Pillow 9.1.0, and can cause a heap buffer overflow.

Opening an image with a zero or negative height has been found to bypass a decompression bomb check. This will now raise a `SyntaxError` instead, in turn raising a

PIL.UnidentifiedImageError

.

Changelog Sourced from pillow's changelog.

9.1.1 (2022-05-17)

• When reading past the end of a TGA scan line, reduce bytes left. CVE-2022-30595 [radarhere]

• Do not open images with zero or negative height #6269 [radarhere]

Commits • `0f44136` 9.1.1 version bump • `f66f5e1` pre-commit: update Black to fix Click • `0153b37` Skip test_realloc_overflow unless libtiff 4.0.4 or higher • `6fcd31b` Added release notes for 9.1.1 • `c846cc8` When reading past the end of a scan line, reduce bytes left • `184b73e` Do not open images with zero or negative height • See full diff in compare view Dependabot compatibility score Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting

@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/flytesnacks GitHub Actions: Mark github pre-release as Release GitHub Actions: Publish artifacts to github release GitHub Actions: Create Prerelease GitHub Actions: Bump Version ✅ 26 other checks have passed 26/30 successful checks

#884 Bump protobuf from 3.20.0 to 3.20.2 in /cookbook/case_studies/bioinformatics/blast Pull request opened by dependabot[bot] Bumps protobuf from 3.20.0 to 3.20.2. Release notes Sourced from protobuf's releases.

Protocol Buffers v3.20.2

C++

• Reduce memory consumption of MessageSet parsing

• This release addresses a Security Advisory for C++ and Python users

Protocol Buffers v3.20.1

PHP

• Fix building packaged PHP extension (#9727)

• Fixed composer.json to only advertise compatibility with PHP 7.0+. (#9819)

Ruby

• Disable the aarch64 build on macOS until it can be fixed. (#9816)

Other

• Fix versioning issues in 3.20.0

Protocol Buffers v3.20.1-rc1

#PHP

• Fix building packaged PHP extension (#9727)

#Other

• Fix versioning issues in 3.20.0

Commits • `a20c65f` Updating changelog • `c49fe79` Updating version.json and repo version numbers to: 20.2 • `806d7e4` Merge pull request #10544 from deannagarcia/3.20.x • `ae718b3` Add missing includes • `b4c395a` Apply patch • `6439c5c` Merge pull request #10531 from protocolbuffers/deannagarcia-patch-7 • `22c79e6` Update version.json • `c1a2d2e` Fix python release on macos (#10512) • `a826282` Merge pull request #10505 from deannagarcia/3.20.x • `7639a71` Add version file • Additional commits viewable in compare view Dependabot compatibility score Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting

@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/flytesnacks GitHub Actions: Mark github pre-release as Release GitHub Actions: Publish artifacts to github release GitHub Actions: Create Prerelease GitHub Actions: Bump Version ✅ 26 other checks have passed 26/30 successful checks

#3349 [UI Feature] Provide a link from dynamic workflow to children workflows Issue created by ena-cradle Motivation: Why do you think this is important? If a dynamic workflow contains subworkflows, they are properly started but not connected to the original execution natively, so it's hard to keep track of the original workflows artifacts and/or failures. For example, in this case: it is very hard to track the number of newly created instances of workflow_2, inputs/outputs to the started subworkflows, and see failures as the parent dynamic workflow (the purple node) collapses into just one node in the graph: Discussion in Slack: https://flyte-org.slack.com/archives/CP2HDHKE1/p1675878411385099 Goal: What should the final outcome look like, ideally? There should be a link to the children workflows, even better if the workflow nodes could be expanded to visualize their DAG. Propose: Link/Inline OR Additional context No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

Release - flytesnacks v0.3.172 New release published by flyte-bot Changelog • 1d6ae68 Fix bioinformatics example (#957) flyteorg/flytesnacks

#3350 [BUG] Swagger UI not accessible from the sandbox Issue created by aswanthkrishna Describe the bug unable to access redoc swagger UI after starting the sandbox at localhost:3081/openapi as mentioned in the [documentation]. (https://docs.flyte.org/en/latest/reference/swagger.html#reference-swagger) Expected behavior Should be able to see the swagger API documentation after navingating to localhost:3081/openapi after launching the sandbox container. Additional context to reproduce No response Screenshots No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#3351 Fix commonAnnotations indent in deployment.yaml Pull request opened by mehraneftekhari99 Describe your changes Fix indentation for annotations and labels in podTemplateSpec in deployment. (commonAnnotations) Check all the applicable boxes ☐ I updated the documentation accordingly. ☐ All new and existing tests passed. ☑︎ All commits are signed-off. Screenshots Note to reviewers flyteorg/flyte ✅ All checks have passed 2/2 successful checks

#389 Bump github.com/containerd/containerd from 1.5.10 to 1.5.18 Pull request opened by dependabot[bot] Bumps github.com/containerd/containerd from 1.5.10 to 1.5.18. Release notes Sourced from github.com/containerd/containerd's releases.

containerd 1.5.18

Welcome to the v1.5.18 release of containerd!

The eighteenth patch release for containerd 1.5 includes fixes for CVE-2023-25153 and CVE-2023-25173 along with a security update for Go.

Notable Updates

• Fix supplementary groups not being set up properly (GHSA-hmfx-3pcx-653p)

• Fix OCI image importer memory exhaustion (GHSA-259w-8hf6-59c2)

• Update Go to 1.19.6 (#8112)

See the changelog for complete list of changes

Please try out the release binaries and report any issues at https://github.com/containerd/containerd/issues.

Contributors

• Akihiro Suda

• Derek McGowan

• Ye Sijun

• Samuel Karp

• Phil Estes

• Swagat Bora

• Wei Fu

Changes

• [release/1.5] Prepare release notes for v1.5.18 (#8117)

• `ddf9de6cb` Prepare release notes for v1.5.18

• Github Security Advisory GHSA-hmfx-3pcx-653p

• `a62c38bf2` oci: fix additional GIDs

• `3b89da580` oci: fix loop iterator aliasing

• `b07ec6b25` oci: skip checking gid for WithAppendAdditionalGroups

• `356672cb5` refactor: reduce duplicate code

• `6a7b7617c` add WithAdditionalGIDs test

• `832bcf300` add WithAppendAdditionalGroups helper

• Github Security Advisory GHSA-259w-8hf6-59c2

• `19a347e45` importer: stream oci-layout and manifest.json

• [release/1.5] Go 1.19.6 (#8112)

• `4209dc243` Go 1.19.6

• [release/1.5] Fix retry logic within devmapper device deactivation (#8089)

• `0d16d045d` Fix retry logic within devmapper device deactivation

• [release/1.5] CI: skip some jobs when

repo != containerd/containerd

(#8084)

• `34451bc66` CI: skip some jobs when

repo != containerd/containerd

... (truncated) Commits • `39bb06f` Merge pull request #8117 from dmcgowan/prepare-v1.5.18 • `ddf9de6` Prepare release notes for v1.5.18 • `28e4618` Merge pull request from GHSA-hmfx-3pcx-653p • `959e1cf` Merge pull request from GHSA-259w-8hf6-59c2 • `b4538c2` Merge pull request #8112 from AkihiroSuda/cherrypick-8109-1.5 • `4209dc2` Go 1.19.6 • `7c3b243` Merge pull request #8089 from swagatbora90/backport-1.5 • `0d16d04` Fix retry logic within devmapper device deactivation • `9e9f4c8` Merge pull request #8084 from AkihiroSuda/ci-skip-on-fork-1.5 • `a62c38b` oci: fix additional GIDs • Additional commits viewable in compare view Dependabot compatibility score Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting

@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 di… flyteorg/flytectl GitHub Actions: Generate documentation GitHub Actions: Goreleaser GitHub Actions: Bump Version ✅ 7 other checks have passed 7/10 successful checks

1 new commit pushed to

<https://github.com/flyteorg/flyteadmin/tree/master|master>

by wild-endeavor

<https://github.com/flyteorg/flyteadmin/commit/fb003b72493cec3ca3e541c5e9356c6cba94c834|fb003b72>

- Only merge system defaults when querying workflow execution config for project attributes (#522) flyteorg/flyteadmin

Release - v1.1.75 New release published by flyte-bot Changelog • fb003b7 Only merge system defaults when querying workflow execution config for project attributes (#522) flyteorg/flyteadmin

1 new commit pushed to

<https://github.com/flyteorg/flytekit/tree/master|master>

by pingsutw

<https://github.com/flyteorg/flytekit/commit/014eea9d5ce963c9970cc791bdea550c0abb6b5c|014eea9d>

- Compile the workflow only at compile time (#1311) flyteorg/flytekit

#1311 Compile the workflow only at compile time Pull request opened by pingsutw TL;DR Compile is done on module load, which we should delay to execution or registration time, else module load causes failures. For example, we use the module loader to load the task function when running a task on flyte cluster. In the meantime, it also compiles the workflow, which is unnecessary. Make compiling the workflow only happen while serializing the PythonFunctionWorkflow. 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 I've tested it by running dynamic workflow on flyte cluster. we compile the workflow only when running

count_characters

import typing
from time import sleep

from flytekit import dynamic, task, workflow


@task
def return_index(character: str) -> int:
    """
    Computes the character index (which needs to fit into the 26 characters list)"""
    sleep(1)
    if character.islower():
        return ord(character) - ord("a")
    else:
        return ord(character) - ord("A")


@task
def update_list(freq_list: typing.List[int], list_index: int) -> typing.List[int]:
    """
    Notes the frequency of characters"""
    freq_list[list_index] += 1
    return freq_list


@task
def derive_count(freq1: typing.List[int], freq2: typing.List[int]) -> int:
    """
    Derives the number of common characters"""
    count = 0
    for i in range(26):
        count += min(freq1[i], freq2[i])
    return count


@workflow
def wf1():
    return_index(character="h")


@dynamic
def count_characters(s1: str, s2: str) -> int:
    freq1 = [0] * 26
    freq2 = [0] * 26

    # looping through the string s1
    for i in range(len(s1)):

        # index and freq1 are not accessible as they are promises
        index = return_index(character=s1[i])
        freq1 = update_list(freq_list=freq1, list_index=index)

    # looping through the string s2
    for i in range(len(s2)):

        # index and freq2 are not accessible as they are promises
        index = return_index(character=s2[i])
        freq2 = update_list(freq_list=freq2, list_index=index)

    wf1()

    return derive_count(freq1=freq1, freq2=freq2)


@workflow
def wf(s1: str = "Pear", s2: str = "Earth") -> int:
    return count_characters(s1=s1, s2=s2)


if __name__ == "__main__":
    print(wf(s1="Pear", s2="Earth"))

Tracking Issue https://github.com/flyteorg/flyte/issues/ Follow-up issue NA flyteorg/flytekit Codecov: 69.29% (-0.18%) compared to c11362f ✅ 29 other checks have passed 29/30 successful checks

#689 feat: add domain settings for project dashboard Pull request opened by 4nalog TL;DR This PR adds support for showing project attributes and project domain attributes in the Project Dashboard for flyteconsole. 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, there is no way for users to directly tell project attributes, project domain attributes. This PR adds support for showing project attributes and project domain attributes in the Project Dashboard for flyteconsole. Note: We currently merge the project attributes with the project domain attributes in a single view. In future and as per designs, we will indicate separately global and project level domain settings so that users can see what changed Tracking Issue #382 Follow-up issue #382 flyteorg/flyteconsole GitHub Actions: Build & Push FlyteConsole Image GitHub Actions: Get Release Tag GitHub Actions: Generate Release GitHub Actions: Build Flyteconsole Image / Push to Github Registry GitHub Actions: unit_tests_with_coverage ✅ 4 other checks have passed 4/9 successful checks

#3352 [FlyteCTL Feature] Hide global flags when printing help Issue created by eapolinario Describe the feature/command for FlyteCTL The output of

flytectl <command> --help

includes all global flags, which ends up pushing the useful info about the command too far up in the screen. Provide a possible output or UX example Global flags should be hidden and only the available flags for a particular command should show up, including all flags in case we run

flytectl --help

. This is possible to be done if we override cobra's usage template. unionai/cloud#1818 is an implementation of this idea for Cloud. Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

1 new commit pushed to

<https://github.com/flyteorg/flytekit/tree/master|master>

by pingsutw

<https://github.com/flyteorg/flytekit/commit/74cbe58bf3f5163a99ca533070bfc1b28c6c49b2|74cbe58b>

- Get the origin type when serializing dataclass (#1508) flyteorg/flytekit

#3011 [BUG] Annotated StructuredDataset with kwtypes leads raises TypeError Issue created by cosmicBboy Describe the bug Using an

Annotated[StructuredDataset, kwtypes(...)]

leads to this error:

return cast(LocallyExecutable, entity).local_execute(ctx, **kwargs)
  File "/Users/nielsbantilan/miniconda3/envs/flyte-vscode-demo/lib/python3.9/site-packages/flytekit/core/base_task.py", line 264, in local_execute
    outputs_literal_map = self.dispatch_execute(ctx, input_literal_map)
  File "/Users/nielsbantilan/miniconda3/envs/flyte-vscode-demo/lib/python3.9/site-packages/flytekit/core/base_task.py", line 525, in dispatch_execute
    raise TypeError(
TypeError: Failed to convert return value for var o0 for function prepare_train_args with error <class 'TypeError'>: unhashable type: 'collections.OrderedDict'

Expected behavior This should work like un-annotated

StructuredDataset

Additional context to reproduce Example:

WineDataset = Annotated[
    StructuredDataset,
    kwtypes(
        alcohol=float,
        malic_acid=float,
        ash=float,
        alcalinity_of_ash=float,
        magnesium=float,
        total_phenols=float,
        flavanoids=float,
        nonflavanoid_phenols=float,
        proanthocyanins=float,
        color_intensity=float,
        hue=float,
        od280_od315_of_diluted_wines=float,
        proline=float,
        target=int,
    )
]

@dataclass_json
@dataclass
class TrainArgs:
    hyperparameters: dict
    data: WineDataset

@task
def prepare_train_args(hp_grid: List[dict], data: WineDataset) -> List[TrainArgs]:
    return [TrainArgs(hp, data) for hp in hp_grid]

Using this in a workflow will lead to the error above Screenshots No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#1511 Remove requirements files Pull request opened by eapolinario TL;DR Remove mentions to requirements.txt and dev-requirements.txt 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 Up to this point we operated under the assumption that maintaining a single set of requirements files would be enough. This would guarantee a semblance of reproducibility (since we would be able to reproduce the environment used for that change). That assumption broke down as we started seeing libraries not being available in all OS+architecture we support, for example,

tensorflow

does not install cleanly on Mac M1's. In this change we trade reproducibility for the maintenance burden of having exhaustive requirements files by environment. jazzband/pip-tools#826 (comment) is the current advice coming from

pip-tools

, basically if we are to do this we need to run

pip-tools

once per-environment. Instead, we're taking one step back in order to figure out what's the right next steps. The idea is that we're going to invest in a real multi-environment solution in the near future, but in the meanwhile, we're going to lose reproducibility in order to decrease the maintenance burden. Note that this change is going to subsume the need for #1424. As a side-note, we removed the legacy

all-spark

extras in #807, but never removed the CI bits related to the spark-2.4 extra. Those are being removed in this PR. Tracking Issue flyteorg/flyte#3284 Follow-up issue NA flyteorg/flytekit ✅ All checks have passed 30/30 successful checks

#3353 [BUG] Overwrite cached outputs flag doesn't work for map tasks Issue created by dyu-bot Describe the bug After running a map task, checking

overwrite cached outputs

in the flyte console doesn't seem to work as the map task succeeds without ever spinning up workloads. It's suspected that it is relying on cache. The map task has caching enabled in the decorator as such:

@task(cache=True, cache_version="1.0")

Expected behavior The map task should spin up pods. Additional context to reproduce No response Screenshots No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#1512 [wip] streaming dir / file Pull request opened by kumare3 TL;DR Please replace this text with a description of what this PR accomplishes. 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 How did you fix the bug, make the feature etc. Link to any design docs etc Tracking Issue https://github.com/flyteorg/flyte/issues/ Follow-up issue NA OR https://github.com/flyteorg/flyte/issues/ flyteorg/flytekit GitHub Actions: build-plugins (3.8, flytekit-polars) GitHub Actions: build-plugins (3.8, flytekit-papermill) GitHub Actions: build-plugins (3.8, flytekit-pandera) GitHub Actions: build-plugins (3.8, flytekit-onnx-scikitlearn) GitHub Actions: build-plugins (3.8, flytekit-onnx-pytorch) GitHub Actions: build-plugins (3.8, flytekit-modin) GitHub Actions: build-plugins (3.8, flytekit-kf-tensorflow) GitHub Actions: build-plugins (3.8, flytekit-kf-pytorch) GitHub Actions: build-plugins (3.8, flytekit-kf-mpi) GitHub Actions: build-plugins (3.8, flytekit-k8s-pod) GitHub Actions: build-plugins (3.8, flytekit-hive) GitHub Actions: build-plugins (3.8, flytekit-greatexpectations) GitHub Actions: build-plugins (3.8, flytekit-dolt) GitHub Actions: build-plugins (3.8, flytekit-deck-standard) GitHub Actions: build-plugins (3.8, flytekit-dbt) GitHub Actions: build-plugins (3.8, flytekit-data-fsspec) GitHub Actions: build-plugins (3.8, flytekit-dask) GitHub Actions: build-plugins (3.8, flytekit-bigquery) GitHub Actions: build-plugins (3.8, flytekit-aws-sagemaker) GitHub Actions: build-plugins (3.8, flytekit-aws-batch) GitHub Actions: build-plugins (3.8, flytekit-aws-athena) GitHub Actions: build (windows-latest, 3.9) GitHub Actions: build (windows-latest, 3.8) GitHub Actions: build (windows-latest, 3.7, -spark2) GitHub Actions: build (windows-latest, 3.7) GitHub Actions: build (ubuntu-latest, 3.10) GitHub Actions: build (ubuntu-latest, 3.9) GitHub Actions: build (ubuntu-latest, 3.8) GitHub Actions: build (ubuntu-latest, 3.7, -spark2) GitHub Actions: build (ubuntu-latest, 3.7) ✅ No checks have passed 0/30 successful checks

#1514 Delay initialization of SynchronousFlyteClient in FlyteRemote Pull request opened by eapolinario TL;DR We shouldn't make a network call in the flyte remote constructor 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 Let's delay the initialization of

SynchonousFlyteClient

in remote. This should speed up total execution time of flytekit unit tests by 4-5x in the slowest tasks (the flytekit unit tests). This should cut 30 minutes from CI runs on average. Tracking Issue https://github.com/flyteorg/flyte/issues/ Follow-up issue NA OR https://github.com/flyteorg/flyte/issues/ flyteorg/flytekit GitHub Actions: build-plugins (3.8, flytekit-hive) GitHub Actions: build-plugins (3.8, flytekit-greatexpectations) GitHub Actions: build-plugins (3.8, flytekit-dolt) GitHub Actions: build-plugins (3.8, flytekit-deck-standard) GitHub Actions: build-plugins (3.8, flytekit-dbt) GitHub Actions: build-plugins (3.8, flytekit-data-fsspec) GitHub Actions: build-plugins (3.8, flytekit-dask) GitHub Actions: build-plugins (3.8, flytekit-bigquery) GitHub Actions: build-plugins (3.8, flytekit-aws-sagemaker) GitHub Actions: build-plugins (3.8, flytekit-aws-batch) GitHub Actions: build-plugins (3.8, flytekit-aws-athena) GitHub Actions: lint GitHub Actions: build (windows-latest, 3.9) GitHub Actions: build (windows-latest, 3.8) GitHub Actions: build (windows-latest, 3.7) GitHub Actions: build (ubuntu-latest, 3.10) GitHub Actions: build (ubuntu-latest, 3.9) GitHub Actions: build (ubuntu-latest, 3.8) GitHub Actions: build (ubuntu-latest, 3.7) GitHub Actions: docs ✅ 2 other checks have passed 2/22 successful checks

1 new commit pushed to

<https://github.com/flyteorg/flytekit/tree/master|master>

by eapolinario

<https://github.com/flyteorg/flytekit/commit/99d3d5048c207d32f469dde8797bcbb4408d6617|99d3d504>

- Remove requirements files (#1511) flyteorg/flytekit

#3354 [BUG] [CONSOLE] gate node in dynamic task Issue created by wild-endeavor Describe the bug Gate nodes inside of dynamic tasks don't behave the same. This workflow https://github.com/flyteorg/flytesnacks/blob/cecf8b1c98b784da3f15c1ab04624619890d1d16/cookbook/core/control_flow/human_in_the_loop.py#L82 is functionally the same as the

mainwf

that we've been testing on, except that it happens inside a dynamic task instead of the top level workflow. However when run inside a dynamic workflow, things don't look the same. None of the gate node stuff is there and the approval node only shows Running not Paused. Expected behavior Things should look the same as the non-dynamic case. This includes all views (node-list, graph, timeline) Additional context to reproduce No response Screenshots No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

1 new commit pushed to

<https://github.com/flyteorg/flytekit/tree/master|master>

by eapolinario

<https://github.com/flyteorg/flytekit/commit/707fc03b88ec08fb10d60ac642f3c80e275bd90c|707fc03b>

- Delay initialization of SynchronousFlyteClient in FlyteRemote (#1514) flyteorg/flytekit

#526 bump golang.org/x/net from 0.5.0 to 0.7.0 Pull request opened by dependabot[bot] Dependabot compatibility score Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting

@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/flytepropeller GitHub Actions: Build & Push Flytepropeller Image GitHub Actions: Goreleaser GitHub Actions: Bump Version ✅ 11 other checks have passed 11/14 successful checks

#3355 Bump golang.org/x/net from 0.5.0 to 0.7.0 Pull request opened by dependabot[bot] Bumps golang.org/x/net from 0.5.0 to 0.7.0. Commits • `8e2b117` http2/hpack: avoid quadratic complexity in hpack decoding • `547e7ed` http2: avoid referencing ResponseWrite.Write parameter after returning • `39940ad` html: parse comments per HTML spec • `87ce33e` go.mod: update golang.org/x dependencies • `415cb6d` all: fix some comments • `7e3c19c` all: correct typos in comments • `296f09a` http2: case insensitive handling for 100-continue • `f8411da` nettest: fix tests on dragonfly and js/wasm • See full diff in compare view Dependabot compatibility score Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting

@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/flyte GitHub Actions: generate_helm GitHub Actions: docs GitHub Actions: compile GitHub Actions: test-bootstrap GitHub Actions: generate_kustomize ✅ 2 other checks have passed 2/7 successful checks

1 new commit pushed to

<https://github.com/flyteorg/flytepropeller/tree/master|master>

by EngHabu

<https://github.com/flyteorg/flytepropeller/commit/812ebc4f09a503d8f3c5f08417371b09ad3a85bf|812ebc4f>

- bump golang.org/x/net from 0.5.0 to 0.7.0 (#526) flyteorg/flytepropeller

Release - v1.1.65 New release published by flyte-bot Changelog • 812ebc4 bump golang.org/x/net from 0.5.0 to 0.7.0 (#526) flyteorg/flytepropeller