-
Notifications
You must be signed in to change notification settings - Fork 12
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
composer require phpactor/phpactor:^0.11 #79
Conversation
Hi @zonuexe |
Hello, Just gave it a shot :
|
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.
Hi @zonuexe
How did you handle the upgrade on your machine ?
At first sight, something did not work as expected on mine (see previous comment)
refs #80 |
#79 (review) According to the testimony of @ kermorgant, it seems that the installation was delayed due to the previous change and an error occurred.
392d6d3
to
3cbc265
Compare
composer.json
Outdated
"phpactor/class-to-file": "@dev", | ||
"phpactor/code-builder": "@dev", | ||
"composer/xdebug-handler": "^1.1", | ||
"monolog/monolog": "^1.0", |
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.
this one was problematic but after removing this line, installation would succeed
"monolog/monolog": "^1.0", |
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.
@kermorgant Thanks!
Running phpactor-status after upgrading generated an error with this message phpactor-action-dispatch: Keyword argument :version not one of (:action :parameters) My guess is that there's been a change in the RPC protocol, but I've asked @dantleech on slack to be sure. |
@zonuexe as a sidenote : I've started targeting develop branch for some pull requests to keep the freedom to experience a bit. Could the develop branch be used for us as a staging phase for potentially disrupting changes, which I start to think this issue is (I've been tempted to define the develop branch as the default one but as I was unsure about the scope of that change, I did not. Does that sound ok to make this switch ?) |
@kermorgant |
@zonuexe thanks !
My bad, the issue disapeared after restarting emacs... ( But still, trying completion ended with this message
|
I added |
Thx ! Now facing this
|
Just talked with @dantleech on slack 1- this error might need another tag for the extension-manager dependency |
You might want to try just falling back to |
@dantleech I tried and it worked. Is that an acceptable solution for a PR ? |
Yeah sure |
@zonuexe you ca now target version 0.11.1 (thanks @dantleech ) which includes the path fix mentioned above. |
@zonuexe I realized I had access to the branch so I pushed the change. OK for you ? |
It is risky to overwrite the platform version, but now seems to work normally.
@kermorgant Sorry for the late reply. |
No worry. I understood the issue was related to a development dependency (php-cs-fixer I remember), which would anyway cause |
@kermorgant |
Ok for me !
Le ven. 4 janv. 2019 à 15:00, USAMI Kenta <[email protected]> a
écrit :
… @kermorgant <https://github.com/kermorgant>
It seems like the problem I saw. I would like to merge this change.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#79 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKEoLAQhbRC2yy8fihHvE2woMaEzkUOgks5u_1B-gaJpZM4Y0y4Z>
.
|
@kermorgant Thanks a lot! |
https://github.com/phpactor/phpactor/releases/tag/0.10.0