Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.prolog > #14375

Re: ANN: Dogelog Player 1.2.5 (bun.js Support)

From Mild Shock <janburse@fastmail.fm>
Newsgroups comp.lang.prolog
Subject Re: ANN: Dogelog Player 1.2.5 (bun.js Support)
Date 2024-12-19 17:00 +0100
Message-ID <vk1fur$131fo$1@solani.org> (permalink)
References <viqrmd$qnts$1@solani.org> <vj1cj8$329t4$1@dont-email.me> <vj1igm$u605$1@solani.org> <vj1j4s$u6d4$1@solani.org> <vk106p$2rakn$1@dont-email.me>

Show all headers | View raw


Ok, thanks!

There is a problem that I haven't resolved yet.
Namely node.js ≥ 22.11.0 is too optimistic.
Especially when using JavaScript together with

the AntScript that runs the test cases. When
I use the AntScript test cases on Dogelog Player 1.2.6,
with node.js version 23.x I see this Warning:

Test run ...
Generating dump ...
comply_reference_report
Warning: Detected unsettled top-level await
Result: 13

The warning doesn't show with node.js version 22.x.
Since it happens when running some test cases which
do all kind of non-sunshine probing, it could be a

problem that somewhere I really miss settling a promise,
or its an ugly timing problem. It doesn't happen when
opening the top-level or running a script.

Like the top-level shows me:

 > node.exe player\canned\dogelog.mjs
Dogelog Spieler, Prolog zum Mond, 1.2.6 (05.12.2024)
(c) 1985-2024, XLOG Technologies AG, Schweiz
?- current_prolog_flag(host_info, X).
X = 'node, JavaScript 23.4.0'.
?- X=0;X=1.
X = 0;
X = 1.
?- end_of_file.

So its all fine if we do simple things. But something
is wrecked when running the test suite. It doesn't
happen with bun.js. I will open a ticket as a reminder.

Aleks Grabowski schrieb:
> Date :Sat, 7 Dec 2024 14:38:36 +0100. Mild Shock wrote:
> 
>> Whats also extremly annonying. A very early version of node 23.x didn't
>> work correctly. So I fell back to node 22.x. Still waiting to do some
>> retest with 23.x.
>>
>> What worked for me in the tip release is actually published here:
>>
>> j	Dogelog Player 1.2.5, Java 23.0.1 js	Dogelog Player 1.2.5,
> JavaScript
>> 22.11.0 py	Dogelog Player 1.2.5, Python 3.10.14
>>
>> https://www.novacuor.ch/exatab/doclet/docs/10_core/ryzen/package.html?
> hash=bench
>>
>> But Python is in fact PyPy and JavaScript is curently node.
>> But the above doesn't reflect really the minimum, rather only the known
>> maximum on Windows 11.
> 
> Current version requirements for arch package are:
> 
> py CPython ≥ 3.10.14 or pypy3 (any version)
> js nodejs ≥ 22.11.0 or bun (any version)
> j  java-runtime ≥ 21
> 
> I expect users to apply common sense when trying to run Dogelog it should
> be obvious that very old interpreters might not work :)
> 

Back to comp.lang.prolog | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

ANN: Dogelog Player 1.2.5 (bun.js Support) Mild Shock <janburse@fastmail.fm> - 2024-12-05 01:21 +0100
  Re: ANN: Dogelog Player 1.2.5 (bun.js Support) Aleks Grabowski <prolog@asap.mozmail.com> - 2024-12-07 11:46 +0000
    Re: ANN: Dogelog Player 1.2.5 (bun.js Support) Mild Shock <janburse@fastmail.fm> - 2024-12-07 14:27 +0100
      Re: ANN: Dogelog Player 1.2.5 (bun.js Support) Mild Shock <janburse@fastmail.fm> - 2024-12-07 14:38 +0100
        Re: ANN: Dogelog Player 1.2.5 (bun.js Support) Aleks Grabowski <prolog@asap.mozmail.com> - 2024-12-19 11:31 +0000
          Re: ANN: Dogelog Player 1.2.5 (bun.js Support) Mild Shock <janburse@fastmail.fm> - 2024-12-19 17:00 +0100
  Re: ANN: Dogelog Player 1.2.5 (bun.js Support) Mild Shock <janburse@fastmail.fm> - 2024-12-12 16:12 +0100
    Re: ANN: Dogelog Player 1.2.5 (bun.js Support) Mild Shock <janburse@fastmail.fm> - 2025-01-13 17:45 +0100

csiph-web