Parse Error #44
Comments
Are you sure you're running PHP 7 on the CLI? |
Are you 100% sure of that? Could you test that on the cli? I'm sorry for asking again, but I've had issues where people thought that web php version === cli php version, and that's not always the case. |
Step to reproduce (I think):
|
Must be something specific to your app/server. I've got this package installed in multiple production sites that have If you find out what is causing it, please report it here. Kinda curious what the problem is. |
This happens with a new Laravel Install on my local Mac using Valet. I wonder if crontab is not running the same php version terminal is showing... |
Yep... crontab isn't running the same php version... I'll fix that... sorry to waste your time... |
Np, glad you found the cause
On Fri, 23 Jun 2017 at 20:27, Vince Mitchell ***@***.***> wrote:
Yep... crontab isn't running the same php version... I'll fix that...
sorry to waste your time...
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#44 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAdiDQIdDvnRcLsB29JJc0pKSQey5KU9ks5sHAOlgaJpZM4OD14h>
.
--
Freek Van der Herten https://spatie.be +32 495 84 27 91
|
I'm getting an interesting error in my logs.
The line in question: https://github.com/spatie/laravel-migrate-fresh/blob/master/src/Commands/MigrateFresh.php#L59
The things that make this error interesting:
It seems to have something to do with the return type. If I remove the return type it works fine.
The text was updated successfully, but these errors were encountered: