@Marvin I get the following warning log message on the most simplest task:

WARNING | Task run 'task_one-0' - Task run 'task_one-0' finished in state Completed()

What could be the issue?

The warning message you received indicating

"WARNING | Task run 'task_one-0' - Task run 'task_one-0' finished in state Completed()"

seems to be more of a notification than an error. Typically, in software logging, a "warning" indicates something that may be of concern but isn't necessarily causing a failure in the process. However, I used the GitHub API to search Prefect's repository for issues related to a task being marked as completed with a warning, and the retrieved issues do not seem to directly address the specific warning message you encountered. Most of the related issues involve task name conflicts, logging format problems, or unexpected behavior when tasks are marked as successful despite failing conditions like timeouts. In absence of a more specific issue in the GitHub repository, here are a few general suggestions to troubleshoot the warning log message: 1. Make sure that the task is intended to have a state of "Completed". A "Completed" state is Prefect's term for a task that has finished executing without any errors. 2. Review the task code for any conditional logging that could unintentionally trigger a warning. Sometimes extra logging is added for debugging and can be removed once the task is behaving as expected. 3. Examine the configuration of your logging system. Ensure that logs at different levels (ERROR, WARNING, INFO, DEBUG) are being handled as expected. 4. If you suspect a bug or a misconfiguration in Prefect, consider raising an issue on the Prefect GitHub repository with details of your flow and task configuration for further assistance. Without further context or specific error messages, these general tips are a starting point for diagnosing the log message you received. If you have additional details or context, feel free to provide them for a more precise analysis.

hi @hagai - this log was inadvertently added in the previous release and has since been removed from main and will be gone next release

@Nate Thanks!

👍

@Marvin has this fix made it into Prefect cloud?

The latest version of Prefect is 2.16.6, which includes a fix related to new behavior in

typer 0.10.0

that broke the

prefect

CLI. This information comes from the Prefect GitHub repository, and you can see the pull request for this specific fix here. As for whether the fix has been deployed to Prefect Cloud, that depends on how Prefect Cloud manages its releases. Given that this fix is included in the latest release, it's reasonable to assume that if Prefect Cloud is up to date, it should include this fix. If you need to confirm this for Prefect Cloud specifically, it is best to check the official announcements or reach out to Prefect support. For more details about the latest version and all changes, you can visit the release comparison on GitHub.

the extra log problem was related to the SDK, which is not tied meaningfully to the version of Prefect Cloud. so yes, the removal the extra log has been released

Thanks @Nate. That's odd then as I still see it in the log messages of our flows in Prefect Cloud. Do we need to upgrade something? Is it the way we're deploying the flows?

what version of prefect are you using to run your flows? i.e. do you have an image pinned to that old version of prefect in your work pool?

Ah! That might be it. We're using this container to run our flows

prefecthq/prefect:2-python3.10

gotcha, not sure what your image pipeline is like, but it may be worth running with

--no-cache

or

--no-cache-filter

to pull the new base