Add integrity checks for lab installations
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
The runlab command ends prematurely for all labs. However, the SQLi lab is the only lab that has some kind of integrity checks before the notebook is available. We should implement a method that will check that every dependency and file is installed before the notebook will run for the students. If not everything is installed, re-run the script (or part of it) until everything is installed.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the runlab command and compare its behavior with the SQLi lab's existing integrity checks. Define completion as verifying every lab dependency and file before the student notebook runs, with missing items causing the relevant installation script or part of it to run again.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100