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 ran a sample code with two steps in my local using the default stack
On doing zenml pipeline list I can see the pipeline but from zenml up I can't
Is there something which is messing or some mapping is not being done in the dashboard?
Does the command - zenml up --blocking -> Doesn't track the pipeline runs in Windows? Directly running zenml up throws this error
Running the ZenML server locally as a background process is not supported on Windows. Please use the --blocking flag to run the server in blocking mode, or run the server in a Docker container by setting --docker instead.
The text was updated successfully, but these errors were encountered:
@debanshu08 Im not sure this is a dashboard issue - more of an issue that belongs on the main ZenML repository.
You should definitely be doing zenml up --blocking on Windows and the run should be tracked. Sometimes however it does take some time for the pipelines to show up. Can you try doing zenml up --blocking again and verifying?
I ran a sample code with two steps in my local using the default stack
On doing zenml pipeline list I can see the pipeline but from zenml up I can't
Is there something which is messing or some mapping is not being done in the dashboard?
Does the command - zenml up --blocking -> Doesn't track the pipeline runs in Windows? Directly running zenml up throws this error
Running the ZenML server locally as a background process is not supported on Windows. Please use the
--blocking
flag to run the server in blocking mode, or run the server in a Docker container by setting--docker
instead.The text was updated successfully, but these errors were encountered: