Suggest configurable timeout for getting operational state data about sysrepo HOT 6 CLOSED

What exactly is the use-case when your operational callbacks are being called? You should always be able to configure the timeout.

from sysrepo.

The function sr_oper_get_subscribe does not have a timeout parameter. Sometimes my callback runs slow, it may use more than 2 seconds.

In src/common.h:

/** default timeout for operational subscription callback (ms) */
#define SR_OPER_CB_TIMEOUT 5000

/** default timeout for RPC/action subscription callback (ms) */
#define SR_RPC_CB_TIMEOUT 2000

I can manually change these two macros to larger values. But I wish this can be configurable.

from sysrepo.

The subscriber, meaning the process calling sr_oper_get_subscribe(), does not get to decide the timeout. It is the callers of the callback that set the timeout. The problem in this case is that there are many ways (operations) when this callback is called so I am asking about the specific use-case so that I can tell you how to increase the timeout.

from sysrepo.

I used netopeer2-server to provide a netconf server. Then I used simple ssh to act as a netconf client. The <get> operation meets timeout error.

from sysrepo.

Use -t <timeout> parameter when starting the server.

from sysrepo.

Thanks a lot! It works.

from sysrepo.