Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Learn Bash by Building a Boilerplate - Glitched in step 106.5 #54432

Open
Emeryx opened this issue Apr 17, 2024 · 4 comments
Open

Learn Bash by Building a Boilerplate - Glitched in step 106.5 #54432

Emeryx opened this issue Apr 17, 2024 · 4 comments
Assignees
@moT01
Labels
scope: curriculum Lessons, Challenges, Projects and other Curricular Content in curriculum directory. status: discussing Under discussion threads. Closed as stale after 60 days of inactivity. type: bug Issues that need priority attention. Platform, Curriculum tests (if broken completely), etc.

Comments

@Emeryx
Copy link

Emeryx commented Apr 17, 2024

Describe the Issue

I at least think it's step 106.5? Weird name for a step, I found it here https://github.com/freeCodeCamp/learn-bash-by-building-a-boilerplate/blob/main/TUTORIAL.md#1065-list

The previous step asks to move a file to the folder before the current one the terminal is in, Then this step asks to check if the file was moved to another folder using ls

In my case, I think I went too fast and the file is still already located in the same folder, And on the other folder

image

(Even after resetting, This is the same result)

Removing the requested file and hitting ls again does not work and does not get me past this stage

image

I'm not sure what to do with this bug, I am really 98% certain this is not my fault and may need a fix

Thanks in advance

Affected Page

https://www.freecodecamp.org/learn/relational-database/learn-bash-by-building-a-boilerplate/build-a-boilerplate

Your code

camper: /website$ cd /workspace/project/website/images
camper: /images$ ls

Expected behavior

I expect to pass the test after hitting ls on the terminal but the conditions aren't met because when i reset my program it doesn't update to the correct state, and updating it manually does not help, Neither does removing the file from both folders, Creating it on images and moving it to the parent folder again

Screenshots

No response

System

  • Device: [e.g. iPhone 6, Laptop]
  • OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04]
  • Browser: [e.g. Chrome, Safari]
  • Version: [e.g. 22]

Additional context

No response
@Emeryx Emeryx added scope: curriculum Lessons, Challenges, Projects and other Curricular Content in curriculum directory. status: waiting triage This issue needs help from moderators and users to reproduce and confirm its validity and fix. type: bug Issues that need priority attention. Platform, Curriculum tests (if broken completely), etc. labels Apr 17, 2024
@moT01
Copy link
Member

moT01 commented Apr 18, 2024 •
edited

I was unable to reproduce this. If it was cause by you going too fast, I'm not sure how we can fix that.

The test for that step checks that you entered the ls command while in the project/website/images folder.

It appears like you did that @Emeryx. You didn't happen to rename the project folder by accident? Unlikely.

We can try some debugging. What do you see when you enter this command: cat /workspace/project/freeCodeCamp/.mocharc.json

You could check the CodeRoad logs to see if something happened between steps. Click the OUTPUT tab in the terminal, you can see it in your screenshots - then find the dropdown on the right and select CodeRoad (logs) - then see what the commands say between steps 1060.1 and 1065.1 (It's just two steps.) - and share the output if you could.

@Emeryx
Copy link
Author

Emeryx commented Apr 18, 2024

I haven't renamed the folder, I went through all the steps methodically

Upon writing down cat /workspace/project/freeCodeCamp/.mocharc.json i get:

{
  "spec": ["./test/1065.test.js"],
  "reporter": "mocha-tap-reporter",
  "fail-zero": false,
  "timeout": "5000",
  "grep": "/./"
}

Accessing my current CodeRoad Logs (After restarting the Gitpod workplace), It looks like this and stays like this even when I go to the images directory and hit ls

coderoad v0.19.4
STATE: "Setup.Startup"
ROUTE: "Setup.Startup": On level unknown, step unknown
EDITOR_STARTUP
Continuing tutorial from progress: level 1065 step 1065.1
LOAD_STORED_TUTORIAL
EDITOR_TUTORIAL_CONTINUE_CONFIG
Tutorial: Learn Bash by Building a Boilerplate (2.0.0)
Command: ./freeCodeCamp/setup.sh
COMMAND_START
Calling command: ./freeCodeCamp/setup.sh
EDITOR_LEVEL_ENTER
EDITOR_STEP_ENTER
STATE: "Tutorial.Level.Load"
ROUTE: "Tutorial.Level.Load": On level 1065, step 1065.1
STATE: "Tutorial.Level.Normal"
ROUTE: "Tutorial.Level.Normal": On level 1065, step 1065.1
Calling command: git log -n 1 --pretty=format:%s 010dcccfea5e53774228ef332f66d16fb431b00e
Calling command: git log -g --grep='1065.1'
Command output: 
COMMAND_SUCCESS
Command: ./freeCodeCamp/reset.sh
COMMAND_START
Calling command: ./freeCodeCamp/reset.sh
Calling command: git cherry-pick -X theirs 010dcccfea5e53774228ef332f66d16fb431b00e
Command output: 
COMMAND_SUCCESS
cherry-pick-commit failed: Command failed: git cherry-pick -X theirs 010dcccfea5e53774228ef332f66d16fb431b00e
error: Cherry-picking is not possible because you have unmerged files.
hint: Fix them up in the work tree, and then use 'git add/rm <file>'
hint: as appropriate to mark resolution and make a commit.
fatal: cherry-pick failed

Calling command: git stash --include-untracked
STATE: "Tutorial.Level.Normal"
ROUTE: "Tutorial.Level.Normal": On level 1065, step 1065.1
STATE: "Tutorial.Level.Normal"
ROUTE: "Tutorial.Level.Normal": On level 1065, step 1065.1
STATE: "Tutorial.Level.Normal"
ROUTE: "Tutorial.Level.Normal": On level 1065, step 1065.1
STATE: "Tutorial.Level.Normal"
ROUTE: "Tutorial.Level.Normal": On level 1065, step 1065.1

I guess it will not show information about steps 106

@Emeryx
Copy link
Author

Emeryx commented Apr 18, 2024

Oh my god. When pressing the run button on CodeRoad it finally got me to the next stage, I just haven't done that - It always worked automatically before

Still with the header.png being present though

image

@naomi-lgbt naomi-lgbt added status: discussing Under discussion threads. Closed as stale after 60 days of inactivity. and removed status: waiting triage This issue needs help from moderators and users to reproduce and confirm its validity and fix. labels Apr 22, 2024
@moT01
Copy link
Member

moT01 commented Apr 26, 2024

The tests are supposed to run automatically. Something happened that caused them to stop doing that. It likely wasn't anything you did. I'm not quite sure what causes that - it's difficult to reproduce. Curious, are you running the course in Gitpod or locally?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@moT01 moT01

Labels
scope: curriculum Lessons, Challenges, Projects and other Curricular Content in curriculum directory. status: discussing Under discussion threads. Closed as stale after 60 days of inactivity. type: bug Issues that need priority attention. Platform, Curriculum tests (if broken completely), etc.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@moT01 @naomi-lgbt @Emeryx