-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'ErrorException' with message 'Use of undefined constant STDOUT - assumed 'STDOUT' #42
Comments
The error is coming from a dependency of Dispatcher. Can you post your |
It looks like there also might be an issue with a dependency here. The stack trace shows |
Apologies, I was without a computer over the weekend. Here are the registered schedule methods, I will try disabling them all and then re-enabling them one by one to see if that changes anything. Note that these are all from different commands.
|
I disabled all the commands (using |
If you could try unregistering them one by one that would be great. Is this running on Windows or Linux? If you could also verify the imports on your commands by looking for |
Will do, I'll do it tomorrow when I'm back at work. This is running on a Linux machine, using cPanel. I'll double-check the imports as well. To be honest, I actually saw an example recently with some other code where the namespace was being all skewed, I never discovered why but it was unrelated to the problem. Really curious. |
Did you have a chance to review this? |
Apologies, was out of town for the remainder of the week. I'm going to try again by unregistering the commands one by one tomorrow and will report back. |
Any luck on the source of the issue? |
I have the same error, mentioned above ('Use of undefined constant STDOUT - assumed 'STDOUT'), if I perform ANY Artisan:call('XY') from somewhere in my application. Everything goes fine if I remove Indatus/Dispatcher from composer.json and the ServiceProvider from the providers-array. I've tested it with a newly created and empty artisan command. Any idea? |
For those who're still suffering.. I was able to solve that Issue by putting those queue's inside the cron manually. I've been suffering that issue each time when I made artisan following up the queue untill I decided to make the queue's run by cron. Somehow or something is blocking that php shell to act with the terminal which provides the error. When manually steering the queue via cron, it doesn't happens. |
PHP only defines STDOUT when being run in cli. Seeing as It'd be helpful to see a project where this error occurs. Is it possible for you to grant me access or send some source code privately via email? |
I've just sent you an email with the url. |
I haven't received that email. |
Then I've got the wrong address. I took the one, mentioned at the end of the instruction slides. |
Indatus is in the process of moving some servers this weekend which may be On Sat, Jul 12, 2014 at 2:00 PM, erixx104 notifications@github.com wrote:
Ben Kuhl |
I've submitted a pull request to php-cli-tools to resolve this: wp-cli/php-cli-tools#57 |
I've pushed an update to the |
Your update works. Artisan::call() works without problems. Scheduled Jobs still running. Everything seems to be fine to me! |
Excellent! Since several of you guys were having this issue, can I get a 2nd confirmation from someone that this resolves the issue? |
I can confirm this has been fixed in the develop branch |
Thanks! Issue is resolved with the latest release: https://github.com/Indatus/dispatcher/releases/tag/v1.3.1 |
I'm just setting up Dispatcher to take over from our cron jobs but I'm seeing this error in my logs whenever a scheduled command is meant to run. The command does not end up completing any of the tasks it was meant to.
Any ideas what could be going wrong here?
The text was updated successfully, but these errors were encountered: