Unexpected behavior when using relative xpath for children of list

[p-fruck]

Hey there,

I'm rather new to libyang and it might be that I have not fully understood xPath as I have only worked with the Python implementation previosuly, but to me the following behavior of libyang seems unexpected:

I am currently trying to parse a list of ietf-interfaces. The following excerpt demonstrates how I would expect to use a relative xpath on each of the interfaces:

struct ly_set *set1 = nullptr;
lyd_find_xpath(child, "/ietf-interfaces:interfaces/interface", &set1);
for (uint32_t i = 0; i < set1->count; i++) {
    struct ly_set *set2 = NULL;
    lyd_find_xpath(set1->dnodes[i], "//name", &set2);
    fprintf(stdout, "Interface %d, count %d\n", i, set2->count);
    for (uint32_t i = 0; i < set2->count; i++) {
        fprintf(stdout, "  name: %s", lyd_get_value(set2->dnodes[i]));
    }
    ly_set_free(set2, NULL);
}
ly_set_free(set1, NULL);

I would expect this code to loop over all <interface> elements inside the <interfaces> parent and print the <name> child once for each interface. Instead, for each interface all of my interface names are printed. Am I missing something here? Shouldn't set->dnodes[i] give me a single interface node? Is this specific to the XPath 1.0 implementation of libyang?

Maybe worth noting I am using the latest libyang from devel branch

I highly appreciate any help/feedback on this!

[p-fruck]

Ok I didn't realize a relative xpath would be specified using name instead of //name, which works as intended :)