chapter/compute: Restructure repo according to updated methodology

[AndreiMiga77]

Prerequisite Checklist

• Read the contribution guidelines regarding submitting new changes to the project;
• Tested your changes against relevant architectures and platforms;
• Updated relevant documentation (if needed).

Description of changes

Restructure Compute chapter to match the OpenEdu methodology

• Break arena into smaller sections and put it under sections
• Make tasks self-contained
• Generate support from solution whenever possible
• Fix linters

[teodutu]

I made an initial, high-level pass. Fix my inline suggestions and the more general ones listed below (especially the one regarding building the site) and then I'll give this another look.

• Add the following line at the end of each task: "If you're having difficulties solving this exercise, go through [this](link to the relevant section in reading/) reading material."
• use git rm -rf content/chapters/compute to remove all remaining files in that folder once they're moved
• Squash your commits into a single one because checkpatch runs on all commits every time. Further amend this single commit and git push -f upon every new review without adding additional commits.

[teodutu]

I gave you the fixes to config.yaml so the website builds properly. Apply them, then take care of my other suggestions.

• Change this line [1] to - 'chapters/compute/**/*' so the PR label for topic/compute is assigned correctly.
• Remove the arena/ folder. Extract all tasks from it and place them in whatever subchapter they fit best under drills/tasks/. You can prefix their names with "BONUS - " in config.yaml if they're more difficult.
• Add the following line at the end of each task: "If you're having difficulties solving this exercise, go through [this](link to the relevant section in reading/) reading material."

[1]

operating-systems/.github/labeler.yml

Line 8 in eb0056b

- 'content/chapters/compute/**/*'

[Alex-deVis]

@teodutu, @razvand, @VladNastase I finished the directory structure change but the builder seems to fail (check action for logs). From what I understand, it complains that some media files are invalid. This is very weird since Software Stack/media, Data/media, and Compute/media are all copies of .view/media (generated with gen-view.py).

The image at "/build/docusaurus/SO/docs/Data/media/exec.svg" can't be read correctly. Please ensure it's a valid image.
unsupported file type: undefined (file: /build/docusaurus/SO/docs/Data/media/exec.svg)

The media paths are defined with extra: media/ in the config.yaml for each chapter. I will not be able to debug this week, so feel free to investigate, or leave suggestions on how to go about this.

[Alex-deVis]

It seems there were other issues I missed:

Warning: nedu_builder.plugins.docusaurus:STDERR: [WARNING] Duplicate routes found!

• Attempting to create page at /operating-systems/74/Compute/, but a page already exists at this route.
• Attempting to create page at /operating-systems/74/Data/, but a page already exists at this route.

This error makes no sense, I ran make clean build and did not change the Data chapter. We should look into this.

The real problem seems to be:

Error: Image docs/Data/media/100-percent-cpu.jpeg used in docs/Compute/lab6.md not found.
at async Promise.all (index 2)

It was either this or solving the dangling references in the .md files.

[github-actions]

Published at https://cs-pub-ro.github.io/operating-systems/74/

[github-actions]

Published at https://cs-pub-ro.github.io/operating-systems/74/

[teodutu]

I only found one rendering issue. Fix that and then I'm OK with this. And fix the merge conflict by moving the tasks to the beginning of each lab.

[github-actions]

Published at https://cs-pub-ro.github.io/operating-systems/74/

[teodutu]

Suggested change

	1. Print the address and value of `var` in each thread.
	See that they differ.
	1. Modify the value of `var` in the `main()` function before calling `pthread_create()`.
	Notice that the value doesn't propagate to the other threads.
	This is because, upon creating a new thread, its TLS is initialised.
	2. Print the address and value of `var` in each thread.
	See that they differ.
	3. Modify the value of `var` in the `main()` function before calling `pthread_create()`.
	Notice that the value doesn't propagate to the other threads.
	This is because, upon creating a new thread, its TLS is initialised.

Now because you removed the indent above, these list items aren't numbered properly because there's a break in the list. Just number them manually, I guess.

[Alex-deVis]

No, I think I just have to indent the subsequent phrases.

1. Print the address and value of `var` in each thread.
See that they differ.

should be written as:

1. Print the address and value of `var` in each thread.
  See that they differ.

[Alex-deVis]

Ignore this, I misread your comment.

[Alex-deVis]

OK, so the problem was that quizzes had the wrong indent. Seems like markdown expects 3 spaces indentation when you are under a numbered list.

[github-actions]

Published at https://cs-pub-ro.github.io/operating-systems/74/