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 1ezJMj-0000EF-FM for pgadmin-hackers@arkaria.postgresql.org; Fri, 23 Mar 2018 09:52:05 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ezJMi-0000jk-2b for pgadmin-hackers@arkaria.postgresql.org; Fri, 23 Mar 2018 09:52:04 +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 1ezJMh-0000ja-I2 for pgadmin-hackers@lists.postgresql.org; Fri, 23 Mar 2018 09:52:03 +0000 Received: from mail-wm0-x234.google.com ([2a00:1450:400c:c09::234]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ezJMd-0007Mr-Ln for pgadmin-hackers@postgresql.org; Fri, 23 Mar 2018 09:52:02 +0000 Received: by mail-wm0-x234.google.com with SMTP id e194so2400329wmd.3 for ; Fri, 23 Mar 2018 02:51:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=QEGu0KSsGebJh8viD/HuK7M0sftINnHyS29e9IGaakY=; b=xSe0LnAUeqlA+oI6T1+jSoe05ARb4uAeSMCPCWW8ZfxJDqU7+BrvFivMkjZ3M4eRI6 aqMNRquke6EGt0N3s00yBg7dZg4z6LtC7mvp097HDNu7zzomuVTpUw8K6n6Rh/TPZQXR cj3C9OSMs+/cUycUqwtKZgRxWV5A/fB5IRKPnManx7nZtiEGlHoioiw/KXeCrvyUp9v2 dkVzVY1tWkvJEU/2WTYrgT1H+krJhKuZQcefWA92nqYFyQmsWxQGL1JJZqLufZlbeRAA 8B7RwZVWcTF2OwobulzRtcRSQFQUVOtcZSn306pW+koxpscI+4TiYhIjyLYVWrZ+U5XQ XWAg== 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=QEGu0KSsGebJh8viD/HuK7M0sftINnHyS29e9IGaakY=; b=cCeeH9Dt9rs1tiyat7R3M26uZgGLGMnxK5OZk1Lh2SGicmp1rL70hSLj27CxM4bh7u 0YIAuEbVxO6AZ/YysPconimuNG1FZ6uNdZd+C1IBspz/TDfAw0bl08jVSWkzlS6wmxue bQy/DXJIOpt5oVuaKv0UML9XVNZ/0TzYPyjR7lRH8V/0t+E/FmTMHcnG/IOzeGFFl0DU Nd7MpCHznHSnUk4qaYxAcffUJozq4ED/+0YdEK+2HxI505mUalIHWoTsxrrqKDKVzkgG p1GUgLucT/P9yFKeWJgU2bhBWWqug0Cozkp3ru5YNjipNE57Fq70+PEu5S1Nj0yNfDtz XqiA== X-Gm-Message-State: AElRT7E+ZGeliYpdagfG/eOtlx9TiLYJTzqXklRbrCliPk/Eonh3NFbD +YfzNBm/t1BIvsLjjHpbOkbeu1zCPwI4jD1gbE70Tg== X-Google-Smtp-Source: AG47ELs92294OEPY0iR+J9QEIG1nNUYlrz7eQ6QAte8L6HtNt59ZMMPKz1O3Etmp+IMsTlG2gx9IhNV9z7dh7aUhL80= X-Received: by 10.28.130.9 with SMTP id e9mr7573404wmd.161.1521798717244; Fri, 23 Mar 2018 02:51:57 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.69.220 with HTTP; Fri, 23 Mar 2018 02:51:56 -0700 (PDT) In-Reply-To: References: From: Dave Page Date: Fri, 23 Mar 2018 09:51:56 +0000 Message-ID: Subject: Re: v3.0 release on hold To: Khushboo Vashi Cc: pgadmin-hackers , Akshay Joshi , Murtuza Zabuawala , Syed Fahar Abbas , =?UTF-8?B?RGV2cmltIEfDnE5Ew5xa?= Content-Type: multipart/alternative; boundary="001a11444b44f624ff0568115f40" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --001a11444b44f624ff0568115f40 Content-Type: text/plain; charset="UTF-8" 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... -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company --001a11444b44f624ff0568115f40 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Fri, Mar 23, 2018 at 5:43 AM, Khushboo Vashi <<= a href=3D"mailto:khushboo.vashi@enterprisedb.com" target=3D"_blank">khushbo= o.vashi@enterprisedb.com> wrote:


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


= On Thu, Mar 22, 2018 at 9:58 AM, Khushboo Vashi <= ;khush= boo.vashi@enterprisedb.com> wrote:


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

<= span>On Thu, Mar 22, 2018 at 9:25 AM, Khushboo Vashi <= khushb= oo.vashi@enterprisedb.com> wrote:
Hi Dave,

On Wed, Mar 21, 2018 at 9:05 PM, Dave Page <dpage@pgadm= in.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 t= he time being, only patches critical to fix these issues should be committe= d.

I'll try to look at 1, though I do have another d= eadline 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?

Thanks all.

1)= There is no longer a system tray in Gnome 3.26 and later, and thus the run= time won't initialise in Fedora 27 and later. We need an alternative fo= r 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 doe= sn't always open a new pgAdmin window as it should. It works fine in th= e debugger, or if you start the app with a command like: "/Application= s/pgAdmin\ 4.app/Contents/MacOS/pgAdmin4". It doesn't work if= you double-click the appbundle or use a command like "open /Applicati= ons/pgAdmin\ 4.app"

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

4) On my Windows 7 machine, a= fter 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, b= ut couldn't reproduce it, It is working fine on both the environments.<= /div>
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.
= =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 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. Re= moving them, and truncating the process table in the sqlite DB seems to hav= e resolved the issue.

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

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

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