Jobs not running about guard-delayed

[suranyami]

Well, that certainly sounds like it needs dealing with.

Can you give me a little more info?

Is there a github repo I can download with your code on it, so I can try the same thing? If not, can you put one up?

Also, some information about your system would be good:

• Ruby version?
• Gemfile contents?
• Are you using RVM?
• Which version of delayed_job is installed?

Anything else you can tell me will help.

In the meantime, I'll try using guard-delayed again on my own machine... the project I built it for hasn't been in use for a while, so it's possible some dependency has caused it to break in the meantime.

Oh, also, you might try running guard with the debug option on, and see if the extra info it prints out helps shed some light on the problem:

guard -d

Thanks in advance.

[rwz]

Having the same issue here. The problem is that
system('RAILS_ENV=developement script/delayed_job', 'start') returns nil and does nothing actually. That's because setting environment variables is not allowed in system() calls at least in 1.9.3.

I'll provide pull request fixing that in couple of minutes.

[suranyami]

I've been having this same problem, too.
So, had a look at delayed-job and there's an issue #7 where they say that the -e flag is deprecated and you NEED to use RAILS_ENV=development.
So, I dunno what to do. Perhaps the -e flag needs to be added back to delayed_job, which would mean them accepting a pull request. Or I could fork delayed_job and have guard-delayed depend on the fork.
Will try to deal with this soon.

[rwz]

@suranyami I've made a dirty fix for that. Just didn't have time to do a proper pull-request.

But you can check out my fork, it works.

[suranyami]

Top work @rwz.

Merged, and pushed up to rubygems.org.

Thanks for your help!

[suranyami]

Actually, can you guys check that this is working for you and get back to me. I'll close the issue then.
Ta.

[rwz]

Works fine for me :)