jiebi/CodeConvo huggingface dataset:
Change:
This should be a relatively easy fix for a first-time contributor :) This challenge says the first two numbers are 1 and 1 when in fact the first two numbers are 0 and 1. The first few numbers are: 0, 1, 1, 2, 3, 5 and 8 So when you update the text to also check the tests and make sure this doesn't change any of the expected test outcomes. The text should correctly state the first numbers as 0, 1, 1, 2, 3, 5 and 8 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
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 The affected file can be found here:
Hello! I'm a rookie software developer and I'm looking for a "good first issue" to start contributing to open-source projects. So could I be assigned to fix this issue please?

Discussion:
Given a positive integer `num`, return the sum of all odd Fibonacci numbers that are less than or equal to `num`. <del> The first two numbers in the Fibonacci sequence are 1 and 1. Every additional number in the sequence is the sum of the two previous numbers. The first six numbers of the Fibonacci sequence are 1, 1, 2, 3, 5 and 8. </del> <ins> The first two numbers in the Fibonacci sequence are 0 and 1. Every additional number in the sequence is the sum of the two previous numbers. The first seven numbers of the Fibonacci sequence are 0, 1, 1, 2, 3, 5 and 8. </ins> For example, `sumFibs(10)` should return `10` because all odd Fibonacci numbers less than or equal to `10` are 1, 1, 3, and 5.
Change:
Currently, the instructions in the module, which happens to be a part of the module ( of the course ), suggest the following as the value of the variable: For the sake of more clarity, I think the value of the variable should be as follows: NOTE: There should a forward slash ( ) before the and should be enclosed within quotes because that particular part is supposed to be a string. The value of the variable should be as follows: NOTE: There should a forward slash ( ) before the and should be enclosed within quotes because that particular part is supposed to be a string. <img width="794" alt="image" src="https://user-"- Device: Laptop OS: macOS 13.0.1 Browser: Chrome Version: 107.0.5304.110 No response_

Discussion:
You can respond to requests with a file using the `res.sendFile(path)` method. You can put it inside the `app.get('/', ...)` route handler. Behind the scenes, this method will set the appropriate headers to instruct your browser on how to handle the file you want to send, according to its type. Then it will read and send the file. This method needs an absolute file path. We recommend you to use the Node global variable `__dirname` to calculate the path like this: ```js <del> absolutePath = __dirname + relativePath/file.ext </del> <ins> absolutePath = __dirname + '/relativePath/file.ext' </ins> ``` # --instructions--
Change:
Similar to issue Please also update another step that has the same issue and should get a similar fix: The sentence: "will only return Yes if num is greater than 5 and less than 10. The same logic can be written as:" should be changed to: "This will only..." (adding This is enough to fix it as a reference to the previous code block) And similarly for this step as well: Multiple As described above No response N/A No response
Proposed change: Question - do we use or for string literals?
"yes" i think
Please assign this issue to me i think can fix this and make my first contribution to open source
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.
I have created a pull request, what should i do next ?(It's my first contribution, don't mind my stupid questions please)

