Diary

• Situation
  • Audio from remote desktop apps not reaching the host
  • Audio stops working after the remote machine goes to sleep
• Environment
  • Host: Windows 11 22H2
  • Remote: Windows 11 22H2
• Solution
  • Search for “service” in Windows search on the remote machine
  • Double-click to open the Services app
  • Select “Windows Audio” service, right-click and choose “Restart the service”

Xcode15.3 Error Thread 1: EXC_BAD_ACCESS (code=1, address=0x0)

Xcode 15.3 came out, so I checked an existing project and got an error:

Thread 1: EXC_BAD_ACCESS (code=1, address=0x0)

Turned out it was crashing around Firebase.

Updated the Firebase package.

SDK Version 10.11 had the error.

SDK Version 10.22 fixed it.

Need to check what changed with the SDK upgrade and if it affects anything else.

swagger

A tool you can use for API design document management. It generates sample code as JSON, and behaves like Postman for testing.

More and more projects are using it lately.

Starting a local server (example with 3 instances, useful when you have 3 external API servers, etc.)

docker pull swaggerapi/swagger-editor
docker run -d -p 8090:8080 swaggerapi/swagger-editor
docker run -d -p 8091:8080 swaggerapi/swagger-editor
docker run -d -p 8092:8080 swaggerapi/swagger-editor

Open http://localhost:8090 etc. in your browser

Copy and paste the yaml file content from your repository into the left window of the browser alongside your source control

Test with get, post, etc.

※You’ll need some understanding of API specifications

Often used together with OpenAPI

This tool reads yaml files in API design format and automatically generates I/O source code in your specified language. However, it’s not all roses—it sometimes generates incorrect code, so you’ll often run into situations where you need to do some debugging and cleanup.

dnf command error

dnf update

AlmaLinux 8 - BaseOS 485 kB/s | 3.4 kB 00:00 
Importing GPG key 0xC21AD6EA: 
Userid : "AlmaLinux <packager@almalinux.org>" 
Fingerprint: E53C F5EF 91CE B0AD 1812 ECB8 51D6 647E C21A D6EA 
From : /etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux 
Is this ok? [y/N]: y 
Key import succeeded 
Importing the key didn't help. Is the key wrong?

The key has been updated

AlmaLinux 8 GPG Key Change

Starting January 12, 2024, AlmaLinux 8 RPM packages and repo metadata will be signed with an updated GPG key. Follow the steps below to continue receiving updates without issues after the switch.

If you want to verify that your system already contains the new AlmaLinux 8 GPG key and trusts it, just import it.

sudo rpm --import https://repo.almalinux.org/almalinux/RPM-GPG-KEY-AlmaLinux

Access from browser:

http://localhost:8081

ME_CONFIG_MONGODB_ADMINUSERNAME: root 
ME_CONFIG_MONGODB_ADMINPASSWORD: password

Tried logging in with the specified ID and password in the browser but couldn’t log in? Hmm…

Turned out Basic authentication environment variables for the browser were needed.

ME_CONFIG_BASICAUTH_USERNAME: admin
ME_CONFIG_BASICAUTH_PASSWORD: password

Create a “docker-compose.yml” file (code below)

Run “docker-compose up -d” command in the terminal

version: '3.1'

services:

  mongo:
    container_name: mongo-dev
    image: mongo
    restart: always
    ports:
      - "27017:27017"
    environment:
      MONGO_INITDB_ROOT_USERNAME: root
      MONGO_INITDB_ROOT_PASSWORD: password
    volumes:
      - ./configdb:/data/configdb
      - mongoDataStore:/data/db

  mongo-express:
    container_name: mongo-express
    image: mongo-express
    restart: always
    ports:
      - 8081:8081
    environment:
      ME_CONFIG_MONGODB_ADMINUSERNAME: root
      ME_CONFIG_MONGODB_ADMINPASSWORD: password
      ME_CONFIG_MONGODB_URL: mongodb://root:password@mongo:27017/
      ME_CONFIG_BASICAUTH_USERNAME: admin
      ME_CONFIG_BASICAUTH_PASSWORD: password

volumes:
  mongoDataStore:
    driver: local

Also verify connection from Mac terminal (make sure testDB and such are created beforehand via express, etc.)

mongosh "mongodb://root:password@localhost:27017/testDB?authSource=admin"

Current Mongosh Log ID: 65be609e7384r68762b10b0