• Rajvir Jhawar

    Rajvir Jhawar

    3 weeks ago
    Hi Prefect Team, I have encountered a issue with deployments: For some reason parameters are required when you want to update a deployment via the UI. For instance if i want to just change work queue you cannot do that without having default parameters already set. Parameters should in this case always be optional. I only supply parameters via api call hence I don't even need to add default params. You can probably get around this by supplying default values, but that is not an optimal experience. The above issues occur in Prefect 2.3.1 Final issue i had so far when the value of "Debug" is set as false Prefect for some reason leaves the value blank. I haven't re-tested this again in a newer version of prefect (i believe in occurred in 2.1.0) . Just wanted to put that on your radar
  • Andy Thurgood

    Andy Thurgood

    3 weeks ago
    Hello, Quick question on the 2.0 UI, specifically the collaborator signup flow. We have added a collaborator, which generates a signup email, but the accept link directs/redirects the user to the login page, with no obvious way to set credentials or accept the signup. The link in the invite points to http://url6711.prefect.io/ls/click with some hefty query params of
    upm
    ,
    data
    ,
    sdata
    and
    reserved.
    Is there a way to debug this at all? Should we be landing at a signup or set credentials type page? Thanks
    Andy Thurgood
    Craig Harshbarger
    3 replies
    Copy to Clipboard
  • y

    Yusuf

    3 weeks ago
    Just wanted to share some honest feedback. I love and support the Prefect project a ton and am super grateful to the community. I just started fiddling with the new Prefect Orion UI. I had been using the Prefect 1 Cloud UI before. I'm a little bit lost on the user experience. I might just be too heavily comparing it to what I was used to seeing before. Here's an example though: When I go to flows, I'm essentially inspecting my data pipelines. When I click on a flow/pipeline, I see the deployments. Which is reasonable. However when I click deployments, I'd expect to see information like a history of runs and states. As well as what used to be the "schematic" tab from the old cloud UI, where I can see the actual flow graph. It just feels like what is essentially your flow/pipline's "homepage" should have more information about the pipeline itself. The visual lineage definition of a flow and run history are the two main things I care about when it comes to an existing pipeline, so its been jarring to have that cut out and put elsewhere.
    y
    Evan Sutherland
    +1
    6 replies
    Copy to Clipboard
  • kwmiebach

    kwmiebach

    1 month ago
    OK, it is solved. I will update later, need a break now.
    kwmiebach
    Jenny
    +3
    17 replies
    Copy to Clipboard
  • a

    Adam Brusselback

    3 weeks ago
    Hey all, I am just trying to run a flow from the UI that works just fine when kicked off from python... I am just using the "Get Github Stars" flow/task from the docs, and wanted to pass in params from the UI. It is not going as expected. When I am trying to pass them in from the UI, I get each character passed to the task instead of each individual string in the parameters. See screenshots in thread. Is this just a formatting issue with the parameters?
    a
    Jenny
    +1
    6 replies
    Copy to Clipboard
  • Tan Li

    Tan Li

    3 weeks ago
    Hi there, I was playing around with the Orion UI, but keep seeing an empty dashboard while I can query something, i.e. actual flow-run records in the DB. Any help on what I could messed up here? Really appreciate it! 🙏
    Tan Li
    2 replies
    Copy to Clipboard
  • o

    Oscar Björhn

    3 weeks ago
    Hey, You need to use .submit if you want to visualize a dependency graph.
    o
    Joao Moniz
    +3
    6 replies
    Copy to Clipboard
  • Marc-Antoine Bélanger

    Marc-Antoine Bélanger

    2 weeks ago
    I have some issues specifying the parameters on a deployment run. I have defined the following properties:
    {"data": {
                            "title": "data",
                            "default": {},
                            "type": "object",
     },
    "train": {
                            "title": "train",
                            "default": {},
                            "type": "object",
     }
    }
    This is what it is showing in the UI: But the run fails:
    Validation of flow parameters failed with error: ParameterTypeError('Flow run received invalid parameters:\n - data: value is not a valid dict\n - train: value is not a valid dict')
    Traceback (most recent call last):
      File "/usr/local/lib/python3.10/site-packages/prefect/engine.py", line 284, in retrieve_flow_then_begin_flow_run
        parameters = flow.validate_parameters(flow_run.parameters)
      File "/usr/local/lib/python3.10/site-packages/prefect/flows.py", line 269, in validate_parameters
        raise ParameterTypeError.from_validation_error(exc) from None
    prefect.exceptions.ParameterTypeError: Flow run received invalid parameters:
     - data: value is not a valid dict
     - train: value is not a valid dict
    They seem to be interpreted as strings in the Parameters tab:
    {
      "data": "{}",
      "train": "{}"
    }
    Any idea what I am doing wrong?
    Marc-Antoine Bélanger
    1 replies
    Copy to Clipboard
  • l

    Lucas Cavalcanti Rodrigues

    3 weeks ago
    Hey, how can I get a list of all UI registered flow group ids using graphQL? I know I can get the flow ID querying for name using:
    gql(
        '''
            query LatestFlowByName($name: String) {
              flow(
                where: {name: {_eq: $name}},
                order_by: {version: desc},
                limit: 1,
              )
              {
                id
              }
            }
        ''',
    )
    But how can I have all flow ids regardless of the name?
    l
    1 replies
    Copy to Clipboard