Hi The candidate build can be found at https://developer.pgadmin.org/~dpage/1.6/.
Note that as the timing is coupled with the PostgreSQL 10b2 release, we'll only rewrap now for showstopper issues, not anything minor. On Tue, Jul 11, 2017 at 1:14 PM, Mike Surcouf <mi...@surcouf.co.uk> wrote: > Hi Dave > > > > Can I suggest you send out another build before you go GA. > > I for one have outstanding issues that were not in 1.3 (see previous > emails). > > I know you said you don’t have my issues on your install but that doesn’t > mean they don’t exist. > > > > Happy to test > > > > Thanks > > > > Mike > > > > *From:* Dave Page [mailto:dp...@pgadmin.org] > *Sent:* 11 July 2017 13:11 > *To:* McDonaldR > *Cc:* pgadmin-hackers; pgAdmin Support > *Subject:* Re: Windows testing required: Updated runtime > > > > Hi > > > > On Tue, Jul 11, 2017 at 10:03 AM, McDonaldR <mcdona...@angus.gov.uk> > wrote: > > Hi Dave, > > > > I’m testing the latest build (10/7/2017) from your download page. > > > > I had a v1.5 build that fixed issues with the proxy server. It took ~30 > secs from start to usable. Before that I could only run the v1.3 release. > > > > This new build starts in about 9 seconds showing the splash screen and > then it crashes with a *Fatal Error: The application server could not be > contacted*. > > > > There is nothing in the Event Viewer logs and the pgAdmin log is empty in > C:\Users\username\AppData\Roaming\pgAdmin > > > > The registry key in HKEY_CURRENT_USER\Software\pgadmin\pgadmin4 is blank > with a value not set. > > > > Windows 7 Enterprise 64 bit > > 16GB RAM > > SSD > > Behind the corporate proxy and firewall > > > > Thanks - this should be fixed for GA. > > > > -- > > Dave Page > Blog: http://pgsnake.blogspot.com > Twitter: @pgsnake > > EnterpriseDB UK: http://www.enterprisedb.com > The Enterprise PostgreSQL Company > -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
