Can't run Red from other programs

[maximvl]

Describe the bug
When I try to execute Red from another program it fails with PROGRAM ERROR: Invalid encapsulated data.

To Reproduce
Steps to reproduce the behavior:

1. Install Elixir
2. Clone https://gitlab.com/maxvel/reddish.git
3. In the repo run iex -S mix
4. In the REPL type

p = Reddish.start
Reddish.send_input(p, "5 + 5\n")
flush()

5. See message {#PID<0.170.0>, :data, :out, "PROGRAM ERROR: Invalid encapsulated data.\n"}
6. After this I can't even run Red as regular:

> red
PROGRAM ERROR: Invalid encapsulated data.

7. And in a new shell instance:

> red
** Script Error: Invalid compressed data - problem: -3
** Near: script: decapsulate 
if none? script

Expected behavior
flush() prints message with "10" returned by Red, Red is runnable.

Screenshots

Platform version(please complete the following information):

Red 0.6.3 for Linux built 11-Oct-2018/3:00:23+02:00 commit #b1f01cc

[9214]

#543, #1547

[maximvl]

I also tried to create a wrapper like this:

#!/bin/bash
red $@

With it I don't get the error, but got no output either. From what I tried this works with cat, bash and ipython, but doesn't work with python (same no output). So it might be more than just fixing encapping.

[dockimbel]

If you need only the Red interpreter, compile the CLI console and use that binary instead of red.exe.

[x8x]

I work around this issue by wrapping the Red call into sh like this:

sh -c "red -r code.red"

I suspect a path issue in certain environment where the console called from red binary can't find the crush decompressor maybe not as in the example the toolchain is called not the console.., but haven't investigated further.

Other example, given %code.red:

Red []
print 123

Run a Red Console:

  o: "" call/output {red code.red} o print o
** Script Error: Invalid compressed data - problem: -3
** Near: script: decapsulate 
if none? script

  o: "" call/output {sh -c "red code.red"} o print o
123

Wondering if it's a regression, must have had similar code working without wrapping long ago.

Not really related.. we should really have something like rebol --do "print 123" for quickies.

[beenotung]

I found similar bug on windows.
I saved red as red.exe, and add the containing folder into PATH.
I found it will raise below error when launch form cmd:

PROGRAM ERROR: Invalid encapsulated data.

below case will trigger error

1. if the current directory is not containing red, and using red or red.exe
2. if the current directory is not containing red, and using ..\local\bin\red

below case will not trigger error

1. if the current directory is containing red, and using red or red.exe
2. if the current directory is not containing red, and using ..\local\bin\red.exe

[beenotung]

I tried the test cases with rebol-core and rebol-view, all the two cases trigger error for red do not trigger error for rebol.

[greggirwin]

Thanks for the note @beenotung.

[pierstitus]

I get the same error when running from ipython3:

Python 3.8.2 (default, Apr 27 2020, 15:53:34) 
Type 'copyright', 'credits' or 'license' for more information
IPython 7.13.0 -- An enhanced Interactive Python. Type '?' for help.

In [1]: import subprocess

In [2]: subprocess.run('./red-064')
** Script Error: Invalid compressed data - problem: -3
** Near: script: decapsulate 
if none? script
Out[2]: CompletedProcess(args='./red-064', returncode=0)

Running from python3 gives a slightly different error:

Python 3.8.2 (default, Apr 27 2020, 15:53:34) 
[GCC 9.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import subprocess
>>> subprocess.run('./red-064')
** Script Error: Not enough memory
** Near: script: decapsulate 
if none? script
CompletedProcess(args='./red-064', returncode=0)

It doesn't matter what arguments are given, subprocess.run(['./red-064','hello.red']) or subprocess.run(['./red-064','-V']) give the same error. Compiled red programs do run normally.

[endo64]

I just realized that, on Windows, if your red.exe is located in your PATH, you get PROGRAM ERROR: Invalid encapsulated data. if you execute red.exe in command prompt (cmd.exe), but it works if you use Powershell.

And also the output speed is much faster on Powershell.

[dockimbel]

The Red binary is now separated in several binaries. The CLI console binary can be called from other languages if needed.