Unable to build a working HopscotchWebIDE.vfuel from latest version

18 views
Skip to first unread message

Milan Zimmermann

unread,
Jan 23, 2024, 7:56:03 PM1/23/24
to newspeak...@googlegroups.com
Gilad,

I wonder if you would have some hints for this - I will try to describe briefly, although I am not sure it will be understandable considering it most likely is not a problem for you.

The core of my issue is that, with the latest version of Newspeak, the HopscotchWebIDE.vfuel build using the ' . ./build.sh' hangs when served. I would think this is a problem at my end (and very well still may be), but if I use Newspeak version 3 commits back (the one with commit message 'Restore README'), this one


running '. ./build.sh' produces a working HopscotchWebIDE.vfuel. 

The EMSDK version I use is 2.0.0 (with any Newspeak version), and the extraRevs primordial soup, which combination always worked for me so far.

The reason I tried the 3 commits back was I got to the end of my rope, and I speculated from the commit messages there were some changes in the last 2 commits that affect memory etc, so I am trying my luck here in case you have a hint.

(PS: I started to have this issue during my work on the PWA versioning changes, which require some changes to the build script, and the whole week was sure it was my fault - still may be - but then I rolled back all my changes completely and the issue remained, so I started to roll back the newspeak commits)

Thanks for any hints, but understand if there were none, I will fight through it one way or another

Milan

Gilad Bracha

unread,
Jan 23, 2024, 8:14:40 PM1/23/24
to newspeak...@googlegroups.com
Hi Milan,

I have built the system quite a few times recently and have not encountered any difficulties. The only difference I can see is the following method in InstanceMixin

public applyTo: superclass <Class> withEnclosingObject: eo <Object> = (
(* Sent by the compiler in nested class accessors. *)
^apply: superclass withName: _name  enclosingObject: eo
)

which is slightly different and was not put back it seems.  So I put that back to extraRevs. Would be interesting to know if it makes a difference.

--
You received this message because you are subscribed to the Google Groups "Newspeak Programming Language" group.
To unsubscribe from this group and stop receiving emails from it, send an email to newspeaklangua...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/newspeaklanguage/CAEc2VK3uNBsnLbkNYv7t5b7iuEs0S2t_G1pne9f2sb1tDo1Cvg%40mail.gmail.com.


--
Cheers, Gilad

Milan Zimmermann

unread,
Jan 23, 2024, 8:51:31 PM1/23/24
to newspeak...@googlegroups.com
Gilad,

Thanks again, solved.  The builds work for me now!  [And it was more than likely my fault, as I predicted :( ]

When I wrote I am using extraRevs of primordialsoup - that was correct, except I have not looked at primordialsoup changes in the last 2 weeks ... and I was actually missing primordialsoup commits from Jan 12 and 13 as well!! Very sorry about that, but I am glad I asked!

 primordialsoup repo does not change that much and I completely forgot to check when I restarted working on this 2 weeks ago or so

 So any of the  Jan 12 and 13 commits, or the last you just committed solved this for me. 

Thanks,
Milan

PS: The build also works with the latest EMSDK, in addition to 2.0.0 which I used all along - I would be curious to know which version of EMSDK you are using to build 

Thanks

Reply all
Reply to author
Forward
0 new messages