jiebi/CodeConvo huggingface dataset:
Code change:
<ins> --- id: 561add10cb82ac38a17213bd title: Full Stack Certificate challengeType: 7 isHidden: false isPrivate: true --- ## Description <section id='description'> </section> ## Instructions <section id='instructions'> </section> ## Tests <section id='tests'> ```yml tests: - id: 561add10cb82ac38a17513bc title: Responsive Web Design Certificate - id: 561abd10cb81ac38a17513bc title: JavaScript Algorithms and Data Structures Certificate - id: 561acd10cb82ac38a17513bc title: Front End Libraries Certificate - id: 5a553ca864b52e1d8bceea14 title: Data Visualization Certificate - id: 561add10cb82ac38a17523bc title: API's and Microservices Certificate - id: 561add10cb82ac38a17213bc title: Legacy Information Security and Quality Assurance Certificate ``` </section> ## Challenge Seed <section id='challengeSeed'> </section> ## Solution <section id='solution'> ```js // solution required ``` </section> </ins>

Related discussion:
text: Some users can claim python, new QA, and new infosec certifications without submitting their required projects on .dev. It seems the api does not find the cert challenge and proceeds by setting the related cert flag on the user object to true. The issue can be resolved by reseeding the db locally. I cannot reproduce this issue at the moment, but I will keep this open in case other users are experiencing the same issue.
Hello! I tested this issue, and I was able to claim the certifications without completing the projects.
could you check if you can see the certification after claiming it? I'm just wondering if this is purely a client-side issue.
I am able to see the four certificates I could claim, yes.
Thanks for checking that. In that case, while it seems likely that it will fine if the database is migrated, the api should definitely default to rejecting certifications it does recognise.
Yes We Can Claim Python Certification Without submitting the Projects.
that's really serious
Code change:
<ins> --- id: 561add10cb82ac38a17213bd title: Full Stack Certificate challengeType: 7 isHidden: false isPrivate: true --- ## Description <section id='description'> </section> ## Instructions <section id='instructions'> </section> ## Tests <section id='tests'> ```yml tests: - id: 561add10cb82ac38a17513bc title: Responsive Web Design Certificate - id: 561abd10cb81ac38a17513bc title: JavaScript Algorithms and Data Structures Certificate - id: 561acd10cb82ac38a17513bc title: Front End Libraries Certificate - id: 5a553ca864b52e1d8bceea14 title: Data Visualization Certificate - id: 561add10cb82ac38a17523bc title: API's and Microservices Certificate - id: 561add10cb82ac38a17213bc title: Legacy Information Security and Quality Assurance Certificate ``` </section> ## Challenge Seed <section id='challengeSeed'> </section> ## Solution <section id='solution'> ```js // solution required ``` </section> </ins>

Related discussion:
text: Currently when you complete/claim a certificate there's an entry on the timeline: <img width="582" alt="Screen Shot 2020-05-27 at 9 37 55 AM" src="https://user-"This doesn't seem to be working for the new Scientific Computing with Python, Data Analysis with Python, and Machine Learning with Python certificates.
I'm a new contributor but I'd like to help out on this.
I think this is mostly working. You just need to refresh the page before it shows up... <img width="598" alt="Screen Shot 2020-05-27 at 11 34 12 AM" src="https://user-"Edit: hmm, it seems to be working locally, but not on .dev - the "view cert" button is there in both environments - it just doesn't show on the timeline on .dev
Ah, interesting. This does seem to work locally but not on .dev for some reason.
This may be a one off issue related to where the new/split certificates (Quality Assurance, Information Security, Scientific Computing with Python, Data Analysis with Python, and Machine Learning with Python) were not seeded to the .dev database for some reason. I can confirm this is working locally like mentioned above. thank you for your interest in contributing. Please check out issues with the label for other things we need help with.
Code change:
Now navigate to your browser and open http://localhost:3001 If the app loads, congratulations - you're all set. Otherwise, let us know by opening a GitHub issue and with your error. <ins> ## Linting Setup You should have [ESLint running in your editor](http://eslint.org/docs/user-guide/integrations.html), and it will highlight anything doesn't conform to [Free Code Camp's JavaScript Style Guide](https://github.com/FreeCodeCamp/FreeCodeCamp/wiki/Free-Code-Camp-JavaScript-Style-Guide) (you can find a summary of those rules [here](https://github.com/FreeCodeCamp/FreeCodeCamp/blob/staging/.eslintrc). Please do not ignore any linting errors, as they are meant to **help** you and to ensure a clean and simple code base. Make sure none of your JavaScript is longer than 80 characters per line.  The reason we enforce this is because one of our dependent NPM modules, [jsonlint](https://github.com/zaach/jsonlint), does not fully support wildcard paths in Windows. </ins> ## Found a bug? Do not file an issue until you have followed these steps:

