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

detect connection close via own handler and auto reconnect #80

Open
vtolstov opened this issue Mar 26, 2019 · 7 comments
Open

detect connection close via own handler and auto reconnect #80

vtolstov opened this issue Mar 26, 2019 · 7 comments
Labels

Comments

@vtolstov
Copy link

i want to have event in my ap when conection to libvirt daemon closed (client disconnected), as i see libvirt sources and this package i can use ConnectRegisterCloseCallback
But how can i work with this function?

@vtolstov
Copy link
Author

python sources have ability to use callback func for this, but in go i don't see such stuff.
https://www.redhat.com/archives/libvir-list/2012-July/msg01675.html

@vtolstov
Copy link
Author

i think that this package have error...
for example calling on libvirt ConnectEventConnectionClosed returns
&errors.errorString{s:"unsupported procedure requested"}

@trapgate
Copy link
Member

trapgate commented Mar 29, 2019

I had a quick look at this. The parser isn't finding the arguments to the ConnectRegisterCloseCallback function, because they don't follow libvirt's usual convention - normally they would be called ConnectRegisterCloseCallbackArgs. So the parser is emitting the function without any arguments at all, which clearly isn't going to work. This will need some looking into.

@vtolstov
Copy link
Author

very bad =(, does this means that also need to create patch to libvirt ?

@vtolstov
Copy link
Author

@trapgate gentle ping..

@trapgate
Copy link
Member

I'll try to look at this later this week.

@vtolstov
Copy link
Author

hi @trapgate do you have time to look at this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants