public inbox for [email protected]
help / color / mirror / Atom feedFrom: Dave Page <[email protected]>
To: Ashesh Vashi <[email protected]>
Cc: Khushboo Vashi <[email protected]>
Cc: pgadmin-hackers <[email protected]>
Cc: Akshay Joshi <[email protected]>
Cc: Murtuza Zabuawala <[email protected]>
Cc: Syed Fahar Abbas <[email protected]>
Cc: Devrim GÜNDÜZ <[email protected]>
Subject: Re: v3.0 release on hold
Date: Fri, 23 Mar 2018 12:03:31 +0000
Message-ID: <CA+OCxozg6K+sH3UJeBnZBnbyZCro5N7PmYQEz6jdYHeNmubEPw@mail.gmail.com> (raw)
In-Reply-To: <CAG7mmozsyQ0=H2Uou48ft3LRPW=WUe2Rfwf=ZK7Vs+2pHky_cA@mail.gmail.com>
References: <CA+OCxozJH1+edWvECQtx0Y0gMbW7X1J-Tzbt8gZ+KLL_narS4A@mail.gmail.com>
<CAFOhELfUTv4MeruG_-Vo0YizmALBxxrCwKGPA7vna_TbYoZTfg@mail.gmail.com>
<CA+OCxow-n0jA_vD+XDEHU0MGG06cZ-PV4g3WxcG+r=6XBAXkOw@mail.gmail.com>
<CAFOhELda0jx+epcY1TTJJbd7kTJXprNvUcNne90CxNct59byog@mail.gmail.com>
<CA+OCxow2LgOoSeqWPaqXJEaDJs+j=cABwoaTZ5Fwe7udc0qo5w@mail.gmail.com>
<CAFOhELdoX-m81cPE7GUfgoSFKNAfdCHORS5itDFDdfk_zA_ykQ@mail.gmail.com>
<CA+OCxoxvZMV4DM5gRf4EqqaJNSvzTV_QuXLKjJ_AotgB4LRVJA@mail.gmail.com>
<CAG7mmozsyQ0=H2Uou48ft3LRPW=WUe2Rfwf=ZK7Vs+2pHky_cA@mail.gmail.com>
On Fri, Mar 23, 2018 at 11:27 AM, Ashesh Vashi <
[email protected]> wrote:
> On Fri, Mar 23, 2018 at 3:21 PM, Dave Page <[email protected]> wrote:
>
>>
>>
>> On Fri, Mar 23, 2018 at 5:43 AM, Khushboo Vashi <
>> [email protected]> wrote:
>>
>>>
>>>
>>> On Thu, Mar 22, 2018 at 3:42 PM, Dave Page <[email protected]> wrote:
>>>
>>>>
>>>>
>>>> On Thu, Mar 22, 2018 at 9:58 AM, Khushboo Vashi <
>>>> [email protected]> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Thu, Mar 22, 2018 at 3:20 PM, Dave Page <[email protected]> wrote:
>>>>>
>>>>>> Hi
>>>>>>
>>>>>> On Thu, Mar 22, 2018 at 9:25 AM, Khushboo Vashi <
>>>>>> [email protected]> wrote:
>>>>>>
>>>>>>> Hi Dave,
>>>>>>>
>>>>>>> On Wed, Mar 21, 2018 at 9:05 PM, Dave Page <[email protected]>
>>>>>>> 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)
>
Hmm, not sure if it's worth it. We should make sure that future changes in
that code can cope with older format logs and DB entries though.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
view thread (27+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: v3.0 release on hold
In-Reply-To: <CA+OCxozg6K+sH3UJeBnZBnbyZCro5N7PmYQEz6jdYHeNmubEPw@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox