jiebi/CodeConvo huggingface dataset:
Change:
"testString": "assert(code.match(/.penguins*?{[sS]*--penguin-skins*?:s*?grays*?;[sS]*}/gi), '<code>penguin</code> class should declare the <code>--penguin-skin</code> variable and assign it to <code>gray</code>.');" }, { <del> "text": "<code>penguin</code> class should declare the <code>--penguin-skin</code> variable and assign it to <code>white</code>.", "testString": "assert(code.match(/.penguins*?{[sS]*--penguin-bellys*?:s*?whites*?;[sS]*}/gi), '<code>penguin</code> class should declare the <code>--penguin-skin</code> variable and assign it to <code>white</code>.');" </del> <ins> "text": "<code>penguin</code> class should declare the <code>--penguin-belly</code> variable and assign it to <code>white</code>.", "testString": "assert(code.match(/.penguins*?{[sS]*--penguin-bellys*?:s*?whites*?;[sS]*}/gi), '<code>penguin</code> class should declare the <code>--penguin-belly</code> variable and assign it to <code>white</code>.');" </ins> }, { <del> "text": "<code>penguin</code> class should declare the <code>--penguin-skin</code> variable and assign it to <code>orange</code>.", "testString": "assert(code.match(/.penguins*?{[sS]*--penguin-beaks*?:s*?oranges*?;[sS]*}/gi), '<code>penguin</code> class should declare the <code>--penguin-skin</code> variable and assign it to <code>orange</code>.');" </del> <ins> "text": "<code>penguin</code> class should declare the <code>--penguin-beak</code> variable and assign it to <code>orange</code>.", "testString": "assert(code.match(/.penguins*?{[sS]*--penguin-beaks*?:s*?oranges*?;[sS]*}/gi), '<code>penguin</code> class should declare the <code>--penguin-beak</code> variable and assign it to <code>orange</code>.');" </ins> } ], "solutions": [],

Discussion:
<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --There is a type in the challenge "Basic CSS - Use CSS Variables to change several elements at once" The tests are asking the user to update the colours for three times, where it should be , and respectively Browser Name: Chrome Browser Version: 66.0.3359.181 Operating System: macOS Sierra 10.12.6 !
I'd be happy to make a pull request, but I don't know where to find the code
Hi I just ran into this issue too. I think you can found the code on . It's from line 4303.
Since it was a typo on the assignment why was it not changed simple penguin class should declare the --penguin-skin variable and assign it to gray. Passed penguin class should declare the --penguin-belly variable and assign it to white. Passed penguin class should declare the --penguin-beak variable and assign it to orange. Instead of all these plenty grammar and drama
Change:
You should assign a list comprehension that iterates over `row` to the `row_str` variable. ```js <del> ({ test: () => assert(runPython(`_Node(_code).find_class("Board").find_function("__str__").find_for_loops()[0].find_bodies()[0].find_variable("row_str").find_comp_iters()[0].is_equivalent("row")`)) }) </del> <ins> ({ test: () => (runPython(` import ast var = _Node(_code).find_class("Board").find_function("__str__").find_for_loops()[0].find_bodies()[0].find_variable("row_str") assert var.find_comp_iters()[0].is_equivalent("row"), "You should iterate over row" assert isinstance(var.tree.value, ast.ListComp), "It's not a list comprehension" `)) }) </ins> ``` The list comprehension assigned to the `row_str` variable should use `i` as iteration variable.

Discussion:
The step asks for a list comprehension, but the following code is accepted as a solution (with parenthesis): I believe the step must only accept the list comprehension with square brackets []: No response Device: Laptop OS: Windows 11 Browser: Brave Version: 1.64.116 No response
Thank you for reporting this issue. I don't think this is a huge problem, since the code works well with a generator expression too. However, since the instructions are asking for a list comprehension, it makes sense to fix the test. The helpers do not discriminate between the various comprehension types, so I'd import the module and check if the value of the variable is an instance of . This additional check should take place within .
Change:
- text: Your <code>red-box</code> class should have a <code>padding</code> property. testString: assert($('.red-box').css('padding-top') != '0px' && $('.red-box').css('padding-right') != '0px' && $('.red-box').css('padding-bottom') != '0px' && $('.red-box').css('padding-left') != '0px'); - text: Your <code>red-box</code> class should give elements 1.5em of <code>padding</code>. <del> testString: assert(code.match(/.red-boxs*?{(s|.)*?padding:s*?1.5em/gi)); </del> <ins> testString: assert(code.match(/.red-boxs*?{[sS]*padding:s*?1.5em/gi)); </ins> ```

Discussion:
I'm doing some practice at the link below but when I pressed "Run The Test" button the webpage froze Browser Name: Firefox Browser Version: 70.0 Operating System: Linux Mint 18.3 (Sylvia) !
When it happens: The issue happens if the test isn't done correctly, that is, if the padding of .red-box is not equal to 1.5em. If you set the padding to anything other than 1.5em or don't set the padding at all, the page freezes with some process running on an infinite loop probably (my laptop's fan started to turn on full speed). Can be reproduced on the following browsers: Browser Name: Google Chrome Browser Version: 78.0.3904.70 (Official Build) (64-bit)Browser Name: Chromium Browser Browser Version: 78.0.3904.70 (Official Build) snap (64-bit)Browser Name: Brave Browser Browser Version: 0.69.135 Chromium: 77.0.3865.120 (Official Build) (64-bit)Browser Name: Firefox Browser Version: 70.0 (64-bit) Canonical Operating System: Ubuntu 19.10
Definitely a regex issue -- pasting it into results in catastrophic backtracking. My first guess is the capture group just goes to infinity, happy to take a closer look.
I already made sure I put the padding with 1.5em within the red-box css class
Then there might be another issue, but when I tested, the issue only happened when the padding wasn't equal to 1.5em. If it was equal to 1.5em, the test passed and the modal with the save progress and go to next challenge came up and worked correctly.
This could be helped with landing, but the current automated challenge test suite needs to be replaced for the PR to be accepted. A potential solution is coming, but time estimates are long.
How does PR close this issue?
Not sure, go give it a test. My browser crashed on production and didn't when looking at this PR.
fixes a bad capture group in the regex for the solution test that was capable of causing stack overflow
Change:
savedChallenges, isChallengeCompleted, output, <del> executeChallenge </del> <ins> executeChallenge, previewMounted </ins> }: ShowClassicProps) { const { t } = useTranslation(); const [resizing, setResizing] = useState(false);

Discussion:
On the initial loading of a Step the preview is showing in the preview pane, but if you either open the preview in the pop-out window or toggle the preview pane off/on then the preview does not load again. All Steps in New RWD preview in pop-out window (preview does not load) page Preview button to toggle preview pane off/on (preview does not load) Preview should load in both pop-out window and after the preview pane has been toggled off/on. No response Verified with Chrome/Firefox on both Linux and Win11. Possibly related to issue , but I think this is newer and slightly different.
Just discovered that if you make any change in the editor (such as adding a single space) then the preview will refresh and display again. But you have to do that every time you either open the pop-out window or toggle the preview pane.
When the preview is blank the iframe attributes are not updated either (which makes sense I guess, it looks to be the default values). Blank before updating: After updating: It feels like a state issue.
The preview also disappears if you toggle the Instructions on any of the certification projects.
Yes, that's a separate issue. I dig around at this a bit, seems to have caused the problem. Before it, these issues aren't present.
Change:
# --description-- <del> You have accessed elements (characters) of a string before, using the index operator `[]`. You can also use the index operator to access a range of characters in a string with `string[x:y:h]`: </del> <ins> You have accessed elements (characters) of a string before, using the index operator `[]`. You can also use the index operator to access a range of characters in a string with `string[start:stop:step]`: </ins> ```python my_string = 'camperbot' <del> camper = my_string[0:6] cp = my_string[0:6:3] </del> <ins> my_string[0:6] == 'camper' # True my_string[0:6:3] == 'cp' # True </ins> ``` <del> Where `x` is the starting index, `y` is the ending index, and `h` is the step (the amount of characters to skip over). </del> <ins> Where `start` is the starting index (inclusive), `stop` is the ending index (exclusive), and `step` is the amount of characters to skip over. If not specified, `step` is default to 1. </ins> Create a variable named `card_number_reversed` and assign it the value of the first 4 characters of `card_number`.

Discussion:
In step 10 of Luhn Algorithm, we teach campers how to create a substring using the operator. I think the explanation is a little short and could improved by: Adding comment next to each example, showing the result of each operation (we are currently communicating the value via the variable name, but I don't think it's clear enough) Mention that the starting index is inclusive, and the ending index is exclusive Additionally, I think we could: Change to to have the syntax more self-descriptive Mention that the default value of is 1 Perhaps the description should be changed to: python mystring = 'camperbot' mystring[0:6] == 'camper' # True my_string[0:6:3] == 'cp' # True `
Different project but same kind of example: I remember we decided not to use because of translations, but using them in the code example and then explain what they mean is fine :+1:
are we able to open this up for contribution?
Personally, I'd prefer to change the snippet into the following: I agree with all the rest.
I've updated the issue description with Dario's code snippet. This issue is open for contributions. 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.
Whoops, sorry. I just noticed that Farhan is assigned to the issue. Are you working on this or could we mark this one up-for-grabs?
Yeah please mark this as up for grab
Change:
] ], "type": "hike", <del> "challengeType": 6 </del> <ins> "challengeType": 6, "nameEs": "JavaScript Lingo: Variables y capitalizaciónCamello", "descriptionEs": [ "Vamos a cubrir lo que constituye una variable, y el razonamiento detrás de la capitalizaciónCamello (<em>camelCase</em>).", "Una variable, también conocida como una 'var', es el nombre o el espacio para un booleano, una cadena, un número, u otra pieza de información estática.", "Puedes usar las Herramientas de desarrollo de Google para inspeccionar la página principal de FreeCodeCamp y buscar algunas variables.", "Tu 'declaras' variables por primera vez con <code>var</code> en frente de ella, pero después puedes referenciarla más adelante en tu programa.", "capitalizaciónCamello es una forma en la que juntas varias palabras y aún así las mantienes legibles. La primera letra de la primera palabra va en minúsculas al igual que el resto de la primera palabra, pero la primera letra de cada palabra que siga se escribe en mayúsculas. No hay espacios. Ejemplos: brianaAmaSusMascotas, laMejorComidaEsElQueso, y valeLaPenaAprenderProgramacion.", "Al asignar un nombre de variable, usa capitalizaciónCamello. Además, trata de mantener los nombres descriptivos y cortos para que los demás (¡e incluso tu!) puedan entender a lo que se refiere la variable simplemente por el nombre." ] </ins> }, { "id": "56b15f15632298c12f31518a",

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:
**User Stories:** 1. You should have an `input` element with an `id` of `"search-input"` <del> 1. You should have a `button` element with an `id` of `"search-button` </del> <ins> 1. You should have a `button` element with an `id` of `"search-button"` </ins> 1. You should have an element with an `id` of `"pokemon-name"` 1. You should have an element with an `id` of `"pokemon-id"` 1. You should have an element with an `id` of `"weight"`

Discussion:
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.
Change:
}: FormControlProps): JSX.Element => { const { controlId } = useContext(FormContext); <del> const defaultClasses = 'outline-0 block w-full py-1.5 px-2.5 text-md text-foreground-primary ' + 'bg-background-primary bg-none rounded-none border-1 border-solid ' + 'border-background-quaternary shadow-none ' + 'transition ease-in-out duration-150 focus:border-foreground-tertiary'; </del> const Component = componentClass || 'input'; <del> let variantClass; </del> if (Component !== 'textarea') variantClass = ' h-8'; //row and componentClass

Discussion:
onChange: func value?: string componentClass?: string placeholder?: string name?: string required?: string rows?: 4 type?: 'text' 'url'FormControl FormControl.Feedback
Form control for chapter: Need to alter the props to account for chapter needs, here is the link to the chakira component
Which prop is being used in the chapter that we are not passing in the component library? Since chapter views are limited, it might be easier to create the components with learn specifications and use those props to control the component. does that make senes?
Instead of checking the chaikra library and comparing it with the current component, I am better off checking chapter itself for prop it's using. for example, in this file we are using and , so I note these down and check if these 2 props are different from the props we are using. depend on how different they are, I may do from the follow: Add new value to existing prop. Add new prop to the component. Do nothing.
Here is what I propose we do. We could continue building the components with the learn spec and ship them. For the second sprint, we collect the Chapter requirements and update the components accordingly.
Change:
"difficulty": "2.10", "description": [ "Sum all the prime numbers up to and including the provided number.", <del> "A prime number is defined as having only two divisors, 1 and itself. For example, 2 is a prime number because it's only divisible by 1 and 2. 1 isn't a prime number, because it's only divisible  by itself.", </del> <ins> "A prime number is defined as having only two divisors, 1 and itself. For example, 2 is a prime number because it's only divisible by 1 and 2. 1 isn't a prime number, because it's only divisible by itself.", </ins> "The provided number may not be a prime." ], "challengeEntryPoint": "sumPrimes(10);",

Discussion:
Need to document the rename challenge tool and the i18n sync tool. Sometime later this week. Not urgent.
I can take this on?
Go for it, Thanks!
I will start with the rename challenge tool, for the i18n sync, I will wait news if it works now
Change:
# --description-- <del> You can build web forms that actually submit data to a server using nothing more than pure HTML. You can do this by specifying an action on your `form` element. </del> <ins> You can build web forms that actually submit data to a server using nothing more than pure HTML. You can do this by specifying an `action` attribute on your `form` element. </ins> For example:

Discussion:
There are a couple of wording changes needed on the lesson. In the description section, should be changed to In the instructions section, needs backticks around "input"
Change:
align-items: center; max-width: 960px; margin: 0 auto; <ins> padding: 0 20px; </ins> } @media screen and (max-width: 630px) { .learn-page-wrapper { <del> padding: 0 25px; </del> <ins> padding: 0 15px; </ins> } }

