Get_edge returning wrong edge

[annielytical]

Describe the bug
In a previous iteration of my MST code, I used get_edge to find the edge with the source and destination flipped. Often this returned the right edge (after subtracting 1), but sometimes it did not. In order to get the right edge all the time, I had to change the bfs call from:

(edge_type)search::binary::execute(get_column_indices(), destination, offsets[source], offsets[source + 1] - 1);

to:

(edge_type)search::binary::execute(get_column_indices(), destination, offsets[source], offsets[source + 1]);

or:

(edge_type)search::binary::execute(get_column_indices(), destination, offsets[source], offsets[source] + int(get_number_of_neighbors(source)));

To Reproduce
Call get_edge with various sources and destinations. Call get_source_vertex and get_destination_vertex on the edge obtained and compare.

Expected behavior
get_source_vertex and get_destination_vertex should reproduce the source and destination from the original call to get_edge (but they do not always).

Environment:

• Linux/Windows: Linux - Ubuntu 21.10
• NVIDIA Driver: 470.103.01
• CUDA version: 11.4
• GCC/G++ version: 11.2