hi @Marvin getting this warning issue using the

from prefect.testing.utilities import prefect_test_harness

: curious if was resolved in future releases. currently running

prefect = {version = "3.1.2", extras = ["shell"]}

Use `verify=ssl.create_default_context(cafile=...)` or `verify=ssl.create_default_context(capath=...)

It seems that there are no specific GitHub issues related to the warning you mentioned with

prefect_test_harness

and

ssl.create_default_context

. However, you might want to check the latest release notes for Prefect to see if any relevant updates or fixes have been introduced since your current version (3.1.2). If the issue persists and is critical for your workflow, you might want to consider upgrading to the latest version or checking with the Prefect community for any workarounds or patches.

@Marvin can you check the release notes for me?

The latest release notes for Prefect do not specifically mention any fixes related to the

prefect_test_harness

or the

ssl.create_default_context

warning. If this issue is significantly impacting your work, I recommend reaching out to the Prefect community or checking for any unofficial patches or workarounds that might be available. You can also keep an eye on the Prefect releases page for any updates that might address this issue in the future.

@Marvin can you check not just the latest? everything from my version till latest?

I couldn't find any specific mention of the

prefect_test_harness

or the

ssl.create_default_context

warning in the release notes from version 3.1.2 to the latest release. It seems that this issue might not have been directly addressed in the official release notes. If this is a persistent problem, you might consider reaching out to the Prefect community or checking for any community-driven solutions. Additionally, staying updated with the latest releases might help, as issues can sometimes be resolved indirectly through dependencies or other improvements.