Related discussion:
text: I'm a new contributor to this project and have run into a few confusing points on that I'd like to clarify for other new contributors. .io - From a few other contributors, I've been told this is no longer used. I'd suggest removing this from the contributor's guide. npm dependencies. This project has a dependency to which is confusing to set up for new NodeJs developers. I'd propose to mention this link to get new Node developers started, especially for Windows, since it involves some unusual installations like Visual Studio for the C++ compiler. isn't any mention of running tests before submitting a pull request. This is something that could be easily missed and cause a pull request to fail the TravisCI build. I've learned that one pre-test dependency, JSONLint, doesn't work for the Windows filesystem. As a workaround, I'd suggest all contributors on Windows to run the tests directly by skipping the pre-test lint run. An additional step could be to manually run JSONLint on individual files, without using the problem-causing wildcard *. For non-Windows contributors, it should be mandatory to run before a pull request.
These all sound like reasonable changes. Go ahead and get a PR going for it.
I'll get started on it.
Code change:
## Instructions <section id='instructions'> <del> Use multiple conditional operators in the <code>checkSign</code> function to check if a number is positive, negative or zero. The function should return "positive", "negative" or "zero". </del> <ins> In the <code>checkSign</code> function, use multiple conditional operators - following the recommended format used in <code>findGreaterOrEqual</code> - to check if a number is positive, negative or zero. The function should return <code>"positive"</code>, <code>"negative"</code> or <code>"zero"</code>. </ins> </section> ## Tests

