jiebi/CodeConvo huggingface dataset:
Code change:
is2018DataVisCert, isApisMicroservicesCert, isFrontEndLibsCert, <del> is2020QaCert, is2020InfosecCert, </del> <ins> isInfosecQaCert, </ins> isJsAlgoDataStructCert, isRespWebDesignCert } = this.props;

Related discussion:
text: Some users can claim python, new QA, and new infosec certifications without submitting their required projects on .dev. It seems the api does not find the cert challenge and proceeds by setting the related cert flag on the user object to true. The issue can be resolved by reseeding the db locally. I cannot reproduce this issue at the moment, but I will keep this open in case other users are experiencing the same issue.
Hello! I tested this issue, and I was able to claim the certifications without completing the projects.
could you check if you can see the certification after claiming it? I'm just wondering if this is purely a client-side issue.
I am able to see the four certificates I could claim, yes.
Thanks for checking that. In that case, while it seems likely that it will fine if the database is migrated, the api should definitely default to rejecting certifications it does recognise.
Yes We Can Claim Python Certification Without submitting the Projects.
that's really serious
Code change:
is2018DataVisCert, isApisMicroservicesCert, isFrontEndLibsCert, <del> is2020QaCert, is2020InfosecCert, </del> <ins> isInfosecQaCert, </ins> isJsAlgoDataStructCert, isRespWebDesignCert } = this.props;

Related discussion:
text: Currently when you complete/claim a certificate there's an entry on the timeline: <img width="582" alt="Screen Shot 2020-05-27 at 9 37 55 AM" src="https://user-"This doesn't seem to be working for the new Scientific Computing with Python, Data Analysis with Python, and Machine Learning with Python certificates.
I'm a new contributor but I'd like to help out on this.
I think this is mostly working. You just need to refresh the page before it shows up... <img width="598" alt="Screen Shot 2020-05-27 at 11 34 12 AM" src="https://user-"Edit: hmm, it seems to be working locally, but not on .dev - the "view cert" button is there in both environments - it just doesn't show on the timeline on .dev
Ah, interesting. This does seem to work locally but not on .dev for some reason.
This may be a one off issue related to where the new/split certificates (Quality Assurance, Information Security, Scientific Computing with Python, Data Analysis with Python, and Machine Learning with Python) were not seeded to the .dev database for some reason. I can confirm this is working locally like mentioned above. thank you for your interest in contributing. Please check out issues with the label for other things we need help with.
Code change:
is2018DataVisCert, isApisMicroservicesCert, isFrontEndLibsCert, <del> is2020QaCert, is2020InfosecCert, </del> <ins> isInfosecQaCert, </ins> isJsAlgoDataStructCert, isRespWebDesignCert } = this.props;

Related discussion:
text: <!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --1) The Full Stack Cert claimed date will only show as the current date and not the date it was claimed on. I claimed mine on the 7th of September and checking back regularly I noticed the claimed on date was always the current date. 2) The Full Stack Cert appears as the Legacy Full Stack Cert on a users profile page, clicking this leads to an error as the legacy cert does not exist. It should be in with the new certificates. That being said, on the settings page the link to view the certificate is linked correctly. ${username-here} /full-stack ${username-here} N.A 1) Just the claimed on date. No screenshot necessary. 2) !
Similar to
I am having the same issue with my Full Stack Certificate
Mine as well. Has this been addressed?
Same here - The issued date shows the current date and not the date on which it was originally issued -
Related
Have the same problem: the date of Full Stack Certificate is always a current date.
If there are no records for a fullstack certificate, a good fallback would be going thought the date of the modern certificates and displaying the date of latest claimed certificate.
optimally, we should add a completion timestamp and an id when campers claim a fullstack certificate with a fallback to the last earned cert if a timestamp is not found.
My full stack certification also updates with the current date not the claimed date.
The date on my full stack certificate is showing the date i claim my Responsive Web design certificate ( the first certificate ). and now if i want to see the certificate it is asking me to claim certificate when i claim it will say is like u have claim the certificate and it will not show me the certificate.
This is an ongoing issue, please use the reactions instead to assert "me too". Potential approach for fixes: and
Also related to the Full Stack cert – the date seems to be the date the first certification was claimed, not the date the full stack certification was claimed:
The fallback is not working properly and I should have caught that. It's not a tricky fix, but I'll make sure it works this time!
Ok thenks On May 5, 2020 11:04, "Oliver Eyton-Williams" <:
Code change:
"Hagamos que nuestro botón "Get message" cambie el texto del elemento con clase <code>message</code>.", "Antes de poder hacer esto, tenemos que implementar un <code>evento de pulsación</code> dentro de nuestra función <code>$(document).ready()</code>, añadiendo este código:", "<blockquote>$("#getMessage").on("click", function(){</br></br>});</blockquote>" <ins> ], "namePt": "Ativando eventos de clique com jQuery", "descriptionPt": [ "Nesta sessão, vamos aprender como obter dados de uma API. As APIS - Interface de Programação de Aplicativos - são ferramentas usadas pelos computadores  para se comunicarem entre si.", "Também aprenderemos como utilizar o HTML com os dados obtidos de uma API usando uma tecnologia chamada Ajax", "Em primeiro lugar, vamos revir o que faz a função <code>$(document).ready()</code>. Esta função faz com que todo o codigo que esteja dentro de seu escopo execute somente quando a nossa página tenha sido carregada.", "Vamos fazer nosso butão "Get message" mudar o texto do elemento com a classe <code>message</code>.", "Antes de poder fazer isso, temos que implementar um <code>evento de clique</code> dentro da nossa função <code>$(document).ready()</code>, adicionando este código:", "<blockquote>$("#getMessage").on("click", function(){</br></br>});</blockquote>" </ins> ] }, {

