Executing on the root Task from the REPL

mkitti · February 18, 2020, 10:39am

I would like to a explore a mechanism by which a user could execute a command from the REPL on the root task rather than the backend.

Motivation: JavaCall

Without JULIA_COPY_STACKS=yes it appears JavaCall will only function correctly if executed on the root Task (Base.roottask) even when using Java 11 or higher.
https://github.com/JuliaInterop/JavaCall.jl/issues/101
Trying to use JavaCall.init() without JULIA_COPY_STACKS=yes will currently cause a segmentation fault. I’ve discussed a potential PR with Avik to throw an error first rather than segfault.

Currently all the REPLs except the fallback mode send all commands to a backend on a different Task due to the use of @async:

github.com

JuliaLang/julia/blob/master/stdlib/REPL/src/REPL.jl#L139


      
          
          
# Allows an external package to add hooks into the code loading.
          # The hook should take a Vector{Symbol} of package names and
          # return true if all packages could be installed, false if not
          # to e.g. install packages on demand
          const install_packages_hooks = Any[]
          
          
function eval_user_input(@nospecialize(ast), backend::REPLBackend, mod::Module)
              lasterr = nothing
              Base.sigatomic_begin()
              while true
                  try
                      Base.sigatomic_end()
                      if lasterr !== nothing
                          put!(backend.response_channel, Pair{Any, Bool}(lasterr, true))
                      else
                          backend.in_eval = true
                          if !isempty(install_packages_hooks)
                              check_for_missing_packages_and_run_hooks(ast)
                          end
                          for xf in backend.ast_transforms

This means that JavaCall cannot be used at all from the LineEdit REPL unless JULIA_COPY_STACKS=yes is set via an environmental variable. However, it could be used if the fallback REPL is forced by using something like $ cat | julia -i

Proposal

We create a mechanism by which the user can execute certain commands on the REPL frontend rather than the backend. Here are a few options to enable a user to execute on the root Task frontend rather than asychronously in the backend:

Create a new REPL mode where all commands are executed on the root Task. This could be done from a package like JavaCall.
Quote the expression using a macro in such a way that a conditional can redirect the AST to be executed on the frontend.
Throw an exception that can be caught by the REPL which would then try to execute the command on the root Task
Create a special Channel by which the REPL backend could send commands to the root Task frontend for execution.

Topic		Replies	Views
Networked REPL? Internals & Design	36	4748	May 9, 2018
Start repl from non-interactive session General Usage question , repl	5	1434	May 23, 2017
How can I run hooks before and after the execution of a command in the REPL? Internals & Design repl , hook	11	1070	August 14, 2020
REPL-like printing from a script? General Usage question	1	515	November 30, 2016
How to start Julia REPL with a command? General Usage question	2	519	July 17, 2017

Executing on the root Task from the REPL

Related topics