With Drupal 11.2 you get such errors:
[warning] Schema errors for prometheus_exporter.settings with the following errors: prometheus_exporter.settings:collectors.node_count.settings.bundles missing schema, prometheus_exporter.settings:collectors.revision_count.settings.bundles missing schema. These errors mean there is configuration that does not comply with its schema.

Issue fork prometheus_exporter-3544374

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

mkalkbrenner created an issue. See original summary.

mkalkbrenner opened merge request !16

mkalkbrenner’s picture

mkalkbrenner
Primary language German
Location 🇩🇪
commented
Status: Active » Needs review
sandeep_k’s picture

sandeep_k commented

I attempted to reproduce this issue on my Drupal version 11.2, but was unable to do so. Please let me know if I may have missed any additional steps.

mkalkbrenner’s picture

mkalkbrenner
Primary language German
Location 🇩🇪
commented

Drupal 11.2 offers the ConfigSchemaChecker in the development services. if activated, you'll get these warnings.

  logger.channel.config_schema:
    parent: logger.channel_base
    arguments: [ 'config_schema' ]
  config.schema_checker:
    class: Drupal\Core\Config\Development\LenientConfigSchemaChecker
    arguments:
      - '@config.typed'
      - '@messenger'
      - '@logger.channel.config_schema'
    tags:
      - { name: event_subscriber }

kim.pepper made their first commit to this issue’s fork.

kim.pepper’s picture

kim.pepper
Primary language English
Location 🏄‍♂️🇦🇺Sydney, Australia
commented
Status: Needs review » Fixed

Committed to 2.x

There is currently a bug and I can't save contribution records, but I will come back and add them when it's fixed.

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

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