Andrew Baxter

Currently following the instructions in the readme you get ``` TypeError: invalidFrees.push is not a function ```

It looks like there's already debug level logging via `FLYCTL_OUTPUT_HAR` here: https://github.com/superfly/flyctl/pull/2289 (undocumented)

But https://github.com/superfly/flyctl/issues/3107

Just spent 30m trying to figure out what I was missing and finally landed here. With sufficient warning, I (and I think others) would prefer an unstable way to do...

Found a workaround for producing the type info at least: for most types I think you can do `String::type_info()` or `i64::type_info()` and piggy back off the blanket implementations to get...

So here's the broken values: ``` XDG_DATA_DIRS=/nix/store/22fla1y46210imn2zhqpp135baq675ka-desktops/share:/home/rootui/.nix-profile/share:/nix/profile/share:/home/rootui/.local/state/nix/profile/share:/etc/profiles/per-user/rootui/share:/nix/var/nix/profiles/default/share:/run/current-system/sw/share GIO_MODULE_DIR unset ``` and the fixed ones per the above suggestions ``` XDG_DATA_DIRS=/nix/store/6ywqswdc2q57mhysnh3jp6dcbxd62yz4-gsettings-desktop-schemas-45.0/share/gsettings-schemas/gsettings-desktop-schemas-45.0:/nix/store/8d431fhwmpfmf9rnpslx8pn98l151wq9-gtk+3-3.24.41/share/gsettings-schemas/gtk+3-3.24.41:/nix/store/22fla1y46210imn2zhqpp135baq675ka-desktops/share:/home/rootui/.nix-profile/share:/nix/profile/share:/home/rootui/.local/state/nix/profile/share:/etc/profiles/per-user/rootui/share:/nix/var/nix/profiles/default/share:/run/current-system/sw/share GIO_MODULE_DIR=/nix/store/xrp3b987wmblhv444xk7aa6v24rgq6am-glib-networking-2.78.0/lib/gio/modules/ ```

It would be great if the example showed doing this, assuming it's best practice. I usually rely on examples for idiomatic usage including things like this.

Are you saying that based on the above report or is there some documentation saying this only applies to google? There are many versioned endpoints for instance and configuration parameters...

To clarify, I think there are two cases here: 1. Formatting a file with genemichaels but skipping a chunk (generated code, or a very weird macro invocation, or something else...

Yeah, rules like that would work! Right now I already have (I think) two rules: 1. Blank lines around `struct{}/enum{}/union{}` definitions 2. Blank lines around groups of `use` statements which...