-
Notifications
You must be signed in to change notification settings - Fork 1
SE-2208 debugging page loads #17
SE-2208 debugging page loads #17
Conversation
This commit upgrades the version of pymongo from 2.x to 3.x, removing usages to deprecated functions usage and fixing tests where necessary. This version of pymongo supports MongoDB 2.x all the way up to 4.2, and this ensures that the platform will be able to run on a supported MongoDB version in the next release. (cherry picked from commit 9b69d5a62684dc3d9d86b7e71081bebd432bd7d9)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@swalladge I had a couple small suggestions but otherwise this looks good and should help with debugging the process of rendering contents of specific units in Studio.
Before deploying this, please rebase the changes on the feature branch of #14 (pooja/cherry-pick-pymongo-upgrade
). Both stage and prod are currently running code from this branch (see this comment for additional details).
35fbf10
to
bd77d60
Compare
@itsjeyd nits addressed and rebased on |
Also a lot of unit tests are failing; not sure if they're related or not. |
@swalladge
Thanks!
Most of them likely aren't -- the reason why we didn't merge #14 yet is because it didn't get a green build. So any failure that shows up here as well as on #14 is probably safe to ignore. I noticed that the latest build for this PR includes some failures that seem related to the changes being applied here, for example:
Things seem to be going south when reaching the following line?
Not quite, test failures unique to this PR need checking first. |
@itsjeyd hmm that's not an issue with the log line, that's an issue with some module not having an
I'll remove that log line. |
@swalladge Looks like the follow-up changes that you pushed made the The output of We need to get this into production and start using it to diagnose the Studio issue soon, so perhaps just go ahead and deploy and sanity-check it on stage during the night IST. And then if there are no obvious issues you can go ahead and do the prod deployment right away, to have that happen during low-traffic hours as well. To help prepare I'll start building an AMI for stage now. |
@swalladge The AMI for stage built successfully, see https://admin.edx-flatu.org:8080/job/build-ami/110/. |
Reasons for closing, for future reference. |
Add debug logging to help debug SE-2088.