- Feb 12, 2021
-
-
edX requirements bot authored
-
- Feb 11, 2021
-
-
Michael Roytman authored
Bump version of edx-proctoring library to 3.4.0 to add interstitial for ready to resume state.
-
Michael Roytman authored
This release adds an interstitial in the proctored exam experience for learners with exam attempts in the ready_to_resume state, impacting Learners.
-
Bianca Severino authored
[MST-572] Add onboarding status view to instructor dashboard
-
Bianca Severino authored
-
Felipe Montoya authored
[TSD] add annotations for ENABLE_HTML_XBLOCK_STUDENT_VIEW_DATA feature flag
-
Feanil Patel authored
test: Don't add a delta to ensure we get rate limited.
-
stvn authored
* Commits: style: Add more type-hints to discussions app
-
David Ormsbee authored
Mobile apps load HTML (and other) XBlocks individually using the render_xblock endpoint. This is an attmept to reduce the number of requests and JS processing needed to do so by detecting when we have math content in HTMLBlocks and only adding the Mathjax resources when necessary. This is controlled by the "courseware.optimized_render_xblock" CourseWaffleFlag. For maximum safety, we currently only optimize in this way when directly hitting HTMLBlocks, and not for ProblemBlock or VerticalBlock. This was made as part of edX's Hackathon XXV.
-
Matt Hughes authored
-
Feanil Patel authored
The rate limiting library computes the rate limit by chunking time since the epoch into chunks of whatever your period is. It then adds some consistent offset based on your key. This means that at certain times, you are closer to the end of your rate limit time period than others. So moving 1 minute into the future would put you into the next time chunk and your rate limit would be reset. I updated the test to test rate limit at the same time as the initial call to ensure that we don't end up on the other side of a time chunk boundary by accident. We were seeing times in CI where it would occasionally fail because time chunking wasn't in our favor.
-
Aarif authored
-
Aarif authored
-
- Feb 10, 2021
-
-
Bianca Severino authored
-
Feanil Patel authored
feat: Update the user_authn app to not log PII by default.
-
alangsto authored
updated for quality
-
Felipe Montoya authored
[TSD] Annotate git export settings and toggles in CMS
-
stvn authored
-
stvn authored
* Commits: fix: Add DiscussionsConfiguration.enabled to admin page
-
stvn authored
* Commits: style: Cleanup DiscussionsConfiguration.__str__
-
Feanil Patel authored
Instead of optionally not logging usernames and emails, do so by default. This mostly removes some complexity from the app and is makes it so that it's more secure by default. I considered the question of allowing people to log usernames and e-mails if they wanted to but opted not to for a couple of reasons: * It would involve adding a new feature flag that would be the opposite of the SQUELCH_PII_IN_LOGS which would be a bit confusing. When do you use which one? or do you need both? etc. * There is still a way to correlate the messages to eachother and in most cases also to a specific user(email being the exception).
-
Usama Sadiq authored
Lower the pylint threshold to 200
-
David Ormsbee authored
The size of commons.js has gradually grown until it is now 4 MB in dev mode. This change brings it back down to 880 KB. This does cause the size of some other JS assets to increase, some by as much as 500 KB. This still seemed like a worthwhile tradeoff.
-
Waheed Ahmed authored
Added to serve old login/register pages for the e2e tests until new tests added or old ones are fixed for the Authn MFE.
-
Usama Sadiq authored
Remove duplicate constraints
-
Usama Sadiq authored
Python Requirements Update
-
usamasadiq authored
-
Saqib authored
-
edX requirements bot authored
-
Jawayria authored
BOM-2345: Applied pylint-amnesty
-
usamasadiq authored
-
Manjinder Singh authored
Now that we always return an existing value from the DB rather than trusting that ID generation is deterministic and constant over time, we're free to change the generation algorithm. Our long term goal is to switch to random IDs, but we need to first investigate the uses of save=False. In the meantime, this is a good opportunity to move away from MD5, which has a number of cryptographic weaknesses. None of the known vulnerabilities are considered exploitable in this location, given the limited ability to control the input to the hash, but we should generally be moving away from it everywhere for consistency. This change should not be breaking even for save=False callers, since those calls are extremely rare (1 in 100,000) and should only occur after a save=True call, at which point they'll use the stored value. Even if this were not true, for a save=False/True pair of calls to result in a mismatch in output, the first of the calls would have to occur around the time of the deploy of this code. Co-authored-by:
Tim McCormack <tmccormack@edx.org> Co-authored-by:
Tim McCormack <tmccormack@edx.org>
-
usamasadiq authored
-
edX requirements bot authored
* Updating Python Requirements * change namespaced_switch_name to name Co-authored-by:
Zulqarnain <muhammad.zulqarnain@arbisoft.com>
-
- Feb 09, 2021
-
-
Adeel Ehsan authored
field added in validate decisions for authn
-
Feanil Patel authored
Make rate limit errors 429s instead of 403s
-
adeelehsan authored
VAN-351
-
Alexander J Sheehan authored
replace bulk transmission task to intended single learner task
-
Alexander J Sheehan authored
bumping enterprise to 3.17.25
-
Alexander Sheehan authored
-