ProTop 3.1415

TomBascom

Curmudgeon
ProTop 3.1415 is almost ready to escape into the wild! If you would like to test the release candidate you can easily obtain by using the pt3upd.sh (or pt3upd.bat) command like this:
Code:
tom@protoptest> pt3upd.sh pt3.1415x
Wed Apr 29 13:24:00 UTC 2020 Updating to pt3.1415x
Wed Apr 29 13:24:00 UTC 2020 pt3.1415x-src.tar
Wed Apr 29 13:24:00 UTC 2020 curl -L -o /home/tom/tmp/pt3.1415x-src.tar.gz http://demo.wss.com/pt3upd/pt3.1415x-src.tar.gz
29/04/2020 13:24:05.655+00:00 getfile: demo.wss.com|/pt3upd/pt3.1415x-src.tar.gz|/home/tom/tmp/pt3.1415x-src.tar.gz
29/04/2020 13:24:05.655+00:00 getURL(): newSocket( demo.wss.com 80 ) size = 118
29/04/2020 13:24:05.657+00:00 connect( -H demo.wss.com -S 80 )
29/04/2020 13:24:05.661+00:00 getURL(): newSocket( demo.wss.com 80 yes )
29/04/2020 13:24:07.171+00:00 HTTP/1.1 200 OK
pt3inst.sh
protop.p
...
ustub/zipenv.x
ustub/zippyng.sh
ustub/portalenv
ustub/pt3inst.sh
Wed Apr 29 13:24:12 UTC 2020 running silent install, detailed log is in pt3inst.log
tom@protoptest>
The release notes can be found in etc/NOTES_3.1415.

Unless someone finds a really horrible bug this will probably be made available for general release next week!

If you don't want to clutter up ProgressTalk with discussion of ProTop: ProTop Community
 

Rob Fitzpatrick

ProgressTalk.com Sponsor
That's an irrational version number... :D

Wow, lots of changes to go through! I like the new colours and the colour picker. :)
And then I crashed with a 49. :(

Holy cow online help!!! o_O
Protop Help
Awesome!
 

TomBascom

Curmudgeon
I have been threatening to go over to Tau. No, really, pi is wrong: The Tau Manifesto

Regarding the error 49 stuff... it has been an annoyance for quite a while. I had assumed that I was doing something wrong and that there must be a memory leak or that I was somehow trying to perform unnatural acts with handles. I have put a ton of energy into tracking that down. Error handling and debugging out the wazoo. I added the temp-table inspection code in large part to try to figure out if I was leaking temp-tables. And so on.

But it was mostly just an occasional annoyance and since it only impacts the character UI it didn't bother me _too_ much.

Until 12.1. Something changed inside the AVM and 12.1 onward are suddenly not just an occasional annoyance but a non-stop horror show for the character UI. I mentioned the problem to someone at Progress and they said "aren't error 49s always *our* problem?" I hadn't ever heard that... but with a bit of encouragement I submitted a bug report and in very little time it was discovered that, yes, it is a Progress bug.

Apparently I should have reported it 10 years ago :(

11.7.6 and 12.2.1 are expected to have it patched.

On the bright side once I knew what was causing it I was able to cleanup some rather messy attempts at avoiding it.

I also might have got ProTop on Windows working reasonably with prowin and prowin32 again. (No, no fancy mouse stuff! Just basic functionality.)
 

Rob Fitzpatrick

ProgressTalk.com Sponsor
I mentioned the problem to someone at Progress and they said "aren't error 49s always *our* problem?"
This was always my impression, that a 49 was Progress, not you (or any developer).

FWIW, my crash was on 11.6.3.
 

TomBascom

Curmudgeon
Oh well! Live and learn.
 

TomBascom

Curmudgeon
tick, tick, tick...

The time for pre-release feedback is drawing to a close!
 
Top