You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Communication systems are prompt to sporadic errors due to multiple different causes. For example, we have observed that the UDP VIs may throw different errors when the network traffic is very high, or consider the simple scenario of a temporary cable disconnection. As it is, the DSF engine will shut-down a thread entirely with the presence of any errors. This requires house-keeping to re-deploy or entirely reboot the system even for errors that could be safely ignored.
Describe the solution you'd like
Allow configuration of the framework (maybe per thread) on how to handle specific errors. As a minimum, an alternative "Ignore" action could be added instead of the default behavior of shutting-down. From there, expand to have a configurable number of retries before shutting down and allow re-launching threads.
Describe alternatives you've considered
For now users have to patch the framework or the specific plugin to handle errors as needed.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Communication systems are prompt to sporadic errors due to multiple different causes. For example, we have observed that the UDP VIs may throw different errors when the network traffic is very high, or consider the simple scenario of a temporary cable disconnection. As it is, the DSF engine will shut-down a thread entirely with the presence of any errors. This requires house-keeping to re-deploy or entirely reboot the system even for errors that could be safely ignored.
Describe the solution you'd like
Allow configuration of the framework (maybe per thread) on how to handle specific errors. As a minimum, an alternative "Ignore" action could be added instead of the default behavior of shutting-down. From there, expand to have a configurable number of retries before shutting down and allow re-launching threads.
Describe alternatives you've considered
For now users have to patch the framework or the specific plugin to handle errors as needed.
The text was updated successfully, but these errors were encountered: