Timeouts Is missing

[Clio75]

Several times I have ended up in a waiting forever on Read and Read all.
I like to have a Timeout so the apllication don't lock if something happends and these don't get any data.

[volks73]

There is the libssh2_session_set_timeout function in the libssh2 C library. According to its documentation:

Set the timeout in milliseconds for how long a blocking the libssh2 function calls may wait until they consider the situation an error and return LIBSSH2_ERROR_TIMEOUT.

By default or if you set the timeout to zero, libssh2 has no timeout for blocking functions.

The default appears to have no timeout and the Read and Read All VIs are blocking functions. So, it is at least the correct and expected behavior, just not very useful.

Interestingly, there is the lv_libssh2_session_timeout and lv_libssh2_session_set_timeout functions in the libssh2lv wrapper library for better compatibility with LabVIEW, but there is no Read/Write Timeout VIs for the Session class in this toolkit. I appear to have missed these functions.

I will work on adding these missing VIs to the Session class and then you should be able to set the timeouts and test with the Read and Read All VIs.

[volks73]

I have added the missing VIs, including adding them to the Session sub-palette for toolkit's package. I have attached an updated ZIP/VIP that includes these changes. The changes are available as of 0587482.

field_rnd_services_libssh2-1.0.0.15.zip

[Clio75]

Added Write Timeout

And it has none blocking behavior. Perfect.
Only one comment, In description let user know in with time domain the timeout is. (mS or Seconds). But I guess that most people would try in mS first :)

[volks73]

Only one comment, In description let user know in with time domain the timeout is. (mS or Seconds). But I guess that most people would try in mS first :)

I am in the process of adding descriptions to all controls, indicators, and VIs. It is a work-in-progress (#10 and #11). I will make sure to include units in the descriptions.

Otherwise, I am going to consider this issue resolved.