Enumerate the tests in order to make sure that execa is as robust as subcommandante
Closed this issue · 6 comments
As discussed in August 15 js-ipfs sprint meeting. @jbenet please enumerate all the tests you would like to see for: #89
//cc @JGAntunes
@diasdavid no sorry I don't have time for this in the next 2 weeks. If you
want me to this it probably won't get done for a while.
On Mon, Aug 15, 2016 at 17:00 David Dias notifications@github.com wrote:
Assigned #95 #95 to @jbenet
https://github.com/jbenet.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#95 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAIcoW4vFe9u4AfL4xneNWF3011-jCDZks5qgNN7gaJpZM4JkxEZ
.
The burden of proof also lies on whoever wants to change the behavior.
Its up to that PR to ensure correctness
On Sun, Aug 21, 2016 at 21:24 Juan Benet juan2@benet.ai wrote:
@diasdavid no sorry I don't have time for this in the next 2 weeks. If you
want me to this it probably won't get done for a while.
On Mon, Aug 15, 2016 at 17:00 David Dias notifications@github.com wrote:Assigned #95 #95 to @jbenet
https://github.com/jbenet.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#95 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAIcoW4vFe9u4AfL4xneNWF3011-jCDZks5qgNN7gaJpZM4JkxEZ
.
Ok, I'll handle this myself with @JGAntunes
I found out the hard way that it isn't :(
Could you elaborate?
Nvm, saw the commits on #140 (comment), closing this one then :)