• seunggs

    seunggs

    2 months ago
    server.yaml:
    ----
    auth:
      appAuth:
        thirdPartyConfig:
          flyteClient:
            clientId: flytectl
            redirectUri: <http://localhost:53593/callback>
            scopes:
            - offline
            - all
      authorizedUris:
      - <https://localhost:30081>
      - <http://flyteadmin:80>
      - <http://flyteadmin.flyte.svc.cluster.local:80>
      userAuth:
        openId:
          baseUrl: <https://accounts.google.com>
          clientId: <http://657465813211-6eog7ek7li5k7i7fvgv2921075063hpe.apps.googleusercontent.com|657465813211-6eog7ek7li5k7i7fvgv2921075063hpe.apps.googleusercontent.com>
          scopes:
          - profile
          - openid
  • seunggs

    seunggs

    2 months ago
    Is this expected?
  • seunggs

    seunggs

    2 months ago
    This might be the reason why I’m getting
    <https://flyte.sidetrek.com/me> (501)
    not implemented error in the flyte console
  • seunggs

    seunggs

    2 months ago
    "unknown service flyteidl.service.IdentityService"
  • krishna Yerramsetty

    krishna Yerramsetty

    2 months ago
    Hello all! Question around the right way of using dynamic workflows with mapped tasks inside them. I adapted the map_task_example to run within a dynamic workflow instead of the general workflow like so:
    @dynamic
    def wrapper_task(a: typing.List[int]) -> str:
        mapped_out = map_task(a_mappable_task)(a=a).with_overrides(
            retries=4,
        )
        coalesced = coalesce(b=mapped_out)
        return coalesced
    
    
    @task
    def a_mappable_task(a: int) -> str:
        inc = a + 2
        stringified = str(inc)
        return stringified
    
    
    @task
    def coalesce(b: typing.List[str]) -> str:
        coalesced = "".join(b)
        return coalesced
    
    
    @workflow
    def my_map_workflow(a: typing.List[int]) -> str:
    
        return wrapper_task(a=a)
    
        if __name__ == "__main__":
            result = my_map_workflow(a=[1, 2, 3, 4, 5])
            print(f"{result}")
    I am seeing a type mismatch compilation error however at run-time:
    User] malformed dynamic workflow, caused by: Collected Errors: 2
    	Error 0: Code: MismatchingTypes, Node Id: dn1, Description: Variable [o0] (type [collection_type:<collection_type:<simple:STRING > > ]) doesn't match expected type [collection_type:<simple:STRING > ].
    Any ideas on why the return is a list of lists from the mapped task? And how do I correctly pass these outputs onto other tasks?
    krishna Yerramsetty
    Yee
    9 replies
    Copy to Clipboard
  • Sandra Youssef

    Sandra Youssef

    2 months ago
    Hi Flyers, If you'd like to learn more about one of Flyte's Ecosystem Projects, UnionML, join @Niels Bantilan in our very first UnionML OSS Planning event! • Bring your questions, ideas and feedback • Take part in the UnionML roadmap discussion Open to the whole community! Tomorrow Wednesday July 6 at 9am PT.Calendar Invite See you there! Flyte Team
  • v

    Vladimir Lialine

    2 months ago
    Hello Flyte users.
  • Bernhard Stadlbauer

    Bernhard Stadlbauer

    2 months ago
    Hi! We've installed the
    flyte-core
    helm
    chart in version
    1.0.2
    on one of our clusters yesterday, and it came up successfully. Whilst trying to upgrade another cluster today, we did get an an
    ImagePullBackoff
    when trying to pull
    <http://cr.flyte.org/flyteorg/flyteadmin-release:v1.0.2|cr.flyte.org/flyteorg/flyteadmin-release:v1.0.2>
    . I can also confirm not being able to pull that image locally:
    ❯ docker pull <http://cr.flyte.org/flyteorg/flyteadmin-release:v1.0.2|cr.flyte.org/flyteorg/flyteadmin-release:v1.0.2>
    Error response from daemon: manifest unknown
    Has anything changed here recently?
    Bernhard Stadlbauer
    Nastya Rusina
    2 replies
    Copy to Clipboard
  • Klemens Kasseroller

    Klemens Kasseroller

    2 months ago
    Hi! While trying to launch workflows from the flyte console, I experienced timeouts with the error message "Request failed with status code 504" coming from the flyte admin after 15s. I figured out, that the problem occurs if the inputs and outputs of the individual tasks are complex/nested dataclasses. Could someone explain to me, what is happening behind the scenes, when launching a (static) workflow, and why the structure of my inputs and outputs matters at that point in time. Does anyone know a solution to this problem? I am using the sandbox deployment (not the DinD deployment) on a local Kubernetes cluster (tested both on a Windows laptop and on a Linux workstation). Chart versions:
    flyte-core-v1.0.2
    flyte-deps-v1.0.2
    Klemens Kasseroller
    1 replies
    Copy to Clipboard
  • Sonja Ericsson

    Sonja Ericsson

    2 months ago
    hey! is there a metric in propeller to measure failures from plugins? We use these recording rules currently, but each time we add a new plugin we need to go and add it to the rules 🧵
    Sonja Ericsson
    k
    8 replies
    Copy to Clipboard