Toby Corkindale comments

Results 37 comments of


                                            Toby Corkindale

Preferred way of parsing a JsonArray or JsonObject?

does this help with what you're after? ``` val o: JsonObject = Parser.default().parse(sourceData) as JsonObject ```

Missing `operationId` doesn't provide context as to where it's missing from

+1 -- This was super annoying to try and figure out!

Example in documentation fails unless -port 8181 is added

[Service] ExecStart=/usr/bin/docker run --rm -p 80:8181 -p 8182:8182 mailgun/vulcand /opt/vulcan/vulcand --etcd=http://172.17.42.1:4001 Unless I append "-port 8181" to that, there's nothing listening on that port. (I tried -p 8181:8181 and -P...

mpremote on Mac OS X: allow env var or option in config file to select default serial port to use

Hi folks, a year on from when this issue was opened. I've been trying to use `mpremote` on OSX too; I figured out quickly that I could get the repl...

mpremote on Mac OS X: allow env var or option in config file to select default serial port to use

``` $ mpremote version mpremote 0.4.0 ```

mpremote on Mac OS X: allow env var or option in config file to select default serial port to use

Ah! Yes, chaining the commands together does work. I had no idea the connection string carries over from one to the next. So now I've made a helper script: ```bash...

mpremote on Mac OS X: allow env var or option in config file to select default serial port to use

Thanks so much for your quick response with a workaround.

ppp interfaces throw error when adding to team

As far as libteam goes, the error is returned from rtnl_link_enslave_ifindex() in team_port_add() I also tested this on kernel 4.2.5 and it presents the same errors.

teamd fails to create team device

I have the same issue as the original poster. I have two virtual machines, that are nearly identical fresh builds from Ubuntu 14.04.3. I built libteam 1.22 on both, but...

teamd fails to create team device

Update: Apologies, it seems one of the VMs is only building the kernel modules for the old 3.13 kernel, not the running 3.19 one. I don't know why (the headers...