ubuntu 20.04 provides git 2.25.1, which has a bug with processing --sparse command line options.
Additionally, python 3.8 acquired dependency problems with the current requirements.txt configuration.
So the prerequisites in install.sh should be updated to git > 2.25.1 and python >= 3.9
Also, the actual problem was not visible because stdout and stderr were completely suppressed and not recoverable in case of a problem. A better way would be to write all messages to a logfile in the TEMP_DIR and erase that in case of success with a stdout message pointing to the log in case of an error.
Originally created by @asgalon on GitHub (Mar 21, 2026).
Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/1268
See discussion item #1087
ubuntu 20.04 provides git 2.25.1, which has a bug with processing --sparse command line options.
Additionally, python 3.8 acquired dependency problems with the current requirements.txt configuration.
So the prerequisites in install.sh should be updated to git > 2.25.1 and python >= 3.9
Also, the actual problem was not visible because stdout and stderr were completely suppressed and not recoverable in case of a problem. A better way would be to write all messages to a logfile in the TEMP_DIR and erase that in case of success with a stdout message pointing to the log in case of an error.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @asgalon on GitHub (Mar 21, 2026).
Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/1268
See discussion item #1087
ubuntu 20.04 provides git 2.25.1, which has a bug with processing --sparse command line options.
Additionally, python 3.8 acquired dependency problems with the current requirements.txt configuration.
So the prerequisites in install.sh should be updated to git > 2.25.1 and python >= 3.9
Also, the actual problem was not visible because stdout and stderr were completely suppressed and not recoverable in case of a problem. A better way would be to write all messages to a logfile in the TEMP_DIR and erase that in case of success with a stdout message pointing to the log in case of an error.