Discussion:
the text is touching the edges of the screen when the screen is between 650 and 750 pixels. Probably needs to wrapped in a grid container but not sure. <img width="706" alt="screen shot 2019-02-19 at 9 10 15 am" src="https://user-"
I have created PR to fix this. There was a media query that sets padding for small sizes (<630px device width). So I just padding for larger devices.
Change:
projectFormValuesSelector(state) ); const endingText = dedent( <del> `**Your browser information:** User Agent is: <code>${userAgent}</code>. **Challenge:** ${challengeTitle} **Link to the challenge:** ${href}` </del> <ins> `${i18next.t('forum-help.browser-info')}nn${i18next.t( 'forum-help.user-agent', { userAgent } )}nn${i18next.t( 'forum-help.challenge' )} ${challengeTitle}nn${i18next.t( 'forum-help.challenge-link' )}n${href}` </ins> ); <del> let textMessage = dedent( `**Tell us what's happening:** Describe your issue in detail here. </del> <ins> let textMessage = dedent(`${i18next.t( 'forum-help.whats-happening' )}n${i18next.t('forum-help.describe')}nn </ins> ${ projectFormValues.length <del> ? `**Your project link(s)**n` : `**Your code so far**` </del> <ins> ? `${i18next.t('forum-help.camper-project')}n` : i18next.t('forum-help.camper-code') </ins> } ${ projectFormValues ?.map(([key, val]) => `${key}: ${transformEditorLink(val)}n`) ?.join('') || filesToMarkdown(files) <del> } ${endingText}` ); </del> <ins> }nn ${endingText}`); </ins> const altTextMessage = dedent( <del> `**Tell us what's happening:** **Your code so far** WARNING The challenge seed code and/or your solution exceeded the maximum length we can port over from the challenge. You will need to take an additional step here so the code you wrote presents in an easy to read format. Please copy/paste all the editor code showing in the challenge from where you just linked. ``` Replace these two sentences with your copied code. Please leave the ``` line above and the ``` line below, because they allow your code to properly format in the post. ```n${endingText}` </del> <ins> `${i18next.t('forum-help.whats-happening')}nnnn${i18next.t( 'forum-help.camper-code' )}nn${i18next.t('forum-help.warning')}nn${i18next.t( 'forum-help.too-long-one' )}nn${i18next.t('forum-help.too-long-two')}nn${i18next.t( 'forum-help.too-long-three' )}nn```n${i18next.t('forum-help.add-code-one')}n${i18next.t( 'forum-help.add-code-two' )}n${i18next.t('forum-help.add-code-three')}nn```n${endingText}` </ins> ); const category = window.encodeURIComponent(helpCategory || 'Help');

