Sergei Kasatkin

In current version (1.1.2) output capture implementation relies on simple command line redirect by adding ">>" or ">" to a command. This will not work for callbacks. BTW, output capture...

In current implementation command being built with output directed to some filepath (`/dev/null` by default) Like: `/usr/local/bin/some-program > /your/output/path` I'm not sure if that's Scheduler responsibility to check if that...

Not sure I fully understand the question. The statement `$schedule->command($command)->cron('...')` itself is asynchronous Each event though will block execution if it doesn't have callbacks. See `\omnilight\scheduling\Event::run`

Sorry, @siyecaoya, I still don't get it. I'll try to make an assumption that what your issue is that you want two commands (events) to be executed asynchronously. In current...

no problems, @siyecaoya. Does this answer your question?

I have doubts that code you posted is exactly what you run, because it has syntax errors, but: * If you are really using an instance of `DateTimeZone` you should...

No, it's not available at this moment

As in the first place this package is a port of Laravel's Scheduler, may be good point would be to check their tests: https://github.com/laravel/framework/blob/master/tests/Console/ConsoleEventSchedulerTest.php https://github.com/laravel/framework/blob/master/tests/Console/Scheduling/EventTest.php https://github.com/laravel/framework/blob/master/tests/Console/Scheduling/CacheSchedulingMutexTest.php

@omnilight please, take a look at https://github.com/omnilight/yii2-scheduling/pull/31, we can use this approach to port Laravel's tests

Merged #31, will you now integrate travis, @omnilight?