• E Li

    E Li

    8 months ago
    Hi, I couldn't create a tenant, and got this error when running 'prefect server create-tenant -n default'. raise ClientError(result["errors"]) prefect.exceptions.ClientError: [{'message': "[{'extensions': {'path': '$', 'code': 'validation-failed'}, 'message': 'no mutations exist'}]", 'locations': [{'line': 2, 'column': 5}], 'path': ['create_tenant'], 'extensions': {'code': 'INTERNAL_SERVER_ERROR', 'exception': {'message': "[{'extensions': {'path': '$', 'code': 'validation-failed'}, 'message': 'no mutations exist'}]"}}}]
    E Li
    Kevin Kho
    +1
    35 replies
    Copy to Clipboard
  • Danny Vilela

    Danny Vilela

    8 months ago
    Hi all — what’s the right way to ensure that a flow always runs according to a schedule, even if the current run goes beyond the next run’s starting time? Does Prefect check for this automatically and execute the next run as expected? I’m using an
    IntervalSchedule
    for daily runs, if that helps.
    Danny Vilela
    Kevin Kho
    2 replies
    Copy to Clipboard
  • k

    Koby Kilimnik

    8 months ago
    how do i make it visible in the run log which parameters my flow used?
    k
    1 replies
    Copy to Clipboard
  • k

    Koby Kilimnik

    8 months ago
    right now the runs have random names
  • k

    Koby Kilimnik

    8 months ago
    what if i want to name the flow ?
    k
    Danny Vilela
    +1
    13 replies
    Copy to Clipboard
  • chelseatroy

    chelseatroy

    8 months ago
    Hiya prefect folks! I have the following composition test for a flow that totally works. This composition test literally perfectly describes the flow in question: ``````
    chelseatroy
    Kevin Kho
    16 replies
    Copy to Clipboard
  • Daniel Komisar

    Daniel Komisar

    8 months ago
    We are seeing flows with missing logs. Right now I’m running the same flow from two different projects and the logs do not show up when one from one project. This was working previously and I don’t think anyone changed anything. We’ve also previously seen this in both projects.
    Daniel Komisar
    Kevin Kho
    +1
    19 replies
    Copy to Clipboard
  • Ian Andres Etnyre Mercader

    Ian Andres Etnyre Mercader

    8 months ago
    Hi, I'am getting an unpickling error when I use Logstash, details in thread
    Ian Andres Etnyre Mercader
    Kevin Kho
    +1
    12 replies
    Copy to Clipboard
  • Miroslav Rác

    Miroslav Rác

    8 months ago
    How does Prefect generate this random but easily readable task run names? it’s very cool feature
    Miroslav Rác
    Kevin Kho
    3 replies
    Copy to Clipboard
  • Henrietta Salonen

    Henrietta Salonen

    8 months ago
    Hey you all, I’m new to Prefect and I’ve managed set up a dev & deployment process for my team to start working with Prefect development in production, however I’m still trying to find a good solution to manage the Agents and automate that part of the deployment as well. The current deployment workflow (done in Github Actions) looks roughly like this: • Build & Push new Docker image (dev/prod) whenever project requirements in the related branch are changed • Build & register flows to Prefect Cloud (dev/prod project) whenever flow files (or default build configs) in the related branch are changed We currently have two Docker Agents running in an AWS EC2 instance. Each agent has its own environment variables and currently, if new env variables need to be added, this is my process: • SSH to EC2 • Start new agents with new environment variables e.g.
    Nohup prefect agent docker start --label dev --env VAR1=<variable1> --env VAR2=<variable2> &
    • Get the PIDs for the old agents with old environment variables
    ps -ef | grep prefect
    • Kill the old agents
    kill <PID>
    As this is not a very smooth approach, I’d like to hear how others have approached automating the Agent part when setting up CI processes. Any tips?
    Henrietta Salonen
    Kevin Kho
    2 replies
    Copy to Clipboard