Skip to content

Conversation

@sebgie
Copy link
Contributor

@sebgie sebgie commented Dec 6, 2013

closes #28
closes #30

  • added stopdone to wait for server to stop
  • renamed done to startdone
  • added conditional for grunt.task.current.async()
  • added testsequence which is able to reproduce the bug without my
    changes to server.js
  • added express:defaults without express:defaults:stop at the end
    of the file to reproduce missing 'async'

closes ericclemmons#28
closes ericclemmons#30
- added stopdone to wait for server to stop
- renamed done to startdone
- added conditional for `grunt.task.current.async()`
- added testsequence which is able to reproduce the bug without my
changes to server.js
- added `express:defaults` without `express:defaults:stop` at the end
of the file to reproduce missing 'async'
@ericclemmons
Copy link
Owner

I can merge this guy, but I still want it to be known that I can run the whole "custom_delay" block in the Gruntfile without any errors. Dunno if it's a race-condition, or what, but I have not been able to reproduce this since the bug was reported.

ericclemmons added a commit that referenced this pull request Dec 16, 2013
Fix multiple instances and no method 'async' bug
@ericclemmons ericclemmons merged commit 173aef0 into ericclemmons:master Dec 16, 2013
ericclemmons added a commit that referenced this pull request Dec 19, 2013
This reverts commit 173aef0, reversing
changes made to 997bbd2.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

rel 0.4.8 Object #<Object> has no method 'async' on exit Bug: starting multiple instances causes error

2 participants