sr_get_node fails when pointing to a leaf-list path about sysrepo HOT 6 CLOSED

I see, sr_get_node can only be used for leafs, is that it ?

If that so, The fact that it returns sr_data_t instead of sr_val_t might seen a bit misleading.
I was also influenced by this part of the doc

  *Compared to ::sr_get_data() or ::sr_get_subtree() this function is a bit more efficient because it returns*

Which made me believe that sr_get_node was equivalent to sr_get_data. But perhaps, it's more similar to sr_get_item ?!?!

thank you for the clarification !

from sysrepo.

Print the actual error message to learn the reason for the error.

from sysrepo.

I updated the original description to make it clear that it refers to SR_ERR_INVAL_ARG error code.
Is that what you meant ?

from sysrepo.

No, I meant an actual error message. Unless you passed NULL as one of the parameters, there is also a detailed error, which is printed if you enable it using sr_log_stderr() or you can retrieve it in a structure from the session using sr_session_get_error().

from sysrepo.

I am running with

sr_log_stderr(SR_LL_DBG);

the piece of code is only this, that can be easily added to any existing examples

    printf("sr_get_node ...\n");
    rc = sr_get_node(session, xpath, 0, &node_data);
    if (rc != SR_ERR_OK)
    {
        printf("sr_get_node (running) error: %d - %s\n", rc, sr_strerror(rc));
    }
    printf("sr_get_node (running) done\n");

the session datastore doesnt matter. i tried several and the result is the same

and the printed result is :

sr_get_node ...
[ERR] More nodes match "/test_examples:cont/l".
sr_get_node (running) error: 1 - Invalid argument
sr_get_node (running) done

please, let me know if you need further info. If you just replace the function sr_get_node by sr_get_data, the same leaf-list path works. That's why i suspect if might be something particular with sr_get_node.

from sysrepo.

I am not sure what is unclear about this then. There is the error:

[ERR] More nodes match "/test_examples:cont/l".

and there is even a clear documentation

from sysrepo.