And now, in the same notebook session, ')read bugs2009':
[IPKernelApp] ERROR | Exception in message handler:
Traceback (most recent call last):
File
"/home/greg/.local/lib/python3.11/site-packages/ipykernel/kernelbase.py",
line 409, in dispatch_shell
await result
File
"/home/greg/.local/lib/python3.11/site-packages/ipykernel/kernelbase.py",
line 720, in execute_request
reply_content = self.do_execute(
^^^^^^^^^^^^^^^^
File
"/home/greg/.local/lib/python3.11/site-packages/jfricas/fricaskernel.py",
line 212, in do_execute
r = self.server.put(block)
^^^^^^^^^^^^^^^^^^^^^^
File
"/home/greg/.local/lib/python3.11/site-packages/jfricas/fricaskernel.py",
line 77, in put
self.output = json.loads(data.rstrip('\\n'))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/json/__init__.py", line 346, in loads
return _default_decoder.decode(s)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/json/decoder.py", line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/json/decoder.py", line 355, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
And no output in the notebook. It seems jfricas stops processing the
command because
of an error in its side. I can evaluate bugs2009.input until
completion in a terminal for information.
I more or less get the same output as you (just that I don´t see
^^^^^^^^^^^^^^^^^^.
But as I said, this bugs2009.input deliberately creates an error. And
this is what jfricas cannot handle. Any errors of the kind where FriCAS
jumps into the lisp debugger are bad.
In my gnome-terminal that is attached to the session, I see the following:
Value = T
Value = WEBSPAD::FRICAS-ACCEPTOR
(1) -> [2023-07-23 22:47:14 [ERROR]] An arithmetic error
SB-KERNEL:FLOATING-POINT-EXCEPTION was signalled.
No traps are enabled? How can this be?
Backtrace for: #<SB-THREAD:THREAD "hunchentoot-worker-127.0.0.1:39328"
RUNNING {1003AA3673}>
0: (TRIVIAL-BACKTRACE:PRINT-BACKTRACE-TO-STREAM
#<SB-IMPL::STRING-OUTPUT-STREAM {7F2DCC68BBF3}>)
1: (HUNCHENTOOT::GET-BACKTRACE)
2: ((FLET "H0" :IN HUNCHENTOOT:HANDLE-REQUEST)
#<SB-KERNEL:FLOATING-POINT-EXCEPTION {100688F113}>)
3: (SB-KERNEL::%SIGNAL #<SB-KERNEL:FLOATING-POINT-EXCEPTION {100688F113}>)
4: (ERROR SB-KERNEL:FLOATING-POINT-EXCEPTION :OPERATION NIL :OPERANDS NIL)
5: ((FLET SB-UNIX::BODY :IN SB-VM:SIGFPE-HANDLER))
6: (SB-UNIX::WITH-DEFERRABLE-SIGNALS-UNBLOCKED T #<FUNCTION (FLET
SB-UNIX::BODY :IN SB-VM:SIGFPE-HANDLER) {7F2DCC68BF2B}>)
7: (SB-VM:SIGFPE-HANDLER #<unused argument> #.(SB-SYS:INT-SAP
#X7F2DCC68C3B0) #.(SB-SYS:INT-SAP #X7F2DCC68C280))
8: ((FLET SB-THREAD::EXEC :IN SB-SYS:INVOKE-INTERRUPTION))
9: ((FLET "WITHOUT-INTERRUPTS-BODY-1" :IN SB-SYS:INVOKE-INTERRUPTION))
10: (SB-SYS:INVOKE-INTERRUPTION #<FUNCTION (FLET SB-UNIX::INTERRUPTION
:IN SB-UNIX::%INSTALL-HANDLER) {7F2DCC68C0BB}>)
11: ((FLET SB-UNIX::RUN-HANDLER :IN SB-UNIX::%INSTALL-HANDLER) 8
#.(SB-SYS:INT-SAP #X7F2DCC68C3B0) #.(SB-SYS:INT-SAP #X7F2DCC68C280))
12: ("foreign function: call_into_lisp")
13: ("foreign function: funcall3")
14: ("foreign function: interrupt_handle_now_handler")
Because
)set break resume
at the beginning of bugs2009, it is not so bad for the fricas session,
but still jfricas cannot (currently) handle this case.
I'll see whether some day jfricas can deal with it.
Thanks for reporting.
Ralf
--
You received this message because you are subscribed to the Google Groups "FriCAS -
computer algebra system" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/fricas-devel/9a451bde-065c-dfd0-7192-6002564acf31%40hemmecke.org.
