Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LabVIEW crash or hang | LabVIEW service didn't implement the required event case #33

Closed
navinsubramani opened this issue Nov 10, 2021 · 1 comment
Labels
type: bug Something isn't working

Comments

@navinsubramani
Copy link
Contributor

navinsubramani commented Nov 10, 2021

When a LabVIEW client API is called to LabVIEW service which doesn't have the required event structure implemented. Then,

  1. The LabVIEW client gets hung and waits infinitely for the LabVIEW service to respond.

So, I notice that's the mistake in the LabVIEW service for missing the implementation of the event. Maybe should it timeout at client's end? Either way, I go to the server and click Stop to stop the service.

  1. LabVIEW service gets hung in the "Stop Server" VI. and client also was hung on the method.

  2. So, I abort client VI and it aborts properly. But the server VI couldn't be aborted.

  3. So, I had to close the project to escape and I get stuck with this.

  4. Kill LabVIEW from task manager.

AB#2973816

@ccifra ccifra added the type: bug Something isn't working label Dec 18, 2021
@jasonmreding
Copy link
Collaborator

I am closing this issue as it appears to no longer be an issue. I'm not sure exactly when it got fixed, but it probably happened over a number of changes as abort procs were added. All of the following now work:

  1. Aborting the client VI now works.
  2. Clicking stop on the server works. The client call will then exit with a grpc error indicating "go away".
  3. Adding a timeout to the client call works. Unfortunately, the client call doesn't return an error, and there is no indicator on the client VI to indicate timeout status. I will create a separate issue for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants