Activate your terminal error, even when creating new console

[piyush-jaiswal]

Constantly getting "Error: Activate your terminal", even when a new console is created with POST request.

Workflow run:

Workflow file:

[umuttopalak]

Hello @piyush-jaiswal,
What type of terminal are you using? Instead of creating manually, delete all terminals and then run action. Action will automatically create a terminal, then go to pythonanywhere and activate that terminal, can you try action again? There should be no problem, as long as you don't open the terminal type as python etc.

[piyush-jaiswal]

I generally use bash. All my consoles were terminated during this run. Which is why, the workflow created one using a POST request (as what I can understand from the code). I've run the workflow multiple times and it has failed.

The few times it successfully ran was when I manually opened a bash console on my browser and was connected to it during the run. The action used that console, and ran commands on it, which I could see. I suspect it is because of this:

Runs:

[umuttopalak]

As shown in the image you sent, the pythonanywhere API only creates a terminal and leaves the activation process to the user. The code I wrote performs the following function: If no terminal exists, it creates an appropriate terminal for itself. Then, as mentioned in the error in the workflow, the terminal needs to be entered once to start the process. Otherwise, if a suitable terminal has already been used to start the process, it works without any issues.

[piyush-jaiswal]

Then this isn't continuous deployment if I have to manually login to pythonanywhere and connect to the console, everytime for pushing code. I am only a git pull and a click away to reloading the site. This should be mentioned in the README, and not left to users to face errors and figure out.

I also don't see how creating a new console helps as that workflow would always fail. There's no time for the user to login and connect to that console. They would always have a failed workflow and would have to connect to the exact console (not create a new one) and somehow run the workflow again, which could involve pushing the same commit again, possibly modifying git history.