jiebi/CodeConvo huggingface dataset:
Change:
This code has the comments, but really we shouldn't be using variables in the user code for tests. Rewrite test to use private variable. No response All No response

Discussion:
assert(!code.match(/.?[sS]*?splice/g)); ``` <del> The `inputCities` array should not change. </del> <ins> You should not mutate the original array passed to the function. </ins> ```js <del> assert( JSON.stringify(inputCities) === JSON.stringify(['Chicago', 'Delhi', 'Islamabad', 'London', 'Berlin']) ); </del> <ins> assert.deepEqual(_inputCities, ["Chicago", "Delhi", "Islamabad", "London", "Berlin"]); </ins> ``` `nonMutatingSplice(["Chicago", "Delhi", "Islamabad", "London", "Berlin"])` should return `["Chicago", "Delhi", "Islamabad"]`. ```js <del> assert( JSON.stringify( nonMutatingSplice(['Chicago', 'Delhi', 'Islamabad', 'London', 'Berlin']) ) === JSON.stringify(['Chicago', 'Delhi', 'Islamabad']) ); </del> <ins> assert.deepEqual(nonMutatingSplice(_inputCities), ["Chicago", "Delhi", "Islamabad"]); </ins> ``` # --seed--

```js function nonMutatingSplice(cities) { <del> // Only change code below this line return cities.splice(3); // Only change code above this line </del> <ins> return cities.splice(3); </ins> } <ins> ``` </ins> <del> const inputCities = ["Chicago", "Delhi", "Islamabad", "London", "Berlin"]; nonMutatingSplice(inputCities); </del> <ins> ## --after-user-code-- ```js const _inputCities = ["Chicago", "Delhi", "Islamabad", "London", "Berlin"]; </ins> ``` # --solutions--

function nonMutatingSplice(cities) { return cities.slice(0,3); } <del> const inputCities = ["Chicago", "Delhi", "Islamabad", "London", "Berlin"]; </del> ```
Change:
There appears to be a slight typo in the English instructions on Step 41 of "Learn Typography by Building a Nutrition Label". The instructions are displayed on the file and read as: The typo is with the text: . The and <p class="bold right"% Daily Value </p% Daily Value ` as part of the exercise. The following code is what the challenge starts with - where the instructions are displayed The expected instructions would read with instead of : This would match the actual text value for the paragraph element the instructions are referencing. ! ! Device: PC OS: Windows 10 Browser: Chrome Version: Version 115.0.5790.110 (Official Build) (64-bit) I would like to point out that I have only seen this issue with English and I am not sure if other languages are also impacted.
Thanks for opening this issue. This looks 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 , 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.

Discussion:
# --description-- <del> The text `* Daily Value %` should be aligned to the right. Create a `.right` selector and use the `justify-content` property to do it. </del> <ins> The text `% Daily Value *` should be aligned to the right. Create a `.right` selector and use the `justify-content` property to do it. </ins> # --hints--
Change:
We got a report that the current test for Step 23 of the Learn CSS Animation by Building a Ferris Wheel project fails in the latest version of Safari. The test works as expected in Firefox and Chrome. This test should pass with the above code like it does in Firefox and Chrome. No response Device: Macbook Air OS: macOS Browser: Safari Version: 16.5.2 In of this project, the CSS helper () returns the string when the correct code is submitted in both Chrome and Firefox. In the latest version of Safari, the CSS helper returns . The test in the should be updated to check for both strings so learners using all supported browsers can complete this step. If this is an issue for other people running Safari, this would be a good candidate for someone's first PR.
Another arguably more verbose option is to look at each individual property. I suspect they will never change values or be different between browsers so that might be more future-proof than looking at the shorthand value.
Thanks for sharing that, I agree – it would be much more future-proof to test those properties / values individually. I'm not sure what our CSS Helper library returns for each individual property in the browsers we support. But if they're consistent across Chrome, Firefox, and Safari, testing each one would be a much better approach.

Discussion:
Your `.cabin` selector should have an `animation` property set to `cabins 10s linear infinite`. ```js <del> assert(new __helpers.CSSHelp(document).getStyle('.cabin')?.animation === '10s linear 0s infinite normal none running cabins'); </del> <ins> const cabinElementStyles = new __helpers.CSSHelp(document).getStyle('.cabin'); assert( cabinElementStyles?.animationName === "cabins" && cabinElementStyles?.animationDuration === "10s" && cabinElementStyles?.animationTimingFunction === "linear" && cabinElementStyles?.animationIterationCount === "infinite" ); </ins> ``` # --seed--
Change:
The hint text for one of the tests in step 54 of the Learn Typography By Building a Nutrition Label project has a minor typo. This typo isn't visible unless a learner fails a specific test. The hint text currently reads "A element should wrap the text ". It should be updated to "A element should wrap the text " to match the instructions for this step, and the test itself. This would be a great first PR for new contributors.
I will be working on it.
why cloning the repo is throwing errors? I have been trying for 52 minutes
Add Newly generated SSH key from your device to your github account then clone
The problem is not with SSH key as half of the repo gets cloned and other gets skipped or deleted. The repo is too large to get cloned, I tried increasing buffer size but it didn't worked. Have you tried cloning it? Cloning depth wise might help but problem could be different if it is only appearing in my machine.
I just forked the main branch of the repository on my account and then git cloned that repository on to my local machine.

Discussion:
assert(document.querySelector('.daily-value.small-text')?.lastElementChild?.querySelectorAll('span')?.length === 3); ``` <del> A `span` element should wrap the text `Sodium 360mg`. </del> <ins> A `span` element should wrap the text `Sodium 160mg`. </ins> ```js assert(document.querySelector('.daily-value.small-text')?.lastElementChild?.firstElementChild?.innerText?.match(/Sodium[s|n]160mg/));
Change:
instructions state -10px failed test done incorrectly. error states that it must be -1degerror instruction bug proven. please be grateful free testing again to your company. I would like to one day do corrections to updated things like this on github, step 78 new responsive web design did not pass with clear instructions. error says -1deg ! 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
Thanks for opening this issue. 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: The test text should be updated to . 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.
Open Source is based upon free contributions. We're always grateful for efforts that move the codebase forward.

Discussion:
# --hints-- <del> Your `.cat-whisker-right-top` selector should have a `transform` property set to `rotate(-1deg)`. </del> <ins> Your `.cat-whisker-right-top` selector should have a `transform` property set to `rotate(-10deg)`. </ins> ```js assert(new __helpers.CSSHelp(document).getStyle('.cat-whisker-right-top')?.transform === 'rotate(-10deg)')
Change:
Uploads: Everyday Downloads: Twice a week This should suffice our deployment targets which are usually Tuesdays? and Thursdays (optional) at around UTC+3 We can shake it up so that PRs can be merged on Mondays and Wednesdays?
So downloads should be triggered on Mondays and Wednesdays?
Yes, or a day before, for all we care. As long as they are: a week only on Mondays and Wednesdays for deployments on Tuesdays and Thursdays

Discussion:
on: workflow_dispatch: schedule: <del> # runs every weekday at 12:15 PM UTC - cron: '15 12 * * 1-5' </del> <ins> # runs Monday and Wednesday at 12:15 PM UTC - cron: '15 12 * * 1,3' </ins> env: GITHUB_TOKEN: ${{ secrets.CROWDIN_CAMPERBOT_PAT }}

on: workflow_dispatch: schedule: <del> # runs every weekday at 12:30 PM UTC - cron: '30 12 * * 1-5' </del> <ins> # runs Monday and Wednesday at 12:15 PM UTC - cron: '15 12 * * 1,3' </ins> env: GITHUB_TOKEN: ${{ secrets.CROWDIN_CAMPERBOT_PAT }}

on: workflow_dispatch: schedule: <del> # runs every weekday at 12:00 noon UTC - cron: '0 12 * * 1-5' </del> <ins> # runs Monday and Wednesday at 12:15 PM UTC - cron: '15 12 * * 1,3' </ins> env: GITHUB_TOKEN: ${{ secrets.CROWDIN_CAMPERBOT_PAT }}
Change:
Here's the last paragraph in the instructions: Notice that where is says "... give you .cat-head..." should actually be "... give your .cat-head ..." N/A N/A ! Device: Laptop OS: Windows 10 Browser: Chrome Version: 116.0.5845.111 Didn't see a better way to report a spelling issue directly from the website.
Thanks for opening this issue. This looks 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 , 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.
Can I Contribute on this issue?
attempting
Hey We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. Issues labelled with or are open for contributions. Please make sure you read . We prioritize contributors following the instructions in our guide. Join us in or if you need help contributing - our community will be happy to assist you.
please check out the update.
Hey yout PR is targeting branch of your own fork, not the .
i think its targeting the right one now.
if you want to tackle some other grammatical errors I found, I know there is a missing space in a step somewhere, and missing punctuation in another. I've forgotten where, but I know they both happened prior to this step I reported here, but not before "Learn the CSS Box Model by Building a Rothko Painting". Both were on different steps.

Discussion:
When you use the `relative` value, the element is still positioned according to the normal flow of the document, but the `top`, `left`, `bottom`, and `right` values become active. <del> Instead of `static`, give you `.cat-head` a position of `relative`, and leave both `top` and `left` properties as they are. </del> <ins> Instead of `static`, give your `.cat-head` a position of `relative`, and leave both `top` and `left` properties as they are. </ins> # --hints--
Change:
The "Control Variable Scope and Logic Using Code Blocks in C#" in the "Add Logic to C# Console Applications" has an question that doesn't really feel quite right for this section. The question is "Which of the following describes the affect of a statement?". The thing is statements aren't covered in the foundational MS Learn Path. It'd be a little unfair to new learners to answer this question with the given material. N/A When answering questions on the FreeCodeCamp foundational certification path, prior C# knowledge should not be required to answer questions. A question like the following might be better suited for this particular lesson. What is the scope of a local variable declared inside a method in C#? a) It's accessible only within the method where it's declared. b) It can be accessed from any method within the same class. c) It's accessible globally from any part of the program. d) It's only visible within the same class, but different methods can't access it. No response Device: Desktop OS: Windows 10 Browser: FireFox Version: 117 I only checked out this certification path for practice reasons.
I came across the same issue. I had to read up on the using statement using different resources in order to answer the question and be able to continue my learning path.
I've created a pull request to fix this issue. Since all the other questions are taken from the "Knowledge Check" portion of related tutorial, I just used the first question found here:

