Oliver Ford

I think what's most sad is all the (to varying degrees of passiveness) aggression in this bug report in free open source software. If it's so much more important to...

Thanks @cptaffe for the workaround - would be good to have this fixed though. It's probably not a trivial fix, since it is of course ambiguous - but probably everyone...

Perhaps the `brew service` (the plist file specified in the formula linked above, I assume) could `--load-sa` on (re)start? Or perhaps `--install-sa` should also load? I suggest these because the...

> This only "solves" the problem until the user relogs, reboots, or Dock.app is restarted. Sure, I just meant for easier UX since that's what I was aware of to...

I've tried again from a different machine, but I still get this - this is on master, not this branch: ``` $ ./mvnw clean package [...] [INFO] [INFO] Results: [INFO]...

Oh, `maven` wasn't installed. Just a bizarre error for it. After installing, `./bin/generate-samples.sh bin/configs/python-flask.yaml` worked fine without running the `mvnw clean package` first.

The docs generator produces a diff, but none of which is related to my changes (all other languages even).

I see similar in installation, but after fixing #273 it seemed to proceed and install ok anyway (seemingly) despite these errors - dialogs popping up to install extensions I'd selected...

Ah, > wine: could not open working directory is resolved (if it's even a problem) by running from within `wineprefixes/default/drive_c`. The rest seems to be the actual error though.

Works after removing everything (because uninstall was broken too) and running `../../../bin/install.sh` from the `drive_c` directory. (i.e. manually `mkdir -p wineprefixes/default/drive_c` first.)