HN user

jo-m

983 karma
Posts8
Comments67
View on HN

I have something similar, but open fzf to select the branches to delete [1].

    function fcleanb -d "fzf git select branches to delete where the upstream has disappeared"
        set -l branches_to_delete (
            git for-each-ref --sort=committerdate --format='%(refname:lstrip=2) %(upstream:track)' refs/heads/ | \
            egrep '\[gone\]$' | grep -v "master" | \
            awk '{print $1}' | $_FZF_BINARY --multi --exit-0 \
        )

        for branch in $branches_to_delete
            git branch -D "$branch"
        end
    end
[1]: https://github.com/jo-m/dotfiles/blob/29d4cab4ba6a18dc44dcf9...
GarminDB 1 year ago

Maybe it is because I am in Europe, but the data export I recently did (2024-10) contained all my FIT files, although in another layer of zip:

    DI_CONNECT/DI-Connect-Uploaded-Files/UploadedFiles_0-_Part\*.zip
    DI_CONNECT/DI-Connect-Fitness/my@email_PrimaryTrainingBackup_Part1.zip
GarminDB 1 year ago

What you can always do to get ALL your raw data out of Garmin connect (as FIT files) is using the data export (https://support.garmin.com/en-US/?faq=W1TvTPW8JZ6LfJSfK512Q8).

There are some good OSS libraries to read and interpret those files (e.g. Python https://github.com/polyvertex/fitdecode, Go https://github.com/tormoder/fit).

To get your _current_ data, it is possible to pull the current .FIT files from your device (watch, bike computer, ..) when it is plugged to your computer and mounted as file system.

I once started a side project to do exactly that, but abandoned it after a while (https://github.com/jo-m/garmin-disconnect).

D3 in Depth 2 years ago

Observable Plot is amazing. It is very flexible and intuitive to use. I now prefer it over Plotly.js which I used to use before.

The docs are pretty OK, the only thing missing is a usable API reference section, so discoverability is not great.

I had something similar once happen at my previous job. The company was using Google Workspace and GCP. The person who had set up GCP initially left the company. 1 month later, HR deleted his Google acc. Little we knew, the payment profile was attached to he GCP projects through his account, so deleting his account effectively removed the CC. All our stuff was shut down immediately (within minutes).

We first had no idea what was going on. GCP support just told us "it seems you deleted your CC". Eventually, we figured out what happened.

Set up a new payment profile and started migrating our GCP projects to it. Eventually had to create multiple of them, because there is an arbitrary quota of how many projects you can have per payment profile (~4), and support told us it would take days to increase it.

Fortunately, all our data was still there. However, support had initially told us that it's "all gone".

Interestingly enough, as of 2023-08-22, Google IoT core is still alive and kicking. We are still getting events delivered, and the web console is still functional.

Have they discovered that their office door locks are actually using it? Or, has the guy who had in his calendar "Turn off IoT core on 2023-08-16" simply been fired?