-
-
Notifications
You must be signed in to change notification settings - Fork 20
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
ok: RuntimeException with message 'Too many arguments, expected arguments "command".' #36
Comments
I'll try it on my M1 tomorrow morning with those versions |
Seems to be related to PsySH maybe... |
I think you are right - this is the bit that suggests this is the case:
Further details follow...
This downloads various
Then ...
from the last command I get the response:
If I use the
Updating .env to show Commenting out If I select text & press Ctrl + Shift + A the dialogue box pops up saying assertion generated. Then ...
Thanks again for all your help. By the way do you know that the |
Any news on this? I assume it will be an issue for all Laravel installs ... |
Sorry, I haven't had time to take a look at it yet. I'll reserve some time for it today. |
Thanks in anticipation ... |
@rightwayround I've fixed the psysh dependency (haven't updated it yet), but the command error doesn't seem to be limited to magic test. See: https://laracasts.com/discuss/channels/laravel/runtimeexception-with-message-too-many-arguments-expected-arguments-command Looking into it.. |
@rightwayround i'm getting that on a clean laravel install, too |
@rightwayround so it's a known issue: bobthecow/psysh#704 Using |
@rightwayround v0.15 has been tagged |
Thanks for your efforts, but I am still having the same issue. I
My composer.json shows My composer.lock shows:
|
I have just been looking here (bobthecow/psysh#705) and can see it's an upstream problem. I will pester those guys. If you have any bright ideas on what I could do as a work around let me know? Otherwise thanks for everything. Also, fix your sponsorship link! |
… is it working for you @mateusjatenee? Are you using valet? |
@rightwayround have you tried this? bobthecow/psysh#705 (comment) |
@mateusjatenee yes I did try that. I get the following - which is why I asked whether you were using valet:
Running
|
... if there was an alternative standard (maybe sail, laradock, docker based) environment that works, that would be cool too. |
hey! running in to this while running in sail. after trying (bobthecow/psysh#705 (comment)) it seems to return the same RuntimeException |
Could throwing cash at this make the problem go away |
@rightwayround I cannot replicate your error. Can you send me a list of the packages you have installed and their versions? |
Very close to being able to use this wonderful tool, any help much appreciated.
I run:
./artisan magic
, aChrome is being controlled by automated test software
browser window comes up, dev console shows:I log in, dev console looks ok, no errors. Nothing in network tab relating to magic-test-laravel or testing generally.
If I select text & press Ctrl + Shift + A the dialogue box pops up saying assertion generated.
I go into psy shell, type
ok
but get the message:RuntimeException with message 'Too many arguments, expected arguments "command".'
in:
Psy Shell v0.10.12 (PHP 8.1.2 — cli)
No major changes are made to the
ExampleTest.php
which has the simplest initial test method in it:What could be wrong? Full output here:
Using
https://chromedriver.storage.googleapis.com/97.0.4692.71/chromedriver_mac64_m1.zip
for the installed browserVersion 97.0.4692.99 (Official Build) (arm64)
./artisan tinker
works fine for the same project../artisan dusk
returnsOK (1 test, 1 assertion)
when I switch commenting onmagic()
andassetSee('Laravel')
.The text was updated successfully, but these errors were encountered: