jiebi/CodeConvo huggingface dataset:
Code change:
# --description-- <del> Find the number of non-empty subsets of ${11, 22, 33, ldots, {250250}^{250250}}$, the sum of whose elements is divisible by 250. Enter the rightmost 16 digits as your answer. </del> <ins> Find the number of non-empty subsets of ${{1}^{1}, {2}^{2}, {3}^{3}, ldots, {250250}^{250250}}$, the sum of whose elements is divisible by 250. Enter the rightmost 16 digits as your answer. </ins> # --hints--

Related discussion:
text: The Project euler problem 250 has a format issue Confront with To fix this issue you will need to change this file so that the numbers are correctly formatted as exponents: (You can use the way ^ is written in the challenge as a guide to fix 1^1, 2^2, and 3^3) 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. An issue with the help wanted or first timers only 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. 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.
I have set up the project in my local machine and looking to contribute for open source is this still open can I work on it
Code change:
# --description-- <del> The phrase `let me show you` can be used to direct attention and introduce something. For example: `Here's the main office area. And over there, let me show you, that's the conference room.` </del> <ins> The phrase `let me show you` can be used to direct attention and introduce something. For example: `This is the main office area. Let me show you to the conference room.` </ins> # --question-- ## --text-- <del> What is the speaker directing attention to after saying `let me show you`? </del> <ins> What is Maria directing attention to? </ins> ## --answers-- <del> The main office area </del> <ins> Main office area </ins> ### --feedback--