Related discussion:
text: [ ] Trigger Click Events with jQuery [ ] Change Text with Click Events [ ] Get JSON with the jQuery getJSON Method [ ] Convert JSON Data to HTML [ ] Render Images from Data Sources [ ] Prefilter JSON [ ] Get Geo-location Data
Working on it!
Code change:
<h2 class="author-name">${author}</h2> <img class="user-img" src="${image}" alt="${author} avatar"> <div class="purple-divider"></div> <del> <p class="bio">${bio.length > 50 ? bio.slice(0, 49) + '...' : bio}</p> </del> <ins> <p class="bio">${bio.length > 50 ? bio.slice(0, 50) + '...' : bio}</p> </ins> <a class="author-link" href="${url}" target="_blank">${author} author page</a> </div> `;

Related discussion:
text: The test is expecting to use 49 in the slice. Which seems like could have been an error….It should be 50 The test is expecting to use 49 in the slice. Which seems like could have been an error….It should be 50 No response Device: [Laptop] OS: [Windows 10] Browser: [ Chrome] No response
Yes, you are correct. The test is incorrect. I will go ahead and open this up for contribution for the community. Please read through the guidelines first. We do not assign issues. If you are interested in working on this, then work on the issue and create a PR. Several changes need to be made Here is the first file that needs to be updated For step , you will need to update these two tests here to use the correct value of 50 for the slice method. You will also need to update the seed code for steps 28 and 29. Remember that step 29 also has the complete solution which needs to be updated as well Happy coding
Code change:
Fulfill the below user stories and get all of the tests to pass. Use whichever libraries or APIs you need. Give it your own personal style. <del> You can use HTML, JavaScript, CSS, and the D3 svg-based visualization library. The tests require axes to be generated using the D3 axis property, which automatically generates ticks along the axis. These ticks are required for passing the D3 tests because their positions are used to determine alignment of graphed elements. You will find information about generating axes at <https://github.com/d3/d3/blob/master/API.md#axes-d3-axis>. Required (non-virtual) DOM elements are queried on the moment of each test. If you use a frontend framework (like Vue for example), the test results may be inaccurate for dynamic content. We hope to accommodate them eventually, but these frameworks are not currently supported for D3 projects. </del> <ins> You can use HTML, JavaScript, CSS, and the D3 svg-based visualization library. The tests require axes to be generated using the D3 axis property, which automatically generates ticks along the axis. These ticks are required for passing the D3 tests because their positions are used to determine alignment of graphed elements. You will find information about generating axes at <https://github.com/d3/d3/blob/master/API.md#axes-d3-axis>. Required DOM elements are queried on the moment of each test. If you use a frontend framework (like Vue for example), the test results may be inaccurate for dynamic content. We hope to accommodate them eventually, but these frameworks are not currently supported for D3 projects. </ins> **User Story #1:** My chart should have a title with a corresponding `id="title"`.

Related discussion:
text: 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.
Code change:
<ins> import request from 'supertest'; import { build } from '../app'; import { endpoints } from './deprecated-endpoints'; describe('Deprecated endpoints', () => { let fastify: undefined | Awaited<ReturnType<typeof build>>; beforeAll(async () => { fastify = await build(); await fastify.ready(); }, 20000); afterAll(async () => { await fastify?.close(); }); endpoints.forEach(([endpoint, method]) => { test(`${method} ${endpoint} returns 410 status code with "info" message`, async () => { const response = await request(fastify?.server)[ method.toLowerCase() as 'get' | 'post' ](endpoint); expect(response.status).toBe(410); expect(response.body).toStrictEqual({ message: { type: 'info', message: 'Please reload the app, this feature is no longer available.' } }); }); }); }); </ins>

Related discussion:
text: Thanks for noticing this, Sem. As this route has been deprecated for a while, we should be able to safely sunset this route - NOT have it in the new API.
Reopening it as we're migrating deprecated endpoints as discussed in todays API meeting
Code change:
Pass in only the first element of the `locations` array by adding `[0]` at the end of the variable. For example: `myFunction(arg[0]);`. <del> This is called <dfn>bracket notation</dfn>. Values in an array are accessed by index. Indices are numerical values and start at 0 - this is called zero-based indexing. `arg[0]` would be the first element in the `arg` array. </del> <ins> This is called <dfn>bracket notation</dfn>. Values in an array are accessed by index. Indices are numerical values and start at `0` - this is called zero-based indexing. `arg[0]` would be the first element in the `arg` array. </ins> # --hints--

Related discussion:
text: The description here is missing backticks for the number zero. Here is the new updated description. 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 Here is the correct file that needs to be updated. Note: Even though the file says step 62 instead of step 63 that is on the site, this is still the correct file that needs updating. We recently made changes to the ordering and those changes haven't shown up yet on the live site. Happy coding 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
Step 145 has the same issue here Here is the file that needs to be updated here is the correct use of backticks for the number zero in the last sentence here
Code change:
```js // doubles input value and returns it const doubler = (item) => item * 2; <ins> doubler(4); // returns 8 </ins> ``` <del> If an arrow function has a single argument, the parentheses enclosing the argument may be omitted. </del> <ins> If an arrow function has a single parameter, the parentheses enclosing the parameter may be omitted. </ins> ```js <del> // the same function, without the argument parentheses </del> <ins> // the same function, without the parameter parentheses </ins> const doubler = item => item * 2; ```

