jiebi/CodeConvo huggingface dataset:
Change:
} } ] <del> } </del>  No newline at end of file <ins> } </ins>

Discussion:
<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --I didn't know where to put this, but in this exercise the example code on line 3 does not define the removedFromOurArray variable with the var keyword. This causes the test to fail if the user follows the exercise explicitly and only changes the code below the commented line. I imagine this would be frustrating to new users. Browser Name: Chrome Browser Version: Version 66.0.3359.181 (Official Build) (64-bit) Operating System: Windows 10 !
Working on it
I think this would need to raised on the repo for learn: cc
Hi we may have created some confusion on where to create issues and PR Issues are welcome to opened on any repo you like learn or the main repo. We ( will take care of moving them around as needed. Just tag us (me, Stuart are actively checking these) when in doubt. But its fine to just report an not worry ! As for which repo to make a PR against: All of the challenge execution logic is now moved to the learn repo. That is to say, it has become our challenge platform. Its based on Gatsby, and is a simple static app.The challenge themselves (just the content, instructions, and the tests) are on the main repo. They are now published as a npm package. And used on learn as a dependency.The main repo, will just serve the welcome page, user settings and portfolio.
Thank you for the information. I am just a beginner student, so I’m sure I’ve done something stupid. I didn’t know where to put this, but thought I’d raise this as it confused me and I thought it would confuse others. Please move this to the correct place or delete if appropriate. Thank you.
its perfectly alright. Thanks for reporting issues. Please keep it up (on any repo you prefer)
Change:
} } ] <del> } </del>  No newline at end of file <ins> } </ins>

Discussion:
<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Browser Name: Firefox Browser Version: 60.0.2 (up-to-date) Operating System: macOS High Sierra, v10.13.5 <img width="407" alt="screen shot 2018-06-13 at 11 16 17" src="https://user-"<img width="227" alt="screen shot 2018-06-13 at 11 16 38" src="https://user-"
While (8.8 + 8.6 + 9.0 + 8.3 + 7.9) / 5 = 8.52, the instructions say As Christopher Nolan didn't direct all of the movies listed, why do we need to find the average of all 5? In other words, don't we need to find the average of the movies that only have listed, which does comes to 8.675?
Good catch. I missed the “Nolan” qualification. I’ll see that it stays as/is. Thank you.
thank you for pointing that out! I also missed that. I'll revert the PR now.
Reopened with
Can someone confirm that no change is required? If yes please comment and close.
no change is required for this challenge. Here's a working solution: With that the original test, 8.675, passes.
Change:
# --description-- <del> When you want to know about someone's character or personality, you can ask, `What is (he/she) like?`. This question is about the qualities of a person, not about their physical appearance. Example: </del> <ins> When you want to know about someone's character or personality, you can ask, `What is (he/she) like?` or `What are they like?`. </ins> <del> Imagine you meet a new student in your programming class and you want to know more about her. </del> <ins> This question is about the qualities of a person, not about their physical appearance. Example: </ins> <del> You can ask a classmate, `What is she like?` </del> <ins> Imagine you meet a new student in your programming class and you want to know more about her. You can ask a classmate `What is she like?`. </ins> You are not asking if the new student likes computers or games; you are asking about her personality. Maybe she's friendly, smart, or really good at coding.

