Demo breaks (macOS 10.13.6).

[RalphieBoy]

New user for SCSCP (version 2.2.3), GAP 4.10.1, macOS 10.13.6. Tried the test in README.md. It blew up. Short transcript attached.

SCSCP.txt

I keyed "return" as instructed, which did nothing. Then ^D got me back to shell prompt.

[olexandr-konovalov]

Thanks, I see what happened - the demo runs through examples from https://github.com/gap-packages/scscp/blob/master/demo/paris2011.g and this line EvaluateBySCSCP( "ChangeInfoLevel", [4], server, port ); for the demo purposes increases the verbosity on the server. But that is only available if https://github.com/gap-packages/scscp/blob/master/example/private.g is loaded, what's not by default. if you would like your SCSCP server to understand ChangeInfoLevel, you can add the block

ChangeInfoLevel:=function( n )
SetInfoLevel( InfoSCSCP, n );
return true;
end;

InstallSCSCPprocedure( "ChangeInfoLevel",  ChangeInfoLevel, 	
    "To change InfoSCSCP level on the server without restarting", 1, 1 );

to your server configuration file. Otherwise, remove that problematic call from demo/paris2011.g (or, instead of calling gap rundemo.g try examples from there line by one.

Thanks for reporting this - I will fix the demo for the next release.

[olexandr-konovalov]

P.S. A demo of distributed parallel calculations with SCSCP at https://github.com/alex-konovalov/scscp-demo is more recently tested. It extends an example of the search in the GAP Small Groups Library from the Carpentries-style GAP lesson at https://github.com/carpentries-incubator/gap-lesson.

[RalphieBoy]

On May 19, 2021, at 00:51 , Alexander Konovalov ***@***.***> wrote: Thanks, I see what happened - the demo runs through examples from https://github.com/gap-packages/scscp/blob/master/demo/paris2011.g and this line EvaluateBySCSCP( "ChangeInfoLevel", [4], server, port ); for the demo purposes increases the verbosity on the server. But that is only available if https://github.com/gap-packages/scscp/blob/master/example/private.g is loaded what's not by default. if you would like your SCSCP server to understand ChangeInfoLevel, you can add the block ChangeInfoLevel:=function( n ) SetInfoLevel( InfoSCSCP, n ); return true; end; InstallSCSCPprocedure( "ChangeInfoLevel", ChangeInfoLevel, "To change InfoSCSCP level on the server without restarting", 1, 1 ); to your server configuration file. Otherwise, remove that problematic call from demo/paris2011.g (or, instead of calling gap rundemo.g try examples from there line by one. Thanks for reporting this - I will fix the demo for the next release.

Thanks for the information. I added the above block to myserver.g, which got me farther, but the “rundemo” run blew up, so I thought I would cleverly divide and conquer to figure out where the problem is. I ran each of the files (other than rundemo.g), and all had problems, so I think I am missing a few subtleties in the operation of the SCSCP operation. Do you want the full output from these tests on the GitHub gap_packages site? In brief, I figured out that the “maple2gap” demo should be run from Maple :-} I tried that, but could not decide whether the responses were in the workbook, or were responses from Gap today. Several demos timed out, and a couple got “connection refused”. Others had internal/code problems - on that occurred a couple of times is a complaint about "'PqStandardPresentation' must have an assigned value”. BTW, I ran each of the “demo/*.g” files with “gap filename”. Also, the server happily sat around, occasionally fielding a request and sending a response. Couldn’t tell easily which ones were accepted (have yet to delve into the code). HTH Justin

…

-- Justin C. Walker, Curmudgeon at Large Director Institute for the Enhancement of the Director's income ----------- Question 43: What if the hokey pokey really *is* what it’s all about? --

[olexandr-konovalov]

@RalphieBoy apologies, demos are in a messy state (see #11). This is what happens when you don't run them regularly. The tests from tst are actually run more often, and I have just fixed CI in #33, switching from Travis CI to GitHub actions. Now you can see e.g. at https://github.com/gap-packages/scscp/runs/2669740442?check_suite_focus=true, by expanding the output section named "Run gap-actions/run-pkg-tests@v2", the tests output. It shows diffs due to some random ID in tests, but otherwise those are working examples of communication. Look for EvaluateBySCSCP calls, if you're interested in a user-level functionality.

SCSCP debugging is not most-user friendly - in particular, when an error occurs on the server during the call evaluation, it catches an error messages, sends it to the client, and resumes waiting for a new call. I am happy to look at error messages, they may look familiar and I might be able to spot the problem quickly. In particular, missing PqStandardPresentation means that the ANUPQ package is not compiled.