Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ezJVk-0000tC-EE for pgadmin-hackers@arkaria.postgresql.org; Fri, 23 Mar 2018 10:01:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ezJVj-00065g-BS for pgadmin-hackers@arkaria.postgresql.org; Fri, 23 Mar 2018 10:01:23 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ezJSW-0003m4-Ox for pgadmin-hackers@lists.postgresql.org; Fri, 23 Mar 2018 09:58:05 +0000 Received: from mail-ot0-x231.google.com ([2607:f8b0:4003:c0f::231]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ezJSS-0007U2-QK for pgadmin-hackers@postgresql.org; Fri, 23 Mar 2018 09:58:03 +0000 Received: by mail-ot0-x231.google.com with SMTP id 23-v6so2105013otj.0 for ; Fri, 23 Mar 2018 02:58:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=8z01Pq5K0ft3GrI/SGB4MYSDJ4ffsuEK5DaL/YpQZwc=; b=ifBOgYusKyfmE3X1bsrm77j6QjUnHOZPhaeIMTrtlIXQJTnWng20k27GNVUDRsTP8l 3KB4+NwheX0wxXjJKPp5W/tau/q4UPOH+BYdie33NxH3Yohkhzzv3eNYJc8sbZPGYzEf 45v8Sv6n1eyLdYHdAq7sIetNa80tor7LqXTxJp/nmBtWdr1xAGIBQx/faQhlNURQuIey c62d+souOSQowuqKnsvk8wEimV3YHzdquAm6pTfdxrQDbzJhJfkqxIWRO8DXBAEC8pgG zvyPZ/3Ri+3kXHj+HSq6QtmhlFBUbEY3TX8LOft9HtNDYK994CHmyxsG9GLGR/obfxPb iJnA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=8z01Pq5K0ft3GrI/SGB4MYSDJ4ffsuEK5DaL/YpQZwc=; b=UZYjv66uKTOkRPikMZpn7DY3dic+QkKpZP6T7+d7CbpL85eDbYrW4Z3s06YskP5Irg QfT1uowKnyVQMn8MI0g/3QxGduipxNol3WLvbPDaYcd84BFOW4zbji8nkJagWX4ZaQFS wgjBsEgCvDzD4YAl5oEvtlp4PWX5t9rh1GLAxXSKld+4u4QjLF+TmRnHUcgfnljzzraY UDxn+4LJmUnT+qCAfzzi1bWkVGb50Lrvfcu+R4IBTpg0or1S/FILsaxDuPnzbn8z3dUG 5L3ecnbJHyIUHRjiiZV11Umhmz7XLhqD5+PnVBiEX7hfoyc7Eqo1M1/jRCcpwrfVenaL U0yQ== X-Gm-Message-State: AElRT7E3vhHhky50ol/okRY0OovLbt/wAeR7ev/CsF/0Cn0RWW/vHCb5 uib8xXtj0MNQ6+UwfOJT8xF6pRf68O5Kuiqlqtet1g== X-Google-Smtp-Source: AG47ELtRMxEsE08VeJ5uocgGNDmuntJ+3RsZvIhXOUxcMoBLWcVCsn4TLTQ+WAr3PeNmqlb807Y7rBqh+ob/hj01LaM= X-Received: by 2002:a9d:25cf:: with SMTP id q73-v6mr9533259ota.296.1521799079858; Fri, 23 Mar 2018 02:57:59 -0700 (PDT) MIME-Version: 1.0 Received: by 10.74.138.251 with HTTP; Fri, 23 Mar 2018 02:57:59 -0700 (PDT) In-Reply-To: References: From: Khushboo Vashi Date: Fri, 23 Mar 2018 15:27:59 +0530 Message-ID: Subject: Re: v3.0 release on hold To: Dave Page Cc: pgadmin-hackers , Akshay Joshi , Murtuza Zabuawala , Syed Fahar Abbas , =?UTF-8?B?RGV2cmltIEfDnE5Ew5xa?= Content-Type: multipart/alternative; boundary="000000000000932ab205681175ea" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --000000000000932ab205681175ea Content-Type: text/plain; charset="UTF-8" On Fri, Mar 23, 2018 at 3:21 PM, Dave Page wrote: > > > On Fri, Mar 23, 2018 at 5:43 AM, Khushboo Vashi < > khushboo.vashi@enterprisedb.com> wrote: > >> >> >> On Thu, Mar 22, 2018 at 3:42 PM, Dave Page wrote: >> >>> >>> >>> On Thu, Mar 22, 2018 at 9:58 AM, Khushboo Vashi < >>> khushboo.vashi@enterprisedb.com> wrote: >>> >>>> >>>> >>>> On Thu, Mar 22, 2018 at 3:20 PM, Dave Page wrote: >>>> >>>>> Hi >>>>> >>>>> On Thu, Mar 22, 2018 at 9:25 AM, Khushboo Vashi < >>>>> khushboo.vashi@enterprisedb.com> wrote: >>>>> >>>>>> Hi Dave, >>>>>> >>>>>> On Wed, Mar 21, 2018 at 9:05 PM, Dave Page wrote: >>>>>> >>>>>>> We've run into a number of unexpected issues with the v3.0 release >>>>>>> that I think we need to resolve before moving forwards. For the time being, >>>>>>> only patches critical to fix these issues should be committed. >>>>>>> >>>>>>> I'll try to look at 1, though I do have another deadline I need to >>>>>>> meet. >>>>>>> Akshay, can you look at 2 please? >>>>>>> Fahar is already looking at 3. >>>>>>> Khushboo, can you look at 4 please? >>>>>>> >>>>>>> Thanks all. >>>>>>> >>>>>>> 1) There is no longer a system tray in Gnome 3.26 and later, and >>>>>>> thus the runtime won't initialise in Fedora 27 and later. We need an >>>>>>> alternative for this, either a tray replacement that the RPM can depend on, >>>>>>> or better yet, support whatever it is Gnome expect such apps to use these >>>>>>> days. >>>>>>> >>>>>>> 2) Starting a second instance of the app bundle on Mac doesn't >>>>>>> always open a new pgAdmin window as it should. It works fine in the >>>>>>> debugger, or if you start the app with a command like: >>>>>>> "/Applications/pgAdmin\ 4.app/Contents/MacOS/pgAdmin4". It doesn't >>>>>>> work if you double-click the appbundle or use a command like "open >>>>>>> /Applications/pgAdmin\ 4.app" >>>>>>> >>>>>>> 3) Fahar saw a crash on Windows 7. I couldn't reproduce this on my >>>>>>> copy, but apparently his is a fresh installation. >>>>>>> >>>>>>> 4) On my Windows 7 machine, after running a backup I get no status >>>>>>> window, and see the following in the logs: >>>>>>> >>>>>>> >>>>>> We have tried to reproduce this issue on Windows 7 and Windows 8, but >>>>>> couldn't reproduce it, It is working fine on both the environments. >>>>>> Can you please provide the options which you have selected while >>>>>> taking a backup? >>>>>> >>>>> >>>>> They were all the default options - I just selected a database, >>>>> right-clicked to select backup, and entered a filename. >>>>> >>>>> >>>> With the default options, it is working fine. >>>> >>> >>> Can you see any way in which the exception below could conceivably >>> happen? Perhaps if run on a system that has process logs from an older >>> version of pgAdmin? >>> >>> >> Not sure as this issue was fixed by Ashesh 1 year back as per git logs. >> > > Well the VM I was testing in did have some process logs from over a year > ago. Removing them, and truncating the process table in the sqlite DB seems > to have resolved the issue. > > So, I think that's something to watch for if people have backup issues and > have used older versions of pgAdmin... > > yes, we should keep in mind this. > -- > Dave Page > Blog: http://pgsnake.blogspot.com > Twitter: @pgsnake > > EnterpriseDB UK: http://www.enterprisedb.com > The Enterprise PostgreSQL Company > --000000000000932ab205681175ea Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Fri, Mar 23, 2018 at 3:21 PM, Dave Page <dpage@pgadmin.org><= /span> wrote:


