Steffen Brüheim

Maybe you didn't flush your buffered Writer, if you're using one?

I don't think you have a problem with the contexts. If the context is cancelled or the deadline exceeded the error would be: ``` rows Close failed: context deadline exceeded...

No I also get the error. Its probably not good, that the connect-context is used as session context. https://github.com/sijms/go-ora/blob/master/v2/network/session.go#L272 It should just be used when dialing, i think

I'm a bit out of my depth here. I think the DB-connection (Session) shouldn't have a context at all. The lifetime of a connection is handled by the connection pool...

The issue isn't fixed. The code from https://github.com/sijms/go-ora/issues/213#issuecomment-1155287245 still errors out the same way with `github.com/sijms/go-ora/v2 v2.5.4-0.20220914231906-d2e384b0dd09`.

Maybe it is possible to configure this for the [Websuggest Package](https://keypirinha.com/packages/websuggest.html) If not there is always the option to develop is new package along the lines of the websuggest package...

[uwp.zip](https://github.com/Keypirinha/Keypirinha/files/1527391/uwp.zip) i tried something similiar with the powershell command `Get-AppxPackage` but its not quite working yet. I haven't figured out how to call [SHLoadIndirectString](https://msdn.microsoft.com/de-de/library/windows/desktop/bb759919.aspx) correctly to get the localized name...

comtypes is already in the python distribution of keypirinha. You can just import it in your code ;)

Since EasySearch is a third party plugin, you could start by opening an issue in the right repository :) https://github.com/bantya/Keypirinha-EasySearch

You could just define your own ItemCategories `running_service` and `stopped_service` and register different sets of actions to these categories. As I already wrote in the chatroom: The plugin developer decides...