Discussion:
We want to localize the Ask-To-Help template that pre-fills the post on the forum. ! The above button which takes you to the forum should render this template: ! In the localized version instead.
Should be able to tackle this today, I think.
Sure. Not a high priority, so take your time.
Change:
--- # --description-- <del> Now that you have some basic understanding of `block` and inline `elements`, pull up your list of `block` and `inline` elements from a couple questions ago and see if you can identify which of the following elements are `block` elements and which are `inline` elements. </del> <ins> Now that you have some basic understanding of `block` and `inline` elements, pull up your list of `block` and `inline` elements from a couple questions ago and see if you can identify which of the following elements are `block` elements and which are `inline` elements. </ins> # --question--

Discussion:
There are some small issues that need to be fixed in the following files: optionfor elementsinline"Check your code" String` This looks like something that can be fixed by "first-time" code contributors to this repository. The files you should look at to work on a fix are those linked above. 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.
Hi I'd like to work on this issue. Thanks
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.
Change:
# --hints-- <del> You should reassign and empty array to your `diceValuesArr` variable. </del> <ins> You should reassign an empty array to your `diceValuesArr` variable. </ins> ```js assert.match(code, /consts+rollDices*=s*(s*)s*=>s*{s*diceValuesArrs*=s*[s*]s*;?/);

Discussion:
There is a typo in the Hint Message of Step 15 of Building a Dice Game, as shown in the Screenshots area. I will raise a PR for it since it is just a typo. The hint message should display: "You should reassign an empty array to your diceValuesArr variable." ! Device: Laptop OS: Windows 11 Browser: FireFox Version: 125.0.2 (64-bit) No response
Change:
## Instructions <section id='instructions'> <del> The navigation bar on this site currently inherits its <code>background-color</code> from the <code>header</code> element. Starting with that color as a base, add a <code>background-color</code> to the <code>nav</code> element so it uses the same cyan hue, but has 80% saturation and 25% lightness values to change its tone and shade. </del> <ins> All elements have a default <code>background-color</code> of <code>transparent</code>. Our <code>nav</code> element currently appears have a <code>cyan</code> background, because the element behind it has a <code>background-color</code> set to <code>cyan</code>. Add a <code>background-color</code> to the <code>nav</code> element so it uses the same <code>cyan</code> hue, but has <code>80% saturation</code> and <code>25% lightness</code> values to change its tone and shade. </ins> </section> ## Tests

Discussion:
Not really an issue but it threw me off. In the visual design challenge linked below, the second paragraph states that the navigation bar inherits its background from the header. Well I wondered so I set the position of the navigation to relative and the top to 20px (and the header text color black so you can see the white text against the white body) and clearly the background of the nav isn't cyan, it's white. Children have transparent backgrounds. That's why they seem cyan against a parent with a cyan background. Browser Name: Chrome Browser Version: Version 68.0.3440.106 (Official Build) (64-bit) Operating System: MacOS !
Interesting wording. It wouldn't be right to say the children of an element inherit its background color. The initial value of is The simplest solution to this would just be a change of wording
Fixed in
This was fixed in . / / please close it