output
stringlengths 1
18.7k
| input
stringlengths 1
18.7k
|
|---|---|
yeah i will get to this in the next few days
merged this in btw.
didn鈥檛 end up doing the local execute bit, it was too much refactoring
just did the compilation part, should be out in the next release 1.1.0
| Ah gotcha. Thanks for the response! Was just thinking about the release tags but this definitely wasnt pressing :sweat_smile:
|
which version of flytekit was used to register?
and which version is in the container?
this shouldn鈥檛 happen if the versions match
| Another question came up, not sure how much overlap there is with the above, but we鈥檙e having trouble executing tasks that were registered with flytekit remote.
Here鈥檚 a series of steps:
1. Remote register_task (entity is a flyte decorated py function) -> works
2. Remote fetch_task (fetching the above registered task) -> works
3. Remote execute the above task -> Fails both programmatically and from UI with the error
```Pod failed. No message received from kubernetes.
...
Usage: pyflyte-execute [OPTIONS] [RESOLVER_ARGS]...
Try 'pyflyte-execute --help' for help.
Error: no such option: --checkpoint-path```
Does anyone have any insight to this?
cc varsha Parthasarathy, feel free to add if I鈥檝e missed anything
|
Ahh oof. Yea Im planning on using an updated container currently im registering with latest version and the container has 0.26
Same steps, different error: `ValueError: Empty module name`
I鈥檓 not sure what the module name would even be though because I鈥檓 remote registering a task from a script. And I didn鈥檛 think that task code had to live in the container ?
| which version of flytekit was used to register?
and which version is in the container?
this shouldn鈥檛 happen if the versions match
|