Opal-T fails to write LossDataSink if executed in parallel
The order of switching of the elements is different on node 0 than on the other nodes.
Code indexing in gitaly is broken and leads to code not being visible to the user. We work on the issue with highest priority.
The order of switching of the elements is different on node 0 than on the other nodes.
changed milestone to %OPAL 2.4.0
mentioned in merge request !412 (merged)
created merge request !412 (merged) to address this issue
This has already been done for branch 2.4, but not in an optimal way, see discussion in !412 (merged).
changed milestone to %OPAL 2021.1
changed weight to 10
changed weight to 9
changed weight to 10
585-opal-t-fails-to-write-lossdatasink-if-executed-in-parallel-2
to address this issue created branch 585-opal-t-fails-to-write-lossdatasink-if-executed-in-parallel-2
to address this issue
mentioned in merge request !439 (merged)
closed via merge request !439 (merged)