Re: Fix for RM2811 - Mailing list pgadmin-hackers

From Harshal Dhumal
Subject Re: Fix for RM2811
Date
Msg-id CAFiP3vxQFa7eHfe-r1nwLU76x01ys=txGmTxAGs2aCBeeXP7nw@mail.gmail.com
Whole thread Raw
In response to Re: Fix for RM2811  (Dave Page <dpage@pgadmin.org>)
Responses Re: Fix for RM2811  (Dave Page <dpage@pgadmin.org>)
List pgadmin-hackers
Hi Dave,

Please find updated patch.

-- 
Harshal Dhumal
Sr. Software Engineer

EnterpriseDB India: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

On Mon, Nov 27, 2017 at 5:28 PM, Dave Page <dpage@pgadmin.org> wrote:
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?

Fixed.
 
Thanks. 

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Attachment

pgadmin-hackers by date:

Previous
From: pgAdmin 4 Jenkins
Date:
Subject: Jenkins build is back to normal : pgadmin4-master-python27 #397
Next
From: Dave Page
Date:
Subject: pgAdmin 4 commit: Display process output as it happens. Fixes #2811