millions-table-8574
09/22/2023, 4:09 AMfreezing-airport-6809
freezing-airport-6809
freezing-airport-6809
freezing-airport-6809
millions-table-8574
09/25/2023, 3:53 AMmillions-table-8574
10/04/2023, 6:08 AM"078b0145-016a-44d8-bac0-fffa2e722f9c"
and flyte complained:
_InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
status = StatusCode.INVALID_ARGUMENT
details = "invalid name format: 078b0145-016a-44d8-bac0-fffa2e722f9c"
debug_error_string = "UNKNOWN:Error received from peer {created_time:"2023-10-04T14:08:18.565966+08:00",
grpc_status:3, grpc_message:"invalid name format: 078b0145-016a-44d8-bac0-fffa2e722f9c"}
don’t see any specific constraints in flytekit other than this:
# remote.py
execution_name = execution_name or "f" + uuid.uuid4().hex[:19]
freezing-airport-6809
millions-table-8574
10/05/2023, 5:55 AMflytekit==1.9.1
and errors still look the same. is the name constraint defined on the Go-side, or inside flytekit? can’t find any refs to it in flytekit.millions-table-8574
10/05/2023, 5:55 AMfreezing-airport-6809
freezing-airport-6809
details: invalid name format: 078b0145-016a-44d8-bac0-fffa2e722f9c
freezing-airport-6809
^[a-z][a-z\-0-9]*$
freezing-airport-6809
freezing-airport-6809
0
a digit, this is not allowed. it has to have a alphabet
. we should explain this clearly, hard to dofreezing-airport-6809
millions-table-8574
10/05/2023, 7:22 AMfreezing-airport-6809