Details
-
Type:
Task
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Story Points:3
-
Epic Link:
-
Sprint:Fall 1, Summer 5, Summer 6
Description
In previous issues (see linked tickets) saideepthi jagarapu re-discovered that the current configuration of App Store development environment can't run as-is and needs to be updated.
To start, let's identity the latest, most robust version of python 3 that can run App Store, with whatever updated dependencies may be required.
To complete this ticket:
- Update the Developer's Guide to show all new development environment configurations that developers need to know about in order to start working on App Store.
- Update code as needed to achieve same
- Focus on the development environment only (we will address the production environment in another ticket)
- Demonstrate that with the required changes, all functionality works as expected (except for the pending apps endpoint, which is fixed as part of a linked ticket)
Attachments
Issue Links
Activity
Sure Ann Loraine, I will create ticket for the same and link to this ticket.
PR for the changes : https://bitbucket.org/lorainelab/appstore/pull-requests/285
Thank you for the clarification saideepthi jagarapu.
I think we should merge these changes into the main branch, and capture tasks "review clarity of development documentation" or "review development documentation changes" in new ticket(s).
Regarding the second option:
Reviewing changes (recent edits in the Google Doc) seems easiest and best.
Next, we could do: "Set up a development / testing environment by following development documentation instructions and report any problems."
Just a correction, Paige used my google email as she doesn't have one. Because of which we were facing little discrepancies in email part. Also, I want someone to check the mail part who have active google account.
Also, I was able to test end to end including mails, but sometimes I'm also not getting mails. This seems to be a local issue nothing to do with the python upgradation as this particular send_mail() django function acts similarly and is not deprecated or changed for newer django version 4.2.
For example, when i pushed my code and tested a couple of weeks back, I was able to test end to end including mails.
But when I tried to test with paige, even I faced issue with mail in my personal space.
I feel there are some gaps in development documention which needs to be reviewed.
attn: Ann Loraine
It sounds like saideepthi jagarapu is able to run the testing environment but Paige Kulzer could not. That is, developer saideepthi jagarapu was able to trouble-shoot the problem and fix it on her system, but tester / verifier Paige Kulzer could not.
Is the documentation misleading, wrong, or unclear?
Ideally, the documentation explaining how to set up the email functionality would be clear and correct enough to enable a tester (e.g., Paige Kulzer) to set up the testing environment without having to delete (comment out) code.
Could you guys work together to ensure that the documentation is correct?
I'm worried that when I try to test the App Store code on my system, or deploy it into production, this same step will fail.
Python version upgraded from 3.6 to 3.13
Django version upgraded from 2.2 to 4.2 and other dependency upgrades can be found here
Branch changes: https://bitbucket.org/lorainelab-deepthi/appstore/branch/python-upgrade
Updated the development guide document
https://docs.google.com/document/d/1_9C03q6TD5wjLqfVLKsuDsIEQ4-qrS0JhONO5VBOwaA
I've successfully run through the documentation again with a new gmail account. I was able to log in and submit an app with no issues. I was also able to log in as admin, accept the pending app, and use all filters present in the app store as expected. Since a new ticket has been created for finalizing the documentation, I'm going to go ahead and close this ticket now.