jiebi/CodeConvo huggingface dataset:
Change:
The above steps will automatically trigger a run on the build pipeline for the `production-staging` branch. Once the build is complete, the artifacts are saved as `.zip` files in a cold storage to be retrieved and used later. <del> The release pipeline is triggered automatically when a fresh artefact is available from the connected build pipeline. For staging platforms, this process does not involve manual approval and the artifacts are pushed to the Client CDN and API servers. </del> <ins> The release pipeline is triggered automatically when a fresh artifact is available from the connected build pipeline. For staging platforms, this process does not involve manual approval and the artifacts are pushed to the Client CDN and API servers. </ins> > [!TIP|label:Estimates] > Typically the build run takes ~20-25 minutes to complete followed by the release run which takes ~15-20 mins for the client, and ~5-10 mins for the API to be available live. From code push to being live on the staging platforms the whole process takes **~35-45 mins** in total.

Discussion:
Hello, I am new to getting involved in open-source projects and simply want to start off slow in getting involved in the community. Under the topic header "Pushing changes to Staging Application" as stated in the second paragraph after step 5, "The release pipeline is triggered automatically when a fresh artefact is available from the connected build pipeline." did you mean "artifact"?
In this context, it's discussing build artifacts. Might just be the case of US English and British English.
Yes. We should probably change it to US English version, . PR is welcome.
You got this?
Oh - Looks like I had accidentally closed this. Up for grabs.
PR
Change:
# --description-- <del> Jake is explaining the purpose of his visit to Sarah. He's there to hand over something that Sarah needs, which will permit him access to certain areas. </del> <ins> Jake is explaining the purpose of his visit to Sarah. He's there to hand over something that Sarah needs, which will permit her access to certain areas. </ins> # --fillInTheBlank--

Discussion:
Jake is explaining the purpose of his visit to Sarah. He's there to hand over something that Sarah needs, which will permit him (should be her) access to certain areas. <!DOCTYPE html<html lang="en" <head</head<body</body</htmlNo 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
Thank you for reporting the issue. This issue is open to first-time code contributors to this repository. The file that you should be updating is 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.
Next step has similar error. Should be
Hii excellent catch. Solved it locally, will be raising a PR in few minutes. This my first valid pull request, pls assign me if possible !
Thank you for your interest in contributing. We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. Issues labeled 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.
Hii fixed the typos in both the task (154 & 155) ! ! Hope it clear all the test and get merged
Change:
return array; // Only change code above this line } <del> bubbleSort([1, 4, 2, 8, 345, 123, 43, 32, 5643, 63, 123, 43, 2, 55, 1, 234, 92]); </del> ``` # --solutions--

Discussion:
The following challenges have an example function call in the seed code. These function calls should be removed and the related tests should be clarified to reflect the call instead. This sorting challenge is correct and could be used for reference.
Hi, nhcarrigan. I'd like to try to help and solve it. I'm still learning about the project so I would like to ask a question so I can understand the issue better. There is a function call in the file.. bubleSort([1,2,3....]) (example: implement-bubble-) ! And it should be removed from the seed section and transferred to here, similarly to implement-quick-sort: ! ! Is it correct or are there other files that I should be concerned about?
That is correct, yes - this same change should be completed on the four files I've linked. I would, however, recommend holding off on working on this until we receive additional consensus that this is the best way to proceed. If you run in to any questions, feel free to review our or ask in our or the .
Sounds great!! Thanks for the fast response. I will wait until further notice.
Hi MuriloMarquesSantos, are you still interested in fixing this issue?
Change:
assert.strictEqual(scoreSpans[3].innerText, ", score = 30"); ``` <del> If a large straight is rolled, your `checkForStraights` function should enable the fifth radio button, set the value to `40`, and update the displayed text to `, score = 0`. </del> <ins> If a large straight is rolled, your `checkForStraights` function should enable the fifth radio button, set the value to `40`, and update the displayed text to `, score = 40`. </ins> ```js resetRadioOptions();

