[Octave-bug-tracker] [bug #59952] [octave forge] (parallel) command line function call issues

[Tasos Papastylianou]

Follow-up Comment #2, bug #59952 (project octave):

Hi Olaf. I'm the person who answered the stackoverflow question and encouraged
Stavros to file this bug.

As I mentioned in that stackoverflow answer, I suspected that the recent move
from fork to bespoke workers might be the reason for this behaviour, as you
also mentioned, and I agree that it is a reasonable limitation, and that it
should be more clearly documented.

However, this was not the only reason I encouraged Stavros to file this as a
bug. The other, presumably *more* important behaviour here which you did not
comment on is the fact that pararrayfun does not raise an error gracefully
when the command-line function is not suitably defined locally on the worker,
but instead this silently returns a -1 as if it were a legitimate return from
the function. Presumably this -1 is a return value from a c/c++ function
denoting an error, which may be expected in the context of the underlying c
calls, but in the context of a legitimate-looking return value to octave
instead of an error message, this is a very serious bug. It is also unclear
whether such silent error values only happen in this particular scenario, or
if this also happens when other errors take place inside a worker.

In my opinion it is this that is the more serious issue in this bug report,
and not simply whether commandline-functions are compatible in the first
place. (Apologies, I don't know if this is a known issue already).

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?59952>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/