"An unexpected error was caught" when calling async callback

[peterbraden]

this code will trigger:

    require('vows').describe('vows').addBatch({
        'foo' : {
            topic : function(){
        this.callback(1)
            }
            , 'bar' : function(x){
                assert.equal(x, 1)
            }        

        }
    }).run()

gives:

    $ node test.js 
    ✗ 

      foo
        ✗ bar
          » An unexpected error was caught: 1
    ✗ Errored » 1 errored (0.004s)

[pgp44]

Hello

Not sure this will help you, but I just ran into the same issue. It seems that the callback in some or all cases interprets the first argument as an error. I think if you try

this.callback(null,1)

it might work

Perhaps it helps

Peter

[ayoung]

Yeah. Confirmed here in the tests. Someone should update the documentation on the vows website. Very misleading.

[Filirom1]

This is a nightmare :

I hate this feature, I lost 30 minutes to find this out :

  "when successful": {
        topic: function () {
            var that = this;
            process.nextTick(function () {
                that.callback(null, "OK");
            });
        },
        "should work like an event-emitter": function (res) {
            assert.equal(res, "OK");
        },
        "should assign `null` to the error argument": function (e, res) {
            assert.strictEqual(e, null);
            assert.equal(res, "OK");
        }

[rapaul]

+1

[adamstallard]

Proposal for alternative system for error-handling #264.

[bentaber]

+1

[giovannic]

+1

[indexzero]

Closing as a duplicate of #264. Adding the "error-handling" label for triage later.