https://flyte.org
Join Slack
I see above that `flyte-cli parse-proto` would work to print out the raw values of a proto, is there...
# flytekit
s
I see above that 
flyte-cli parse-proto
would work to print out the raw values of a proto, is there a way to get the proto from the flyte metastore directly? I’m trying to add an architecture feature to flytekit, and flyteidl and flyteadmin have both been updated, but the value isn’t making it from my register step all the way to the pod runtime, so I’m trying to debug where the breakdown is happening. I’ve copied the closure field from the tasks table, but the proto parsing isn’t outputting any information for me.
flyte-cli parse-proto -f closure.pb -p flyteidl.core.tasks_pb2.TaskTemplate
is what I’m trying, and I just get 
{}
as the output
t
you’re sure the closure was downloaded correctly?
just cat it…
there should at least be some ascii characters in there, might mess up your terminal though
and which table is this from?
s
I get a 
\x200….
value, I manually copy pasted from the closure field, so that may not be the right way
t
what’s the size of the file?
probably not, this is postgres right?
s
yep
t
i think you can query a binary column to a file..
will probably need to set up a tunnel though since you need the file locally.
what table is this?
oh tasks table
you’re referring to the 
closure
field? this one?
if you are, then after you pull the data, you should use
Copy code
flyteidl.admin.task_pb2.TaskClosure
instead (in your command)
s
t
wouldn’t the UI show that?
s
size is super small.
Copy code
4.0K    task_closure.pb
t
and if not the ui, just hitting the admin api.
s
I was hoping it would, but I’m not seeing it, though the version of flyteconsole we have deployed is using flyteidl 
0.18.9
ah, perfect!
t
try the admin api
s
awesome, I see it there, thanks so much!
164 Views
Open in Slack
PreviousNext
Powered by

Flyte

Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Powered by