Discussion:
## --text-- <del> Which of the following describes the affect of a `using` statement? </del> <ins> Which of the following statements is true about showing/removing the curly braces for code blocks associated with an `if` statement? </ins> ## --answers-- <del> Affects only the first code block in the code file. </del> <ins> The curly braces can't be removed from the code block for `else if` and `else` statements. </ins> --- <del> Affects only the current code block in the code file. </del> <ins> If the curly braces are removed from the code blocks of an `if-elseif-else`, the white space must also be removed. </ins> --- <del> Affects all of the code in the code file. </del> <ins> Always choose a style that improves readability. </ins> ## --video-solution--
Change:
We see this every so often and it might warrant a note. See the examples for more context. Warn the user so they do not waste time debugging something that is out of their control. 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] Examples:
Thanks for opening this. I forgot this was still a thing. 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: To Close This Issue Change this file: Add the following to the description: If you have any issues with contributing, be sure to join us on the , or on the
I hope this message finds you well. I am writing to seek your advice and assistance regarding a minor issue I've encountered with a project I am working on. As a beginner, your guidance and support would be greatly appreciated. In the course of my work, I've noticed that the tests for this project do not function properly when using To ensure transparency and clarity, I believe it would be beneficial to add a note in the project documentation, specifically under the "Note" section, stating the following: Note: This project's tests do not work when using I believe that adding this note would help inform other contributors and users about this limitation, ensuring a smoother development and testing process for everyone involved. Furthermore, I would like to seek your opinion on whether it would be appropriate to raise a Pull Request (PR) to implement this change. Your guidance on this matter would be invaluable to me as a newcomer to the project. I genuinely believe that your expertise could help me navigate this process more effectively. Your mentorship has been an inspiration to me, and I am truly grateful for any assistance you can provide. If adding the mentioned note is indeed the appropriate action to take, I would be thrilled to have the opportunity to submit a PR for this purpose. Your approval and support in merging the PR would be an incredible motivation for me to continue contributing to the project. I would be grateful for your thoughts and guidance on this matter. Your expertise and mentorship are highly regarded, and I look forward to your response. Thank you for your time and consideration. Sincerely, K S Sai Teja
I have raised PR. Regarding this issue.. Please review my PR.

Discussion:
When you are done, make sure a working demo of your project is hosted somewhere public. Then submit the URL to it in the Solution Link field. Optionally, also submit a link to your project's source code in the GitHub Link field. <ins> **Note:** This project's tests do not work when using `glitch.com`. </ins> # --instructions-- - Complete the necessary conversion logic in `/controllers/convertHandler.js`
Change:
Challenge can be passed with solution that will serve files from the root folder, not just directory. Ref By using as a path serving static assets, and not giving explicit path to the , the static assets will be served from (root folder in this case) at the (root) path. Since folder is then served where it is expected to be served, this fulfills test requirements: However, using just serves also other files and directories, starting from the root folder. Ie. or . Reasonable solution seems to be adding test that will check if one of the files from root folder (ie. are not served as static assets. To reproduce: replit starter from to , below line : replit on passes works, so is or . Files outside of folder should not be served as static assets. Otherwise the test should fail. No response No response_
Thanks for opening this. This does sound like a reasonable fix. 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

Discussion:
); ``` <ins> Your app should not serve files from any other folders except from `/public` directory ```js (getUserInput) => $.get(getUserInput('url') + '/server.js').then( (data) => { assert.equal( data?.status + '', 404 + '', 'Your app must serve files only from "public" directory' ); }, (xhr) => { assert.equal( xhr?.status + '', 404 + '', 'Your app must serve files only from "public" directory' ); } ); ``` </ins> # --solutions-- ```js
Change:
I've run into this several times in the forum in the past week. The active editor is placed within the existing rule set and apparently people don't notice that and instead create a new rule set and add the there. This is what I'm seeing in the forum: I think the active editor should include the entire existing rule set so that it is clear it already exists and that that is where the property should be . We can add an empty line at the bottom of the rule set to indicate where the property should go. No response N/A No response
I definitely agree. I went ahead and made a PR that moves the editable region to include the full selector.

