Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix not setting semantics in SelectResultInfo #2578

Merged
merged 1 commit into from
Jul 4, 2022
Merged

fix not setting semantics in SelectResultInfo #2578

merged 1 commit into from
Jul 4, 2022

Conversation

awildturtok
Copy link
Collaborator

No description provided.

@awildturtok awildturtok requested a review from thoniTUB July 4, 2022 11:07
@awildturtok awildturtok merged commit 89ca817 into release Jul 4, 2022
@delete-merged-branch delete-merged-branch bot deleted the fix/semantics-not-set branch July 4, 2022 12:38
thoniTUB
thoniTUB reviewed Jul 4, 2022
View reviewed changes
Copy link
Collaborator

@thoniTUB thoniTUB left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh, hatte ich das nur auf develop gefixt?

@awildturtok
Copy link
Collaborator Author

Das war was anderes, hier hatte SelectResultInfo in der call chain noch Probleme, aber vlt ist es auch nur auf develop.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@thoniTUB thoniTUB thoniTUB left review comments

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@awildturtok @thoniTUB