Discussion:
The course currently only supports binary gender, he and she, they is excluded. -Advance to 3rd chapter, task 41 -oberserve the text all platforms, all fw Please make this course more inclusive, with something like: What do/does (he/she/they) look like? !
The string "What is (he/she) like?" also appears in Task 42.
"they" is taught in task 43. Even if it is discussed in task43, it can still be used in respective string from Task 41 onwards.
I have updated the issue as asked . Please review it .
Hi there, Thanks for your interest in contributing. This issue has not been triaged yet, and a solution has not been agreed upon. Once the issue is open for contribution, you are welcome to create a pull request to reflect the issue consensus. Please also note that we typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue.
Hmmmmmm, While I am always advocating for inclusivity, in this case it may not make sense. Specifically because in English, even when using the singular "they", plural verb conjugations are used. "What does (he/she) look like?" -"What do they look like?" "What is (he/she) like?" -"What are they like?"
I have made the changes as said .
The following tasks need to be updated with these texts.
Change:
); const GridProjectBlock = ( <del> <div className='block block-grid grid-project-block'> <Link className='block-header' onClick={() => { this.handleBlockClick(); }} to={challengesWithCompleted[0].fields.slug} > <div className='tags-wrapper'> <span className='cert-tag'>{t('misc.certification-project')}</span> {!isAuditedCert(curriculumLocale, superBlock) && ( <Link className='cert-tag' to={t('links:help-translate-link-url')} > {t('misc.translation-pending')} </Link> )} </div> <div className='title-wrapper map-title'> {this.renderCheckMark(isBlockCompleted)} <h3 className='block-grid-title'>{blockTitle}</h3> </div> {this.renderBlockIntros(blockIntroArr)} </Link> </div> </del> <ins> <ScrollableAnchor id={blockDashedName}> <div className='block block-grid grid-project-block'> <Link className='block-header' onClick={() => { this.handleBlockClick(); }} to={challengesWithCompleted[0].fields.slug} > <div className='tags-wrapper'> <span className='cert-tag'> {t('misc.certification-project')} </span> {!isAuditedCert(curriculumLocale, superBlock) && ( <Link className='cert-tag' to={t('links:help-translate-link-url')} > {t('misc.translation-pending')} </Link> )} </div> <div className='title-wrapper map-title'> {this.renderCheckMark(isBlockCompleted)} <h3 className='block-grid-title'>{blockTitle}</h3> </div> {this.renderBlockIntros(blockIntroArr)} </Link> </div> </ScrollableAnchor> </ins> ); const blockrenderer = () => {

Discussion:
The anchors or whatever for the new RWD cert projects aren't working. to are taken to the block within that page to are not taken to the block within that page To be taken to the block within that page. Side effect: Clicking the breadcrumbs for these projects also doesn't take you to that part of the page Also, you can notice the URL change as you scroll down the page - the block/anchor thing gets at the end of the URL when you scroll to one. It does not get when you scroll to one of the cert projects on this page.
Change:
<ins> [![Stories in Ready](https://badge.waffle.io/FreeCodeCamp/freecodecamp.png?label=ready&title=Ready)](https://waffle.io/FreeCodeCamp/freecodecamp) </ins> <img src="https://s3.amazonaws.com/freecodecamp/logo4.0LG.png"> Free Code Camp!

Discussion:
We are currently grouping the articles in the Trending Guides section using a : But I think we should use and to group the items instead. This helps communicate the relationship of the links better, and allows us to remove the attribute from the code (ref: ). Pseudo code: Links in the Trending Guides section are rendered as a and are grouped within a . The change should be made to the following files: Learn platform: News platform: Forum platform: There is no visual regression All attributes in are removed (there are 2 of them in the file) Both Footer snapshot and e2e tests are updated accordingly Bonus point if you can merge tests in this suite into a single test case: This change is to improve cost efficiency as e2e tests are expensive to run.
This issue is not yet open for contribution. I'll wait for others to review the proposal first before marking the issue up for grab.
Can i contribute on this
Sounds like a plan. This is also a problem on and
Oh, thanks I forgot about /news and /forum. I found the repo for /news but I'm not sure where the code for /forum is. Could you help link it to the PR description? (I've already the /news link there.)
Here is the relevant code for the forum:
Alright, thank you Shaun! I'm going to open this one for contribution. we will be happy to review your PR if you are interested in contributing
Can I contribute to the above issue?
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 isnt open for contribution
Sorry, I'll need your (and the staff team's) help with this. The PR targeting /learn has been merged, but the changes include some CSS modifications and require local testing. I'm happy to apply the changes to the and repos myself, but I'm not really sure how to setup and test them properly I think it's probably faster to let a staff member handle these changes.
I know how to test and deploy forum changes, but I do not know how to test the changes in . Maybe can test please?
Change:
], "tests": [ "assert($("img").hasClass("smaller-image"), 'message: Your <code>img</code> element should have the class <code>smaller-image</code>.');", <del> "assert($("img").width() === 100, 'message: Your image should be 100 pixels wide.');" </del> <ins> "assert($("img").width() === 100, 'message: Your image should be 100 pixels wide. Browser zoom should be at 100%.');" </ins> ], "challengeType": 0, "nameEs": "Da tamaño a tus imágenes",

