feat(#454): support multiple outputs#523
Merged
kitsudaiki merged 2 commits intodevelopfrom Mar 16, 2025
Merged
Conversation
Result-datasets were changed. When making a request-task against a cluster with multiple outputs, each output-hexagon generates its own dataset. Because of this, the uuid of the request-task is no longer the uuid of the resulting dataset, because there can be multiple datasets as result. So the datasets now have a 'task_uuid'-field, which contains the uuid of the request-task.
kitsudaiki
force-pushed
the
feat/update-for-multiple-inputs-and-outputs
branch
from
4bc1a6a to
3dacd00
Compare
The section of possible next hexagons, while initializing the cluster, was not correct, when there were multiple possible next hexagon. This was fixed by a workaround to make all next statistically equal.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request
Description
Result-datasets were changed. When making a request-task against a cluster with multiple outputs, each output-hexagon generates its own dataset. Because of this, the uuid of the request-task is no longer the uuid of the resulting dataset, because there can be multiple datasets as result. So the datasets now have a 'task_uuid'-field, which contains the uuid of the request-task.
Related Issues
How it was tested?