Related discussion:
text: <!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Describe your problem and how to reproduce it: The usage of the word "argument" ist unclear to me. The title of this challenge uses the word "parameter". Then the instructions state: "If an arrow function has a single argument, the parentheses enclosing the argument may be omitted." But the following snippet cited from the instructions shows the parameter "item" without parentheses: The functions are never invoked with an argument in the examples. As I understand it the sentence should say: "If an arrow function has a single parameter, the parentheses enclosing the parameter may be omitted." Add a Link to the page with the problem: or, Tell us about your browser and operating system: Browser Name: Browser Version: Operating System: If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box):
Hello~! I agree that the verbiage is wrong here. should probably be replaced with in the examples and text, with the exception of the top line (which, at a quick glance, is the only correct use of ):
These are the ones that should be changed, I think. In fact, we could use instead.
I like that approach. Think this could be opened up to first timers?
I would go for: Just like a regular function, you can pass arguments into an arrow function. If an arrow function has a single parameter, the parentheses enclosing the parameter may be omitted. It is possible to pass more than one argument into an arrow function.
Sure, that works.
Code change:
const allowedSocialsAndDomains = { githubProfile: 'github.com', linkedin: 'linkedin.com', <del> twitter: 'twitter.com', </del> <ins> twitter: ['twitter.com', 'x.com'], </ins> website: '' };

