^^10 killing backend of site

If you are having this problem here is a temporary fix:

Find the key_value_expire table in your database.
Find the record WHERE the collection field = 'update_available_releases' AND the name field = 'at_tool'
Download the blob data and change "^^" to "^"
Update the blob data in the database.

You should be ok then, until the next time cron runs ..

Getting error when tring to enable the latest version.
Drupal\Core\Extension\InfoParserException: The 'core_version_requirement' constraint (^^10 || ^11) is not a valid value in modules/contrib/at_tool/at_tool.info.yml in Drupal\Core\Extension\InfoParserDynamic->parse() (line 77 of /var/www/html/diet/vb1020/web/core/lib/Drupal/Core/Extension/InfoParserDynamic.php).

Gautam_105@ → made their first commit to this issue’s fork.

Gautam_105@ → changed the visibility of the branch 3441631-10-killing-backend to hidden.

@roblog and @dineshkumarbollu , i have tested the abive patch it working fine and i have created MR for the same.

@dineshkumarbollu I have version 2.0.5 installed and the info.yml file reads like this:

core_version_requirement: ^9.3 || ^10

I'm not really sure what is going on but I do not think the problem is coming from the code that is on my site, but from some code or configuration on this (Drupal.org) site.

If I fix the problem in my database, the site runs fine, until next time cron runs, or I visit the Updates report in the back end of the site. At this point it updates the key_value_expire table again with the dodgy ^^ record, which causes the site to break again. (I basically cannot load any /admin* page on the site whilst the problem exists in the database).

If you look at the main project page for the module ( https://www.drupal.org/project/at_tool → ), under the 3.0.0 Releases section it says:

"Works with Drupal: ^^10 || ^11"

I think this is the cause of the problem, although I couldn't say if this is coming from your code, or a misconfiguration on the Drupal site. It seems that when cron runs (or I visit the Updates page) on my site, it is harvesting data on module availability from Drupal.org and storing it in the database, but because there is the ^^ error on the Drupal.org site it is getting transposed to module users.

This has been fixed.

@mattbloomfield Thanks I confirm that I can now access the Updates report on the back end of the site, and also run cron, without the database becoming corrupted. Thanks for rapid response.

I am having the same issue with the 2.0.5 version of at_tool. Is there a patch for that version as well?

Note that my at_tool.info.yml is looking the same as in the patch but I still get the error.

Taking into account roblog's comments, I temporarily(??) fixed it with the following SQL on my database:

UPDATE key_value_expire SET value = REPLACE(value, '^^', '^') WHERE collection = 'update_available_releases' AND name = 'at_tool';

I was having the same issue on all my D9 sites using at_tool 2.0.5.

I am finding that reinstalling at_tool 2.0.5 is resolving the error messages. Running cron and clearing caches before reinstalling didn't resolve the error messages for me. So far, reinstalling is working.

I'm not sure why. The ^^10 error was not in at_tool 2.0.5, only in at_tool 3.0.0.

Many thanks to @roblog for reporting the issue, to @dineshkumarbollu for creating a patch, and to @mattbloomfield for fixing the issue.

On my production site I had to disable the "update" module to regain access to the admin pages.

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