pricer

SVIG/pricer

Fork 0

1400h: started

Discussed the new method of issues for problem solving, everyone seems to agree it's a good idea.

Karen reports that she's still having trouble accessing Docker from inside wsl.

Sloetjes is still unable to connect to the docker container, see #3

Mentioned the MacOS text extraction feature
Asked to paste text instead of screenshots
Mentioned the issue number syntax convention (#number means an issue, repository#number means an issue in that repository)
Mentioned that git commit messages should reference issues (#number). Issues are linked to commits automatically when they're referenced in a commit message, and the commit appears in the issue timeline.
Don't begin a git comment with an issue reference, because # is a comment character in that context.
Tested issue linking from git commit comments, it works fine and appears in the issue timeline.
Mystery: why do the issue numbers in the repository's issue view sometimes have a green background? We all refreshed the page, and saw it flip from green to black for some reason.
Karen somehow got X Windows running by herself to remote the Chrome windows onto her Windows desktop. Impressive. I mentioned that having documentation on how to set it up in the wiki, or even better, a Powershell script to automate the setup, would be better than just doing it.
Reviewed the history of computing window systems:

Project Athena: https://en.wikipedia.org/wiki/Project_Athena

X Windows: https://en.wikipedia.org/wiki/X_Window_System

Quartz Compositor (MacOS): https://en.wikipedia.org/wiki/Quartz_Compositor

Showed how to look up a process by name. MacOS: pgrep, Windows: Get-Process
Mentioned the sysinternals procdump and procexp for examining kernel threads
Showed the pushd \\live.systinternals.com\tools trick for getting access to the sysinternals repository from cmd.exe
net use y: \\live.sysinternals.com\tools is the powershell equivalent
Demonstrated the use of process explorer from there to look into the kernel threads to see the display server
Reminded Karen to run process explorer (procexp64.exe) as Administrator
Explained compositing vs client-server window managers, why we don't want to have any pixels output for performance reasons
Described Wayland and mutter, tried to run mutter in headless mode in wsl, but this happened:

j@DESKTOP-EEP8R1F:~$ mutter --wayland --headless --virtual-monitor 1280x800
libmutter-Message: 15:54:20.517: Running Mutter (using mutter 42.5) as a Wayland display server
libmutter-Message: 15:54:24.748: Created surfaceless renderer without GPU
libmutter-Message: 15:54:37.091: Disabling DMA buffer screen sharing (not hardware accelerated)
libmutter-Message: 15:54:37.092: Disabling DMA buffer screen sharing (implicit modifiers not supported)
libmutter-Message: 15:54:37.094: Added virtual monitor Meta-0

(mutter:3129): libmutter-ERROR **: 15:54:37.103: Failed to start X Wayland: Directory "/tmp/.X11-unix" is not writable
Trace/breakpoint trap (core dumped)

Looked at Karen's issue some more; she's not even at the point where things should be drawn on the screen, because the ansible playbook can't get to the point where snapd runs via systemd to install the chromium snap. See #4.
Mentioned how to get ansible module help on the command line:

ansible-doc MODULE_NAME

How to get the documentation for a specific module option/parameter:

ansible-doc -j docker_container | jq .docker_container.doc.options.published_ports

Run this by pasting into the command line to create a helper function:

function ad() {
  ansible-doc -j "$1" | jq ".$1.doc.options.$2"
}

Use like this:
$ ad docker_container name                                                                                                               {
  "description": [
    "Assign a name to a new container or match an existing container.",
    "When identifying an existing container name may be a name or a long or short container ID."
  ],
  "required": true,
  "type": "str"
}

When creating a new task, you can generate a skeleton for the module you're calling like this:

ansible-doc -s module MODULE_NAME

Running ansible in check mode is a good way to see if your play arguments are correct:

ansible -C -m community.docker.docker_container -a "name=dev image=dev" localhost