You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently working on #2369 and in turn adding a new serializer effectively breaks its use with Core's server due to the version of prefect that the server has being behind (using the latest build).
This means that once #2369 (or any future serializers) are merged then when running the Core server images you would need to specify a --version master in order for it to work. I'm opening this issue as a discussion point on if this is the functionality we want or if there is a better way.
The text was updated successfully, but these errors were encountered:
Good call I like that approach and it should cover almost all cases when using the master branch. The main issue though will be for local development when working with the serializer changes before merge. In those cases I will run the services directly
I am currently working on #2369 and in turn adding a new serializer effectively breaks its use with Core's server due to the version of prefect that the server has being behind (using the
latest
build).This means that once #2369 (or any future serializers) are merged then when running the Core server images you would need to specify a
--version master
in order for it to work. I'm opening this issue as a discussion point on if this is the functionality we want or if there is a better way.The text was updated successfully, but these errors were encountered: