jiebi/CodeConvo huggingface dataset:
Change:
# --description-- <del> Let an be the largest real root of a polynomial $g(x) = x^3 - 2^n times x^2 + n$. </del> <ins> Let $a_n$ be the largest real root of a polynomial $g(x) = x^3 - 2^n times x^2 + n$. </ins> For example, $a_2 = 3.86619826ldots$

Discussion:
he Project euler problem 356 has a format issue Confront with To fix this issue you will need to change this file so that the beginning of the description is correctly formatted with a pedix: will need to be written as Please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this. An issue with the help wanted or first timers only label is open for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors. Sometimes we may get more than one pull requests. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.
Change:
const client = new MongoClient(MONGOHQ_URL, { useNewUrlParser: true }); <del> log('Connected successfully to mongo'); </del> const db = client.db('freecodecamp'); const user = db.collection('user');

Discussion:
when mongodb is off at dev environment and someone trying to run seed script 'connected successfully to mongo' message displayed 'pnpm run seed' mongo down to run 'pnpm run seed' will see errror message at the terminal but still at the begining - 'connected successfully to mongo' message displayed in case mongodb is not running - you should see Failed to connect to mongo message ! 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] No response
hi i would like to work on this issue
Thanks for the report, and thanks for the offer of help, Anyone is free to work on this, but we recommend new contributors read our contribution guide first:
HI I WOULD LIKE TO WORK ON THIS ISSUE
Hey the is up, can you help me take a look at it? Thanks.
Change:
var dashedName = !{JSON.stringify(dashedName)}; var challengeType = !{JSON.stringify(challengeType)}; var started = Math.floor(Date.now()); <del> .col-xs-12.col-sm-12.col-md-5.col-lg-6 </del> <ins> .col-md-5.col-lg-6 </ins> .editorScrollDiv(style = "overflow-y: auto; overflow-x: hidden;") #mainEditorPanel form.code

Discussion:
A camper relayed this to me: There is some problem with the first challenge ending button on android with firefox browser. And in this moment I tried in chrome too, the issue is the same, the button is not active after the challenge is done. Xperia Z1 compact, android: 5.0.2, firefox: 39.0 Chrome: 43.0.2357.93
This is an issue whenever the screen size is small. It will also happen on a desktop if you resize the window to half screen or less.
Change:
browser.assert.success(); browser.assert.text('span#name', 'Marco'); browser.assert.text('span#surname', 'Polo'); <del> browser.assert.element('span#dates', 1); </del> <ins> browser.assert.elements('span#dates', 1); </ins> done(); }); }

Discussion:
<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --At the affected page the following code snippet is given: But, according to the documentation of the function, the second argument is supposed to be a message and not the number of elements found. To check that an element exists n number of times, assert.elements() should be used. Affected page System (please complete the following information): Device: Laptop OS: Windows 10 Browser: Firefox Version: 86.0 Additional context Add any other context about the problem here.
Hello there, Thank you, for pointing this out. I can confirm this is incorrect. I am opening this up to first timers, and expect the best change to be: 1) Change the lesson to include () 2) Change the test to look for instead of (test is located in same file as lesson) An issue with the help wanted or first timers only label is open for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors. If you would like to contribute, and have not read the contributors docs, please do so here: If you have any issues with contributing, be sure to join us on the , or on the
Change:
Your `section` element should have a closing tag. Closing tags have a `/` just after the `<` character. ```js <del> assert(code.match(/</section>/)); </del> <ins> assert(code.match(/</sections*>/i)); </ins> ``` The entire `section` element should be between the opening and closing tags of the `main` element.

Discussion:
The catphotoapp project’s step 16 asks users to use a section element however if a user type Section as the tag name, the test rejects the code even though html tags are supposed to be case insensitive. It is expected that this code passes since the correct section element is being created. No response Not applicable Issue found on the forum
Change:
The `.split()` method takes a string and splits it into an array of strings. You can pass it a string of characters or a RegEx to use as a separator. For example, `string.split(",")` would split the string at each comma and return an array of strings. <del> Use the `/,s*/g` regex to split the `value` string by commas. You can tweak it based on the number of spaces seperating your values. Store the array in an `array` variable. </del> <ins> Use the `/,s*/g` regex to split the `value` string by commas. You can tweak it based on the number of spaces separating your values. Store the array in an `array` variable. </ins> # --hints--

Discussion:
We have a spelling error for step 3 of the stats calculator project. The word separating is spelled wrong in the description. see explanation above see explanation above No response 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] No response
This has been opened for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors. If you would like to contribute and have not read the contributors docs, please do so here: If you have any issues with contributing, be sure to join us on the , or on the Happy coding
Change:
exports.preSubmit = function(req, res) { var data = req.query; <del> var cleanData = sanitizeHtml(data.url); </del> <ins> var cleanData = sanitizeHtml(data.url, { allowedTags: [], allowedAttributes: [] }).replace(/&quot;;/g, '"'); </ins> if (data.url.replace(/&/g, '&amp;') !== cleanData) { <del> debug('data and cleandata', data, cleanData, data.url === cleanData); </del> req.flash('errors', { msg: 'The data for this post is malformed' });

Discussion:
<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Test for this lesson may not check the syntax for any constructor syntax, instead looks like it's tested by output. EIther user provide the constructor(correct/expected way) or not, challenge passes. Browser Name: Chrome Browser Version: 67 Operating System: Win7
I'm on it.
following solution works to passs the test: function makeClass() { "use strict"; / Alter code below this line / class Vegetable { constructor(Vegetable) { this. Vegetable = Vegetable; } } / Alter code above this line / return Vegetable; } const Vegetable = makeClass(); const carrot = new Vegetable('carrot'); (); // =should be 'carrot'
Hello, Unfortunately, this solution doesn't work for me. (The same as in the "Hint": ) Error message: // running tests should return carrot. // tests completed
sorry to hear that! Would you mind posting your solution here so we could take a look?
Hello Kristofer, Thank you for your email. (ES6: Use class Syntax to Define a Constructor Function) I have already got help from FreeCodeCamp. I used the solution from "HINT", but it didn't work. class Vegetable { constructor(Vegetable){ this.Vegetable = Vegetable; } } What worked is the code below: class Vegetable { constructor(name) { = name; } } Thank you. Kind regards, Zsolt
Change:
</h1> <h3>has successfully completed the freeCodeCamp.org</h3> <h1> <del> <strong>{certTitle} Certification</strong> </del> <ins> <strong>{certTitle}</strong> </ins> </h1> <h4> Developer Certification, representing approximately{' '}

Discussion:
Please see below screenshot. The Algorithms and Data Structures certification has an extra "certification" in it: <img width="1277" alt="2NotificationsTwitter" src="https://user-"We should also check the other 10 certifications to make sure the variable text does not contain the word "certification" at the end of it, since that is already part of the certification template.
Change:
id: 587d78a4367417b2b2512ad2 title: Learn about Tertiary Colors challengeType: 0 <del> videoUrl: 'https://scrimba.com/c/c3bRDAb' </del> forumTopicId: 301057 ---

Discussion:
After some discussion on the forum, it was concluded the following challenges need the removed from the the frontmatter of the challenge files.
I am first timer to contribute it. please help with it. We need to remove the from right.
Yes and the same goes for the other challenge too.
Thank you for your contribution. For future reference, you can make changes to multiple files on the same. Also, you really should make your changes on a different branch than to avoid soiling it. I suggest taking a look at our documentation on when you want to work on more complex PRs.
Change:
toggleFlag={ toggleFlag('showTimeLine') } /> </FullWidthRow> <ins> <FullWidthRow> <Spacer /> <Button block={true} bsSize='lg' bsStyle='primary' download={`${user.username}.json`} href={ `data:text/json;charset=utf-8,${ encodeURIComponent(JSON.stringify(user)) }` } > Download all your data </Button> </FullWidthRow> </ins> </div> ); }

Discussion:
Once we've built the JSON we want to output, I believe we can just use Pug like this for the button to initiate the file download:
Change:
You should add the first `input` after the `label` text `Enter Your First Name:`, and include a space after the colon. ```js <del> assert.equal(document.querySelectorAll('label')?.[0]?.innerHTML, 'Enter Your First Name: <input>'); </del> <ins> assert.equal(document.querySelectorAll('label')?.[0]?.innerHTML.trim(), 'Enter Your First Name: <input>'); </ins> ``` You should add the second `input` after the `label` text `Enter Your Last Name:`, and include a space after the colon. ```js <del> assert.equal(document.querySelectorAll('label')?.[1]?.innerHTML, 'Enter Your Last Name: <input>'); </del> <ins> assert.equal(document.querySelectorAll('label')?.[1]?.innerHTML.trim(), 'Enter Your Last Name: <input>'); </ins> ``` You should add the third `input` after the `label` text `Enter Your Email:`, and include a space after the colon. ```js <del> assert.equal(document.querySelectorAll('label')?.[2]?.innerHTML, 'Enter Your Email: <input>'); </del> <ins> assert.equal(document.querySelectorAll('label')?.[2]?.innerHTML.trim(), 'Enter Your Email: <input>'); </ins> ``` You should add the fourth `input` after the `label` text `Create a New Password:`, and include a space after the colon. ```js <del> assert.equal(document.querySelectorAll('label')?.[3]?.innerHTML, 'Create a New Password: <input>'); </del> <ins> assert.equal(document.querySelectorAll('label')?.[3]?.innerHTML.trim(), 'Create a New Password: <input>'); </ins> ``` # --seed--

