Skip to content

fix(challenges): Fix octal escape sequence error#16385

Closed
scissorsneedfoodtoo wants to merge 5 commits intofreeCodeCamp:stagingfrom
scissorsneedfoodtoo:fix/Octal-escape-sequences-error
Closed

fix(challenges): Fix octal escape sequence error#16385
scissorsneedfoodtoo wants to merge 5 commits intofreeCodeCamp:stagingfrom
scissorsneedfoodtoo:fix/Octal-escape-sequences-error

Conversation

@scissorsneedfoodtoo
Copy link
Copy Markdown
Contributor

@scissorsneedfoodtoo scissorsneedfoodtoo commented Dec 31, 2017

Pre-Submission Checklist

  • Your pull request targets the staging branch of freeCodeCamp.
  • Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
  • You have only one commit (if not, squash them into one commit).
  • All new and existing tests pass the command npm test. Use git commit --amend to amend any fixes.

Type of Change

  • Small bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds new functionality)
  • Breaking change (fix or feature that would change existing functionality)
  • Add new translation (feature adding new translations)

Checklist:

  • Tested changes locally.
  • Addressed currently open issue (replace XXXXX with an issue no in next line)

Closes #16396

Description

Another user is having a problem with their pull request because the
Travis Cl build keeps failing. Each time the Travis Cl build throws an
error about an octal literal escape sequence not being allowed in strict
mode, and it seems to happen with the Create a Priority Queue Class
challenge.

BREAKING CHANGE: None

AungMyoKyaw and others added 2 commits December 31, 2017 15:09
Another user is having a problem with their pull request because the
Travis Cl build keeps failing. Each time the Travis Cl build throws an
error about an octal literal escape sequence not being allowed in strict
mode, and it seems to happen with the Create a Priority Queue Class
challenge.

BREAKING CHANGE: None
@BerkeleyTrue BerkeleyTrue added the status: waiting review To be applied to PR's that are ready for QA, especially when additional review is pending. label Dec 31, 2017
@raisedadead
Copy link
Copy Markdown
Member

@AungMyoKyaw will you be interested in QA for this?

@scissorsneedfoodtoo
Copy link
Copy Markdown
Contributor Author

@raisedadead, Sorry! I should have thought of this sooner.

If @AungMyoKyaw can add the code here to the pull request that keeps failing the build, then we don't need to coordinate between two separate pull requests to solve one issue.

@raisedadead
Copy link
Copy Markdown
Member

Hi @scissorsneedfoodtoo scissorsneedfoodtoo#1
Please squash and merge there.

That will update this PR of yours.

@scissorsneedfoodtoo
Copy link
Copy Markdown
Contributor Author

Sure thing! I'll do that now.

Another user is having a problem with their pull request because the
Travis Cl build keeps failing. Each time the Travis Cl build throws an
error about an octal literal escape sequence not being allowed in strict
mode, and it seems to happen with the Create a Priority Queue Class
challenge.

BREAKING CHANGE: None

feat(euler-problem): Add tests and solution for Problem 4: Largest palindrome product
@camperbot
Copy link
Copy Markdown
Contributor

@scissorsneedfoodtoo updated the pull request.

@scissorsneedfoodtoo
Copy link
Copy Markdown
Contributor Author

Turns out I was way off base. There was no problem with the "Create a Priority Queue Class" challenge, and it was either the tests, solution, or both from Euler "Problem 4: Largest palindrome product" causing the issues.

@raisedadead
Copy link
Copy Markdown
Member

Yikes, we have some unwanted commits in there.

I am sorry I should have been clearer for you in the instruction earlier, that you should have had to only hit the 'Squash and merge' button on the PR that I created.

Never mind, I'll take a look asap and fix this.

Sorry once again.

@scissorsneedfoodtoo
Copy link
Copy Markdown
Contributor Author

scissorsneedfoodtoo commented Jan 3, 2018

@raisedadead, I'm sorry about that! I should have pressed the button, but ended up running the autogen commands instead and played with the files trying to solve the issue. Ended up messing up the commit pretty badly!

@raisedadead
Copy link
Copy Markdown
Member

No worries, it git and hence fixable..! BTW just to confirm we want the commit you have for this PR originally and the commit from @AungMyoKyaw 's original PR.

i.e:

  1. 5ec8341
  2. 4521e20

Correct ?

@scissorsneedfoodtoo
Copy link
Copy Markdown
Contributor Author

Actually, maybe the best thing to do is close this. Turns out the problem has to do with the solution in @AungMyoKyaw's original PR. If we remove the solution there, npm test should pass just fine.

@raisedadead
Copy link
Copy Markdown
Member

Okay, then lets proceed with that discussion there and close this

@scissorsneedfoodtoo
Copy link
Copy Markdown
Contributor Author

Okay! Thanks again for all your help. Sorry about the trouble.

@raisedadead
Copy link
Copy Markdown
Member

No worries thanks for all the effort in this!

@BerkeleyTrue BerkeleyTrue removed the status: waiting review To be applied to PR's that are ready for QA, especially when additional review is pending. label Jan 3, 2018
@scissorsneedfoodtoo scissorsneedfoodtoo deleted the fix/Octal-escape-sequences-error branch January 4, 2018 12:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants