When I try to run the following Drupal Console command:

$ drupal webprofiler:benchmark "http://my-drupal8-site"

the following Symfony (fatal) error comes out ...

104/104 [============================] 100% Compute GIT hash...PHP Fatal error:  Call to undefined method Symfony\Component\Yaml\Inline::isHash() in /Users/italo/Sites/ddd-forms-talk/vendor/symfony/yaml/Dumper.php on line 61
PHP Stack trace:
PHP   1. {main}() /usr/local/bin/drupal:0
PHP   2. require() /usr/local/bin/drupal:10
PHP   3. require() phar:///usr/local/bin/drupal/bin/drupal:3
etc. … (omissis)

Comments

itamair created an issue. See original summary.

Eyal Shalev’s picture

Eyal Shalev
he/him
CreditAttribution: Eyal Shalev as a volunteer commented

I don't think that this has any relation to the devel module.

I suggest to move it to the drupal console project page.

lussoluca’s picture

lussoluca
he/him
Primary language Italian
Location Italy
CreditAttribution: lussoluca at H2H Creative Productions commented

web profiler:benchmark is a Drupal Console command defined in Webprofiler so this is most probably a Devel issue.

Eyal Shalev’s picture

Eyal Shalev
he/him
CreditAttribution: Eyal Shalev as a volunteer commented

I'm having the same issue without the above module.

For some unknown reason the symfony code in the local vendor directory is mixed up with the symfony code of the composer phar file.

I resolved this issue by adding drupal/composer to the dev dependencies of my project and used that executable instead.

clint.beacock’s picture

clint.beacock CreditAttribution: clint.beacock as a volunteer and at Therefore commented

I'm having this same error. In my case, it's happening when I run drupal site:mode dev

In my case, I think it's a core version issue of some sort. I just upgraded to 8.1 from 8.0, and this is when it started happening.

lussoluca’s picture

lussoluca
he/him
Primary language Italian
Location Italy
CreditAttribution: lussoluca at H2H Creative Productions commented
Status: Active » Closed (cannot reproduce)

I cannot reproduce this error, but at this point I don't think that this is caused by web profiler or devel