maxvram / signifier

A modular Python framework for interactive LED/audio installations.

Hi there 👋

signifier's Issues

No pyalsaaudio intellisense in VS Code

After installing pyalsaaudio like I do any other module python3 -m pip install pyalsaaudio on the remote machine I'm developing on, the import alsaaudio module would not play ball with my VS Code's Intellisense.

The package import auto-completes, but stays grey, even after being called later in the script. None of the functions or constants I use from the module appear to be registered, so I've had to work of the examples and source code in another window to navigate the library. However, all the functions appear to work fine during runtime. So I figure it's just a weird Pylance import issue or something of the sort. This is the first package it's happened to though.

I'm not using any virtual environments, it's bare-metal Python package install on Raspberry Pi OS Bullseye Lite 64-bit. I'm accessing it from a remote Windows 11 desktop.

Dev Signifier OS environment has Docker memory error and cannot run commands

On my development Pi environment I ran into a restart-persistent error that prevents Docker commands from functioning:

> docker compose ps -a

runtime.bucketMask(...)
        /usr/local/go/src/runtime/map_fast64.go:132
runtime.bucketMask(...)
        /usr/local/go/src/runtime/map_fast64.go:132
runtime.bucketMask(...)
        /usr/local/go/src/runtime/map_fast64.go:132
...

The Docker service is running, but reports it can't find the memory controller:

```bash
> sudo systemctl status docker

● docker.service - Docker Application Container Engine
     Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
     Active: active (running) since Sat 2022-01-15 13:19:32 AEDT; 19min ago
TriggeredBy: ● docker.socket
       Docs: https://docs.docker.com
   Main PID: 730 (dockerd)
      Tasks: 29
        CPU: 2.788s
     CGroup: /system.slice/docker.service
             ├─730 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock
             ├─959 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 9001 -container-ip 172.17.0.2 -container-port 9001
             └─966 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 9001 -container-ip 172.17.0.2 -container-port 9001

Jan 15 13:19:03 sigdev dockerd[730]: time="2022-01-15T13:19:03.485258959+11:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc
Jan 15 13:19:14 sigdev dockerd[730]: time="2022-01-15T13:19:14.794604952+11:00" level=info msg="[graphdriver] using prior storage driver: overlay2"
Jan 15 13:19:14 sigdev dockerd[730]: time="2022-01-15T13:19:14.937609414+11:00" level=warning msg="Unable to find memory controller"
Jan 15 13:19:14 sigdev dockerd[730]: time="2022-01-15T13:19:14.939336801+11:00" level=info msg="Loading containers: start."
Jan 15 13:19:17 sigdev dockerd[730]: time="2022-01-15T13:19:17.856453554+11:00" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address"
Jan 15 13:19:21 sigdev dockerd[730]: time="2022-01-15T13:19:21.904047826+11:00" level=info msg="Loading containers: done."
Jan 15 13:19:31 sigdev dockerd[730]: time="2022-01-15T13:19:31.842295617+11:00" level=info msg="Docker daemon" commit=459d0df graphdriver(s)=overlay2 version=20.10.12
Jan 15 13:19:31 sigdev dockerd[730]: time="2022-01-15T13:19:31.869054408+11:00" level=info msg="Daemon has completed initialization"
Jan 15 13:19:32 sigdev dockerd[730]: time="2022-01-15T13:19:32.359792900+11:00" level=info msg="API listen on /run/docker.sock"
Jan 15 13:19:32 sigdev systemd[1]: Started Docker Application Container Engine.

System memory is okay:

> free -m
               total        used        free      shared  buff/cache   available
Mem:            1849         153        1320           0         376        1637
Swap:             99           0          99

htop shows containerd processes are consuming resources:

    604 root       20   0 1374M 38964 24724 S  0.0  2.1  0:00.89 ├─ containerd
    623 root       20   0 1374M 38964 24724 S  0.0  2.1  0:00.10 │  ├─ containerd
    624 root       20   0 1374M 38964 24724 S  0.0  2.1  0:00.03 │  ├─ containerd
    625 root       20   0 1374M 38964 24724 S  0.0  2.1  0:00.13 │  ├─ containerd
    626 root       20   0 1374M 38964 24724 S  0.0  2.1  0:00.00 │  ├─ containerd
    627 root       20   0 1374M 38964 24724 S  0.0  2.1  0:00.00 │  ├─ containerd
    635 root       20   0 1374M 38964 24724 S  0.0  2.1  0:00.08 │  ├─ containerd
    636 root       20   0 1374M 38964 24724 S  0.0  2.1  0:00.16 │  ├─ containerd
    637 root       20   0 1374M 38964 24724 S  0.0  2.1  0:00.15 │  ├─ containerd
    979 root       20   0 1374M 38964 24724 S  0.0  2.1  0:00.07 │  └─ containerd

I'm unsure why this has become an issue. It's possible an update/procedure I conducted along the way altered something. I haven't been maticulously documenting package installs.

Without success, I tried adding the line cgroup_enable=memory to the file /boot/cmdline.txt.

Which was suggested for a similiarly appearing issue provided from here:
https://www.linuxquestions.org/questions/slackware-arm-108/trouble-with-kernel-5-4-65-and-docker-unable-to-find-memory-in-controller-set-4175682623/

Concurrent audio clips are slightly out of sync