Noticing a change in behaviour for results since upgrading t

Question

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

Josh Paulin · Answer

``` task def my task return flow def my flow result = my task print result ``` In 2 5 `results == ` In 2 6 `results is None`

Zanie · Answer

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

Josh Paulin · Answer

That did the trick

Josh Paulin · Answer

thanks

Zanie · Answer

In the meantime you can do ` task persist result=True ` as well for a fix

Zanie · Answer

I reproduced successfully and will get a fix out asap

Zanie · Answer

Ah this is a weird edge case in Pydantic

Zanie · Answer

Zanie · Answer

Hey This is fixed in 2 6 1 which is now available

Zanie · Answer

Thanks again for the report

Josh Paulin · Answer

Yep Just ran the failing test suite against the new version and it s working

Josh Paulin · Answer

My pleasure

Liz McCutcheon · Answer

Thank you for this Was just about to post with the same issue

Zanie · Answer

There are some additional minor fixes for results in the latest release as well slightly smiling face