Discussion:
Sometimes you will need to test more than one thing at a time. The <dfn>logical and</dfn> operator (`&&`) returns `true` if and only if the <dfn>operands</dfn> to the left and right of it are true. <del> The same effect could be achieved by nesting an if statement inside another if: </del> <ins> The same effect could be achieved by nesting an `if` statement inside another `if`. </ins> ```js if (num > 5) {

return "No"; ``` <del> will only return `Yes` if `num` is greater than `5` and less than `10`. The same logic can be written as: </del> <ins> This code will return `Yes` if `num` is greater than `5` and less than `10`. The same logic can be written with the <dfn>logical and</dfn> operator. </ins> ```js if (num > 5 && num < 10) {

The <dfn>logical or</dfn> operator is composed of two pipe symbols: (`||`). This can typically be found between your Backspace and Enter keys. <del> The pattern below should look familiar from prior waypoints: </del> <ins> The pattern below should look familiar from prior waypoints. </ins> ```js if (num > 10) {

return "Yes"; ``` <del> will return `Yes` only if `num` is between `5` and `10` (5 and 10 included). The same logic can be written as: </del> <ins> This code will return `Yes` if `num` is between `5` and `10` (`5` and `10` included). The same logic can be written with the <dfn>logical or</dfn> operator. </ins> ```js if (num > 10 || num < 5) {
Change:
In the build a bike shop interactive project, the term "subshell", also "sub shell" (1 instance) is first used in step 1450 as an instruction without any definition of what a sub shell / subshell is. The challenge has been using subshells since much earlier in the tutorial as well as in the prior coding challenges where bash is used to access a PSQL database, but the term is never explained. This creates cognitive friction during this step and doesn't allow for the "interactive video game flow state" that is desired in the FCC curriculum. I'd suggestion a simple sentence that explains what a subshell is before using the term as part of a coding instruction step. It would probably be best to introduce this term back in the Build a student database project since that is the first occurence of using the syntax NA - for instructions issue NA - for instructions issue No response Device: [Laptop] OS: [e.g. iOS 12.6.1] Browser: [Chrome] Version: [e.g. 109] Address how the wording interferes with the flow state described here: .
Where should I add the definition of subshell ? can you tell me the name of the file and path of the file ? Definition of Subshell : A subshell is a child process launched by a shell (or shell script). A subshell is a separate instance of the command processor. Also, is above definition of subshell correct ?
Hey do you mind taking a look and triage this?
I really didn't think anything needed to be here. Campers have been using subshells quite a few times before this course. It's never thoroughly explained exactly what it is, but it's explained how it behaves... step in OP: next step: A forum search yields no results of people asking about this: I decided to add a small snippet in the course before this where that syntax is first used to hopefully ease campers into the terminology.

Discussion:
1: "Move the .target element from #location1 to #location2.", 2: "Change the background color of .target to red.", 3: "Change the background color of the even-numbered targets to red.", <del> 4: "Change the background color of the target4 to red.", 5: "Clone the target2 in #location1 so that it also exists in #location2.", 6: "Remove the target3 from element from #location1.", </del> <ins> 4: "Change the background color of target4 to red.", 5: "Clone target2 in #location1 so that it also exists in #location2.", 6: "Remove the target3 element from #location1.", </ins> 7: "Check the following checkboxes using jQuery.", 8: "Make the text input field read-only.", <del> 9: "Select the target2 option in the select box.", </del> <ins> 9: "Select target2 option in the select box.", </ins> 10: "Add the following css classes to .target: 'animated' and 'hinge'.", 11: "Use jQuery to read the data of .target.", 12: "Use 'length' to count the number of child elements in #location1, then display that value in #location2.",
Change:
It isn't a huge deal, but I do think the camper has a point, see the forum thread for more info. I think updating the example code with something less ambiguous wouldn't be a horrible idea. Current example New example (I can't think of anything better right now, you get the point). Less ambiguous example code that does not involve letter case logic or identifiers with the word in it when teaching about and . 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]
I agree, the example is unnecessarily confusing. I have submitted a pull request that uses a classic fruit example. The console log is also more explicit on what is being selected. Additionally, may I suggest that we also change the instructions to be more explicit? So instead of: it'll be something like:Additionally, additionally, may I also suggest we expand the explanation on strict equality testing? So add a simple sentence like: "Strings with different cases will be treated as different values"
I guess the conditions can be clarified, but I don't remember seeing this being a problem. That isn't how strict equality works. It has to do with type coercion. Letters with different casings always have different values.
Yes I get that, but for this specific example, I just thought it would be good to keep it simple. On second thought, the explanations / instructions are good enough. Lets leave it as it is.
hello can you please tell me why my pull requests are getting blocked when I am trying to close an issue

Discussion:
Here is an example of a `switch` statement: ```js <del> switch (lowercaseLetter) { case "a": console.log("A"); </del> <ins> switch (fruit) { case "apple": console.log("The fruit is an apple"); </ins> break; <del> case "b": console.log("B"); </del> <ins> case "orange": console.log("The fruit is an orange"); </ins> break; } ```
Change:
It would be nice if we allowed the camper to log out the result without having the last test fail because of it. One option might be to use code comments as delimiters to help make the regex more targeted. The camper should be allowed to log out the result without failing with the correct code. 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]
We could update the test to check for the assignment operator, instead of just a variable reference:
To fix the issue change the third test: To what Naomi suggested Here is the file for the challenge: If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our prolific contributors will guide you through this.
Can I work on this issue ? It would mean a lot
Go for it.
Can I work on this issue?

Discussion:
The quotient variable should only be assigned once ```js <del> assert(code.match(/quotient/g).length === 1); </del> <ins> assert(code.match(/quotients*=/g).length === 1); </ins> ``` # --seed--
Change:
Step 96Passed Give wave four waypoints starting at 10%, and incrementing by 10%. tests allow duplicate waypoints for the four required percentages. tests allow other waypoint values not specified in the instructions. wave { 10% { } 20% { } 10% { } 30% { } 10% { } 40% { } 10% { } 50% { } } When I read the instructions, I thought it said do four wave points starting at ten and add ten to each one. Once I failed. I calculated it to do each ten and add ten percent to each one after. I guess even though I did not read the instructions the way they were adviced I found a bug. I passed and when I went to next step it automatically fixed my mistake and removed the 50% also. 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] The instructions from what I read confused me to do four tens and add ten percent under each one. I was able to find the bug due to this so yay I am pleased to help. By doing a total of four I was able to add 50 percent, on the last one too. My suggestion to fix the sentence on instructions, would be to not say make four waves starting at ten. Instead maybe you could say make four waves start at 10 percent and then for the rest add ten percent to each one for a total of four waves only.
We should add new test with hint as following Here is the test If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our prolific contributors will guide you through this.
Can I work on this ?
go for it. Edit: btw if you solve one of the two issue, leave the other for first timer.
This test should be at the last of the other tests right? I mean after completing the other tests. Checking for 4 wavepoints should be the last one right? like this : !
Good point , if it's earlier it would trigger before the other, and wouldn't provide coherent hints for different issues.
, I am a first-timer so I do not really know where to make these changes . Also do I need to add the logic using jest or can I just add it to the call-back function of the event listener of that button which submits the user input for that challenge. can i assist you ?
Im working on this. Find another issue.
I have made the changes (addition of code which is mentioned in the above screenshot) in this file : ! This should work now right?
yeah you can work since obviously you got it assigned to yourself first . I am just here to learn . I just want to get familiar with the workflow that's it .

Discussion:
assert([...[...new __helpers.CSSHelp(document).getCSSRules('keyframes')].find(rule => rule?.name === 'wave')?.cssRules].some(css => css?.keyText === '40%')); ``` <ins> You should have 4 waypoints in your keyframe. ```js assert([...[...new __helpers.CSSHelp(document).getCSSRules('keyframes')].find(rule => rule?.name === 'wave')?.cssRules].length === 4); ``` </ins> # --seed-- ## --seed-contents--
Change:
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.

Discussion:
}; const StepPreview = ({ <del> disableIframe }: Pick<PreviewProps, 'disableIframe'>) => { </del> <ins> disableIframe, previewMounted }: Pick<PreviewProps, 'disableIframe' | 'previewMounted'>) => { </ins> return ( <Preview className='full-height'

savedChallenges, isChallengeCompleted, output, <del> executeChallenge </del> <ins> executeChallenge, previewMounted </ins> }: ShowClassicProps) { const { t } = useTranslation(); const [resizing, setResizing] = useState(false);

showToolPanel: false })} notes={<Notes notes={notes} />} <del> preview={<StepPreview disableIframe={resizing} />} </del> <ins> preview={ <StepPreview disableIframe={resizing} previewMounted={previewMounted} /> } </ins> testOutput={ <Output defaultOutput={defaultOutput} output={output} /> }

isFirstStep={isFirstStep} layoutState={layout} notes={<Notes notes={notes} />} <del> preview={<StepPreview disableIframe={resizing} />} </del> <ins> preview={ <StepPreview disableIframe={resizing} previewMounted={previewMounted} /> } </ins> resizeProps={resizeProps} testOutput={ <Output defaultOutput={defaultOutput} output={output} />
Change:
I've come across two forum posts from Safari users in the past few days saying that they can't pass step 47 even though their CSS is correct. Based on the hint they are getting, the test that is not passing is: I'm wondering if Safari has recently changed the string being returned for the border properties when set to ? I don't have a mac so I can't test this for myself. Opening this issue with the hopes that a Safari user can figure out what is going on here. Should be tested on a very recent version of Safari. This is the correct CSS but it is apparently not passing for Safari users. Correct CSS should pass. No response For both posters, user agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.4 Safari/605.1.15 No response

Discussion:
```js const borderBottom = new __helpers.CSSHelp(document).getStyle('fieldset:last-of-type')?.borderBottom; <del> assert(borderBottom === 'none' || borderBottom === 'medium none'); </del> <ins> assert(borderBottom === 'none' || borderBottom === 'medium none' || borderBottom === 'medium'); </ins> ``` # --seed--
Change:
The wording on this step is a bit awkward. Based on , the wording isn't quite accurate. This resulted in the camper writing the following code: I'm not sure how to better describe this, tbh. No response System info isn't relevant for a verbiage issue (: No response
Agreed, that is clunky. Just to get the ball rolling.
is anyone working on this, but i can take this up
Hey there, This issue is still under discussion and has not been opened up for contribution yet.
Hi there, I read through the issue related to the wording in step 5 of the 'Learn CSS Colors by Building a Set of Colored Markers' challenge, and I think I might have a suggestion for how to improve the wording. Here's a revised version of the step that I came up with: 'Add a new meta element for each attribute that you want to specify. To specify the viewport attributes, add the following meta element to the head of your HTML document: <meta name='viewport' content='width=device-width, initial-scale=1.0'' I hope this helps clarify the step for other campers. Let me know if you have any feedback or if there's anything else I can do to help with this issue.
What about :
Simpler language is better. Complex sentence structure is harder for learners (and non-learners tbh) to understand. I like wording, as its close to MDN's. We really need to go on a linguistic simplification campaign though the lessons. I just haven't had the time to do so.
I like this wording, it's much clearer than the current instructions. Can I open a PR with these changes?
What did we finalize?
Thanks for opening this issue. This looks like something that can be fixed by "first-time" code contributors to this repository. Here are the files that you should be looking at to work on a fix: List of files: The of the challenge should be updated to the following text: 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.

Discussion:
# --description-- <del> You can have multiple self-closing `meta` elements on a web page. What distinguishes one `meta` element from the other is the attribute. You should add a new meta element for each attribute you want to specify. </del> <ins> You can have multiple self-closing `meta` elements on a web page. Each `meta` element adds information about the page that cannot be expressed by other HTML elements. </ins> Add another self-closing `meta` element within the `head`. Give it a `name` attribute set to `viewport` and a `content` attribute set to `width=device-width, initial-scale=1.0` so your page looks the same on all devices.
Change:
In chapter, we have files that run scripts when the is finished, it use and for this, we can do the same here to solve the issues related to installing needed files, copy and stuff a like, and provide a easier way to setup the curriculum for newer developers. This should stop issues which these PRs try to solve, like and , that are related to setting up freeCodeCamp. Here is the file in chapter , for more context.
I dislike post/pre -install scripts a lot. Actually, I dislike most life-cycle scripts. However, I would be fine with adding a script. Essentially, what is missing with the seed step is:
can we not add to the npm script?
Adding it to the postinstall script would duplicate the run in the CI and deployment pipelines, since it is also included in prebuild. I'd lean more toward Shaun's solution.
I don't mind, as long as the issue is solved, one more agreement and we can open it for contribution.
I see what you mean, it does add a bit of an overhead. It does solve this particular issue albeit with a bit of an overhead. I am not sure of the overall impact, but I'd presume it is minimal? I am happy to re-write it to what was suggested above. But does it make more sense for it to be part of the install lifecycle () script or the develop () lifecycle? let me know your thoughts. Thanks.
I have no idea, I don't meddle with the config files, or scripting tools. This is outside my scope, I just hate that new contributors are facing issues installing the repo.
It should be as a script, like Shaun suggested:
If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our prolific contributors will guide you through this.

Discussion:
"lint:ts": "tsc && tsc -p config && tsc -p tools/ui-components && tsc -p utils && tsc -p api", "lint:prettier": "prettier --list-different .", "reload:server": "pm2 reload api-server/ecosystem.config.js", <ins> "preseed": "npm-run-all create:*", </ins> "seed": "cross-env DEBUG=fcc:* node ./tools/scripts/seed/seed-demo-user", "seed:certified-user": "cross-env DEBUG=fcc:* node ./tools/scripts/seed/seed-demo-user certified-user", "serve:client": "cd ./client && pnpm run serve",