You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If possible, include information about your project and its structure. Open source projects or examples are always easier to debug.
If you can provide an example code base to reproduce the issue on, we will generally be able to provide more help, and faster.
Current behaviour
Describe the current behaviour. In case of a failure, crash, or exception, please include the result of running the command with debug information:
DEBUG=1 rebar3 <my failing command>
Expected behaviour
Hello
I am not sure if it is a expected behavior or not.
I am trying to use 'rebar3 shell' and 'rebar3 auto' and seeing that when code is being compiled as expected but the prompt '>' is not returned - which is not what I expect.
This is a bug in Erlang/OTP. From the ERTS version in the prompt, you are currently running on OTP-26.0. Try going up even to OTP-26.0.2 and it should be fixed. That patch release had a lot of corrections that improve the new shell handling mechanism released in OTP-26.0 and had multiple small bugs.
Pre-Check
Environment
rebar3 report
to your message:If you can provide an example code base to reproduce the issue on, we will generally be able to provide more help, and faster.
Current behaviour
Describe the current behaviour. In case of a failure, crash, or exception, please include the result of running the command with debug information:
Expected behaviour
Hello
I am not sure if it is a expected behavior or not.
I am trying to use 'rebar3 shell' and 'rebar3 auto' and seeing that when code is being compiled as expected but the prompt '>' is not returned - which is not what I expect.
/**********
$ rebar3 shell
===> Verifying dependencies...
===> Analyzing applications...
===> Compiling myproj
Erlang/OTP 26 [erts-14.0] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:1] [jit:ns]
Eshell V14.0 (press Ctrl+G to abort, type help(). for help)
1> ===> Booted myproj
===> Booted sasl
/**********
notice missing '2>'
I am using 'Ubuntu 23.10' in stock configuration, TERM env is 'xterm-256color'.
this is mildly announcing and I am wandering if there is some configuration setting to fix this?
Regards, Roman
The text was updated successfully, but these errors were encountered: