Rick van de Loo
Rick van de Loo
ran into this too: ``` # make make all-recursive make[1]: Entering directory '/usr/etc/wslay' Making all in lib make[2]: Entering directory '/usr/etc/wslay/lib' Making all in includes make[3]: Entering directory '/usr/etc/wslay/lib/includes' make[3]:...
I found that I needed to wrap the communicate.execute in a "communicate.ready?" because otherwise issuing a vagrant destroy would fail because the machine is already down before cleaning up the...
I tried net-destroy and net-undefine yesterday as well on all vagrant related networks but no success. I'll wait until 0.2.0 is released but untill then I'll keep my systems on...
I've come up with something like this: ``` #lang sweet-exp racket require rackunit mock (module+ test (test-case "check-mock-num-calls does not fail when amount of calls is equal" (check-mock-num-calls 0 (void-mock)))...
Mmm, I don't understand why the inner checks still fail even though we raise them with the parameterize and wrap them in check-exn instead of printing them. The outer checks...
The [join procedure](https://github.com/alandipert/gherkin/blob/master/core.gk#L124) from the core library gets trapped in an infinite loop with this change. Any idea what might be causing this? edit: never mind, found it. Next commit...
HI @shiyang-fei, this repo does not come with a pre-built and hosted Vagrant box. If you want to just run `vagrant up` you'd have to build the box yourself first,...