arkitekt port build is failing for cuda about arkitekt HOT 3 OPEN

Ah i understand the error. When inspecting the definitions in the container the definition registry is dumped to stdin, which is then parse through the CLI. However if the app.py dumps to stdin anyways it cannot parse the JSON. easiest fix is to prepfix the inspectedted definitions with a magic phrase so that we could detect that in the cli. But open for other ideas!

from arkitekt.

Ok, I have the following thoughts.

1. As a fix, I can also silence the CUDA message which seems to be the problem here but we should look for a more stable solution like you suggest.
2. Would it be possible to use the tasks API to get the task logs. I believe they can be separated by the task ID and don't read from the stdout. -in, -err interface?

from arkitekt.

1. I think we could still rely on stdout and integrat a magic bytstring that would indicate the beginning of the definitions and the end e.g. "MY_MAGIC_ARKITEKT_KEYWORD::{"json": "defintions"}::MY_MAGIC_ARKITEKT_KEYWORK", this would be the easiest workaround for now.

2. I believe this should be the long term goal, especially if we would like to run a container with a specific task once and then shut it down, something like "arkitekt call function_name arg=0 arg1=1". There was a functional prototype for this behaviour once, but I have not investiragted it further.

This is the relevant codepart:
arkitekt/cli/commands/call/local.py, however with reuest_next the api is going to change slightly (i think it might still be worthwhile to test it out though.

from arkitekt.