When I attempted to install the module I received the following error:

Drupal\Component\Serialization\Exception\InvalidDataTypeException: yaml_parse(): scanning error encountered during parsing: found character that cannot start any token (line 17, column 9), context while scanning for the next token (line 17, column 9) in Drupal\Component\Serialization\YamlPecl::errorHandler()

This seems to be an issue with the drupalmoduleupgrader.services.yml file

  plugin.manager.drupalmoduleupgrader.analyzer:
    class: Drupal\Core\Plugin\DefaultPluginManager
    arguments:
      - Plugin/DMU/Analyzer
      - @container.namespaces
      - @module_handler
      - Drupal\drupalmoduleupgrader\AnalyzerInterface
      - Drupal\drupalmoduleupgrader\Annotation\Analyzer

I commented out the `@container.namespaces` line, and the error moved down to line 18, column 9 which is the @module_handler line. I am not sure if this is related or what those lines even mean. Will continue to trouble shoot this, but I did replicate it on multiple site installs.

Comments

markie created an issue. See original summary.

broon’s picture

Just wrap these arguments in quotes. Using PHPStorm, you can replace them all (Cmd+R) with a regex:

Search for: (@[a-z\._]+)(\s)
Replace with: '$1'$2

shrop’s picture

I ran into this issue, but realized I needed to run form the dev branch and it worked well from there (install).

May be a good time to release 8.x-1.3.

HongPong’s picture

This may be a duplicate of #2682185: Quote '@' characters in drupalmoduleupgrader.services.yml. As a new comaintainer for the last hour or so, I agree we should tag a new release very soon!

attheshow’s picture

Ha. Same issue here. Thanks for posting the tip about upgrading to the dev version instead of 1.2. :)

HongPong’s picture

Oh wow, yeah we should tag a new release since 2015 :/ ... if everyone can try to take a pass over the issue queue and get any other patches RTBC, I can tag a release next week.

HongPong’s picture

Status: Active » Fixed

I believe this was fixed on tagged release 1.3 . Please reopen the issue if it recurs.
https://www.drupal.org/project/drupalmoduleupgrader/releases/8.x-1.3

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.