-
Notifications
You must be signed in to change notification settings - Fork 14
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
Error (psycopg2.InterfaceError) connection already closed #425
Comments
never mind, I saw that. please check the edited description, if it's the same you observe over there. |
the one I described how to reproduce starts like this:
|
Corrado, questo succede con 1.0, giusto? ho una patch per 3.1, se vuoi provarla. |
@RoDuth have you ever had this problem? since a specific version? or in some specific setting? or it sounds totally new to you? |
Sorry for the late reply on this (finally looking at all my notifications)... Yes, on osx and ghini-1.0.87 I get this error Must say I have not noticed it before, but then I have not had need to do those steps before.
I'll try to |
👍 |
well bisect didn't get me anywhere, as far back as the feature was introduced gave me errors with a postgres database... changing: Line 805 in 7da3203
to
seems to work though. |
hey, thanks for looking into it. this is a very funny patch. how can it be that after ignoring a session.rollback because of an exception, the session is again usable? I mean I'm not doubting it helps, but I would like to understand what is going on. |
not really sure and no not a fan of try except either. Nor can I see why psycopg2 would report that the socket is shut down. Losing the connection even when the database is on localhost? But then I didn't trace it back further, not a lot of time. If it helps here are the scratchy notes from earlier in the evolution of this feature while trying to find a starting point for a bisect (i got the same error but also a few other random one so gave up.):
|
when you say »evolution of this feature«, what are you referring to? is it the "counting records"? |
no the items on the home screen (total, in use, unused...) but I do think that the counting records may have something to do with it. (running in different threads?) |
definitely running in different threads yes, you don't want to do database stuff on the main (GUI) thread. in popular platforms as Android this was made impossible. |
Ghini 1.0.86 on kubuntu 17.04 LTS 64 bit on PostgresSQL.
Steps to reproduce the behaviour
every second time, you will get this pop-up window:
The error is:
(psycopg2.InterfaceError) connection already closed
This is the trace:
opinions
It seems that the connection closes between one operation and the next, and ghini has difficulties in reopening it.
The text was updated successfully, but these errors were encountered: