🇪🇸Spain @marthinal

Reroll

I have this error when updating Drupal core:

>  [notice] Update started: system_post_update_add_langcode_to_all_translatable_config
>  [notice] Processed 50 items of 1278.
>  [notice] Processed 100 items of 1278.
>  [notice] Processed 150 items of 1278.
>  [notice] Processed 200 items of 1278.
>  [notice] Processed 250 items of 1278.
>  [notice] Processed 300 items of 1278.
>  [notice] Processed 350 items of 1278.
>  [notice] Processed 400 items of 1278.
>  [notice] Processed 450 items of 1278.
>  [notice] Processed 500 items of 1278.
>  [notice] Processed 550 items of 1278.
>  [notice] Processed 600 items of 1278.
>  [notice] Processed 650 items of 1278.
>  [notice] Processed 700 items of 1278.
>  [notice] Processed 750 items of 1278.
>  [error]  AssertionError: assert($typed_config instanceof Mapping) in assert() (line 264 of /var/www/html/docroot/core/modules/system/system.post_update.php) #0 /var/www/html/docroot/core/modules/system/system.post_update.php(264): assert(false, 'assert($typed_c...')

I updated the schema + implemented hook_update_N

We have to use addClass method

Rerolled

Thanks for reviewing @jwilson3. Okay, in that case we can try something like this.

Duplicate https://www.drupal.org/project/swiftmailer/issues/3359916 💬 Conflicts with drupal/core-recommended 10.1.x-dev requires egulias/email-validator ~4.0.1 Active

And here is the patch

marthinal → created an issue.

Thanks @rodetrev. We also found some regressions. Your patch looks correct. Re-rolled. Needs more QA

Re-rolled

Rerolled

Hey I found some regressions

Hey @jwilson3, I found a regression

I found one more problem

Thanks @jwilson3. Fixing more errors!

#4 does not apply anymore. Refactored.

It works. Thanks @seanB

I have the same issue

$ ddev composer show -a drupal/fullcalendar_view
name     : drupal/fullcalendar_view
descrip. : This is a lightweight View plugin module that provides a calendar view format powered by FullCalendar JavaScript.
keywords : Drupal, fullcalendar_view
versions : 6.x-dev, 5.x-dev, * 5.1.11, 5.1.10, 5.1.9, 5.1.8, 5.1.7, 5.1.6, 5.1.5, 5.1.4, 5.1.3, 5.1.2, 5.1.1, 5.1.0, 5.0.8, 5.0.7, 5.0.6, 5.0.5, 5.0.4, 5.0.3, 5.0.2, 5.0.1, 5.0.0, 4.5.0, 4.4.0, 4.3.0, 4.2.0, 4.1.0, 4.0.0, 3.x-dev, 2.x-dev, 2.8.0, 2.7.0, 2.6.0, 2.5.0, 2.4.0, 2.3.0, 2.2.0, 2.1.0, 2.0.0, 2.0.0-rc10, 2.0.0-rc9, 2.0.0-rc8, 2.0.0-rc7, 2.0.0-rc6, 2.0.0-rc5, 2.0.0-rc4, 2.0.0-rc3, 2.0.0-rc2, 2.0.0-rc1, 1.x-dev, 1.0.0-rc3, 1.0.0-rc2, 1.0.0-rc1, 1.0.0-beta2, 1.0.0-beta1, 1.0.0-alpha10, 1.0.0-alpha7, 1.0.0-alpha6, 1.0.0-alpha5, 1.0.0-alpha4, 1.0.0-alpha3, 1.0.0-alpha2, 1.0.0-alpha1, dev-6.x, dev-5.x, dev-3.x, dev-2.x, dev-1.x
type     : drupal-module
license  : GNU General Public License v2.0 or later (GPL-2.0+) (OSI approved) https://spdx.org/licenses/GPL-2.0+.html#licenseText
homepage : http://drupal.org/project/fullcalendar_view
source   : [git] https://git.drupalcode.org/project/fullcalendar_view.git 5.1.11
dist     : [zip] https://ftp.drupal.org/files/projects/fullcalendar_view-5.1.11.zip 5.1.11
path     : /var/www/html/web/modules/contrib/fullcalendar_view
names    : drupal/fullcalendar_view

support
source : http://cgit.drupalcode.org/fullcalendar_view
issues : http://drupal.org/project/issues/fullcalendar_view

requires
drupal/core ^9.2.0 || ^10

Yep, same issue from backend.

We can reproduce this issue by updating the main menu (/admin/structure/menu/manage/main). The only change in the DB is that menu_update_flag is 1.

And we are saving it again from template_preprocess_we_megamenu_frontend()

    if(isset($data_config->menu_update_flag) && $data_config->menu_update_flag)  {
      // drupal_flush_all_caches();
      $theme_name = $block_theme;
      $menu_items = WeMegaMenuBuilder::getMenuTreeOrder($menu_name, FALSE);
      WeMegaMenuBuilder::updateMegamenuFromDrupalMenu($data_config, $menu_items, 0);
      $data_config->menu_update_flag = 0;
      WeMegaMenuBuilder::saveConfig($menu_name, $theme_name, json_encode($data_config));
      // drupal_flush_all_caches();      
    }

I think 110c5e22 is the commit where the bug was introduced.