Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[5.6] Updated to use new release of cron-expression (#21637)
* Updated to use new release of cron-expression * fix test
- Loading branch information
e9e1860
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dragonmantank I am getting an error with this update, attached is my composer.json file.
Is there something I am missing here:
e9e1860
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Position 5 was the year position, which the library no longer supports (it was barely supported by most traditional cron parsers). Just check any scheduled jobs you have, and if they have 6 parameters, remove the last one.
Though ideally I should also have that error be 1-based instead of 0-based to make that much more clear.
e9e1860
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dragonmantank thank you for your quick reply. I don't think I understand what you mean here, all I am using is laravels scheduler:
I have this in my
Kernel.php
file:Is this what you are referring to?
e9e1860
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dragonmantank thanks again for your help, it looks like the updates you and @taylorotwell made may have introduced a bug. In order to get around the bug I had to change the file:
e9e1860
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm. The change was for Laravel 5.6/
master
(laravel/framework#21637), but according to yourcomposer.json
you've requestedlaravel/framework:5.5.*
, so you should not even be using the new code that dropped the year.Check your
composer.lock
file and see if you havemtdowling/cron-expression
ordragonmantank/cron-expression
, and what version it's pinned at. That will shed a bit more light on what is going on.e9e1860
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dragonmantank thanks for the heads up about the
composer.lock
file.Here is the gist of the file: https://gist.github.com/cmosguy/e4a1bd13a06984ee90e464996941f13a
Can you you tell what could be causing the conflict? I got this situation by just doing
composer update
and just includingaws-php-sdk
. In thereaws-php-sdk
it usesmtdowling
but then you forked it and now I believe it causes a conflict with LaravelsCronExpression
class.