On Fri= , Mar 23, 2018 at 5:43 AM, Khushboo Vashi <khushboo.vashi@en= terprisedb.com> wrote:


On Thu, Mar 22, 2018 at 3:42 PM, Dave Page <= ;dpage@pgadmin.org> wrote:

On Thu, Ma= r 22, 2018 at 9:58 AM, Khushboo Vashi <khushboo.vashi@enterp= risedb.com> wrote:


On Thu, Mar 22, 2018 at 3:20 PM, Dave Page <dpage@pgadmin.org&g= t; wrote:
Hi
<= div class=3D"gmail_extra">
On Thu, Mar = 22, 2018 at 9:25 AM, Khushboo Vashi <khushboo.vashi@enterpri= sedb.com> wrote:
Hi Dave,<= /div>

= On Wed, Mar 21, 2018 at 9:05 PM, Dave Page <dpage@pgadmin.org> wrote:
W= e've run into a number of unexpected issues with the v3.0 release that = I think we need to resolve before moving forwards. For the time being, only= patches critical to fix these issues should be committed.

I'll try to look at 1, though I do have another deadline I need to m= eet.=C2=A0
Akshay, can you look at 2 please?
Fahar is a= lready looking at 3.
Khushboo, can you look at 4 please?

Thanks all.

1) There is no longer= a system tray in Gnome 3.26 and later, and thus the runtime won't init= ialise in Fedora 27 and later. We need an alternative for this, either a tr= ay replacement that the RPM can depend on, or better yet, support whatever = it is Gnome expect such apps to use these days.

2)= Starting a second instance of the app bundle on Mac doesn't always ope= n a new pgAdmin window as it should. It works fine in the debugger, or if y= ou start the app with a command like: "/Applications/pgAdmin\ 4.app/Co= ntents/MacOS/pgAdmin4". It doesn't work if you double-click t= he appbundle or use a command like "open /Applications/pgAdmin\ 4.app&= quot;

3) Fahar saw a crash on Windows 7. I couldn&= #39;t reproduce this on my copy, but apparently his is a fresh installation= .

4) On my Windows 7 machine, after running a back= up I get no status window, and see the following in the logs:


We have tri= ed to reproduce this issue on Windows 7 and Windows 8, but couldn't rep= roduce it, It is working fine on both the environments.
Can you p= lease provide the options which you have selected while taking a backup?

They were all = the default options - I just selected a database, right-clicked to select b= ackup, and entered a filename.
= =C2=A0
With the= default options, it is working fine.=C2=A0

Can you see any=C2=A0 way in which the exce= ption below could conceivably happen? Perhaps if run on a system that has p= rocess logs from an older version of pgAdmin?
=C2=A0
Not sure as this issue was fixed by A= shesh 1 year back as per git logs.

Well the VM I was testing in did have some process l= ogs from over a year ago. Removing them, and truncating the process table i= n the sqlite DB seems to have resolved the issue.

= So, I think that's something to watch for if people have backup issues = and have used older versions of pgAdmin...

yes, we should keep in mind= this.=C2=A0
--
Dave Page<= br>Blog: http://p= gsnake.blogspot.com
Twitter: @pgsnake

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

--000000000000932ab205681175ea--