Hey folks, we found a problem on how the SyncAgent...
# flyte-connectors
b
Hey folks, we found a problem on how the SyncAgent grpc client is streaming into the grpc server. I've proposed a fix here https://github.com/flyteorg/flyte/pull/5884 issue: https://github.com/flyteorg/flyte/issues/5885. cc: @damp-lion-88352
f
This is a bad big, but where do we use streaming
b
I found out when trying to implement the SyncAgentService. I'm not sure how you folks implemented it in flytekit, it seems some magic iterating stuff happening there.
we didn;t support streaming agent yet
langchain will be supported in the future
b
We're probably talking about different streamings xD
d
can you say more?>
b
You're sending the ExecuteTaskSyncRequest in two different calls. So basically server side I'm using the onNext (Java implementation) to capture thoses but since the call never closes, it doesn't move over to the onCompleted.
https://docs.python.org/3/library/collections.abc.html#collections.abc.AsyncIterator you're somewhat doing the same with typing, you just handle things straight away once you have both the templates and request https://github.com/flyteorg/flytekit/blob/61b58966188d5d33bc6ab4af209f647de0b51995/flytekit/extend/backend/agent_service.py#L164C17-L164C24. It would be best to have my change so we know when the client stopped sending data and we can process accordingly.
Also @freezing-airport-6809 it's not a critical bug per-se, it's just when implementing things ourselves things aren't properly done. We can work around it but would prefer to do it properly.