Related discussion:
text: <!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Describe your problem and how to reproduce it: Bug - Test for below code fails with error: checkSign should use multiple conditional operators. Screenshot -1: ! Screenshot - 2: ! How to reproduce It. Instead of Error: “checkSign should use multiple conditional operators.” Error should be: Using multiple ternary operators in statement-if-true part of ternary operator is not best practice. (Increasing clarity of error message) Add a Link to the page with the problem: Link to ; Link to reporting bug on forum:
I agree that some tweaking makes sense. I'd would help if we can capture the fact that the test fails if a) you aren't using a multiple ternary or b) the ternary isn't in the expected format.
I do not think this is what the challenge asks for: This is the code from the docs: What you have constructed is: I agree, you have accomplished_ the task. However, the expected implemented logic is of the form: So, perhaps we should change the challenge instructions to be more specific as to the format...
Sir, please note: this repository is of . Thank You for your reply.
, haha. Yes, I am well aware. I linked to the Mozilla documentation to retrieve an example of Multiple Conditional Ternary Operators. My point is still entirely valid.
` Please try the above code in this . Please check what is required to pass the challenge.
, I have, and I understand exactly why this issue was created. I am pointing out that the format of your solution is not what is expected, which is clearly seen in the example given in the lesson: I agree, you have accomplished the task. However, the expected implemented logic is of the form: Your solution does not contain logic.
Sir the condition to win the challenge is: Use multiple conditional operators in the checkSign function to check if a number is positive, negative or zero. The function should return "positive", "negative" or "zero". We should Use Multiple Conditional (Ternary) Operators.
Perhaps the error message should be "... multiple conditional operators in the recommended format."
Code change:
## Instructions <section id='instructions'> <del> Use multiple conditional operators in the <code>checkSign</code> function to check if a number is positive, negative or zero. The function should return "positive", "negative" or "zero". </del> <ins> In the <code>checkSign</code> function, use multiple conditional operators - following the recommended format used in <code>findGreaterOrEqual</code> - to check if a number is positive, negative or zero. The function should return <code>"positive"</code>, <code>"negative"</code> or <code>"zero"</code>. </ins> </section> ## Tests

Related discussion:
text: And perhaps adding a note along the lines of "It's is a best practice to format the multiple conditional operators so that each condition is on a separate line, as shown in the example, for readability."
"It's is a best practice to format the multiple conditional operators so that each condition is on a separate line, as shown in the example, for readability." I would be for adding a note similar.
Closed? Was an update to the description merged?
It is not possible to implement if/else if/else logic using ternary Operator. But the task can be accomplished. No, the expected implemented logic is of the form:
Expected solution (one of 6, very similar to your final answer): If-else version A ternary, or multiple ternary, always can be written with if-else. The challenge and the description is accurate. We just want to add a clarifying comment or two to emphasize the best practice formatting for readability.
Nevermind.
It looks to me like adding clarifying comments is the best solution. So, let's leave this open until a PR gets merged.
I'd like to jump on this, if possible. I'm a first-timer but really excited to learn!
Go for it, This should be a good issue for a first-timer. I recommend taking a look at the , and if you get stuck ask away in the
Code change:
<ins> { "name": "Full Stack Certificate", "dashedName": "full-stack-certificate", "order": 5, "time": "", "template": "", "required": [], "superBlock": "certificates", "superOrder": 12, "challengeOrder": [ [ "561add10cb82ac38a17213bd", "Full Stack Certificate" ] ], "isPrivate": true, "fileName": "12-certificates/full-stack-certificate.json" } </ins>

Related discussion:
text: Some users can claim python, new QA, and new infosec certifications without submitting their required projects on .dev. It seems the api does not find the cert challenge and proceeds by setting the related cert flag on the user object to true. The issue can be resolved by reseeding the db locally. I cannot reproduce this issue at the moment, but I will keep this open in case other users are experiencing the same issue.
Hello! I tested this issue, and I was able to claim the certifications without completing the projects.
could you check if you can see the certification after claiming it? I'm just wondering if this is purely a client-side issue.
I am able to see the four certificates I could claim, yes.
Thanks for checking that. In that case, while it seems likely that it will fine if the database is migrated, the api should definitely default to rejecting certifications it does recognise.
Yes We Can Claim Python Certification Without submitting the Projects.
that's really serious
Code change:
<ins> { "name": "Full Stack Certificate", "dashedName": "full-stack-certificate", "order": 5, "time": "", "template": "", "required": [], "superBlock": "certificates", "superOrder": 12, "challengeOrder": [ [ "561add10cb82ac38a17213bd", "Full Stack Certificate" ] ], "isPrivate": true, "fileName": "12-certificates/full-stack-certificate.json" } </ins>

Related discussion:
text: Currently when you complete/claim a certificate there's an entry on the timeline: <img width="582" alt="Screen Shot 2020-05-27 at 9 37 55 AM" src="https://user-"This doesn't seem to be working for the new Scientific Computing with Python, Data Analysis with Python, and Machine Learning with Python certificates.
I'm a new contributor but I'd like to help out on this.
I think this is mostly working. You just need to refresh the page before it shows up... <img width="598" alt="Screen Shot 2020-05-27 at 11 34 12 AM" src="https://user-"Edit: hmm, it seems to be working locally, but not on .dev - the "view cert" button is there in both environments - it just doesn't show on the timeline on .dev
Ah, interesting. This does seem to work locally but not on .dev for some reason.
This may be a one off issue related to where the new/split certificates (Quality Assurance, Information Security, Scientific Computing with Python, Data Analysis with Python, and Machine Learning with Python) were not seeded to the .dev database for some reason. I can confirm this is working locally like mentioned above. thank you for your interest in contributing. Please check out issues with the label for other things we need help with.
Code change:
<ins> { "name": "Full Stack Certificate", "dashedName": "full-stack-certificate", "order": 5, "time": "", "template": "", "required": [], "superBlock": "certificates", "superOrder": 12, "challengeOrder": [ [ "561add10cb82ac38a17213bd", "Full Stack Certificate" ] ], "isPrivate": true, "fileName": "12-certificates/full-stack-certificate.json" } </ins>

Related discussion:
text: <!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --1) The Full Stack Cert claimed date will only show as the current date and not the date it was claimed on. I claimed mine on the 7th of September and checking back regularly I noticed the claimed on date was always the current date. 2) The Full Stack Cert appears as the Legacy Full Stack Cert on a users profile page, clicking this leads to an error as the legacy cert does not exist. It should be in with the new certificates. That being said, on the settings page the link to view the certificate is linked correctly. ${username-here} /full-stack ${username-here} N.A 1) Just the claimed on date. No screenshot necessary. 2) !
Similar to
I am having the same issue with my Full Stack Certificate
Mine as well. Has this been addressed?
Same here - The issued date shows the current date and not the date on which it was originally issued -
Related
Have the same problem: the date of Full Stack Certificate is always a current date.
If there are no records for a fullstack certificate, a good fallback would be going thought the date of the modern certificates and displaying the date of latest claimed certificate.
optimally, we should add a completion timestamp and an id when campers claim a fullstack certificate with a fallback to the last earned cert if a timestamp is not found.
My full stack certification also updates with the current date not the claimed date.
The date on my full stack certificate is showing the date i claim my Responsive Web design certificate ( the first certificate ). and now if i want to see the certificate it is asking me to claim certificate when i claim it will say is like u have claim the certificate and it will not show me the certificate.
This is an ongoing issue, please use the reactions instead to assert "me too". Potential approach for fixes: and
Also related to the Full Stack cert – the date seems to be the date the first certification was claimed, not the date the full stack certification was claimed:
The fallback is not working properly and I should have caught that. It's not a tricky fix, but I'll make sure it works this time!
Ok thenks On May 5, 2020 11:04, "Oliver Eyton-Williams" <:
Code change:
"assert(typeof(myBike.addUnit) === 'undefined', 'message: <code>myBike.addUnit</code> should remain undefined.');" ], "challengeSeed":[ <del> "//Let's create an object with a two functions. One attached as a property and one not.", </del> <ins> "//Let's create an object with two functions. One attached as a property and one not.", </ins> "var Car = function() {", "  this.gear = 1;", "  function addStyle(styleMe){",

Related discussion:
text: Challenge has an issue. User Agent is: <codeMozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.99 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code: There's a typo in the top comment. Instead of reading "Let's create an object with a two functions." it should read "Let's create an object with two functions."
Code change:
If the `bio` text is greater than `50` characters, you should extract the first 50 characters with `slice()` and replace the rest with `...`. Don't forget that indexes are zero-based. ```js <del> assert.match(code, /<ps*class=("|')bio1>${s*bio.lengths*>s*50s*?s*bio.slice(s*0,s*49s*)s*+s*("|')...2s*:/) </del> <ins> assert.match(code, /<ps*class=("|')bio1>${s*bio.lengths*>s*50s*?s*bio.slice(s*0,s*50s*)s*+s*("|')...2s*:/) </ins> ``` If the `bio` text is less than 50 characters, use the `bio` text directly. ```js <del> assert.match(code, /<ps*class=("|')bio1>${s*bio.lengths*>s*50s*?s*bio.slice(s*0,s*49s*)s*+s*("|')...2s*:s*bios*}</p>/) </del> <ins> assert.match(code, /<ps*class=("|')bio1>${s*bio.lengths*>s*50s*?s*bio.slice(s*0,s*50s*)s*+s*("|')...2s*:s*bios*}</p>/) </ins> ```

Related discussion:
text: The test is expecting to use 49 in the slice. Which seems like could have been an error….It should be 50 The test is expecting to use 49 in the slice. Which seems like could have been an error….It should be 50 No response Device: [Laptop] OS: [Windows 10] Browser: [ Chrome] No response
Yes, you are correct. The test is incorrect. I will go ahead and open this up for contribution for the community. Please read through the guidelines first. We do not assign issues. If you are interested in working on this, then work on the issue and create a PR. Several changes need to be made Here is the first file that needs to be updated For step , you will need to update these two tests here to use the correct value of 50 for the slice method. You will also need to update the seed code for steps 28 and 29. Remember that step 29 also has the complete solution which needs to be updated as well Happy coding
Code change:
"description": [ "So we've proven that id declarations override class declarations, regardless of where they are declared in your <code>style</code> element CSS.", "There are other ways that you can override CSS. Do you remember inline styles?", <del> "Use an <code>in-line style</code> to try to make our <code>h1</code> element white. Remember, in line styles look like this:", </del> <ins> "Use an <code>inline style</code> to try to make our <code>h1</code> element white. Remember, in line styles look like this:", </ins> "<code>&#60;h1 style="color: green"&#62;</code>", "Leave the <code>blue-text</code> and <code>pink-text</code> classes on your <code>h1</code> element." ],

Related discussion:
text: Challenge has an issue. User Agent is: <codeMozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:50.0) Gecko/ Firefox/50.0</code. Please describe how to reproduce this issue, and include links to screenshots if possible. There is inconsistent spelling in the instructions. Is it "inline" or "in-line"?
thanks for the issue. They should all be .
Code change:
smOffset={ 1 } xs={ 12 } > <del> <p </del> <ins> <div </ins> className={ `${ns}-description` } dangerouslySetInnerHTML={{ __html: info }} />

Related discussion:
text: <!-- freeCodeCamp Issue Template --<!-- Please provide as much detail as possible for us to fix your issue --<!-- Remove any heading sections you did not fill out --<!-- NOTE: If your issue is CodePen Project / Test Suite related, please open it using the below URL instead --<!-- --<!-- Insert link to challenge below -- <!-- Describe below when the issue happens and how to reproduce it --going to step 2/2, the last 3 paragraphs of step 1/2 are still displayed I click "Go to my previous step", the same 3 paragraphs are displayed twice, with different font <!-- Describe your workspace in which you are having issues--Browser Name, Version: Chrome 60.0.3112.90 Operating System: Windows NT 10.0; Win64; x64 Mobile, Desktop, or Tablet: Desktop <!-- If relevant, paste all of your challenge code in here --<!-- Add a screenshot of your issue --
Can I give it a try?
Confirmed. Go ye forth
Code change:
: '/' + clientLocale; module.exports = { <ins> flags: { DEV_SSR: false }, </ins> siteMetadata: { title: 'freeCodeCamp', siteUrl: homeLocation

Related discussion:
text: Potentially, upgrading to MongoDB 4 has broken the GitPod Development. I am looking into it, but here are the errors: Shortened Error (me trying to restart Mongodb, after an initial crash): <details<summarymongod --version</summary</details<details<summaryFull Error</summary</details<details<summaryPotentially relevant client error</summary</details
To the best of my knowledge no code changes were made to upgrade MongoDB on GitPod. The base image using MongoDB 4 needs to be looked at. In other words, the move to MongoDB 4.0.x (not same as 4.x) breaking GitPod is coincidental?
To be honest, I have no idea. The base image: Source: Docs: From what I can see, the docker hub provides no information about the image, but the GitHub repo suggests the image has not been updated in 4 months. To me, this suggests an issue definitely on our side.
That is pretty easy to confirm. On GitPod you should be able to checkout a commit (any commit) that was best known to working from a few days ago. A diff should bring you closer to the root cause, say for example a dependency update somewhere. But to prevent beating around the bush, I think we instead provide our own base image with requirements set in the local setup file. Let me know if you need help with this & thanks for looking into it.
Update: There is a high likelyhood I have been looking into the wrong section for where the problem is. Here is the original error which lead me to look into the database stuff: <details<summaryClient Error</summary</detailsSteps to reproduce: 1) Open any instance off fCC GitPod 2) Wait for client to finish developing 3) Open browser preview of app 4) See client crash with above error I tried killing the database, restarting it, and restarting the client, but the app crashes, everytime the browser tries to load.
I can't reproduce this, sorry! If I go to it just works. I know we've talked about this before, but do you have any special settings for GitPod besides Enable feature preview? Environment variables are the only thing I can see that might cause an issue.
Other than the Feature Preview, everything is bog-standard. I will try to disable FP.