Related discussion:
text: When I want to add my x account to my profile the format of the link must be but the domain nowadays is and when I add it with x instead of twitter it shows me an error ! to the settings of your profile the Your Internet Presence section to add/change the Twitter account link It should allow both domains to be entered not only ! Device: [Desktop] OS: [Ubuntu 22.04] Browser: [Firefox v128.0 - 64bit] If the context is not enough for the issue reply to this issue and mention my username
! Huh?? That's me too!!!
Hello, I am new to contributing so please inform me if I am doing anything wrong. The Line254 effects social link validation. could be changed to X.com for a quick patch although moderators may want to redefine all twitter references to x. Line239
Hey Yes, I think the same but I think it should not be changed to x.com we have to change the value to array instead of string like this: then use a conditional statement to be sure the entered data from a user includes one of these two.
Code change:
Congratulations on behalf of the freeCodeCamp.org team! `; <ins> const failureMessage = name => dedent` Something went wrong with the verification of ${name}, please try again. If you continue to receive this error, you can send a message to support@freeCodeCamp.org to get help. `; </ins> function ifNoSuperBlock404(req, res, next) { const { superBlock } = req.body; if (superBlock && superBlocks.includes(superBlock)) {

Related discussion:
text: Some users can claim python, new QA, and new infosec certifications without submitting their required projects on .dev. It seems the api does not find the cert challenge and proceeds by setting the related cert flag on the user object to true. The issue can be resolved by reseeding the db locally. I cannot reproduce this issue at the moment, but I will keep this open in case other users are experiencing the same issue.
Hello! I tested this issue, and I was able to claim the certifications without completing the projects.
could you check if you can see the certification after claiming it? I'm just wondering if this is purely a client-side issue.
I am able to see the four certificates I could claim, yes.
Thanks for checking that. In that case, while it seems likely that it will fine if the database is migrated, the api should definitely default to rejecting certifications it does recognise.
Yes We Can Claim Python Certification Without submitting the Projects.
that's really serious
Code change:
Congratulations on behalf of the freeCodeCamp.org team! `; <ins> const failureMessage = name => dedent` Something went wrong with the verification of ${name}, please try again. If you continue to receive this error, you can send a message to support@freeCodeCamp.org to get help. `; </ins> function ifNoSuperBlock404(req, res, next) { const { superBlock } = req.body; if (superBlock && superBlocks.includes(superBlock)) {

Related discussion:
text: Currently when you complete/claim a certificate there's an entry on the timeline: <img width="582" alt="Screen Shot 2020-05-27 at 9 37 55 AM" src="https://user-"This doesn't seem to be working for the new Scientific Computing with Python, Data Analysis with Python, and Machine Learning with Python certificates.
I'm a new contributor but I'd like to help out on this.
I think this is mostly working. You just need to refresh the page before it shows up... <img width="598" alt="Screen Shot 2020-05-27 at 11 34 12 AM" src="https://user-"Edit: hmm, it seems to be working locally, but not on .dev - the "view cert" button is there in both environments - it just doesn't show on the timeline on .dev
Ah, interesting. This does seem to work locally but not on .dev for some reason.
This may be a one off issue related to where the new/split certificates (Quality Assurance, Information Security, Scientific Computing with Python, Data Analysis with Python, and Machine Learning with Python) were not seeded to the .dev database for some reason. I can confirm this is working locally like mentioned above. thank you for your interest in contributing. Please check out issues with the label for other things we need help with.
Code change:
Congratulations on behalf of the freeCodeCamp.org team! `; <ins> const failureMessage = name => dedent` Something went wrong with the verification of ${name}, please try again. If you continue to receive this error, you can send a message to support@freeCodeCamp.org to get help. `; </ins> function ifNoSuperBlock404(req, res, next) { const { superBlock } = req.body; if (superBlock && superBlocks.includes(superBlock)) {

Related discussion:
text: <!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --1) The Full Stack Cert claimed date will only show as the current date and not the date it was claimed on. I claimed mine on the 7th of September and checking back regularly I noticed the claimed on date was always the current date. 2) The Full Stack Cert appears as the Legacy Full Stack Cert on a users profile page, clicking this leads to an error as the legacy cert does not exist. It should be in with the new certificates. That being said, on the settings page the link to view the certificate is linked correctly. ${username-here} /full-stack ${username-here} N.A 1) Just the claimed on date. No screenshot necessary. 2) !
Similar to
I am having the same issue with my Full Stack Certificate
Mine as well. Has this been addressed?
Same here - The issued date shows the current date and not the date on which it was originally issued -
Related
Have the same problem: the date of Full Stack Certificate is always a current date.
If there are no records for a fullstack certificate, a good fallback would be going thought the date of the modern certificates and displaying the date of latest claimed certificate.
optimally, we should add a completion timestamp and an id when campers claim a fullstack certificate with a fallback to the last earned cert if a timestamp is not found.
My full stack certification also updates with the current date not the claimed date.
The date on my full stack certificate is showing the date i claim my Responsive Web design certificate ( the first certificate ). and now if i want to see the certificate it is asking me to claim certificate when i claim it will say is like u have claim the certificate and it will not show me the certificate.
This is an ongoing issue, please use the reactions instead to assert "me too". Potential approach for fixes: and
Also related to the Full Stack cert – the date seems to be the date the first certification was claimed, not the date the full stack certification was claimed:
The fallback is not working properly and I should have caught that. It's not a tricky fix, but I'll make sure it works this time!
Ok thenks On May 5, 2020 11:04, "Oliver Eyton-Williams" <:
Code change:
</Modal.Body> <Modal.Footer> {isSignedIn ? null : ( <del> <Login block={true} bsSize='lg' bsStyle='primary' className='btn-cta' > Sign in to save your progress </Login> </del> <ins> <Login block={true}>Sign in to save your progress</Login> </ins> )} <Button block={true}

Related discussion:
text: Describe the bug The completion model buttons are not correctly aligned. To Reproduce Steps to reproduce the behavior: to out. to the challenge run tests error Screenshots ! This is only on the development server, probably created by the css changes introduced by the landing page redesign.
I am able to confirm this bug. Looking at the elements: The Go To Next Challenge button has a left margin of 5px. ! The Download My Solution button has a top margin of 5px. !
Code change:
padding-bottom: 10px; } <del> .help-modal-heading { line-height: 1.5; font-weight: 400; word-spacing: -0.4ch; } </del> .help-form-legend { color: var(--secondary-color); border: 0;

Related discussion:
text: The following classes in are unused and should be removed: .help-modal .help-modal-heading .btn-lgRemove the above classes from Test and confirm that the modal displays properly after the changes