I used the exact same SQL command as @multisonic. UPDATE characters SET favorite_color=‘Orange’ WHERE name=‘Daisy’;
Hey @shreecheryl & @multisonic,
It appears you have both done it correctly. The test that is supposed to be used is here. It checks that your database has the correct info, and both of the screen shots appear to be correct.
There’s some strange bugs that occur sometimes when going through these tutorials. We are continuously trying to improve their stability. One of them is that sometimes a new test doesn’t properly load and/or the instructions get a little misaligned with the tests. I think something like that has happened here. The error message you say you see is, “characters” should have the correct rows for “Daisy” and “Yoshi”
. It looks like the test for that message is two before the one you are seeing. Change Daisy’s color back to yellow to see if it will pass: UPDATE characters SET favorite_color=‘Yellow’ WHERE name='Daisy’;
That should be all you would need to do to pass the test two before the one the instructions show.
Not exactly sure what will happen if it does. The instructions may stay the same, but the next test would load - still one before what the instructions show. If you made it that far, enter SELECT * FROM characters;
to pass that step and it should be caught back up to the instructions.
Let us know if you have any luck with any of that. If not, I can try and help some more.
If all else fails, you can always start the tutorial from the beginning again. I know it stinks, but it does make for some good practice
I am COMPLETELY stuck now. I am now trying to start over and nothing is working. I have closed and restarted everything several times and it is unable to complete the Remote-Containers: Rebuild and Reopen in Container command. I don’t know what else to do. Is it possible that I need to delete my current copy of RDB and clone it to my computer again?
Thanks for the guidance. Unfortunately, using the previous command to “trick” the misaligned test doesn’t work.
When I tried running: UPDATE characters SET favorite_color='Yellow' WHERE name='Daisy';
, I got a test failure message “You should have the correct values for ‘Daisy’”.
When I then tried to re-run the command UPDATE characters SET favorite_color='Orange' WHERE name='Daisy';
, I get the earlier test failure message: “‘characters’ should have the correct rows for ‘Daisy’ and ‘Yoshi’”
In your experience, how likely does it seem that we would encounter this same bug at this same point if we started from the beginning of this particular tutorial?
Thanks again for all your work on this. Let me know if I can provide any further information to help debug this.
Hey @shreecheryl,
Sorry for your troubles. Your command to build the container worked the first time you tried - or at least one other time. You probably tried, but I would close everything and try again. If it keeps happening, you could check the logs for errors and see what they say. Maybe try to troubleshoot or share them here. I doubt that re-cloning the rdb-alpha repo would help - nothing changed in it. I guess unless you cloned it a while ago - the last change was November 30th.
Hey @multisonic,
So what I think happened for you is that a new test loaded, and the old test didn’t get commented out. It might be tough, and I can’t promise it will work, but I can try to help fix it. You need to change the test files within the project. There’s a .vscode/settings.json
file, with a property, that is keeping them hidden. Open a regular terminal (not the psql one in the images), and enter this in it:
sed -i -e 's/".freeCodeCamp": true,/".freeCodeCamp": false,/g' ~/project/.vscode/settings.json
That will unhide the tutorial files in your vscode. In your screenshot, the files aren’t shown. You would need to click that top left button that looks like two pieces of paper to see them. You should then see a .freeCodeCamp
folder - expand it and the test
folder within it. Look at the few most recent test files - they will be something like 680.test.js
and 690.test.js
. All of them, except for the most recent one (likely 690.test.js
) should be commented out. Comment out all of them except the most recent one - carefully - only comment out the files I suggested and don’t change anything else. If that’s the problem, the tests might run automatically and pass after you comment it out - assuming your database still has Orange
for Daisy’s color. If the database isn’t correct any more, change her color back - or whatever else you need to do. Good luck - I’ll be here.
Thank you for getting back to me. I lost my patience yesterday so I ended up deleting/uninstalling everything and starting over from scratch. I am up and running again but I am staying away from the Mario Database tutorial until I am sure it is okay. Has anyone successfully completed it?
I completed the tutorial about a couple of weeks ago.
Sometimes when I go through the challenge one of the challenges doesn’t register and I have to reset it for it to go through.
But I am not sure why your mario database isn’t working
Hopefully it will work now
If you are skipping mario right now, then you will probably have to skip celestial bodies right now too since the mario lessons prepare you for that project.
You can do the Learn Bash scripting by building 5 projects and then try mario again later.
Thank you so much for all of your help, Jessica. I appreciate you!
This method worked for me. After running the command to unhide the test files I found that 670.test.js was not commented out. Once I did that I received a “Level Complete” and moved on to 700.
Ran into some issues that completely blocked tests passing out of the gate yesterday after install on Win10. The very first tests would not pass after rebuilding container w and w/o cache, resetting lesson, resetting terminal, etc. Theorizing it may be a bug on Windows and/or with my VScode extensions. I also had changed the default terminal to Git Bash months ago…at any rate I am going to try out on my macbook instead today. I did finally get the first test to pass after multiple resets, but was then encountering the same thing on the second (‘pwd’) test. Here’s video of what I was experiencing:
Youtube clip of my issue
I did. Up and running fine on Mac. I am still uncertain as to the root of the issue on Win10, but I am grateful it’s without a hitch on the Mac.
Thanks for the followup!
Thanks for the solution!! I was really struggling with it.
No it does not work (having the same exact issue)
But what I noticed changing is that before resetting Daisy to yellow the error (upon clicking “run”) was “characters” should have the correct rows for “Daisy” and “Yoshi”
But if I changer Daisy back from Orange to Yellow then the error becomes “you should have the correct values for Daisy”
What I think also may be the issue here is than when you try (for the first time ) to change the color of Daisy, then Daisy gets on the last row of the table (despite having id 6 and Yoshi id 7 ) maybe thats just a noob remark and its how things work but I found it strange
Anyway trying to revert her back to the 6th row still didnt work
A number of people have gotten around this by following the instructions in the comment above. I would try that @papajo - you’re still seeing the test text for the lesson a few before the one you are on, so that test is still running.
I also had the same problem in the last exercise, so I commented the 1670.test.js to pass the test, because I had the same problem there.
Yes although I am a noob I did not understand what “commenting out” meant in this particular case, I assume to rename them?
What I did is just move the 690 test file along with a couple of other non test files (e.g pg.log ) one folder back, rm -r the test folder, create a new test folder move the files to that test folder and then it works.
I would suggest adding such a script in the “reset” function (so delete all test files except the current one) as a workaround, I noticed that they eventually get replaced once you pass the test so no harm done.
And again I am new here so if you are not the person for that please refer me to the person I should message this to.
I would also like to suggest an additional lesson (after the bash lesson and before the mario database lesson or exactly after it ) When I started to learn SQL in linux I found it hard to:
A) restore a bak file because of the graphical environments -except azuredatastudio which I initially did not use- did not have such an option) and in general how to back up and how to restore (what to look for e.g I saw in restore dialogues -besides the absence of an option to restore a bak file- that there are more than 1 filetypes that are needed simultaneously in order to restore a database ? what are they ? etc.
B) how to configure an SQL server and link it with a program such as SQL workbench
C) I couldnt make sense (and still cant) of the general structure e.g what are master databases, where can I list the users and change their credentials why am I logging in locally as SA by default? Who is SA and what does it stand for? how to change that(like not only change a username/password but list and link user privileges to a database preferably via console commands)?
D) I was getting a “couldn’t find map” error when running my queries despite them running successfully and showing their desired outcome, I suppose this has to do with something about the schema . Adding tables and rows is fine, but what is the “proper etiquette” to make a fully structured database e.g do I need to enter some data about the schema or info/code about the general structure etc?
I mean besides understanding the statements being able to have a solid grasp of the general environment is also something that one needs to know it creates lots of stress to me learning more code on sql without knowing the above.
Just to let you know - I had the exact same problem and had to comment out test 670 to get it working again. Hope this helps.
I reset the exercise and switch the positions when filling the table:
INSERT INTO characters(name, homeland, favorite_color) VALUES (‘Yoshi’, ‘Dinosaur Land’, ‘Green’), (‘Daisy’, ‘Sarasaland’, ‘Orange’);
It worked for me.