Related discussion:
text: Description and question refers to the Here's the main office area. And over there, let me show you, that's the conference room. text. However the audio mentions let me show you in context of showing to the desk. n/a Audio used in task should match the description context. Or the other way around. No response n/a No response
Yes, this is a problem. None of the answers are correct. Here's how I'd fix it: change the option "the conference room" to "the desk". This should solve the problem. We could also: simplify the question to "What is Maria directing attention to?" simplify the example to "Here's the main office area. Let me show you to the conference room."
I am fine with the suggestion. You could use as the example. What do you think
Agreed I'm going to add the help wanted label.
Code change:
import debug from 'debug'; import { isEmail } from 'validator'; import format from 'date-fns/format'; <ins> import { reportError } from '../middlewares/sentry-error-handler.js'; </ins> import { ifNoUser401 } from '../utils/middleware'; import { observeQuery } from '../utils/rx';

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:
import debug from 'debug'; import { isEmail } from 'validator'; import format from 'date-fns/format'; <ins> import { reportError } from '../middlewares/sentry-error-handler.js'; </ins> import { ifNoUser401 } from '../utils/middleware'; import { observeQuery } from '../utils/rx';

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:
import debug from 'debug'; import { isEmail } from 'validator'; import format from 'date-fns/format'; <ins> import { reportError } from '../middlewares/sentry-error-handler.js'; </ins> import { ifNoUser401 } from '../utils/middleware'; import { observeQuery } from '../utils/rx';

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:
.hero-subtitle, .author, .quote, <del> .list-header { </del> <ins> .list-title { </ins> font-size: 1.8rem; }

Related discussion:
text: In [()] step it is written but in the html file there is no selector instead there is selector present. ( In [()] step it is written but in the html file there is no selector instead there is selector present. either change the to or remove the totally from the step to do. No response
Page File: the seed content doesn't have , and the step after it do include it as well. we should swap with This looks something that can be fixed by "first time" code contributors to this repository. Here is the file that you should be looking at to work on a fix: file: 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.
I would like to work on this issue. Please assign this issue to me .
We don't give assignment unless to an old time contributor to the repo. Edit: sorry should have provided more info. There were times when people assigned an issue and didn't commit to it, because of that the guide mentions we don't assign people and seek quality and fast commits. Sorry if my original answer was uninformative. I hope you have a good day and happy coding.
Code change:
-   Your function must always return the entire `records` object. -   If `value` is an empty string, delete the given `prop` property from the album. -   If `prop` isn't `tracks` and `value` isn't an empty string, assign the `value` to that album's `prop`. <del> -   If `prop` is `tracks` and value isn't an empty string, add the `value` to the end of the album's `tracks` array. You need to create this array first if the album does not have a `tracks` property. </del> <ins> -   If `prop` is `tracks` and `value` isn't an empty string, you need to update the album's `tracks` array. First, if the album does not have a `tracks` property, assign it an empty array. Then add the `value` as the last item in the album's `tracks` array. </ins> **Note:** A copy of the `recordCollection` object is used for the tests. You should not directly modify the `recordCollection` object.

Related discussion:
text: This part is still tripping people up Usually one piece or another gets lost: Maybe this is clearer Side note - I still don't love the fact that we say like a variable instead of like a string literal. I think that's confusing here. (I know, I know, the style guide hates "s) No response All No response
Agreed, it has the potential to be confusing. Can we reword to say: "If is the string and ..."
I'm still not clear on the reason why string literals in inline code blocks are forbidden by the style guide since it makes the instructions less clear in this case. do you have some context?
I don't remember the full reason, only that it was a decision made as part of our i18n efforts. We reference a discussion in but I can't for the life of me find where that discussion is.
Code change:
programmer = "CamperChan"; ``` <del> Note that when reassigning a variable that has already been declared, you do **not** use the `let` keyword. </del> <ins> Note that when reassigning a variable, you do **not** use the `let` keyword again. </ins> After your `console.log`, assign the value `"World"` to your `character` variable.

Related discussion:
text: Currently on step number 5 there's a note that reads Note that when reassigning a variable that has already been declared, you do not use the let keyword. As it stands this note is incorrect and unnecessary. No code, just instructions re-wording. The note could be changed to: Note: You can only re-assign a variables that has been declared with Or we can simply remove it altogether instead. <img width="1217" alt="Screen Shot 2024-05-02 at 10 31 38" src=""- Device: [Laptop] OS: [MacOS 12.7.4] Browser: [Chrome] Version: [124.0.6367.91] No response
The note is correct. I think you are interpertering it wrong? It is saying does not need to be used when re-assinging the variable with a new value. edit: It is not saying that you can use any kind of keyword like or
I understand what's it's trying to convey, but it's written in a confusing way. Here's the text directly copied into ChatGPT for some additional context: <img width="820" alt="Screen Shot 2024-05-02 at 11 01 54" src=""
Text refers to potential situation when both assignments are using , ie: Depending on where exactly both are used, this can result in . - - x = 10; There's no on this line. It's one of the cases when chat doesn't know what it's talking about.
Hi thank you for creating the issue. As Sem pointed out, we don't think the note should be updated to because the new version communicates different information from the original. I think the confusion came from the word "declared". The word isn't needed since "reassigning" already implies that the variable has been declared, so I'd propose changing the sentence a little: cc'ing for input, since you're much more experienced with this kind of change than I am
Thanks for the input your proposal addresses the issue I presented
That change works for me. Let's open it up for first timers 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.
Code change:
programmer = "CamperChan"; ``` <del> Note that when reassigning a variable that has already been declared, you do **not** use the `let` keyword. </del> <ins> Note that when reassigning a variable, you do **not** use the `let` keyword again. </ins> After your `console.log`, assign the value `"World"` to your `character` variable.

Related discussion:
text: 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 js let programmer = "Naomi"; programmer = "CamperChan"; ` Happy coding
Code change:
Your `#video` should have a `src` attribute. ```js <del> const el = document.getElementById('video') assert(!!el && !!el.src) </del> <ins> let el = document.getElementById('video') const sourceNode = el.children; let sourceElement = null; if (sourceNode.length) { sourceElement = [...video.children].filter(el => el.localName === 'source')[0]; } if (sourceElement) { el = sourceElement; } assert(el.hasAttribute('src')); </ins> ``` You should have a `form` element with an `id` of `form`.

Related discussion:
text: The following test (user story) prevents my previously passing project from passing: Important: Notice I use instead of just I never claimed to be a UI expert Do we want to keep such a test? No response Unrelated No response
Maybe you should update your project Honestly I think small tweaks are going to be okay - my tribute page fails because the image needs a height now.
I am also happy with small tweaks, but we did (largely) want to keep the requirements exactly the same. The only change we agreed upon is to add requirements for tags.
Looks like they accommodated for the tag in that test. Maybe we can just add it here too.
although, I think it's good, that we moved on from the old test. tag is extremely useful in html, it has attribute that help developers use less needed css, which lead to better experience, . it should be accepted to use Edit: if you paste this code in it won't pass although there is a media query but in the html Edit: I changed the for easier testing
Code change:
editor.addAction({ id: 'toggle-accessibility', label: 'Toggle Accessibility Mode', <del> keybindings: [monaco.KeyMod.CtrlCmd | monaco.KeyCode.KEY_E], </del> <ins> keybindings: [ monaco.KeyMod.CtrlCmd | monaco.KeyCode.KEY_E, monaco.KeyMod.WinCtrl | monaco.KeyCode.KEY_E ], </ins> run: () => { const currentAccessibility = storedAccessibilityMode();

Related discussion:
text: Even though on macOS it would seem that Ctrl+Enter does not work & Cmd+Enter does; website still tells you to use Ctrl+Enter. I think this might end up being confusing for some - and should be fairly straightforward of a change. All coding pages You must use macOS for this issue. to any coding challenge your changes will see button underneath says "Check your code (Ctrl + Enter)" Ctrl + Enter will happen. Cmd + Enter behaviour will occur. It should tell the user correct shortcut (Cmd + Enter) instead of (Ctrl + Enter) depending on the platform. <img width="647" alt="Screenshot 2022-06-09 at 16 52 28" src="https://user-"- Device: M1 MacBook Pro OS: macOS 12.0.1 Browser: Safari Version: 15.1 No response
I would like to handle this issue as a first contribution. My proposal would be to use (). Use Ctrl + Enter as a fallback and define a special case for macOS cases. Alternatively we could use () however that is not widely supported as opposed to . As far as I can tell on mobile we don't show modifier keys on the button; so I'll preserve that behaviour. I can't change the labels on this issue - I don't think this is severe enough to be classified as a bug based on definition; my apologies regarding that.
Hey thanks for raising this issue and don't worry about the labels, they need to be handled by maintainers. What you've suggested does sound good to me, so if you're happy to take this on, that's awesome.
I've created the PR however; I've updated non English translations as well in here to use dynamic values; however not really sure how to align it with the crowdin. Since updated translations should coincide with this change; any opinions on this?
Do not worry, I think you are putting too much effort into it. Simply drop the changes to those files and as the bot mentioned, they will get updated eventually via our translation workflow. As for the bug itself: I am 100% sure at some point we introduced a regression, because (in addition to the implicit Cmd + Enter) was working since the inception of the code editor. do you happen to know if this was just an accident with the new editor?
Code change:
editor.addAction({ id: 'toggle-accessibility', label: 'Toggle Accessibility Mode', <del> keybindings: [monaco.KeyMod.CtrlCmd | monaco.KeyCode.KEY_E], </del> <ins> keybindings: [ monaco.KeyMod.CtrlCmd | monaco.KeyCode.KEY_E, monaco.KeyMod.WinCtrl | monaco.KeyCode.KEY_E ], </ins> run: () => { const currentAccessibility = storedAccessibilityMode();

Related discussion:
text: To be clear it should always work with regardless of the OS in addition to implicitly working with just like it was before.
I can't check this myself, since I don't have a mac, but it should work. This is the code: and could you try and reproduce the issue?
I've shot a short video of the behaviour I am seeing; if that helps.
That does help, yeah. It seems to be ignoring the command button entirely, which is odd. I can't investigate myself, but this will help anyone that has access to a Mac.
Thanks for the video I don't recall if ctrl+enter ever worked on mac - I may or may not have ever used it. I just hit buttons without looking I'm not sure if you are trying to show something specific with those code snippets - that's the code on main. Which results in the current behavior. Edit: I get it now - you were just showing the code and that it should be working. I thought you trying to show new changes or something. Here's the current behavior I see (all on mac) - there's some nuance... New RWD: Execute: only command+enter works on mac Submit: Enter alone works, so any key+enter works Legacy RWD, JS, etc: Execute: Only cmd+enter works Submit: Enter alone does not work - both ctrl+enter or command+enter do work Multiple choice Python video questions: Execute: Enter alone does not work - ctrl+enter and cmd+enter work Submit: Enter alone does not work - both ctrl+enter or command+enter do work Projects with URL inputs - e.g. front end libs cert project, or backend api challenges, etc: Execute: Enter alone works cause it's a form I suppose, which also means any key+enter works Submit: Enter alone does not work - both ctrl+enter or command+enter do work The last three groups there have the same submit modal, so the behavior is the same on all of them. What I see is that the submit modal, and the video question both allow [ctrl or cmd] +enter - we should see what those are doing. Looking into to it...
K, I think I found a fix. ctrl+enter works when the hotkeys package/component is used. So crtl+enter actually does work on the legacy challenges when the instructions are focused.
Code change:
editor.addAction({ id: 'toggle-accessibility', label: 'Toggle Accessibility Mode', <del> keybindings: [monaco.KeyMod.CtrlCmd | monaco.KeyCode.KEY_E], </del> <ins> keybindings: [ monaco.KeyMod.CtrlCmd | monaco.KeyCode.KEY_E, monaco.KeyMod.WinCtrl | monaco.KeyCode.KEY_E ], </ins> run: () => { const currentAccessibility = storedAccessibilityMode();

Related discussion:
text: When the editor is focused, those hotkeys don't get used, the actions/hotkeys we add to the editor take over. I made ctrl+enter work when the editor is focused by changing that line 431 mentioned to this: That should work. There's a number of actions in that file that use the same hotkeys - lines 457 and 469 for example. There may be others. I think we should be safe to change all those. Do you mind playing with that a bit and updating the PR to make those changes.
Nice work, Tom. I thought CtrlCmd was "Ctrl or Command", but it must be Ctrl on Windows and Command on Mac :man_facepalming: I guess this has never worked properly.
happy to give it a look and update the PR. Thank you
Here's an I had created sometime back when working on the . Apparently the logic goes like this - the first word is Windows and the second one is Mac button.
Code change:
isDonating } = user; <del> console.log(showDonation); </del> return ( <Fragment> <Camper

Related discussion:
text: Describe the bug 1) It appears a was accidentally left in the script. 2) A request to my/(a user's) page-data is returning a 404. To Reproduce Steps to reproduce the behavior: to DevTools log or in console, due to: File: Line 126 error in console as in picture below. Expected behavior No Errors, no logs. Screenshots ! Desktop (please complete the following information): OS: Windows 10 Browser: Chrome Version: 83.0.4103.97 Additional Info I believe the: 'progress updates processed where possible' Is useful, and should stay.
I think it would be better to remove all the logs, since we can use the flash messages if we need to communicate information. Ideally, all errors should go to Sentry. This currently does happen for the server, but we haven't implemented it for the client, yet. Basically because there's still a bit too much noise (like the page- 404 in your screenshot).
Yep, git blame and me for missing it in the QA. Reference: A PR is welcome to remove this and any other rogue logs. This is an expected side-effect of us using Gatsby's routing to query and get the user profile available at . Essentially, when you hit , we first let Gatsby check in the static files if something is available at that path, if not we query the API to lookup there for a username. If both conditions fail, we would render an actual 404 page. But for this to work the status code 404 is sort of abused. Its hacky but there is no way around this to the best of my knowledge. Just to clarify, this should be left as is.
any suggestions where to search? I am trying to search around, but there doesn't seem to be, or I am finding those in the challenges code maybe there aren't
It's a bit tricky, because we use console logs as part of the challenge code, but the place to look is in could you explain why 'progress updates processed where possible' should appear in the console?
there are a few, but they all seems needed where they are
I don't know why, but it comes from file line 98
there are some s, s s, too. gets me: of which probably should not be there.