reytech-dev

1. Check if docker zone exists in firewall-cmd

$ firewall-cmd --get-active-zones

2. If "docker" zone is available, change interface to docker0 (not persisted)

$ sudo firewall-cmd --zone=docker --change-interface=docker0

3. If "docker" zone is available, change interface to docker0 (persisted, thanks rbjorklin)

daverigby

1. Install package libstdc++6 (Ubuntu 16.04)
2. Add following to ~/.gdbinit

python
import sys 
sys.path.insert(0, '/usr/share/gcc-9/python')
from libstdcxx.v6.printers import register_libstdcxx_printers
register_libstdcxx_printers (None)
end

kudaba

If an application is crashing during a github actions run then you can use this guide to capture the core as an artifact for debugging.

This guide was developed to debug Mac crashes specifically. It should mostly apply to Linux as well but getting dumps from Windows is unknown for now.

Mac / Linux

By default these systems will not be in a state where they are recording core dumps, and even when enabled you need to run with elevated permissions for a core to even be written. To capture dumps you need to do the following:

jannismain

#!/usr/bin/env python3
from __future__ import annotations

import json


class CompactJSONEncoder(json.JSONEncoder):
    """A JSON Encoder that puts small containers on single lines."""

    CONTAINER_TYPES = (list, tuple, dict)

dahu

#!/bin/sh

# Attribution: unknown. Probably taken from the fossil-users mailing list.

usage() { echo usage: $0 'archive.fossil "project name" "project description"' ; exit 1 ; }

dbname="$1"
pname="$2"
pdesc="$3"