jiebi/CodeConvo huggingface dataset:
Change:
] }, { <del> "_id": "5900f3831000cf542c50fe95", "challengeType": 5, "type": "bonfire", "title": "Problem 22: Names scores", "tests": [ "assert.strictEqual(euler22(), 871198282, 'message: <code>euler22()</code> should return 871198282.');" ], "solutions": [], "translations": {}, "challengeSeed": [ "function euler22() {", "  // Good luck!", "  return true;", "}", "", "euler22();" ], "description": [ "Using names.txt (right click and 'Save Link/Target As...'), a 46K text file containing over five-thousand first names, begin by sorting it into alphabetical order. Then working out the alphabetical value for each name, multiply this value by its alphabetical position in the list to obtain a name score.", "For example, when the list is sorted into alphabetical order, COLIN, which is worth 3 + 15 + 12 + 9 + 14 = 53, is the 938th name in the list. So, COLIN would obtain a score of 938 × 53 = 49714.", "What is the total of all the name scores in the file?" ] }, { </del> "_id": "5900f3831000cf542c50fe96", "challengeType": 5, "type": "bonfire",

Discussion:
This problem does not work with the freeCodeCamp platform since the description says to use an external file. This is impossible with the platform. After consulting with & it was decided to delete this challenge completely. This needs to be done.
Does this involve just removing the problem from the project-euler- file? I can take this.
Yup! Pretty simple. Just delete the entire problem from project-euler- Thanks for claiming this one.
Change:
"id": "cf1391c1c11feddfaeb4bdef", "title": "Create Decimal Numbers with JavaScript", "description": [ <del> "We can store decimal numbers in variables too. Decimal numbers are sometimes refered to as <dfn>floating point</dfn> numbers or <dfn>floats</dfn>.", </del> <ins> "We can store decimal numbers in variables too. Decimal numbers are sometimes referred to as <dfn>floating point</dfn> numbers or <dfn>floats</dfn>.", </ins> "<strong>Note</strong><br>Not all real numbers can accurately be represented in <dfn>floating point</dfn>. This can lead to rounding errors. <a href="https://en.wikipedia.org/wiki/Floating_point#Accuracy_problems" target="_blank">Details Here</a>.", "<h4>Instructions</h4>", "Create a variable <code>myDecimal</code> and give it a decimal value."

Discussion:
Challenge has an issue. User Agent is: <codeMozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. The word refered should be written with 2 Rs: referred. !
Change:
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--

Discussion:
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
Change:
pm2 logs ``` <del> > [!DANGER] </del> <ins> > [!ATTENTION] </ins> > For client applications, the shell script can't be resurrected between Node.js versions with `pm2 resurrect`. Deploy processes from scratch instead. This should become nicer when we move to a docker based setup. ## Installing and Updating Azure Pipeline Agents

Discussion:
We are currently using the for our Docsify-powered contributing documentation. One of the alert types, , also accepts the keyword to render. We currently render one of these boxes with and four of them with . For consistency sake, we should use the same keyword to render these. IMHO, with the displayed text being "Attention" we should use the keyword, but I wanted to get some feedback before opening this up to first timers. As an alternative, if we prefer the text, we can modify the plugin config to render on the end-user view instead of .
At this time, there are 4 instances of usage of and 1 instance for , I think it would make sense to make it consistent. And seeing that with the displayed being "Attention" I agree on that being the one used.
+1 on making it
I am happy either way. The only reason I came into this is because I am used to the Bootstrap way of naming, and naturally put DANGER.
Alright, I am going to open this up to first timers. A pull request that closes this issue will: Replace all instances of with in the directory Will not modify any of the files in the directory (these will be updated through our translation worfklow) If you are interested in resolving this issue, we recommend starting with our . If you have further questions feel free to join us in our .
Hi, can I try this out?
Sure thing! Let us know if you have any questions :)
Hey Nick, I would like to work on this!
I also thought of that, but as this issue has been already received by someone, let's give them some time! If it is more than a week without no response, you can grab this!
Yup I got that. That's why I commented so if they are unable then I can pick that up
Change:
); ``` <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

Discussion:
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
Change:
padding: 4vw 15px; } <del> .certification-section { </del> <ins> .certification-section, .faq-section { </ins> padding-inline: 4vw; }

Discussion:
! Frequently asked question segment is not aligned with the previous elements on the homepage to down to frequently asked questions the misalignment of frequently asked questions segment with the previous elements The frequently asked question segment should be aligned with the previous elements of the homepage for a better UI ! Device: Laptop OS: Windows 11 Browser: Brave Version: 1.64.122 No response
This issue is because the Certifications section has extra side padding: We can add a class to the FAQ section, and give it , too. I'm not sure if this change would collide with the changes you're making to the landing page. I'm also wondering if the Certification section being so wide (comparing to the one on /learn) is still desired. If it's not, I think we can take this opportunity to update the section.
Yes, we can standardize all of them. My changes are effecting the landing top section.
Thanks, Ahmad. I'm temporarily blocking this issue until the CSS situation is a little less messy. I'll get back to this and come up with a suggestion after is merged.
We will be making changes to the certification section in the near future, so I think we can keep the scope of this issue to just adding some extra padding to the FAQ section, as suggested here: This issue is open for contribution. We typically do not assign issues. Instead, we accept the most quality contribution followed by the one that is made first. Please make sure you read our as well as 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. Happy contributing.
Change:
color: var(--danger-color); } <ins> .has-error .form-control, .has-warning .form-control, .has-success .form-control { border-color: var(--quaternary-background); } .has-error .form-control:focus, .has-warning .form-control:focus, .has-success .form-control:focus { border-color: var(--tertiary-color); } </ins> .panel-primary { border-color: var(--primary-color); }

Discussion:
Describe the bug Some of the input boxes (Email Settings and Your Internet Presence at least) get the old green border when valid inputs are entered. To Reproduce Steps to reproduce the behavior: to down to 'Your Internet Presence' below 'Twitter' on something else to remove focus the green border. Expected behavior The border should fit with the current colour scheme. Screenshots !
Hey there! I could handle this! :slightlysmilingface:
Thanks Feel free to submit a PR when you're ready.
Hi I had tested this on all input boxes in setting page. Affected input are only in Email Settings and Internet Presence like you described. The green border is caused by Bootstrap default class . I also had overridden color changes caused by another Bootstrap default classes which is and . The focus state was actually also affected but it is harder to see because the border became dark green (which is quite hard to distinguish with dark gray in general). I had fixed that too. I had tested my fix both on day and night mode. In night mode, border color on normal and focus state is hard to see but it should be correct with and . I am also sure that accessibility is not negatively affected even though there are no longer border color changes, because the input label is still able to change color correctly based on previous validation result classes
I tried out your PR and it looks great! Before we go ahead with that I would like your thoughts on a couple of things. Firstly, are you getting the appropriate error and warning classes applied? Testing locally I don't seem to be. Secondly, what do you think about inverting the input boxes in night mode? i.e. dark background + light text to fit in with the rest of the aesthetic.
Thanks for testing it :) I realized about those two points you mentioned when I was working with this issue, I intended to create several new issues about it and another accessibility issue. Yes the client validation for email settings and internet presence is all over the place and need some improvements. Border color for focus state on input boxes with night mode is also hard to see. Inverting some colors looks like a good idea. Now that this issue is already closed, let's move the discussion to new issues. I will mention you when it have been created.
Change:
<del> import { Button, Panel } from '@freecodecamp/react-bootstrap'; </del> import React from 'react'; import { connect } from 'react-redux'; import { bindActionCreators, Dispatch } from 'redux'; import { useTranslation } from 'react-i18next'; <ins> import { Panel, Button } from '@freecodecamp/ui'; </ins> import { openModal } from '../../redux/actions'; import Spacer from '../../../../components/helpers/spacer'; import SurveyModal from './survey-modal';