Discussion:
typo error on the console warning: If a large straight is rolled, your checkForStraights function should enable the fifth radio button, set the value to 40, and update the displayed text to , score = 0. i recreated the last step to get to the warnings. it's supposed to say :If a large straight is rolled, your checkForStraights function should enable the fifth radio button, set the value to 40, and update the displayed text to , score = 40. ---- not 0. <img width="442" alt="Screenshot 2024-08-25 at 8 08 39 PM" src=""- Device: Mac OS: Ventura 13.6.9 Browser: Brave, Safari Version: Brave - , Safari - Version 17.6 (.3.11.11.7, ) No response_
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:
"Replace the paragraph elements with an unordered list of three things that cats love.", "HTML has a special element for creating unordered lists, or bullet point-style lists.", "Unordered lists start with a <code>&#60;ul&#62;</code> element. Then they contain some number of <code>&#60;li&#62;</code> elements.", <del> "For example: <code>&#60;ul&#62;&#60;li&#62;milk&#60;/li&#62;&#60;li&#62;cheese&#60;/li&#62;&#60;ul&#62;</code> would create a bulleted list of "milk" and "cheese"." </del> <ins> "For example: <code>&#60;ul&#62;&#60;li&#62;milk&#60;/li&#62;&#60;li&#62;cheese&#60;/li&#62;&#60;/ul&#62;</code> would create a bulleted list of "milk" and "cheese"." </ins> ], "tests": [ "assert($('ul').length > 0, 'Create a <code>ul</code> element.')",

Discussion:
Challenge has an issue. Please describe how to reproduce it, and include links to screen shots if possible. What I see: You can apply a class to an HTML element like this: <h2 class="blue-text"CatPhotoApp<h2What I expected to see: You can apply a class to an HTML element like this: <h2 class="blue-text"CatPhotoApp</h2
Markdown's getting in the way, see screenshot. !
Change:
# --description-- <del> Since you subtracted health from the player, you need to check `if` the player's `health` is less than or equal to `0`. If it is, call the `lose` function. </del> <ins> Since you subtracted health from the player, you need to check if the player's `health` is less than or equal to `0`. If it is, call the `lose` function. </ins> # --hints--

Discussion:
There is a typo in Step 174, the structure of the phrase is harming translation effort as mention in crowdin by translator here is the sentence Here is the original issue they have recommended using I recommend something else Removing the code tags, the word if is used as an English word hinting about the keyword, and there is a hint about keyword in the hints, so I don't see an actual use for the code tags.
Your suggestion LGTM
You mean this? That would totally work I think
Change:
<meta attribute="value"> ``` <del> Tell the browser to parse the markup into multiple languages by creating a `meta` element as a child of the `head` element. Set its `charset` attribute to `UTF-8`. </del> <ins> Inside the `head` element, nest a `meta` element with an attribute named `charset`. Set to the value to `utf-8` which tells the browser how to encode characters for the page. Note that `meta` elements are self-closing. </ins> # --hints--

Discussion:
This particular lesson does not correctly explain the attribute. It says "Tell the browser to parse the markup into multiple languages by creating a meta element as a child of the head element. Set its charset attribute to UTF-8." which implies that the charset attribute can automatically translate the markup. Compare this with the explanation from Learn Basic CSS by Building a Cafe Menu: Step 3 which says "Inside the head element, nest a meta element with an attribute named charset set to the value utf-8 to tell the browser how to encode characters for the page. Note that meta elements are self-closing." see explanation above see explanation above No response Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] No response
I agree with updating the text here Let's go with this change html <meta attribute="value"` This has been opened 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 Happy coding
Change:
# --description-- <del> D3 is about visualization and presentation of data. It's likely you'll want to change the styling of elements based on the data. You can use a callback function in the `style()` method to change the styling for different elements. </del> <ins> D3 is about visualization and presentation of data. It's likely you'll want to change the styling of elements based on the data. </ins> For example, you may want to color a data point blue if it has a value less than 20, and red otherwise. You can use a callback function in the `style()` method and include the conditional logic. The callback function uses the `d` parameter to represent the data point: ```js

Discussion:
In the step: We see the text: "You can use a callback function in the style() method to change the styling for different elements." Which is a repetition in part of the later sentence "You can use a callback function in the style() method and include the conditional logic." I feel the first sentence can be skipped entirely and make for a better step overall. Instead of the current step text, we could rewrite as follows: No response N/A No response
opened pr that gets rid of first sentence
Change:
assert.equal(locations[4].name, 'kill monster'); ``` <del> Your fifth `locations` value should have a `button text` property with the value an array with three `Go to town square` strings. </del> <ins> Your fifth `locations` value should have a `button text` array with three `Go to town square` strings. </ins> ```js assert.deepEqual(locations[4]["button text"], ['Go to town square', 'Go to town square', 'Go to town square']); ``` <del> Your fifth `locations` value should have a `button functions` property with the value an array with three `goTown` variables. </del> <ins> Your fifth `locations` value should have a `button functions` array with three `goTown` variables. </ins> ```js assert.deepEqual(locations[4]["button functions"], [goTown, goTown, goTown]);

Discussion:
reported sentence that looks weird, and I agree. it is used in 4 files here is the sentence I noticed in the last file, we are using deepEquel, should we mention that array's variables' respective position matter?
Can I be assigned to this? We can simply improve it as "property with the value of an array".
contribution isn't open for issues with label , you are more than welcome to discuss how to improve it
I would shorten them to just use ... e.g. "Your fifth value should have a array with three strings."
there is no one has provided a better option yet, so I am opening this for contribution, and when the JS is published, we can come back to this when campers are taking the course. You should follow Tom comment here because no one has answered this, I think it doesn't matter 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 moderators will guide you through this.
Hello Sir, can you assign me this issue? hacktoberfest
how does this sounds? "Your fifth locations value should have a with the value being an array consisting of three strings." I for one think we don't need to over explain this, as the values are described in order most people will put them in that exact order.
Although, we are trying to include everyone, you are right this is me trying to overtune something simple. It's good, but we should keep Tom suggestion. In HTML/CSS projects steps, we are using the same sentence structure that Tom mentioned, so there will be comfort, and subtle hints that is an object that carry variables.
you can open a PR, after reading our guideline. more info in this comment
Your fifth locations value should have a property and an array value with three strings. kept most of the original wordings.
Opened a PR for this issue!
Change:
<ins> import { type FastifyPluginCallbackTypebox } from '@fastify/type-provider-typebox'; export const statusRoute: FastifyPluginCallbackTypebox = ( fastify, _options, done ) => { fastify.get('/status/ping', async (_req, _reply) => { return { msg: 'pong' }; }); done(); }; </ins>

Discussion:
This is a a health check endpoint
Check the issue of internet ping, connect with network [ ]way run of tickettttttttt....... thank
Change:
box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075), 0 0 8px rgba(102, 175, 233, 0.6); } <ins> .wallet { overflow-wrap: break-word; } </ins>

Discussion:
Describe the bug Some pages overflow horizontally on mobile browsers. To Reproduce Steps to reproduce the behavior: a mobile with a small enough screen (i.e. iPhone 6/7/8 in the chrome dev console) to to scroll horizontally (it should not work) on 'Show other ways to donate' to scroll Expected behavior The browser should not let you scroll horizontally. Screenshots Donate: ! Also, the welcome page: ! Desktop (please complete the following information): OS: Linux Browser chrome Version 76.0.3809.87 Smartphone (please complete the following information): Device: Galaxy S6 OS: 7.0 Browser chrome Version 76.0.3809.111
This looks like it's fixed on .dev - want to give it a quick test
Still there, I'm afraid. The wallets are too long and cause overflow. I'll have a fix in a sec.
Change:
); ``` <del> The third image should have an `src` attribute set to `https://cdn.freecodecamp.org/curriculum/cat-photo-app/cats.jpg`. </del> <ins> The third image should have a `src` attribute set to `https://cdn.freecodecamp.org/curriculum/cat-photo-app/cats.jpg`. </ins> ```js const catsImg = document.querySelectorAll('figure > img')[1];

Discussion:
I noticed that we are using both "a attribute" and "an attribute" in challenge descriptions. And we even use both in the same challenge (): <img width="596" alt="Screenshot 2024-05-21 at 22 44 29" src=""I think both are acceptable, since the articles depend on how we pronounce "src" ("es-ar-see" vs "source"), but I think we should stick to one for consistency. I'll let native English speakers make the call
I always pronounce it as , so I vote
I'm with Jessica on this one. The second sentence should be changed to .
This issue is open to first-time code contributors to this repository. The files that you should be updating are: 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. 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 everyone. This is a great pick up! I am happy to help out there and will get a initial PR up for review today :)
I have reviewed the changes made in PR, all the related file have been fixed correctly and checked locally.
Hello, This is my first Open source contribution so if you guys can give me feedback on what i did wrong and how i should correct it please guide me. from the seven files mentioned above, I have created pull request for each one which is as below. sorry if i messed up, as it is my first try. I am actively looking for any advice, suggestion, criticism. Thank You.
Change:
"" ], "tail": [ <del> "(function(t) { if(typeof t !== 'undefined') { return "Total = " + t; } else { return "Total is undefined";}})(total);" </del> <ins> "(function(){if(typeof total !== 'undefined') { return "total = " + total; } else { return "total is undefined";}})()" </ins> ], "solutions": [ "var myArr = [ 2, 3, 4, 5, 6];nvar total = 0;nnfor (var i = 0; i < myArr.length; i++) {n  total += myArr[i];n}"

Discussion:
Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. conditions are not displayed ... not abele to continue. !
It does still pass if the correct code is provided. Your code uses the variable named when the instructions ask for a variable called . For testers: Able to reproduce on Attempting to run any code, except passing code, does not make the tests appear as it has with previous similar issues. After successful code is run the tests appear, but will disappear again with a hard refresh.
ou that's right, i passed, but i only see conditions after i passed... tanks sludge256
Change:
# --hints-- <del> You should declare a `cleanInputString` variable. ```js assert.isDefined(cleanInputString); ``` Your `cleanInputString` variable should be a function. </del> <ins> You should declare a `cleanInputString` function. </ins> ```js assert.isFunction(cleanInputString);

Discussion:
The instructions in step 18 of the js beta to build a calorie counter says: Start by declaring a cleanInputString function that takes a str parameter. However if you misspell the function's name you receive this hint: You should declare a cleanInputString variable. I believe this message should be changed to say "function" instead of "variable" the hint should refer to a not a No response N/A No response
Similar issue was seen in step 28 where the hint said: You should declare an isInvalidInput variable. while the instructions were again to create a function: Start by creating a function called isInvalidInput – it should take a single str parameter. And again, similar issue in step38 hint says: You should declare an addEntry variable. while the step is asking for a function
From Pyramid Generator A function is a block of code that can be reused throughout your application. Functions are declared with the following syntax:
Step 42 mentioned in the previous comment should be fixed. It should say: “The function declaration tells JavaScript that the name identifier is going to be a function.” (Replacing ‘variable’ with ‘identifier’ and ‘keyword’ with ‘declaration’) My understanding is that a function is actually an object in js but I would be surprised if a js course starts telling learners to “declare an object called myFunction” instead of saying “declare a function called myFunction”. Edited…
Step 42 should be a separate issue IMO. It shouldn't be lumped in with the corrections being made to the calorie counter steps
Here the updates for this issue remove this hint and test js assert.isDefined(cleanInputString); the current second hint and test should say this instead js assert.isFunction(cleanInputString); remove this hint and test js assert.isDefined(isInvalidInput) remove this hint and test js assert.isDefined(addEntry); udpate the second hint to the following js assert.isFunction(addEntry); `
Change:
# --solutions-- ```js <del> function countingFractionsInARange(limit) { let result = 0; const stack = [[3, 2]]; while (stack.length > 0) { const [startDenominator, endDenominator] = stack.pop(); const curDenominator = startDenominator + endDenominator; if (curDenominator <= limit) { result++; stack.push([startDenominator, curDenominator]); stack.push([curDenominator, endDenominator]); </del> <ins> class PrimeSeive { constructor(num) { const seive = Array(Math.floor((num - 1) / 2)).fill(true); const upper = Math.floor((num - 1) / 2); const sqrtUpper = Math.floor((Math.sqrt(num) - 1) / 2); for (let i = 0; i <= sqrtUpper; i++) { if (seive[i]) { // Mark value in seive array const prime = 2 * i + 3; // Mark all multiples of this number as false (not prime) const primeSquaredIndex = 2 * i ** 2 + 6 * i + 3; for (let j = primeSquaredIndex; j < upper; j += prime) { seive[j] = false; } } </ins> } <ins> this._seive = seive; } isPrime(num) { return num === 2 ? true : num % 2 === 0 ? false : this.isOddPrime(num); } isOddPrime(num) { return this._seive[(num - 3) / 2]; } }; const primeSeive = new PrimeSeive(12001); function countingFractionsInARange(num) { const moebius = Array(num + 1).fill(1) // Generate Moebis function terms for (let i = 2; i <= num; i++) { if (!primeSeive.isPrime(i)) continue; for (let j = i; j <= num; j += i) moebius[j] *= -1; for (let j = i * i; j <= num; j += i * i) moebius[j] = 0; } // Evaluate totient sum let sum = 0; for (let i = 1; i <= num; i++) { const coeff = Math.floor(num / i - 2); sum += moebius[i] * Math.floor(coeff * coeff / 12 + 0.5); </ins> } <del> return result; </del> <ins> return sum; </ins> } ```

Discussion:
I've seen CI failing with the following error multiple times: <img width="1680" alt="Screenshot 2023-11-06 at 15 33 10" src=""The error can be seen here: I'm not sure if this is also an issue in /learn, but here is the link to the challenge: Link to the code: I haven't tried reproducing the issue locally, but I think running multiple times on that challenge would surface it. The test should always pass.
When it's a random failure like this, it means that the loop-protect timeout has been exceeded. Unless the solution algorithm is obviously terrible (and it isn't to me), then I think it's fine to delete the offending test.
At one point there was trying to go through the various solutions and optimize them, maybe he can take a look here too? Or just let do without that test.
I fixed up the ones with prime numbers. I can take a look at this one and see if a better algorithm is out there