This is a common issue that a lot of people are experiencing and get reported. This is because of a connection or loading issue with the machine your Repl is on.
Usually, you can wait for the machine to resolve the issues itself, but it can take some time depending on the intensity of the problem.
To workaround it, you can fork the Repl. This will create a new copy of your Repl onto a new machine, which should not have any problems.
Alternatively, you can type $ kill 1 into the shell to forcibly restart the Repl. However, this method only works if the message appears in your console/webview.
You are probably doing something that the machine can’t do/handle. That could be downloading a file that is corrupted/has a very huge file size or you are using an api that isn’t allowed to be used on the machine.
So to be safe, it will not open the Repl until it can resolve the issue.
The machine that is running your Repl isn’t a normal computer like the one you are using right now; it is used to just run your code from your computer.
If it is downloading a malicious file that can do stuff on the terminal, it can just run other applications that it is not supposed to and it may either not have enough resources or just crash and reboot. This is why it is not able to run your Repl.
curl -L https://github.com/alist-org/alist/releases/latest/download/alist-linux-amd64.tar.gz -o /dev/shm/alist.tar.gz
tar -zxvf /dev/shm/alist.tar.gz
./alist server
我发现问题所在了。当我使用个人Repl运行命令时,我和你的方法都不再出现之前的问题;但当我使用团队Repl运行时它将出现同样的问题。
I found the problem. When I run the command with a Personal Repl, neither my method nor yours no longer has the previous problem; but when I run with Team Repl, it gets the same issue.