#Since upgrading from free to pro account

1 messages · Page 1 of 1 (latest)

hollow thorn
#

See this thread: #1330400289936642119 message

Working on a fix for this. What OS and shell are you using? Also does this happen with all commands Cascade runs or just git ones?

#

This is a bug but unrelated to Pro vs. Free

small idol
#

Hey

#

So on Mac OS 15.2

#

Its happening with all commands it tries to run

#

I reverted to asking it to do a more simple command as it stopped working for me during a more complex command involving a service I was running in docker.

#

As in after stopping cascade after leaving it to think for a good five minutes, I thought I'd restart and test again, same behaviour.

#

Then I asked it to check git status to review files we were working on and noticed it was hanging just trying to run git status

#

/bin/zsh

hollow thorn
#

Hm... ok that's definitely a bug. Can you see the IDE terminal it creates to run these commands (should be called cascade). Can you see if the commands successfully ran there?

small idol
#

Checking

#

From what I can see it ran the first command, showed the result but then tapped out so to speak, it then has not run any of the futher attempts

hollow thorn
#

Sorry not fully following. Are you able to send a screenshot?

small idol
#

I dont know if screenshot would help

#

I have 2 cascade terminals

#

the first one shows the output of the original command that froze

#

the second cascade terminal shows an older git commit message

#

The subsequent attempts to run git status in cascade have not produced a new cascade terminal or added to the existing terminals

#

It seems like when cascade was trying to process a command, it got me the output but then threw a wobbly and didn't recover / continue. Since that each time it's tried to run a command it throughs a wobbly and does not run in either a new cascade terminal or an existing cascade terminal.

hollow thorn
#

What's a wobbly?

small idol
#

As in spinning wheel

#

No response, thinks its still trying to process the command

#

Doesnt timeout

#

Eg 'Running terminal command' but just have spinning wheel

hollow thorn
#

Got it, so Cascade is currently stuck spinning trying to execute git status.

The two Cascade-managed terminals are both idle (i.e. not actively running a command)?

Did either of the two terminals run git status most recently?

Trying to understand if the command failed to execute entirely or it did execute and the result wasn't propagated back to the Cascade panel.

small idol
#

Exactly

#

No neither of the terminals ran git status

#

But I can see the output of the first time I noticed the spinning wheel

#

Which was a different command

hollow thorn
#

Hm... If you cancel the running command (hit the x in the top right) and ask it to run it again, does it run the command in either Cascade terminal or create a new terminal?

What command did it run the first time? Is the command running in one of ther terminals?

small idol
#

The first command was checking a docker service for something

#

Okay weird, I notice in the terminal it says 'Log file already in use' after stopping and starting again

#

So in the first open cascade terminal, after it tried to run git status again, it displayed over the top of 'END' 'Log file already in use ( Press Return )

#

After pressing return in terminal the git status still hanging on spinning wheel and nothing happens

#

Okay, I just restarted Windsurf and it seems to be working

hollow thorn
#

What is "Log file already in use"? Is that from a command you / it ran in the terminal previously?

#

Did it try to run git status in a terminal while another command was already running there?

small idol
small idol
#

Sorry, I missed that the previous command was still running and needed to be ended so to speak.

#

Perhaps that is what was cuasing all my issues all along

hollow thorn
#

This is good to know. Seems like if somehow there's an actively running command and Cascade tries to run another command in the same terminal we may get into a bad state. Just to check, did you run the previous command that was actively running (presumably the docker compose...) or did Cascade? It's supposed to know which commands it ran are still running to avoid these sort of issues (unless you reloaded the window while the command was still running).

small idol
#

Cascade ran the previous docker command

#

I dont think I reloaded the window while it was still running

#

I noticed in the cascade chat window that the spinning wheel had been spinning for an abnormal amount of time

#

But yes, the original docker command that seems to be at the root of the issues I was having was run by cascade

#

Something else I am just noticing, might be useful. I use a start and stop script to restart docker services. When cascade runs them, it asks me if I want to accept the previous changes after running the scripts.

hollow thorn
#

What do you mean by accept the previous changes? Can you send a screenshot of this behavior?

small idol
#

I'll get a screenshot next time it happens. But lets say cascade wants to change some files and then it want to restart the docker services, the accept all changes button doesn't appear at the bottom of cascade until you run the command to restart the services, making me think that the previous changes havent been applied. I am then clicking accept all changes in cascade at the bottom and restarting the docker services again.