Skip to content

Conversation

@PProfizi
Copy link
Contributor

@PProfizi PProfizi commented Sep 10, 2024

The StreamsContainer cannot currently be instantiated or manipulated for a remote server via gRPC.

It looks like it is by design but I do not see why that would be.

This prevents from running a script working when InProcess, on a gRPC type server, if it contains any StreamsContainer instance.

We do for example have operators which take a StreamsContainer as input or provide one as output. Those can't be fed back into other operators.

@PProfizi PProfizi added the bug Something isn't working label Sep 10, 2024
@PProfizi PProfizi added this to the v0.13.1 milestone Sep 10, 2024
@PProfizi PProfizi requested a review from oparreno September 10, 2024 13:06
@PProfizi PProfizi self-assigned this Sep 10, 2024
Signed-off-by: paul.profizi <[email protected]>
Signed-off-by: paul.profizi <[email protected]>
Signed-off-by: paul.profizi <[email protected]>
@PProfizi PProfizi changed the title Fix connecting StreamsContainer as input or output of Operator or Workflow Fix connecting StreamsContainer as input or output of Operator or Workflow when InProcess Sep 12, 2024
@PProfizi PProfizi merged commit 1ef61ed into master Sep 12, 2024
@PProfizi PProfizi deleted the fix/connect_streams_container_as_input branch September 12, 2024 14:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants