9.6.0-beta5 available

44 views
Skip to first unread message

Eric Iverson

unread,
Apr 11, 2024, 5:09:16 PMApr 11
to fo...@jsoftware.com
j9.6.0-beta5 available

Release notes: https://code.jsoftware.com/wiki/System/ReleaseNotes/J9.6

To upgrade the JE from previous beta install:
   load'pacman'
   'upgrade'jpkg'jengine'

Use pacman to install the base library and update all addons to be sure everything is at the same level and then restart.

To install from scratch:
https://code.jsoftware.com/wiki/System/Installation/J9.6

Michael Day

unread,
May 4, 2024, 1:16:25 PMMay 4
to fo...@jsoftware.com
I've just tried this update,  which appeared to proceed correctly,  but on reloading J
I get :

|read-only data: boot

| coclass =:18!:4@boxxopen

|[-428] C:\d\j9.6\system\main\stdlib.ijs

Press ENTER to inspect

|value error: boxdraw_j_

| 0 0$ boxdraw_j_ 0


Attempting to reveal the version details yields:

   JVERSION
|value error: JVERSION


Trying to load a recent script:

load 'c:/users/mike_/j9.6-user/aoc2323.ijs'

|value error: load

| load'c:/users/mike_/j9.6-user/aoc2323.ijs'


Trying to list any monads

names 3

|value error: wcsize

| w=.{. wcsize''

Press ENTER to inspect


... or nouns

names 0

|value error: wcsize

| w=.{. wcsize''

Press ENTER to inspect

|value error

| 'Use y___1 to look inside top stack frame; see code.jsoftware.com/wiki/Debug/Stack#irefs'[ dbg_z_ 513

*list_z_[0]


I thought I might already have done this update,   but expected the process

to detect if it was already at beta level 5 and bail out. 


I don't know where to go from here, apart from to revert to J9.5,  and reinstall J9.6 from scratch.


Thanks,


Mike

To unsubscribe from this group and stop receiving emails from it, send an email to forum+un...@jsoftware.com.

Raul Miller

unread,
May 4, 2024, 3:53:52 PMMay 4
to fo...@jsoftware.com
Hmm...

I tried the upgrade myself.

I was able to get the 9.6 beta to work by commenting out the offending
line (and one other line) in stdlib.ijs:

NB. coclass=: 18!:4 @ boxxopen
cocreate=: 18!:3
NB. cocurrent=: 18!:4 @ boxxopen

This brings up a few warnings, but I think this change is going to
need more thought and work.

Maybe it's also something of a teaching moment about the value of
stable interfaces?

--
Raul

Don Guinn

unread,
May 4, 2024, 4:02:14 PMMay 4
to fo...@jsoftware.com
I got the same failure in Windows 11.

Henry Rich

unread,
May 4, 2024, 5:11:56 PMMay 4
to forum
boot.ijs, stdlib.ijs, and all addons should be updated /before/ the J engine is updated. The script changes are backward compatible but the new engine needs them. 

I apologize for not making this clear. 

Henry Rich 

Raul Miller

unread,
May 4, 2024, 5:35:03 PMMay 4
to fo...@jsoftware.com
I did
install'all'

before upgrading the jengine. I was still hit with this problem.

I did another install'all' after upgrading and it reverted this aspect
of stdlib.ijs and I had to comment out those two lines again.

What happens when you do an install'all'?

What procedure should I have used instead?

Thanks,

--
Raul

Michael Day

unread,
May 6, 2024, 3:20:29 PMMay 6
to J Forum
Thanks,  again, to Raul for his tips.

This message relates to J9.6 beta 5 under Windows 11 on this HP Envy
Laptop.

So J9.6 beta 5 is now loading,  albeit with the 4 (009) messages about
calls to 18!:4 which I
haven't yet traced.   I find coclass and cocurrent are both defined,
despite following Raul's
advice to comment  out their definitions in stdlib.ijs .

BUT - JHS now fails.  I don't use it much,  just using it to support
some data swapping between
J on this laptop and on the iPad using ~addons/ide/jhs/jjserver.ijs .
I've just checked - JHS is still fine under J9.5,  but under the latest
9.6 beta I get variations on:

<<
This site can’t be reached127.0.0.1 refused to connect.
Try:

Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSED
>>

(this is in Avast Secure Browser - similar behaviour with M/S Edge and
Google Chrome.)

It might be significant that under J9.5,  the console/terminal window
stays during the JHS
session;  under J9.6 beta 5 it soon disappears,  too quickly for me to
catch it;  I thought I
saw another (009) error message about 18!:4,  and other errors might
have been reported,
but I could be mistaken.

Thanks,

Mike

On 04/05/2024 22:10, Michael Day wrote:
> Thanks, Raul,  that did the trick,  though I'm not too sure what you
> mean by the remark about
> stable interfaces.
>
> Anyway,  the error messages reminded me of Henry's post about the
> removal of 18!:4 .
>
> I'm now getting 3 x (009) 18!:4 messages,  on Qt load,  before
> JVERSION (called by
> my startup.ijs),  and 1 more after the JVERSION print.  I don't THINK
> my startup.ijs
> gives rise to these warnings,  so don't know what gives rise to
> them.   I don't see how
> to use 9!:55 for these 4 instances.
>
> I'm pretty clueless about locales,  so avoid using them,  with the
> co... verbs.  I never
> use 18!:4 .
>
> Thanks again,  cheers,
>
> Mike

Eric Iverson

unread,
May 6, 2024, 3:37:29 PMMay 6
to fo...@jsoftware.com
beta5 vs JHS
I will take a look, but probably not until tomorrow.

You could try capturing that output before the screen disappears with:

$ j9.6/bin/jconsole  ~addons/ide/jhs/config/jhs.cfg >> log.txt 2>&1

The above is from linux and may need adjustment to run for you. The output that flies by will be in the file log.txt.



Michael Day

unread,
May 6, 2024, 4:01:45 PMMay 6
to fo...@jsoftware.com
Thanks,  Eric

Yes, I managed to capture the session with that command line,  minus the $,  in a
Windows Power Shell console.  It turns out to be rather unhelpful,  after all:

<<
(009) 18!:4 has been removed, use cocurrent/coclass
(009) 18!:4 has been removed, use cocurrent/coclass
(009) 18!:4 has been removed, use cocurrent/coclass
startup: have started startup.ijs
startup: have set affinity
+-------+--------------------+
|time ''|2024 5 6 20 54 8.678|
+-------+--------------------+
JVERSION
Engine: j9.6.0-beta6/j64avx2/windows
Build: commercial/2024-05-03T02:44:26/clang-16-0-6/SLEEF=1
Library: 9.6.5
Platform: Win 64
Installer: j9.6 install
InstallPath: c:/d/j9.6
Contact: www.jsoftware.com
startup: have loaded comb.ijs
startup: have defined cperm
Startup.ijs finished
JHS - J HTTP Server

if you don't see a new jijx tab in your browser,
 manually browse to: http://127.0.0.1:65001/jijx

best practice:
 close server with shortcut Esc-q (Escape then q) in the jijx page

Ctrl+c here signals an interrupt to J.
>>

The various "startup" messages are from my config/startup.ijs
routine .

No rush!

Mike

Eric Iverson

unread,
May 6, 2024, 5:01:14 PMMay 6
to fo...@jsoftware.com
I understand and can reproduce the problem. A mismatch between 9.6 JE, base library, and JHS. I will let you know when we have a fix.

Mike Day

unread,
May 6, 2024, 5:07:07 PMMay 6
to fo...@jsoftware.com
That's quick.  
No great problem for me, but some might need the repair,  so good news!
Thanks,

Mike

Sent from my iPad

On 6 May 2024, at 22:01, Eric Iverson <eric.b....@gmail.com> wrote:



Eric Iverson

unread,
May 6, 2024, 5:37:25 PMMay 6
to fo...@jsoftware.com
If you upgrade your  9.6 JE to be beta7, then I think JHS will start properly. Let me know if this works.

Michael Day

unread,
May 6, 2024, 6:55:49 PMMay 6
to fo...@jsoftware.com
Thanks - it looks as if I've inadvertently updated to beta 6,  although I'd thought I was
catching up late with your announcement of beta 5,  on 11 April. 

J9.6 Release Notes name(s) beta 5 as current and 6 as unreleased;  but will an update
now lead to beta 7?

Bedtime for me in Blighty,  so I'll try ß7 when I can,  if it appears to be available.

Cheers,

Mike
Reply all
Reply to author
Forward
0 new messages