-
Notifications
You must be signed in to change notification settings - Fork 628
Composer & Xhprof fail provisioning #1071
Comments
This is because phacility/xhprof has removed composer.json support. See phacility/xhprof@e3df210 and phacility/xhprof#40 |
What a drama... oh. my. god. Still something should be done as it breaks the build. |
+1 getting same error. Don't understand why they removed composer in the first place... |
Fwiw I'm maintaining a fork at https://github.com/lox/xhprof, which is what https://packagist.org/packages/facebook/xhprof presently points to. When they come to their senses I'll redirect to the "official" package. |
Haha. Thanks @lox. I will use your fork for the time being. |
@lox Thanks for taking this burden on you... as long as composer is so incredibly "unsafe" to use. |
👍 to @lox for being so logical unlike some. |
what changes do i need to make to config.yaml to use lox's fork? |
Unfortunately puphet uses regular git clone instead composer. See here: https://github.com/puphpet/puppet-puphpet/blob/049e28a9c4232b30d8ed957eb980889f7ad08646/manifests/php/xhprof.pp#L15 You can change source link in |
Probably would be better if @jtreminio can change it or somebody could make an 'official' updated puphpet fork for the time being. This situation with composer is still ridiculous... |
Thanks. I'll just do manual installs for now until jtreminio fixes puphpet. |
I still have this error even after editing the source link of xhprof with fork repo and recreating the vm with vagrant up. Did I miss something ? Does this work wit php-fpm 5.6 or only with php-fpm 5.5 ? ==> default: Notice: /Stage[main]/Puphpet::Php::Xhprof/Exec[configure xhprof]/returns: executed successfully |
Same happens to me. |
Fixed in #1411 |
During provisioning, the following error(s) occur. I have no idea what the root cause could be. The thing that gives me headaches is that it seems to install Xhprof just fine, but then fails on ... something. Note, that I had to add the following to my
Vagrantfile
to prevent thefacter fqdn
not found error:Here's the full error incl. trace.
The contents of the
config.yaml
:The text was updated successfully, but these errors were encountered: