jiebi/CodeConvo huggingface dataset:
Change:
<!-- 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

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

(getUserInput) => $.get(getUserInput('url') + '/_api/get-tests?type=functional&n=4').then( (data) => { <del> assert.equal(data.assertions[3].method, 'browser.element'); </del> <ins> assert.equal(data.assertions[3].method, 'browser.elements'); </ins> assert.match(data.assertions[3].args[0], /('|")span#dates1/); assert.equal(data.assertions[3].args[1], 1); },
Change:
<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Affected page Add a link to the coding challenge with the problem. Your code Copy and paste the code from the editor that you used in between the back-ticks below: Expected behavior Add a clear and concise description of what you expected to happen. The code should pass the fcc tests Screenshots If applicable, add screenshots to help explain your problem. you can drag and drop, png, jpg, gif, etc. in this box. ! System (please complete the following information): Irrelevant Additional context Add any other context about the problem here. The solution at uses ( s missing ) and the tests are using that. It is inconsistent with the previous lesson, and according to the Zombie docs, we could either use ('span#name') or ('span#name', 1)
Hello there, Thank you, for taking the time to open this. It appears this was missed with the previous PR: , and issue. As such, it is a simple fix to correct the test at: So, I am going to open this up to first timers 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

Discussion:
(getUserInput) => $.get(getUserInput('url') + '/_api/get-tests?type=functional&n=5').then( (data) => { <del> assert.equal(data.assertions[3].method, 'browser.element'); </del> <ins> assert.equal(data.assertions[3].method, 'browser.elements'); </ins> assert.match(data.assertions[3].args[0], /('|")span#dates1/); assert.equal(data.assertions[3].args[1], 1); },
Change:
In this table, the left column represents the same duration as in the right column, but in seconds. The left middle-left cell should be instead of . <img width="293" alt="2021-05-25 -Learn Rosetta Code Convert seconds to compound duration freeCodeCamp org" src="https://user-"
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 our chat room or the forum 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:
| Input number | Output number                         | | ------------ | ------------------------------------- | | 7259         | <code>2 hr, 59 sec</code>             | <del> | 728640059    | <code>1 d</code>                      | </del> <ins> | 86400        | <code>1 d</code>                      | </ins> | 6000000      | <code>9 wk, 6 d, 10 hr, 40 min</code> | <div style="font-size:115%; font-weight: bold;">Details</div>
Change:
Description: I use IntelliJ Idea on Windows 10 with WSL2 to run the project locally. The specific problem I ran in to was running tests via the IDE instead of the command line. I had to configure IntelliJ to use the version of Node I have installed in WSL2. This is the error I encountered when trying to run the tests via the IDE: CMD.EXE was started with the above path as the current directory. UNC paths are not supported. Defaulting to Windows directory. 'jest' is not recognized as an internal or external command, operable program or batch file. Recommended fix, suggestions: I think it would be worth while to add a small section to the WSL set up doc () for anyone using IntelliJ products.
I really liked how the Windows and WSL set up guides were easy to read and follow! I think adding this would lower barrier of entry for people who are using or evaluating IntelliJ IDEs. If this change is approved I'd be happy to update this docs :)
Sure, go ahead and add a line to this area:

Discussion:
Essentially, you will edit and store your code on Ubuntu-18.04 with VS Code installed on Windows. <ins> If you use [IntelliJ Idea](https://www.jetbrains.com/idea/), you may need to update your Node interpreter and Npm package manager to what is installed on your WSL distro. You can check these settings by going to Settings > Languages & Frameworks > Node.js and NPM. </ins> ## Installing Docker Desktop **Docker Desktop for Windows** allows you to install and run database and services like MongoDB, NGINX, etc. This is useful to avoid common pitfalls with installing MongoDB or other services directly on Windows or WSL2.
Change:
<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Affected page Your code Expected behavior Importing must be outside the tag not inside it. This code above will pass the test cases even tho the font isn't applied and imported inside the tag. Screenshots As you can see the lobster font is not applied to the tag but it still passes all the tests. ! This is the right implementation of importing a tag ! System (please complete the following information): Device: Laptop OS: Windows 10 Browser: Chrome Version: 90.0.4430.212 (Official Build) (64-bit) Additional context Add any other context about the problem here.
Thanks for the report the regex for this one is a bit too permissive. It should check that the link is not inside the style tags (without using lookbehinds, because we've broken safari often enough recently)

Discussion:
You should import the `Lobster` font. ```js <del> assert(new RegExp('googleapis', 'gi').test(code)); </del> <ins> assert($('link[href*="googleapis" i]').length); </ins> ``` Your `h2` element should use the font `Lobster`.
Change:
<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Affected page Add a link to the coding challenge with the problem. Your code Copy and paste the code from the editor that you used in between the back-ticks below: Expected behavior Given that this is the Replit starter project and the GET route has no code, I expected test no. 3 to fail. Screenshots If applicable, add screenshots to help explain your problem. you can drag and drop, png, jpg, gif, etc. in this box. System (please complete the following information): Device: [PC] OS: [Windows 10] Browser: [chrome] Version: Version 91.0.4472.77 (Official Build) (64-bit) Additional context Add any other context about the problem here. I am working through this project and found test 3 passes even before I had written any code. I made a new copy of the Replit starter project and ran the tests to see if I could replicate the issue. Test 3 still passes. The github personal- file shows that it supposedly makes several post requests and a get request, but somehow it passes without GET or POST routes.
It seems asserts are not even run, because promises are not fulfilled. Not sure if this is to be expected, but I'm surprised there isn't timeout like in other tests. I guess internally that doesn't make test not finished, so there's nothing to timeout...? Adding before or each post request in , , , would make it timeout as expected.

Discussion:
# --instructions-- <del> 1.  Add your MongoDB connection string to `.env` without quotes as `DB` </del> <ins> 1.  Add your MongoDB connection string to `.env` without quotes as `DB` </ins> Example: `DB=mongodb://admin:pass@1234.mlab.com:1234/fccpersonallib` 2.  In your `.env` file set `NODE_ENV` to `test`, without quotes 3.  You need to create all routes within `routes/api.js`

let a = $.post(url, { title: 'Faux Book A' }); let b = $.post(url, { title: 'Faux Book B' }); let c = $.post(url, { title: 'Faux Book C' }); <del> Promise.all([a, b, c]).then(async () => { </del> <ins> await Promise.all([a, b, c]).then(async () => { </ins> let data = await $.get(url); assert.isArray(data); assert.isAtLeast(data.length, 3);

```js /** <del> Backend challenges don't need solutions, because they would need to be tested against a full working project. </del> <ins> Backend challenges don't need solutions, because they would need to be tested against a full working project. </ins> Please check our contributing guidelines to learn more. */ ```
Change:
The challenge instructions says "Use the <code+=</codeoperator similar to how it is shown in the editor.", but the seed code is empty It should mention the example instead of the editor. This needs the change of one word, as such I am opening this issue to first timers. This is the challenge And its related file Issues are not assigned, the first comprehensive PR is reviewed. If you haven't already done so, read the contributing guidelines at If you need any help feel free to reach on the contributors subforum on the forum, or the contributor chatroom at

Discussion:
# --instructions-- <del> Build `myStr` over several lines by concatenating these two strings: `This is the first sentence. ` and `This is the second sentence.` using the `+=` operator. Use the `+=` operator similar to how it is shown in the editor. Start by assigning the first string to `myStr`, then add on the second string. </del> <ins> Build `myStr` over several lines by concatenating these two strings: `This is the first sentence. ` and `This is the second sentence.` using the `+=` operator. Use the `+=` operator similar to how it is shown in the example. Start by assigning the first string to `myStr`, then add on the second string. </ins> # --hints--
Change:
<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Affected page Expected behavior The following two code snippets are both correct and semantically equivalent js, but one passes all tests and the other does not. Either both should pass or both should fail. Passes: Fails: Declaring multiple comma separated const's fails this test: Your code Copy and paste the code from the editor that you used in between the back-ticks below: System (please complete the following information): Browser: Firefox 90.0b6
The test currently checks for two separate declarations. You can view it here - I think the regex can be updated to fix this.
I can grab this, if no one else is working on it.
Hi any issue with the help wanted or first timers only label is open for contribution. So yeah you can start working on it.

Discussion:
```js const noWhiteSpace = __helpers.removeWhiteSpace(code); assert( <del> /constLOGIN=(['"`])LOGIN1/.test(noWhiteSpace) && /constLOGOUT=(['"`])LOGOUT1/.test(noWhiteSpace) </del> <ins> (/constLOGIN=(['"`])LOGIN1/.test(noWhiteSpace) && /constLOGOUT=(['"`])LOGOUT1/.test(noWhiteSpace)) || /const(LOGIN|LOGOUT)=(['"`])12,(?!1)(LOGIN|LOGOUT)=(['"`])34/.test(noWhiteSpace) </ins> ); ```
Change:
<!-- NOTE: If you want to become an author on freeCodeCamp, you can find everything here: --<!-- If you are reporting an issue with an article on our News publication, please follow this link to send an email to our editorial team --Describe your problem and how to reproduce it: Viewing Documentation in mobile view as shown in bellow image the content is narrower. Need to make the content little more wider for easy readability. This is also true in landscape view lot of empty space left both sides. Add a Link to the page with the problem: Recommended fix, suggestions (how would you update it?): If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): ! !
Thanks for the report I agree that margins are too wide. Would you be interested in creating a PR to fix this?
sure will work on this issue

Discussion:
.universal-nav a.translations-link { visibility: hidden; } <ins> body .content { max-width: 100%; } </ins> } /****** Cover Page ******/

color: var(--text-color-tertiary); } <ins> @media screen and (max-width: 768px) { .markdown-section { max-width: 90%; padding: 40px 15px 40px 15px; } } </ins> /****** CODE HIGHLIGHTING ******/ .token.string { color: #42b983;
Change:
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

Discussion:
be a rolling update or a manual update. The later is essential when changing dependencies or adding environment variables. <del> > [!DANGER] The automated pipelines are not handling dependencies updates at the </del> <ins> > [!ATTENTION] The automated pipelines are not handling dependencies updates at the </ins> > minute. We need to do a manual update before any deployment pipeline runs. #### 1. Manual Updates - Used for updating dependencies, env variables.

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

| npm (comes bundled with Node)                                                                 | `6.x`   | Does not have LTS releases, we use the version bundled with Node LTS | | [MongoDB Community Server](https://docs.mongodb.com/manual/administration/install-community/) | `4.0.x` | [Release Notes](https://docs.mongodb.com/v4.0/release-notes/)        | <del> > [!DANGER] </del> <ins> > [!ATTENTION] </ins> > If you have a different version, please install the recommended version. We can only support installation issues for recommended versions. See [troubleshooting](#troubleshooting) for details. If Node.js is already installed on your machine, run the following commands to validate the versions:
Change:
The challenge title of challenge Use && for a More Concise Conditional is not translatable on Crowdin ! (the greyed out text is for not translatable strings) An other challenge where the title is translatable ! this is the link for crowdin file: markdown file for the challenge:
mind taking a look?
I have manually marked the string as translatable today. After our workflows run tomorrow, I will confirm the string is still translatable - if it is not, I will investigate further.
Reopen if still and issue.
this actually happened again with last update
Just to add that this is also happening in pt-BR. The entry is blocked for translation. I suspect this has to do with the double ampersand.
Hello, we are a group of researchers developing machine learning techniques to locate issues suitable for newcomers, and our model consider this issue as likely a "good first issue". May we recommend you to label it as "good first issue" so newcomers know where to choose? Thank you!
thanks but it is not - this needs to be done through Crowdin pipeline, will need to do it, again

Discussion:
CROWDIN_API_URL: 'https://freecodecamp.crowdin.com/api/v2/' CROWDIN_PROJECT_ID: ${{ secrets.CROWDIN_PROJECT_ID_CURRICULUM }} CROWDIN_PERSONAL_TOKEN: ${{ secrets.CROWDIN_CAMPERBOT_SERVICE_TOKEN }} <ins> - name: Unhide Title of Use && For a More Concise Conditional uses: ./tools/crowdin/actions/unhide-specific-string with: filename: 'react/use--for-a-more-concise-conditional.md' string-content: 'Use &amp;&amp; for a More Concise Conditional' env: CROWDIN_API_URL: 'https://freecodecamp.crowdin.com/api/v2/' CROWDIN_PROJECT_ID: ${{ secrets.CROWDIN_PROJECT_ID_CURRICULUM }} CROWDIN_PERSONAL_TOKEN: ${{ secrets.CROWDIN_CAMPERBOT_SERVICE_TOKEN }} </ins>

<ins> name: 'Unhide Specific String' description: "Updates a specific string to be not hidden" runs: using: 'node12' main: './index.js' inputs: filename: description: 'name of file with specific string to hide' required: true string-content: description: 'text content of string to unhide' required: true </ins>

<ins> require('dotenv').config({ path: `${__dirname}/../../.env` }); const core = require('@actions/core'); const { getFiles } = require('../../utils/files'); const { getStrings, changeHiddenStatus } = require('../../utils/strings'); const filename = core.getInput('filename'); const stringContent = core.getInput('string-content'); const hideString = async (projectId, fileName, string) => { const fileResponse = await getFiles(projectId); const targetFile = fileResponse.find(el => el.path.endsWith(filename)); if (!targetFile) { core.setFailed(`${fileName} was not found.`); return; } const stringResponse = await getStrings({ projectId, fileId: targetFile.fileId }); const targetString = stringResponse.find(el => el.data.text === string); if (!targetString) { core.setFailed(`${string} was not found.`); return; } await changeHiddenStatus(projectId, targetString.data.id, false); console.log('string unhidden!'); }; const projectId = process.env.CROWDIN_PROJECT_ID; hideString(projectId, filename, stringContent); </ins>
Change:
Affected page Any profile with a portfolio item: To Reproduce 1) Go to above portfolio link 2) Scroll to first and only portfolio item 3) Be shocked and horrified at word-wrapping Expected behaviour There should be no word wrapping breaking the word. I suggest something be to the CSS like: Screenshots ! Reported on forum: 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
Hi I had a look at this. It appears that this line is creating the mess. Wouldn't it be better to just remove that rule? I've tested it through dev tools and it works. Also checked the source and it appears that is only referenced in , so there are probably no unwanted side effects. Unfortunately, I can't access the profile page on my local setup to test. On a sidenote, how could I setup my local instance so that I can access the profile page? Anyway, what do you think?
Potentially. But, as you say, only if there are no side-effects. It is in this section of the . If you want to make the change, and open a PR, I think that makes sense. We will QA it, and, if anyone notices the change breaking something else, then we can work from there. Thanks, for digging deeper into this.
Thanks! Will send a PR, tomorrow!

Discussion:
min-width: 150px; } <del> .media { word-break: break-all; } </del> /* Timeline pagination */ .timeline-pagination_list { list-style: none;
Change:
When trying to view a JS solution, the following error appears in dev, explaining the issue in production. It seems we followed the expected prop-types too early (ref: ). The object is still an object literal. Reported on forum:
I have the same problem as I said in the forum, the bottom error says it responded with 404 to the request for the certification on JS algorithms and data structures. Seems like there's an issue with the backend reaching that certification. !

Discussion:
type SolutionStateType = { projectTitle: string; <del> challengeFiles: ChallengeFileType[] | null; </del> <ins> files?: ChallengeFileType[] | null; </ins> solution: CompletedChallenge['solution']; isOpen: boolean; }; const initSolutionState: SolutionStateType = { projectTitle: '', <del> challengeFiles: null, </del> <ins> files: null, </ins> solution: null, isOpen: false };

return null; } <del> const { solution, githubLink, challengeFiles } = completedProject; </del> <ins> const { solution, githubLink, files } = completedProject; </ins> const onClickHandler = () => setSolutionState({ projectTitle, <del> challengeFiles, </del> <ins> files, </ins> solution, isOpen: true }); <del> if (challengeFiles) { </del> <ins> if (files) { </ins> return ( <button className='project-link-button-override'

name, user: { username } } = props; <del> const { challengeFiles, isOpen, projectTitle, solution } = solutionState; </del> <ins> const { files, isOpen, projectTitle, solution } = solutionState; </ins> return ( <div> {t(

<Spacer /> {isOpen ? ( <ProjectModal <del> files={challengeFiles} </del> <ins> files={files} </ins> handleSolutionModalHide={handleSolutionModalHide} isOpen={isOpen} projectTitle={projectTitle}

challengeType?: number; completedDate: number; challengeFiles: ChallengeFileType[] | null; <ins> // TODO: remove once files->challengeFiles is refactored files?: ChallengeFileType[] | null; </ins> }; // TODO: renames: files => challengeFiles; key => fileKey; #42489 export type ChallengeFileType =