https://prefect.io
Join Slack
<@ULVA73B9P> Hi all, I am going in circles with resolving the misconfiguration between prefect and ...
m

Mitch

over 1 year ago
@Marvin Hi all, I am going in circles with resolving the misconfiguration between prefect and pydantic. I have tried many versions, but currently failing with prefect 3.1.12 and pydantic 2.7.0 Using above config
pydantic.errors.PydanticUserError: If you use `@root_validator` with pre=False (the default) you MUST specify `skip_on_failure=True`. Note that `@root_validator` is deprecated and should be replaced with `@model_validator`.
Tried reverting back to pydantic 1.10.11 as that's what we has used in the past.
And because prefect (3.1.11) depends on pydantic (>=2.7,<2.10.0 || >2.10.0,<3.0.0)
 and prefect (3.1.13) depends on pydantic (>=2.9,<2.10.0 || >2.10.0,<3.0.0), prefect (>=3.0,<3.1.12 || >3.1.12,<3.1.14 || >3.1.14,<4.0) requires pydantic (>=2.7,<3.0.0).
And because prefect (3.1.14) depends on pydantic (>=2.9,<2.10.0 || >2.10.0,<3.0.0)
 and prefect (3.1.12) depends on pydantic (>=2.7,<2.10.0 || >2.10.0,<3.0.0), prefect (>=3.0,<4.0) requires pydantic (>=2.7,<3.0.0).
Reverting to prefect 2.20.X I get the following for any prefect cli or run.
pydantic.v1.error_wrappers.ValidationError: 1 validation error for Profile
settings
  Unknown setting 'PREFECT_SERVER_ALLOW_EPHEMERAL_MODE'. (type=value_error)
m
m
n
  • 3
  • 10
  • 152
Hello <@ULVA73B9P>, I have tried basic auth in prefect 3.1.11, like: `PREFECT_SERVER_API_AUTH_STRIN...
m

Murad-AIQ

over 1 year ago
Hello @Marvin, I have tried basic auth in prefect 3.1.11, like:
PREFECT_SERVER_API_AUTH_STRING="admin:admin" prefect server start
but it does not work. • Any password i use prefect logged me in. • Even if I inserted the right password, I cannot see any of my flows, runs, work-pools... etc did i miss something?
m
m
  • 2
  • 3
  • 152
<@ULVA73B9P> Is there any integrations with meltano
a

Abhishek Singh

over 1 year ago
@Marvin Is there any integrations with meltano
a
m
  • 2
  • 58
  • 152
Hey everyone, how do I change the default path so that when I run something like "Prefect deploy .."...
c

Charles

about 2 years ago
Hey everyone, how do I change the default path so that when I run something like "Prefect deploy .." it wont look in the default C:\ drive for my python.exe file? I have a weird usecase where my venv is in another machine and we access it via UNC path to the python.exe
c
n
m
  • 3
  • 10
  • 152
prefect.server.utilities.messaging.memory - Message failed after 4 retries and will be moved to the ...
j

Jason

over 1 year ago
prefect.server.utilities.messaging.memory - Message failed after 4 retries and will be moved to the dead letter queue02/04 115702 what is this about?
j
n
  • 2
  • 1
  • 151
<@ULVA73B9P> I'm still struggling with the return value of the wait() method of tasks. I always get ...
a

Andreas Geissner

almost 2 years ago
@Marvin I'm still struggling with the return value of the wait() method of tasks. I always get None. Can you tell me what is wrong with the following minimal example:
import time
from prefect import flow, task, get_run_logger

@task
def wait_task(t):
    time.sleep(t)
    return_value = f'Waited for {t} seconds'
    get_run_logger().info(f'Now returning the following sentence: {return_value}')
    return return_value

@flow
def minimal_wait():
    logger = get_run_logger()
    status = wait_task.submit(5).wait(10)
    <http://logger.info|logger.info>(f'Status when waiting 5 s with time limit 10 s: {status}')
    status = wait_task.submit(15).wait(10)
    <http://logger.info|logger.info>(f'Status when waiting 15 s with time limit 10 s: {status}')


minimal_wait()
I also get the following Warning: A future was garbage collected before it resolved. Please call
.wait()
or
.result()
on futures to ensure they resolve. See https://docs.prefect.io/latest/develop/task-runners for more details.
a
m
  • 2
  • 6
  • 151
Hi all, is anyone facing the below problem when you try to load the github storage in the flow afte...
m

Majo Dencilin

almost 2 years ago
Hi all, is anyone facing the below problem when you try to load the github storage in the flow after saving the block
prefect.exceptions.ScriptError: Script at '/var/folders/rm/bm2spvzj6qq477q54wdvmqd40000gp/T/tmp0vkt8jv1/github-repository-majo-github-repo/datalake/cids/c008/flows/migration/test.py' encountered an exception: TypeError('Result storage configuration must be persisted server-side. Please call `.save()` on your block before passing it in.')
āœ… 1
m
v
+2
  • 4
  • 12
  • 151
Hey Hey :slightly_smiling_face: We use the Prefect Teams Notification Block, which employs the Team...
m

Michael Michael

about 2 years ago
Hey Hey šŸ™‚ We use the Prefect Teams Notification Block, which employs the Teams Webhook. However, since Teams transitioned to 'Workflows,' this functionality seems to be broken. https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/ Has anyone else encountered this issue? Are there any existing solutions to fix it? Thaanks āœŒļø
m
n
  • 2
  • 2
  • 151
how do i get a list of all prefect deployments in python
d

Derrell

over 2 years ago
how do i get a list of all prefect deployments in python
d
j
n
  • 3
  • 6
  • 151
Hi all, I'm trying to get a secret key using the Prefect Secret Block in the Jupyter notebook UI. Wh...
g

Gordon

over 2 years ago
Hi all, I'm trying to get a secret key using the Prefect Secret Block in the Jupyter notebook UI. When doing so, I get the error:
AttributeError: 'coroutine' object has no attribute 'get'
Below is the code to generate this error:
from prefect.blocks.system import Secret

secret_block = Secret.load("name-of-my-block")
secret_block.get()
I believe this is specific to working in Jupyter. Any recommendations to resolve this error? I've added a couple of related docs in this thread.
g
a
  • 2
  • 2
  • 151
Previous565758Next

Prefect Community

Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Powered by