Setup issues with Ubuntu 22 (within Windows Subsystem for Linux 2)

[Arpanio]

Setup via make doesn't fully work with a fresh Ubuntu 22 VM (installed via Windows Subsystem for Linux 2).

I got a number of errors and was able to resolve them to be able to get jupyter-notebook running. None of the notebooks have been tested yet.

Error message (there were more than 1):

arpanio@DESKTOP-CF2G2MB:~/projects/toronto-bids$ make run-jupyter-notebook
python3.9 -m venv venv
Error: Command '['/home/arpanio/projects/toronto-bids/venv/bin/python3.9', '-Im', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1.
make: *** [Makefile:23: venv] Error 1

Steps to resolve with the links that worked for me (may not be exhaustive as I didn't keep good notes while working on this):

1. Setup Python 3.9. The current default version that ships with Ubuntu is 3.10.
2. Setup pip for python 3.9.
3. Install Google Chrome

Can we incorporate all of this setup into make?

[sonalranjit]

Yeah we should definitely bump up the python version, i set 3.9 because that was the one that worked for my machine. But a another LTS version like 3.10 should be fine.

[Arpanio]

Instead of bumping up the python version, could we do the following?

• Detect if python3.9 exists
• If it appears like it doesn't, give a prompt to users to update the path to v3.9 and inform that python3.9 will be used as the alias for it
• If there is no v3.9, then download and install it setting python3.9 as the alias
• Setup pip for python3.9 (or ask for the path to it if the user indicated earlier that they already have python3.9 installed somewhere non-standard)
• Detect if Google Chrome exists in the default location. If not, then prompt the user for the path to Google Chrome.
• If the user indicates that there is no Chrome installation, get permission to install at the default location and install

I think the above steps will let someone setup python v3.9 on their Linux system without overwriting other stuff that they might need for other projects. Tomorrow if the LTS version changes to 3.11 then our make still works.

Another question is when do we want to work on this? At the moment, I think we've overcommitted to ensuring a reproducible setup and build, and under-committed to building features. We should keep this bug for documentation purposes and focus more on building the features.

[AcharyaS97]

I'm wondering if we could use this issue as a catch-all for bugs with running the scraper on WSL. The issues Arpan mentioned above, they're generic to the makefile regardless of how it runs no?