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
First, thanks for all the work going into this project. I just updated to 0.27.4 and confirmed the postgres gssenc fix. It was something I found a couple days ago and was digging into.
On to the thread topic...
When I updated from 0.26.1 to 0.27.1, I stopped the service, updated the binary and restarted the service. There were 2 active HTTP sessions at the time (my own and another user). Those 2 sessions are stuck as "active" and won't go away. They can't be closed. There have been multiple service restarts. This is pretty minor, but hopefully it is something easy to take care of. How can I get rid of these rogue active sessions?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Greetings!
First, thanks for all the work going into this project. I just updated to 0.27.4 and confirmed the postgres gssenc fix. It was something I found a couple days ago and was digging into.
On to the thread topic...
When I updated from 0.26.1 to 0.27.1, I stopped the service, updated the binary and restarted the service. There were 2 active HTTP sessions at the time (my own and another user). Those 2 sessions are stuck as "active" and won't go away. They can't be closed. There have been multiple service restarts. This is pretty minor, but hopefully it is something easy to take care of. How can I get rid of these rogue active sessions?
Thanks!
All reactions