Discussion:
Overly strict whitespace tests The space between the input element and closing label tag shouldn't matter, right? No response All No response
Here is the markdown file: we can use regex in these tests Something like , but we have to use regex which is headache.
could we just trim the string?
Sure, I don't mind, because they aren't required to type text in this step, but the description will be altered
I'm not sure I see why the description would be changed. I was thinking of this:
Yes, this line while be unnecessary. And the test will check for `EnterYourLastName:<input' But I maybe misunderstanding something
Trim won't remove spaces in the middle. We are comparing against:
Change:
return sortedChallengeFiles.map((file, index) => ({ ...file, <del> contents: sortedSavedChallengeFiles[index].contents </del> <ins> contents: sortedSavedChallengeFiles[index].contents, editableRegionBoundaries: sortedSavedChallengeFiles[index].editableRegionBoundaries </ins> })); }

Discussion:
1) Navigate to a multifile challenge: 2) Input some code over multiple lines: 3) Save code 4) Refresh page ! Seen in: I assume this has to do with the container defaulting to the size it is originally given (e.g. 1 line), even though the saved code spans more.
An issue with the label is open for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors. If you would like to contribute, and have not read the contributors docs, please do so here: If you have any issues with contributing, be sure to join us on the , or on the
This is where the bounds come from. A function called in . In order to fix this, we're going to have to save the current editable region boundaries and then load from them in this function.
Hi Would using be appropriate for persisting the editable region bounds? We could potentially leverage the existing or methods to handle this, rather than writing to every time is called. Please let me know your thoughts or if there’s a better approach. Thanks!
The editable region boundaries are already persisted in local storage, as shown in the screenshot. The issue is when the editor component is mounted, it is preferring the editable regions defined in the challenge seed, as opposed to using the boundaries kept in the saved code from local storage.
Change:
assert($('p > a').length); ``` <del> The link's href value should be `https://freecatphotoapp.com`. You have either omitted the href value or have a typo. </del> <ins> The link's `href` value should be `https://freecatphotoapp.com`. You have either omitted the `href` value or have a typo. </ins> ```js const nestedAnchor = $('p > a')[0];

Discussion:
In both the sentences on this line the word should be surrounded with backticks: In this line there is a period (full-stop) where there should be a comma. This looks like something that can be fixed by "first-time" code contributors to this repository. Here are the files that you should be looking at to work on a fix: List of files: Please make sure you read our , we prioritize contributors following the instructions in our guides. Join us in our or our if you need help contributing; our moderators will guide you through this. Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.
Hello, I want to work on this.
Heyy, is this assigned to anyone?
I will work on this.
Hey! I would like to work on this issue.
Hi I have fixed the issue and you can find the PR here
Is this issue available or has it been resolved?
Change:
"assert($("p").length > 1, 'You need 2 <code>p</code> elements with Kitty Ipsum text.')", "assert(editor.match(/</p>/g) && editor.match(/</p>/g).length === editor.match(/<p/g).length, 'Make sure each of your <code>p</code> elements has a closing tag.')", "assert.isTrue((/Purrs+jumps+eat/gi).test($("p").text()), 'Your <code>p</code> element should contain the first few words of the provided additional <code>kitty ipsum text</code>.')", <del> "assert($("p.red-text").length === 2, 'Give each of your <code>p</code> elements the <code>red-text</code> class.')", </del> "assert($("p").css("font-size") === "16px", 'Give elements with the <code>red-text</code> class a <code>font-size</code> of 16px.')" ], "challengeSeed": [

Discussion:
This challenge didn't say both p should be in red-text, and the 2nd p shown in black in next challenge (Waypoint: Set the Font Family of an Element).
You are absolutely right about this. I've put in a PR to remove the erroneous test :smile:
:smiley:
Please don't close the issue until the PR has been merged. This way we can ensure that the issue eventually does get fixed (though I'm looking at the PR right now so that won't be a problem this time, often PRs don't get looked at for long periods of time and having the issue around that the PR resolves can speed up the process). Thanks :)
Sorry.. And thanks for the reminding~
^ and as you can see, when I merged the PR the issue auto-closed :)
Wow, coool! I got to spend some time to know this system~
Change:
::after { padding: 0; margin: 0; <ins> box-sizing: border-box; </ins> } html { font-size: 62.5%; <del> box-sizing: border-box; </del> } body {

Discussion:
Someone in the forums pointed out that adding the property just to will not have the intended effect since the property is not inherited. It appears to me that removing this property completely from in the final product does not seem to make any difference to the layout. Do we need ? If so, if the intent is to apply it to all elements then it should probably be moved to the rule set. Either remove completely or move it into the ruleset. No response N/A No response
Pretty sure I saw this in another challenge too and it got fixed. The CSS used looks like the of setting the but with the actual inheriting missing from the code. It should be fixed, but I would not suggest we remove , setting that (in my opinion) is pretty much a best pratice.
I'm guessing it would be easier and take less explaining to update step 26 to add the on that selector and then remove the mention of it in step 27. Then update all the seed code.
Just a heads up, if lasjorg PR merged without issue, balance sheet project suffer the same issue, we can open a PR or issue for it, if the PR is merged. Except that the balance sheet project , doesn't do much and moving it break the layout.
Change:
# --hints-- <del> You should use dot notation to access the `innerText` propertry of `text`. </del> <ins> You should use dot notation to access the `innerText` property of `text`. </ins> ```js assert.match(code, /text.innerText/);