Discussion:
background-color: #c9d2fc; } <ins> --fcc-editable-region-- </ins> .cat-head { width: 205px; height: 180px; border: 1px solid #000; border-radius: 46%; <del> --fcc-editable-region-- --fcc-editable-region-- </del> } <ins> --fcc-editable-region-- </ins> ```
Change:
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.

Discussion:
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');

}; const run = async () => { <ins> await client.connect(); log('Connected successfully to mongo'); </ins> await dropUserTokens(); await dropUsers(); if (args.includes('certified-user')) {
Change:
The current instructions say: But they don't specifically say where the new text should be within the . If you add the text before the (with the anchor correctly to the text) then you get the following hint: This creates even more confusion since the anchor was correctly. I think these instructions are relying on the fact that the text for the radio buttons was after the and thus the assumption is that the text for the check box should also be after the . And I agree that usually the text for radio buttons/check boxes is placed after the , but this is not a requirement. Also, in step 26 when we have them add the text for the radio buttons, we explicitly say "immediately after the element", so it seems like this is important information to add. N/A Change the instructions to: I should have done better testing :slightlysmilingface: The tests don't care if there is a space between the and the text. We might also want to update the tests so it gives a better hint if they put the text before the . No response N/A No response
I like the proposed change in wording.
Please let me know if there are any other changes needed.
the issue is not marked as ready for contribution yet.
This issue has been around for a while and I'm still seeing it come up in the forums. Do we need any more discussion on this? Two things to fix in this PR: Update instructions to make it clear that the text comes after the Fix the test that is erroneously telling the user they need to add an anchor element when it is already there.
I don't think so, no. The requirements are nice and clear, thanks!

Discussion:
# --description-- <del> Add `I accept the terms and conditions` text to the newly added label, then link the text `terms and conditions` to the following location: </del> <ins> Add the text `I accept the terms and conditions` immediately after the `input` element in the newly added label. Then link the text `terms and conditions` to the following location: </ins> ```md https://www.freecodecamp.org/news/terms-of-service/

assert.equal(document.querySelector('fieldset:nth-child(3) + label')?.innerText.trim(), 'I accept the terms and conditions'); ``` <del> You should use an `a` element to link to the terms and conditions. </del> <ins> You should use an `a` element to link to the terms and conditions. ```js assert.exists(document.querySelector('fieldset:nth-child(3) + label a')); ``` You should put the new text immediately after the `input` element in the `label`. </ins> ```js assert.exists(document.querySelector('fieldset:nth-child(3) + label > input + a'));
Change:
Describe the bug if you type something in searchbar while using the dark mode, and hover over the produced links, it will hide the link. To Reproduce Steps to reproduce the behavior: to '' something over it how the hover is hiding the result Screenshots ! Browser: chrome
Can you please assign this to me
Hi I've been looking into the issue you reported regarding dark mode and hover behavior on the search results. I'd like to contribute a fix, but I'm having trouble locating the exact code or files that need modification. Could you please provide more specific details about the file or code that's related to this issue? A direct link to the relevant code or even just the file path would be immensely helpful. Your guidance would ensure that I'm making the correct changes to address this problem effectively. Thank you!

Discussion:
padding: 0; } <del> .sidebar ul li a { </del> <ins> .sidebar ul li a, .search a { </ins> color: var(--quaternary-color); } <del> .sidebar ul li > a:hover { </del> <ins> .sidebar ul li > a:hover, .search a:hover { </ins> color: var(--primary-color); }