https://flyte.org logo
Join Slack
Powered by
I feel like I'm missing something really stupid wi...
# flyte-support
c
I feel like I'm missing something really stupid with the run command. I posted an image of the config. It is going to the right URL. The job gets spawned and will start to run, but the URL in the 
pyflyte run
response is wrong. Could this be a bug?
t
actually in the latest versions we’ve moved all the sandbox web ports to 30080.
c
We're note using the sandbox.
t
oic
c
We're trying to test a more production deployment. @hundreds-toothbrush-11241
t
that you’ve port-forwarded?
c
essentially.
we stand up the services in a local kubernetes cluster using k3s
and I can get to the UI
And the job posts and starts. It just looks like the url in the print is off,
t
perhaps the config is not getting used…
h
sorry for clarity we're not port-forwarding as we're using the nodeport 30081 from the admin -- my understanding is the config above should also print 30081 in the output as it's being told that's where the console is?
t
it very explicitly looks at that value.
can you re-try with 
pyflyte -c <config file> ...
c
same
message has been deleted
message has been deleted
t
which flytekit version?
h
1.1.1
t
could you bump to 1.3.1?
h
ys
ya one sec
sorry for the wait -- mini dependency hell bumping there (flytekit -> flyteidl -> grpcio -> google stuffs etc) that bump fixed it
thanks! 😄
t
yup sure
c
🦜
excellent 1
t
yeah the recent protobuf break is pretty annoying.
going forward we are planning on maintaining both 1.2.x and 1.3+ with the former being protobuf 3 and latter versions protobuf 4
sorry forgot to mention that.
may have been easier to just go to 1.2.x 😬
h
np -- ended up working so no foul there 😄
150 Views
Open in Slack
PreviousNext
Powered by