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 1ezKun-0006cg-8G for pgadmin-hackers@arkaria.postgresql.org; Fri, 23 Mar 2018 11:31:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ezKum-0001Ct-8w for pgadmin-hackers@arkaria.postgresql.org; Fri, 23 Mar 2018 11:31:20 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ezKrO-0006CM-7d for pgadmin-hackers@lists.postgresql.org; Fri, 23 Mar 2018 11:27:50 +0000 Received: from mail-io0-x22c.google.com ([2607:f8b0:4001:c06::22c]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ezKrK-0004mz-1f for pgadmin-hackers@postgresql.org; Fri, 23 Mar 2018 11:27:49 +0000 Received: by mail-io0-x22c.google.com with SMTP id q84so9289699iod.10 for ; Fri, 23 Mar 2018 04:27:45 -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=Pl7a5XPNvbKI5pAIxzpZfwINKyQZDC0OO4bXwOUgL6M=; b=p551wjUZkSwJkDXm7Q8kbMe0p8y9VIPB+J44e2Ei/ENnWFhmowqnXqLCQSMD6g1qtV iK8MYaKhmvIxNPA2AnjDpOOADGXpeBXdmK6rO26WVELgTTTiGbv9iOy/RtGxnPj1eqqZ tYdKKv/Te2S50e6FJK3x04bLG9htoXozC6NFsd2fZjxLV5rvz5hKuDSiOscbBOPy4Lip 1X3q9XoiNFSeq6uhoN/34A2gcIHqhG6Pjyx8/X/CwtCON5pVpjLr2h+OjmQuOILJBqFK 8PcnMz1UPQ2YOEbL9Mrhl4bPtsUeLCFsoxyGn3tHyQct5W6e0Y9gPKFA2obYKfQmAqnQ RppA== 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=Pl7a5XPNvbKI5pAIxzpZfwINKyQZDC0OO4bXwOUgL6M=; b=XsFSxt37JXQBF38AmqoVib02Yb1vMDfzg+IyBpaHeb+kEr/P7TegnftJ/wk5fU1p6K TTaZeDTo8haq2DIjxlsuFBO5cQC2UvoF47d0dZMfnKuHEa9C0I5KKXHxpSXFYXYFjwPZ ut/hVmPFd2OfZdX/J4k1T4yZRnQtSCf660DY46T0iF8DZaLh9u55UlV0gStjPaLbkgG5 AzMQ39P3vU7dJm9ZSf7b5DioCOv6xuZa0l1B8xS2JhGxoZ54NrHSbLFpJhMAybMxLER9 mSrxp9WkEAA2S0h8cZh5VXXD3/OouBlU/dQsPR5X26CDJTN6i2xIzHZZXRk7hMW21/Xg r4fA== X-Gm-Message-State: AElRT7FN6cI7v4ayGwgTc44WM88/UDdxMWzvvHemoe9zThSuvvYDpHhB sz+meLUr7PdAnYzcQw9KCFvx5OXod3xjH0fxCbqwJg== X-Google-Smtp-Source: AG47ELsBv4KOsFRdYB2Wz8Zr5+AQFc3PGOyDt9n7cLYtDImOCo4xSd91aMN9al+7E8NLhPcZx/K349HkpiuEvhnONW4= X-Received: by 10.107.40.147 with SMTP id o141mr13192665ioo.72.1521804463723; Fri, 23 Mar 2018 04:27:43 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.141.195 with HTTP; Fri, 23 Mar 2018 04:27:23 -0700 (PDT) In-Reply-To: References: From: Ashesh Vashi Date: Fri, 23 Mar 2018 16:57:23 +0530 Message-ID: Subject: Re: v3.0 release on hold To: Dave Page Cc: Khushboo Vashi , pgadmin-hackers , Akshay Joshi , Murtuza Zabuawala , Syed Fahar Abbas , =?UTF-8?B?RGV2cmltIEfDnE5Ew5xa?= Content-Type: multipart/alternative; boundary="001a1141d8187a708e056812b60a" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --001a1141d8187a708e056812b60a 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... > Should we have a job to purge them on a timely basis? (Of course - configurable) -- Thanks, Ashesh > > -- > Dave Page > Blog: http://pgsnake.blogspot.com > Twitter: @pgsnake > > EnterpriseDB UK: http://www.enterprisedb.com > The Enterprise PostgreSQL Company > --001a1141d8187a708e056812b60a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On F= ri, Mar 23, 2018 at 3:21 PM, Dave Page <dpage@pgadmin.org> w= rote:


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


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


On Thu, Mar 22, 20= 18 at 9:58 AM, Khushboo Vashi <khushboo.vashi@enterprisedb.c= om> wrote:


O= n Thu, Mar 22, 2018 at 3:20 PM, Dave Page <dpage@pgadmin.org> 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 <dpage@pgadmin.org> 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.=C2= =A0
Akshay, can you look at 2 please?
Fahar is already = looking at 3.
Khushboo, can you look at 4 please?

<= /div>
Thanks all.

1) There is no longer a syst= em 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 repl= acement that the RPM can depend on, or better yet, support whatever it is G= nome expect such apps to use these days.

2) Starti= ng 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 star= t the app with a command like: "/Applications/pgAdmin\ 4.app/Contents/= MacOS/pgAdmin4". It doesn't work if you double-click the appb= undle or use a command like "open /Applications/pgAdmin\ 4.app"

3) Fahar saw a crash on Windows 7. I couldn't r= eproduce this on my copy, but apparently his is a fresh installation.
=

4) On my Windows 7 machine, after running a backup I ge= t no status window, and see the following in the logs:

<= /div>

We have tried to r= eproduce this issue on Windows 7 and Windows 8, but couldn't reproduce = it, It is working fine on both the environments.
Can you please p= rovide the options which you have selected while taking a backup?

They were all the def= ault options - I just selected a database, right-clicked to select backup, = and entered a filename.
=C2=A0<= /div>
With the defaul= t options, it is working fine.=C2=A0

Can you see any=C2=A0 way in which the exception b= elow could conceivably happen? Perhaps if run on a system that has process = logs from an older version of pgAdmin?
=C2=A0
=
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 fro= m over a year ago. Removing them, and truncating the process table in the s= qlite DB seems to have resolved the issue.

So, I t= hink that's something to watch for if people have backup issues and hav= e used older versions of pgAdmin...
Should we have a job to purge them on a timely basis? (Of course - conf= igurable)

-- Thanks, Ashesh=C2=A0

--
Dave Page
Blog: http://pgsnake.blogspot.comTwitter: @pgsnake

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

--001a1141d8187a708e056812b60a--