2025-02-09 Sun

• #Work
  • work log for c74/M4L/Idea/Alits in Person/codekiln/GitHub/alits
  • A bit more work on learning DevContainers
    • GitHub/codekiln/dev-container-test
      • VSCode/Docs/remote/faq/Can I run VSCode Server on Older Linux Distributions

        • When it started up, I saw this warning: [10160 ms] !!! WARNING: Using legacy server, please check https://aka.ms/vscode-remote/faq/old-linux for additional information !!!
          • That link now redirects to the docs page linked above, which says,

            • Starting with VS Code release 1.86.1 (January 2024), the minimum requirements for the build toolchain of the remote server were raised. The prebuilt servers distributed by VS Code are compatible with Linux distributions based on glibc 2.28 or later, for example, Debian 10, RHEL 8, or Ubuntu 20.04. VS Code will still allow users to connect to an OS that is not supported by VS Code (OS that does not provide glibc >= 2.28 and libstdc++ >= 3.4.25) until February 2025
              

        • I saw GitHub/microsoft/vscode/issues/204269 Disappointment with Latest VSCode Update
        • I also saw StackOverflow/VSCode server unexpected Missing GLIBC gt eq 2.28
        • #Observation for now, DevContainer working, but it makes me wonder if it will soon break by the end of the month
          • #Q what version of glibc is available on Mac/OS?
            • Ans: I think it has nothing to do with macOS per se, it's about the image that you use, and I'm using mcr.microsoft.com/vscode/devcontainers/typescript-node:1-22-bookworm
            • node ➜ /app (main) $ ldd --version

              ldd (Debian GLIBC 2.36-9+deb12u9) 2.36
              Copyright (C) 2022 Free Software Foundation, Inc.
              This is free software; see the source for copying conditions. There is NO
              warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
              Written by Roland McGrath and Ulrich Drepper.
              

            • node ➜ /app (main) $ cat /etc/os-release

              PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
              NAME="Debian GNU/Linux"
              VERSION_ID="12"
              VERSION="12 (bookworm)"
              VERSION_CODENAME=bookworm
              ID=debian
              HOME_URL="https://www.debian.org/"
              SUPPORT_URL="https://www.debian.org/support"
              BUG_REPORT_URL="https://bugs.debian.org/"
              
      • 2025-02-08 16:58 - 32609957 - chore: basic devcontainer setup almost there #git/commit
        • Upon logging in this morning, I made a commit with the current dev container setup
        • Dev Container/Issue/Extension Not Found
          • result: filed Dev Containers not installing valid VS Code Extension - Minimal Reproduction - Bug Report - Cursor - Community Forum Software/Bug/Report
• #Learned
  • DevContainer/Commands
    • added VSCode/Command/Dev Containers/Show Container Log
• #Discovered
  • GitHub/jkomyno/pnpm-monorepo-template
    • a reference for turbo, pnpm with monorepo
  • GitHub/Barnard-PL-Labs/MaxPy
• #Filed
  • CursorAI/Project Rule/markdown-output
  • c74/M4L/.amxd/How To/Decompile .amxd into json
  • c74/max/obj/node.script/Ref/Node for Max
    • Apparently, it is possible to create a node.script Node for Max object and then bundle it in an c74/M4L/.amxd, but the docs on how to do that are centered on c74/max/standalone installations, not c74/M4L.
    • the key insight is that all js files in the context of c74/js must have unique file names
  • c74/Forum Forum/post/my
    • Live Javascript API: Observe multiple properties from one LiveAPI object - Max For Live Forum | Cycling '74 #c74/js #c74/M4L
      • note: Person/Zack Steinkamp also commented here
  • #Discovered
    • ts-node
    • c74/Node for Max API
      • const maxAPI = require("max-api");