Re: Fix for RM2811 - Mailing list pgadmin-hackers

From Dave Page
Subject Re: Fix for RM2811
Date
Msg-id CA+OCxoxORVgzgvSLosDPso2xOQGkm8GfEnUkjs0ea8Hv5JgA0Q@mail.gmail.com
Whole thread Raw
In response to Fix for RM2811  (Harshal Dhumal <harshal.dhumal@enterprisedb.com>)
Responses Re: Fix for RM2811  (Harshal Dhumal <harshal.dhumal@enterprisedb.com>)
List pgadmin-hackers
Hi On Mon, Nov 27, 2017 at 11:23 AM, Harshal Dhumal < harshal.dhumal@enterprisedb.com> wrote: > Hi, > > Please find attached patch to fix RM2811 > > Issue was caused due to assumption made when current position in log file > while reading it reaches to last line then > we were assuming process is finished. However this is not the case. > Background process may be busy performing > some other task and logs might not be logged to file immediately. So we > should also check process exit code along > with above condition. > > Apart from above this patch also includes minor fix related to status text > colour. > Seems to work nicely, except that the text scrolls out of view almost immediately. Can you fix it to jump to the end of the text when more is appended please? Thanks. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company

pgadmin-hackers by date:

Previous
From: Dave Page
Date:
Subject: Re: [pgAdmin4][Patch]: To decode database errors properly
Next
From: Dave Page
Date:
Subject: pgAdmin 4 commit: Use sufficiently long random strings in testobjects