Discussion:
Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.111 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code:
Hmm, I can't repro this. Do you have your browser zoomed in at all? Have you tried any other browsers?
Hey Itegman, Thanks for the response, yes my browser was size at 75%. After setting zoom to 100% the challenged passed.
Closing as a duplicate of . We've got a PR up now that will add a warning about needing to be 100% zoom for this particular challenge.
Change:
"CSS has a property called <code>width</code> that controls an element's width. Just like with fonts, we'll use <code>px</code> (pixels) to specify the image's width.", "For example, if we wanted to create a CSS class called <code>larger-image</code> that gave HTML elements a width of 500 pixels, we'd use:", "<blockquote>&#60;style&#62;<br>&nbsp;&nbsp;.larger-image {<br>&nbsp;&nbsp;&nbsp;&nbsp;width: 500px;<br>&nbsp;&nbsp;}<br>&#60;/style&#62;</blockquote>", <del> "Create a class called <code>smaller-image</code> and use it to resize the image so that it's only 100 pixels wide." </del> <ins> "Create a class called <code>smaller-image</code> and use it to resize the image so that it's only 100 pixels wide.", "<strong>Note</strong><br>Due to browser implementation differences, you may need to be at 100% zoom to pass the tests on this challenge." </ins> ], "challengeSeed": [ "<link href="http://fonts.googleapis.com/css?family=Lobster" rel="stylesheet" type="text/css">",

Discussion:
Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.111 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code:
Hmm, I can't repro this. Do you have your browser zoomed in at all? Have you tried any other browsers?
Hey Itegman, Thanks for the response, yes my browser was size at 75%. After setting zoom to 100% the challenged passed.
Closing as a duplicate of . We've got a PR up now that will add a warning about needing to be 100% zoom for this particular challenge.
Change:
npm run create-next-step ``` <del> ## create-empty-steps </del> <ins> ### create-empty-steps </ins> A one-off script that automatically adds a specified number of steps. The challenge seed code for all steps created will be empty. **Note:** This script also runs [update-step-titles](#update-step-titles). <del> ### How to run script: </del> <ins> #### How to run script: </ins> 1. Change to the directory of the project. 2. Run the following npm command:

Discussion:
challenge-editor should be to the "How to work on practice projects" documentation here:
I'll tackle this today.
Change:
```js const stat = document.querySelectorAll('.stat')[1]; <del> assert.equal(stat.innerText, 'Health: 100'); </del> <ins> assert.equal(stat.innerText.trimEnd(), 'Health: 100'); </ins> ``` You should add a `strong` element in your third `.stat` element.

Discussion:
I was helping a with in the new JS curriculum and they weren't able to pass the tests because of the way they formatted their answer. Here was their code We should allow for that code to pass because they got it right. Here are the current tests For all of the tests that use we should instead update it to use a regex solution with instead. That will make it possible for campers to submit answers with different spacing. All of the tests with the to make sure they have a or element should stay the same though. For those, interested in working on this issue, please read through the first. There will be no assignment for this issue. If you are interested in working on it, then you can submit a PR The following code should pass regardless of different formatting with spaces. 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
Change:
it('shows test output when the tests are triggered by the keyboard', () => { cy.visit(locations.index); // first wait for the editor to load <del> cy.get(selectors.editor, { timeout: 10000 }); </del> <ins> cy.get(selectors.editor, { timeout: 15000 }); </ins> cy.get(selectors.hotkeys) .focus() .type('{ctrl}{enter}')

Discussion:
!
Dropping Firefox support temporarily with . This was causing me to slow down with the PRs and rapid testing we are doing on the staging. I will let someone else investigate this.
any thoughts on this one? I'll take a look when I can, but I figured you might have some insight.
I'll look into it soon. Will let you know when I get to the bottom of it.
Mrugesh shared two links to the CI runs that failed and both of them failed for the . So, I was looking at the test and saw a lot of explicit timeout increasing... this is probably the reason why it fails on Firefox. Because the timeout were increased by watching the time it took on Chrome and manually adjusting it. But Firefox normally needs a few more seconds to finish running (this is due to ). I think increasing the timeout limit should do the trick.
We do wait for the editor, but everything after that should be basically instantaneous. Thanks for investigating that, but it should be fixed for Firefox 80 () and that's what we run the tests on. Also, suggests we should be using which could be a factor, but would have thought that would make things fail entirely rather than run slowly. That could work, yeah. The strange thing is the dev mode works perfectly locally and the CI should be even faster, since it uses the built site.
The bug is fixed on Firefox but Cypress still manually triggers GC as it is said in the Cypress docs (also when you run the tests locally in Firefox, it'll show you a message about GC. This is because Cypress doesn't manually run GC on but when it's run in CI using then Cypress manually triggers GC). I agree. I don't think this is the reason. I couldn't reproduce the bug locally... maybe we should try to reproduce it in CI by running it repeatedly?
Right, but would this make a test fail? If it runs between tests, which is the default, it should just make the whole run a bit slower. If it's included in the timeout for a particular test, that would be a massive oversight. My assumption is that the only timeout you might hit because of this is the limit for the entire run. Sure.

I'll let decide when he wants to do this, though, since it makes deploying a bit of a headache (if you're being bombarded with fail negatives, I mean).
I am open to creating a new branch on the upstream if you need to test it on CI by adding random commits? In theory you should be able to test it on a fork as well.
Change:
tests: - text: The <code>AppWrapper</code> should render to the page. testString: assert((function() { const mockedComponent = Enzyme.mount(React.createElement(AppWrapper)); return mockedComponent.find('AppWrapper').length === 1; })()); <del> - text: The <code>Presentational</code> component should render an <code>h2</code>, <code>input</code>, <code>button</code>, and <code>ul</code> elements. </del> <ins> - text: The <code>Presentational</code> component should render to page. </ins> testString: assert((function() { const mockedComponent = Enzyme.mount(React.createElement(AppWrapper)); return mockedComponent.find('Presentational').length === 1; })()); - text: The <code>Presentational</code> component should render an <code>h2</code>, <code>input</code>, <code>button</code>, and <code>ul</code> elements. testString: assert((function() { const mockedComponent = Enzyme.mount(React.createElement(AppWrapper)); const PresentationalComponent = mockedComponent.find('Presentational'); return ( PresentationalComponent.find('div').length === 1 && PresentationalComponent.find('h2').length === 1 && PresentationalComponent.find('button').length === 1 && PresentationalComponent.find('ul').length === 1 ); })());

Discussion:
Describe your problem and how to reproduce it: Go to: Look for: Test outputs in the bottom-left corner Duplicated test output: Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Chrome Browser Version: 79 Operating System: Mac OS 10.13.6 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): !
The same duplicated test output exist in the following Challenge: Go to: Look for: Test outputs in the bottom-left corner Duplicated test output: The Presentational component should render an h2, input, button, and ul elements. !
You are correct, the 2nd test should actually state: The <codePresentational</codecomponent should render to the page.
Taking this up.
Change:
# --description-- <del> Add one final property to the object named `text`. Give this property the final `text.innerText` value from the `goTown` function. </del> <ins> Add one final property to the object named `text`. Give this property the same string value as the one assigned to `text.innerText` in the `goTown` function. </ins> # --hints--

Discussion:
I think we can make the instructions more clear. They are a bit confusing. Or something like that. Clear instructions. 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] Forum:
I think that is much clearer. We can open this up for contribution
Hi, is someone working on this issue? If not, I'd like to contribute.
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.
Change:
```html <!DOCTYPE html> <html> <head> <meta charset="UTF-8" /> <link rel="stylesheet" type="text/css" href="./styles.css" />

Discussion:
An issue was brought up in the forum where the user could not pass the challenge using firefox. They had the correct code and weren't using browser extensions. On google chrome and safari the test does pass. The test will only pass on Firefox using this code Correct answer not passing in firefox <img width="936" alt="Screen Shot 2022-01-25 at 8 44 56 AM" src="https://user-"Incorrect answer passing in firefox <img width="981" alt="Screen Shot 2022-01-25 at 8 45 31 AM" src="https://user-"- Device: [macbook pro] OS: [macOs Catalina] Browser: [Firefox] Version: [96.0.2]
Step 14 has the same issue. This is the correct code that passes in google chrome <img width="905" alt="Screen Shot 2022-01-25 at 8 57 21 AM" src="https://user-"Here is the same code but it doesn't pass with firefox <img width="915" alt="Screen Shot 2022-01-25 at 9 00 09 AM" src="https://user-"
Change:
/> ) : null} <SignoutModal /> <del> {isChallenge && !examInProgress && isRenderBreadcrumb ? ( <div className='breadcrumbs-demo'> <BreadCrumb block={block as string} superBlock={superBlock as string} /> </div> ) : isExSmallViewportHeight ? ( <Spacer size='xxSmall' /> ) : ( <Spacer size='small' /> )} </del> <ins> {isChallenge && !examInProgress && (isRenderBreadcrumb ? ( <div className='breadcrumbs-demo'> <BreadCrumb block={block as string} superBlock={superBlock as string} /> </div> ) : ( <Spacer size={isExSmallViewportHeight ? 'xxSmall' : 'small'} /> ))} </ins> {fetchState.complete && children} </div> {showFooter && <Footer />}

Discussion:
There is an extra spacer in the top of the donate page. It might be cause by the donate page or its wrappers. The spacer should be removed or adjusted so it does not show up unecessarly. The issue is viewable locally or on production by viewing the donate page. <img width="1067" alt="Screenshot 2024-07-23 at 3 02 34 PM" src=""- 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, can I be assigned to this task?
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.
sorry, the issue not so clear for me... where is extra space mentioned in issue? is it this gap under the topbar? !
I think we should just remove the spacers: If the page content needs some extra space below the nav, then the content could have some margin/padding in its CSS.
Change:
</style> <del> <img src="https://s3.amazonaws.com/freecodecamp/FCCStickers-CamperBot200x200.jpg" alt="freeCodeCamp sticker that says 'Because CamperBot Cares'"> </del> <ins> <img src="https://cdn.freecodecamp.org/curriculum/responsive-web-design-principles/FCCStickers-CamperBot200x200.jpg" alt="freeCodeCamp sticker that says 'Because CamperBot Cares'"> </ins> ``` # --solutions--

Discussion:
We need to replace all images and audio samples for the legacy content with the ones that were just to our freeCodeCamp cdn. Here are all of the files that will need to be updated Here are all of the new asset links