GRAPH fails if accessing a result of a subgraph that's a sibling of the body graph

Description

Some refactoring to fix a separate bug (https://hpccsystems.atlassian.net/browse/HPCC-20864) introduced this issue.

The symptom of this bug is a crash with a stack like:

The cause/regression is that the results container was being created in the context of the wrong graph, and as a consequence, when the slaves requested the global result and sent a message to the master to do so, it sent the wrong graphId. This then failed to find any results (localResults==null) and crashed.

Conclusion

None

Activity

Show:
Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Components

Assignee

Reporter

Priority

Compatibility

Point

Fix versions

Pull Request URL

Created January 21, 2020 at 12:33 PM
Updated January 21, 2020 at 1:36 PM
Resolved January 21, 2020 at 1:36 PM