Discussion:
<img width="810" alt="image" src="" all the trophy challenges night theme to the exam page UI to be legible. No response Browser: Chrome <details<summaryLight theme is fine</summary<img width="742" alt="image" src=""</details
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
Hey I would like to work on this. Can you tell me the file that I will be working with?
Hey how can we complete the trophy challenges when working in the dev environment?
To test locally, I just alter the database to have the relevant challenges in the array. That is, I , but I now see we have a flag.
Taking a look at this, I noticed that the flag doesn't work. should fix that. Also, it was that the surveys and exams get seeded when you run the seed command. So to see that alert - you need to seed the trophy challenges, and then delete the collection.
The The fix is to import from instead of and give the component a prop and you should be able to remove the prop. I only played with it for a short time, but I think this will fix it all up.
Change:
"title": "Manipulate JavaScript Objects", "difficulty":"9.9823", "description":[ <del> "There are many ways to add and add and remove properties from objects.", </del> <ins> "There are many ways to add and remove properties from objects.", </ins> "For example, we can add properties to objects like this:", "<code>myObject.myProperty = "myValue";</code>", "We can also delete them like this:",

Discussion:
Challenge has an issue. Please describe how to reproduce it, and include links to screenshots if possible. "There are many ways to add and add and remove properties from objects." Should probably read as: "There are many ways to add and remove properties from objects."
Change:
try { // Based on the context retrieve the parent // object of the comment (Story/Comment) <del> Context.find( { '_id': data.associatedPost }, function (err, associatedContext) { </del> <ins> Context.find({'_id': data.associatedPost}, function (err, associatedContext) { if (err) { return next(err); } associatedContext = associatedContext.pop(); if (associatedContext) { associatedContext.comments.push(data._id); associatedContext.save(function (err) { if (err) { return next(err); } res.send(true); }); } // Find the author of the parent object User.findOne({'profile.username': associatedContext.author.username}, function(err, recipient) { </ins> if (err) { return next(err); } <del> associatedContext = associatedContext.pop(); if (associatedContext) { associatedContext.comments.push(data._id); associatedContext.save(function (err) { if (err) { return next(err); </del> <ins> // If the emails of both authors differ, // only then proceed with email notification if ( typeof data.author !== 'undefined' && data.author.email && typeof recipient !== 'undefined' && recipient.email && (data.author.email !== recipient.email) ) { var transporter = nodemailer.createTransport({ service: 'Mandrill', auth: { user: secrets.mandrill.user, pass: secrets.mandrill.password </ins> } <del> res.send(true); </del> }); <del> } // Find the author of the parent object User.findOne( { 'profile.username': associatedContext.author.username }, function(err, recipient) { </del> <ins> var mailOptions = { to: recipient.email, from: 'Team@freecodecamp.com', subject: data.author.username + ' replied to your post on Camper News', text: [ 'Just a quick heads-up: ', data.author.username, ' replied to you on Camper News.', 'You can keep this conversation going.', 'Just head back to the discussion here: ', 'http://freecodecamp.com/news/', data.originalStoryLink, '- the Free Code Camp Volunteer Team' ].join('n') }; transporter.sendMail(mailOptions, function (err) { </ins> if (err) { <del> return next(err); </del> <ins> return err; </ins> } <del> // If the emails of both authors differ, // only then proceed with email notification if ( typeof data.author !== 'undefined' && data.author.email && typeof recipient !== 'undefined' && recipient.email && (data.author.email !== recipient.email) ) { var transporter = nodemailer.createTransport({ service: 'Mandrill', auth: { user: secrets.mandrill.user, pass: secrets.mandrill.password } }); var mailOptions = { to: recipient.email, from: 'Team@freecodecamp.com', subject: data.author.username + ' replied to your post on Camper News', text: [ 'Just a quick heads-up: ', data.author.username, ' replied to you on Camper News.', 'You can keep this conversation going.', 'Just head back to the discussion here: ', 'http://freecodecamp.com/news/', data.originalStoryLink, '- the Free Code Camp Volunteer Team' ].join('n') }; transporter.sendMail(mailOptions, function (err) { if (err) { return err; } }); } } ); } ); </del> <ins> }); } }); }); </ins> } catch (e) { <ins> // delete comment </ins> return next(err); } });

Discussion:
Seeing this in production here: solution: Use and/or check for user existence and end early. cc:
Change:
- We serve this file as a SPA using `docsify` and GitHub Pages. - The `docsify` script generates the content of `markdown` files in the `docs` directory on demand. - The homepage is generated from the [`_coverpage.md`](_coverpage.md). <del> - the sidebar navigation is generated from [`_sidebar.md`](_sidebar.md). </del> <ins> - The sidebar navigation is generated from [`_sidebar.md`](_sidebar.md). </ins> ### Serving the documentation site locally

Discussion:
I noticed that the doc describing the process for updating the docs (how-to-work-on-the-docs-) doesn't explicitly say that when adding a brand new doc file, the file should be updated (or evaluated to see if the new file should be listed there). I'm not sure if 100% of new doc files should in fact get to the , but I feel it should be mentioned as a possible area that needs to be looked at when a person is adding a brand new doc file. (ps. About a month ago I created a new doc file for onboarding of mods and the PR was accepted and merged, but no change was made to the because I was unaware of it till just now... I now need to go back to modify this file to 'publish' the new doc) how-to-work-on-the-docs- N/A Update the how-to-work-on-the-docs- to call out the need to evaluate updating the specifically when creating a brand new doc file. No response
Change:
] ], "type": "hike", <del> "challengeType": 6 </del> <ins> "challengeType": 6, "nameEs": "JavaScript Lingo: Vectores y objetos", "descriptionEs": [ "Si desea almacenar más de una pieza de información en una variable, puedes hacerlo mediante la creación de un vector o de un objeto.", "** Exención de responsabilidad: Los objetos de JS no son exactamente lo mismo que los objetos en otros lenguajes. Vamos a discutir aquí objetos con respecto a JS. ", "Los vectores son conjuntos de valores entre [corchetes]. Los valores se separan con comas. Cada valor puede ser booleano, cadena, número, o incluso otro vector. A esto último le llamamos vector anidado. A un vector compuesto por vectores de la misma longitud le llamamos matriz. ", "Los objetos son un tipo de datos que pueden verse o comportarse como un vector, en la medida que se trata de más valores almacenados en una variable de una manera organizada. Oirás que un objeto se puede representar en JSON, y con frecuencia cuando haces llamadas a la API de algunos sitios (para obtener información que necesitas mostrar en tu propia página) está será devuelta en JSON. ", "Un ejemplo de la notación de objetos es:  <code>var obj = { 'nombre': 'Briana', 'comida': 'queso', 'perro': 'Maurice'};</code>", "Fíjate que un objeto se encierra entre llaves { ... }, que los diferentes atributos se separan por comas, que cada atributo consta de una palabra llave y de un valor. Por ejemplo son llaves 'nombre', 'comida' y 'perro' y sus respectivos valores son 'Briana', 'queso' y 'Maurice'. En este ejmplo todos los valores fueron cadenas, aunque también son válidos booleanos, números y otros tipos de datos." ] </ins> }, { "id": "56b15f15632298c12f315189",

Discussion:
[ ] JavaScript Lingo: MDN and Documentation [ ] JavaScript Lingo: Value Types [ ] JavaScript Lingo: Variables & camelCase [ ] JavaScript Lingo: Arrays & Objects [ ] JavaScript Lingo: Finding and Indexing Data in Arays [ ] JavaScript Lingo: Manipulating Data [ ] JavaScript Lingo: Math [ ] JavaScript Lingo: Loops [ ] JavaScript Lingo: Regular Expressions
Working on this one
Change:
"The "row" class is applied to a <code>div</code>, and the buttons themselves can be wrapped within it." ], "tests": [ <del> "assert($('div.row:has(button)'), 'Your buttons should all be wrapped within the same <code>div</code> element with the class "row".')", </del> <ins> "assert($('div.row:has(button)').length > 0, 'Your buttons should all be wrapped within the same <code>div</code> element with the class "row".')", </ins> "assert($('div.col-xs-4:has(button)').length > 2, 'Each of your Bootstrap buttons should be wrapped within its own a <code>div</code> element with the class "col-xs-4".')", "assert(editor.match(/</button>/g) && editor.match(/<button/g) && editor.match(/</button>/g).length === editor.match(/<button/g).length, 'Make sure each of your <code>button</code> elements has a closing tag.')", "assert(editor.match(/</div>/g) && editor.match(/<div/g) && editor.match(/</div>/g).length === editor.match(/<div/g).length, 'Make sure each of your <code>div</code> elements has a closing tag.')"

Discussion:
Challenge has an issue. Please describe how to reproduce it, and include links to screen shots if possible. I passed the test, but I should not, because I did not wrapped all my buttons within the same div element with the class "row". Screenshot:
Change:
<Helmet> <title>{block} | freeCodeCamp.org</title> </Helmet> <del> <div className='intro-layout-container'> </del> <ins> <Grid className='intro-layout-container'> </ins> <FullWidthRow> <div className='intro-layout'

Discussion:
Describe the bug Unnecessary horizontal page scroll bar. It is not the scrollbar, its the page scroll bar. To Reproduce Steps to reproduce the behavior: to , it does not occur in all pages. for the page horizontal scrollbar (Not the scrollbar). Expected behavior No horizontal scroll bar. Screenshots  Desktop: I have no other env to test. OS: Ubuntu. Browser: chrome, chromium, firefox. Version: not applicable. Additional context This visual problem is generated by: Applied to:
Change:
Your `sortSongs` function should use arrow function syntax. ```js <del> assert.match(code, /consts+sortSongss*=s*(s*)s*=>s*{s*}s*;?/) </del> <ins> assert.match(code, /const|lets+sortSongss*=s*(s*)s*=>s*{s*}s*;?/) </ins> ``` # --seed--

Discussion:
The description nor the tests mention the answer needs to use as demonstrated by this forum post here It is clear that the camper understood the assignment. So I don't think they should be penalized for using instead of so the tests should be updated to accept both 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