Challenge
Take a look at the stderr.txt file. The error was redirected to the file and nothing printed in the terminal. You used 2> to redirect stderr . Similarily, you can use 1> to redirect stdout . Enter echo hello bash again and use it to redirect stdout to the stdout.txt file.
What’s happening
I seem to enter the correct command but I get prompt from CodeRoad saying I need to enter the correct command
The command I’m entering is echo hello bash 1> stdout.txt
I have also tried echo hello bash > stdout.txt as well as echo hello bash 1>> stdout.txt just in case but that didn’t work either
I also tried restarting GitPod and CodeRoad but that didn’t help
I am using the latest Microsoft Edge browser on windows 11.
1 Like
That happened to me too. I’m using Firefox on Linux.
I did those things also, and even tried with echo "hello bash" 1> stdout.txt with no success. I don’t know what is the problem.
Hi! Don’t ask me why, but I’ve just entered the bad_command 2> stderr.txt command and it succeed! 
Hope it helps you!
2 Likes
Thanks! That worked. Maybe it is a good thing to not always do as you are told!
Is there a place to let them know there is a bug in the exercise, so they can fix it?
1 Like
I already made a post on the github for bug reports about the issue, and I’ve updated them about the situation with wrong command passing the test so it should hopefully be fixed soon
2 Likes
I had the same problem, thanks for the solution! I found another problem a few steps later and also found the solution for it:
This was the task:
Enter the same command but use redirection to set the stdin to name.txt
I could succeed to the next step by entering the command without the < . I hope it helps those with the same problem.