Failed test: Client config(): sends config command 10 times about node-ar-drone HOT 4 CLOSED

Not really on topic, but related, since you are so active improving the nodecopter code:

The behavior that this code tests is questionable but its the best we have so far. It stems from not properly reading the acks for our config commands. I did a little writeup on this a while back: https://gist.github.com/bkw/4416785 but never got around implementing it. Maybe you want to have a go at it. Not only would this make communication with the drone more efficient and reliable, it would also obsolete the multiple sends and last but not least, the failing test ;-)

from node-ar-drone.

@bkw Thanks for sharing this! I'm not sure if I want to dive into low level drone communication stuff :-) I never felt any reliability issue with the drone yet, so I don't feel any urgency to improve the communication part. Maybe in the meanwhile we should just scrap the test, so that we can at least benefit of travis?

from node-ar-drone.

I'm not sure if I want to dive into low level drone communication stuff :-)

It's fairly easy and lots of fun - you totally should!

Maybe in the meanwhile we should just scrap the test, so that we can at least benefit of travis?

I'm fine with something like this at the top of the test:

return console.log('skipped - currently broken, needs investigation');

But obviously an actual fix would be much nicer. Maybe I'll get some time to hack at the jsconfus nodecopter!

from node-ar-drone.

Closing this as it's not had any activity in over a year, please re-open if it's still affecting you.

from node-ar-drone.