Discussion:
There is a typo in Step 45, the word is misspelled. Here is the typo it should be in step 26, is incorrect grammar, it should be or If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution, followed by the one that is made first. Happy contributing.
Is anybody working on this issue? if not I would like too
Hello.. I would like to contribute to this issue.. Kindly assign me the same
Change:
import { Button, Modal } from '@freecodecamp/react-bootstrap'; import ga from '../../../analytics'; <ins> import Login from '../../../components/Header/components/Login'; </ins> import GreenPass from '../../../assets/icons/GreenPass'; import { dasherize } from '../../../../../utils/slugs';

Discussion:
I'm testing beta. Describe the bug When submitting a challenge using Ctrl+Enter it automatically completes also the following challenge. To Reproduce Steps to reproduce the behavior: a logged out user to the first challenge it Ctrl+Enter marks as solved also the following challenge and you can go ahead Expected behavior It should solve the current challenge and present the following one. Screenshots As you can see I can submit multiple challenges: ! Desktop (please complete the following information): OS: Ubuntu Browser Firefox Version 69.0.1 Additional context I've been able to reproduce it on but I could skip only one challenge. On my local dev I managed to skip 4.
I've digged a bit on this issue, and I think the problem is somehow related to this line: As this is triggered also when I'm submitting the finished challenge. If I comment that line out everything works fine, meaning I can Ctrl+Enter to run the tests and submit and the bug disappear. I'm going to dig a bit more, but does that makes any sense to you?
Thanks for testing our beta version and reporting this! You rock. /cc
Thanks It looks like I didn't test the logged out behaviour. so, what do we want to happen for logged out users? The issue I see is that it currently says 'Submit and go to the next challenge', but clearly they can't submit. For now, do we just want them to see the same as logged in users (and quietly not submit)?
Here is what I would do: ! Of course the modal should close as well like you mentioned. The signin button can link to same as the home page CTA. And we could remove from the first button
Turns out it's not working properly even when the user is logged in. I think it's a race condition between and . was quite right, the problem is on that line. It shouldn't be called if the modal is open since it's listening to as well.
yes I think it's with the in the editor and the in the . I can give a further look later if you wish.
Thanks for the offer but I think (with your help!) I've fixed it. It seemed only fair, since I introduced the bug.
Excellent!
Release on its way, should be available within the hour.
Change:
); ``` <del> `bubbleSort` should return an array that is unchanged except for order. </del> <ins> `bubbleSort([1,4,2,8,345,123,43,32,5643,63,123,43,2,55,1,234,92])` should return an array that is unchanged except for order. </ins> ```js assert.sameMembers(

Discussion:
The following challenges have an example function call in the seed code. These function calls should be removed and the related tests should be clarified to reflect the call instead. This sorting challenge is correct and could be used for reference.
Hi, nhcarrigan. I'd like to try to help and solve it. I'm still learning about the project so I would like to ask a question so I can understand the issue better. There is a function call in the file.. bubleSort([1,2,3....]) (example: implement-bubble-) ! And it should be removed from the seed section and transferred to here, similarly to implement-quick-sort: ! ! Is it correct or are there other files that I should be concerned about?
That is correct, yes - this same change should be completed on the four files I've linked. I would, however, recommend holding off on working on this until we receive additional consensus that this is the best way to proceed. If you run in to any questions, feel free to review our or ask in our or the .
Sounds great!! Thanks for the fast response. I will wait until further notice.
Hi MuriloMarquesSantos, are you still interested in fixing this issue?