This is here more as a PSA than a request for fix.
I was testing the Drupal Automatic Updates module on one of my sites and ran into an interesting bug where "if" a module has conflicts with the signature file and errors out, backdrop_upgrade_status will cause the site to go into a batch update loop, rendering the site unusable.
I bring this up as a PSA because the conflicting module in question was the "Fences" module specifically the latest 2.x-beta version.
automatic_updates chokes when trying to figure out the status of Fences, and that causes BUS to choke.
It's literally a perfect storm of modules, however it's pretty nasty when it happens.
"If" we had a way to collect the module usage statistics of BUS we could see how many sites are using both automatic_updates and fences to determine how badly we need to focus on a fix.
This is here more as a PSA than a request for fix.
I was testing the Drupal Automatic Updates module on one of my sites and ran into an interesting bug where "if" a module has conflicts with the signature file and errors out, backdrop_upgrade_status will cause the site to go into a batch update loop, rendering the site unusable.
I bring this up as a PSA because the conflicting module in question was the "Fences" module specifically the latest 2.x-beta version.
automatic_updates chokes when trying to figure out the status of Fences, and that causes BUS to choke.
It's literally a perfect storm of modules, however it's pretty nasty when it happens.
"If" we had a way to collect the module usage statistics of BUS we could see how many sites are using both automatic_updates and fences to determine how badly we need to focus on a fix.
+1 for https://github.com/backdrop-contrib/backdrop_upgrade_status/issues/6 ;-)