https://prefect.io
Join Slack
Noticing a change in behaviour for results since upgrading to 2.6. A task that would return an empt...
# ask-community
j
Noticing a change in behaviour for results since upgrading to 2.6. A task that would return an empty list now returns 
None
. Wondering if this is intentional. Minimal example in the thread. Also found out I can’t downgrade from 2.6 to 2.5 because of what looks like some database migrations? Running 
prefect orion database reset -y
on a database with 2.5 after upgrading to 2.6 and it fails.
👀 1
✅ 1
🙏 1
Copy code
@task()
def my_task():
    return []


@flow()
def my_flow():
    result = my_task()
    print(result)
In 2.5 
results == []
In 2.6 
results is None
z
You can downgrade your database on 2.6 then upgrade it on 2.5 and it should work. This change is definitely not intentional. I’ll look into it, thanks for pointing it out!
🙏 1
j
That did the trick
thanks!
z
In the meantime you can do 
@task(persist_result=True)
as well for a fix.
I reproduced successfully and will get a fix out asap.
🙏 2
Ah this is a weird edge-case in Pydantic
Hey! This is fixed in 2.6.1 which is now available.
Thanks again for the report.
j
Yep. Just ran the failing test suite against the new version and it’s working!
👏 1
My pleasure
l
Thank you for this! Was just about to post with the same issue
z
There are some additional minor fixes for results in the latest release as well 🙂
👍 1
Open in Slack
PreviousNext
Powered by

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