New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bugs in the next branch (TypeScript migration) #42660
Comments
The private |
I couldn't reproduce it reliable on beta and not at all on .dev. So, yes, it definitely sounds like a caching problem, but it might be a new one. |
Editor throws error in console, on render (ref #42651):
|
@raisedadead I get the errors any time I click the Ask me later button. Also, I realise I am being redirected to |
I am still unable to reproduce. I would appreciate some detailed steps to debug and see the console logs.
So you mean you do not see the errors with donate modal anymore? Are these the same errors as the modal?
Again I will need a detailed sequence of steps to reproduce, but it is possible that you can get that. The reason being we haven't defined "beta.freecodecamp.dev" as the "home" anywhere in code. Meaning, some routing will default to the TLD, as you might have been experiencing. That said, it's an issue that we would want to keep for the QA cycle later on staging. |
To reproduce:
|
I have managed to reproduce this many times, and even disabled React Devtools extension for good measure. Python.for.Everybody.-.Strings.in.Python._.Learn._.freeCodeCamp.org.-.Google.Chrome.2021-06-29.21-40-12_Trim.mp4Also, it seems, if I click on Ask me later , the DonationModal will not reappear, unless I refresh the page. That is, after closing the modal, I can complete 30+ lessons without it reappearing - My understanding is it should reappear:
|
I took a look at the donation modal and was able to reproduce that error message on both beta.freecodecamp.dev and www.freecodecamp.dev. It seems like an existing issue with the PayPal script complaining about the container element being removed, and isn't due to the TS migration. Not the exact same error object as in the screenshot, but here's another for reference:
I haven't been able to reproduce the issue with the Not sure if this is intended behavior or not, but it seems to work this way on both beta.freecodecamp.dev and www.freecodecamp.dev. |
Thanks for the additional steps Shaun. Now that I have wiped my glasses, I have now been able to reproduce and see this consistently. I believe Kris is correct in his findings, I think we haven't configured PayPal's sandbox script environment to accept the test site as an origin correctly and hence the errors. But, I was able to successfully make a donation and dismiss the modals - meaning the behaviour seems to be unaffected. So, I guess we are good? |
The Ctrl + Enter, shortcuts work partially. That I am able to run tests using the shortcut, but I am unable to trigger the completion modal once all tests have passed. The completion modal shows up only when the "Run the tests" button is clicked. I think the shortcuts are flaky on the modal as well, that sometimes they move to the next challenge. But sometimes they are stuck. Tested on a deployed commit as of this comment: 46fd785 |
@raisedadead Sounds related to the upcoming changes editor which specifically has the logic to not show the modal when EDIT: Comment ref: https://github.com/freeCodeCamp/freeCodeCamp/blob/next/client/src/templates/Challenges/classic/editor.tsx#L313 |
Thanks for the quick debugginging, those bits should be reinstated. Do you know how? |
It is a bit confusing, as I am unsure where we are going with the upcoming changes. That is, typically,
EDIT: Please ignore me 🤦 I realise what needs to be done. |
@moT01 I'm unable to reproduce that. Can anyone else reproduce it? |
Same here, I couldn't also reproduce Toms bug. |
@ShaunSHamilton found it, so I can't take credit. I was able to reproduce it on production and dev. I believe it's some sort of caching or storage issue. I wasn't able to reproduce on private browsing or a fresh browser. |
@moT01 and @ShaunSHamilton, I took a look and was able to reproduce that Turns out that it's probably related to the LastPass extension, at least in Chrome. I haven't tried it in Firefox yet. Like @moT01 mentioned, I'm unable to reproduce the bug in an incognito window, or once I disable LastPass in my main window. This thread has more information about possible workarounds and fixes: mui/material-ui#14860 |
@scissorsneedfoodtoo Ah... brilliant. Well done, for catching that. |
I'm not sure if this issue is related to the TS migration, but I helped a user to create their FCC account just moment ago, and I found that after the user entered the code and authenticated successfully, they could briefly see the introduction screen (IntroDescription) for a few seconds before automatically got redirected to /learn. |
Thanks, @huyenltnguyen we have actually pushed the changes live a few minutes ago. I am going to close this umbrella issue and we should start reporting and fixing issues independently. Can you log a fresh issue for the same? |
Please add any problems with https://beta.freecodecamp.dev/learn to this issue.
Condensed list of issues below:
The text was updated successfully, but these errors were encountered: