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

GetSetExport into GetAdjacentIds gives incorrect results #3119

Open
t92549 opened this issue Nov 24, 2023 · 0 comments
Open

GetSetExport into GetAdjacentIds gives incorrect results #3119

t92549 opened this issue Nov 24, 2023 · 0 comments
Labels
bug Confirmed or suspected bug
Milestone
Backlog

Comments

@t92549
Copy link
Contributor

t92549 commented Nov 24, 2023

Describe the bug
When a GetAdjacentIds with multiple element definitions (for example, two edge groups) is preceded by a GetSetExport to provide its input, it produces incorrect results. This seems to work with just one element definition.

When a ToSet is included immediately after the GetSetExport and before the GetAdjacentIds (for no reason other than to avoid the erroneous behaviour), things seem to work.

Additional context
This might have something to do with generics and the return types of these operations.
@t92549 t92549 added the bug Confirmed or suspected bug label Nov 24, 2023
@cn337131 cn337131 self-assigned this Jan 9, 2024
@GCHQDeveloper314 GCHQDeveloper314 added this to the v2.3.0 milestone Mar 15, 2024
@GCHQDeveloper314 GCHQDeveloper314 modified the milestones: v2.3.0, Backlog Jun 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Confirmed or suspected bug
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
3 participants
@t92549 @GCHQDeveloper314 @cn337131