Problem/Motivation

Hello project maintainers,

This is an automated issue to help make this module compatible with Drupal 10.

To read more about this effort by the Drupal Association, please read: The project update bot is being refreshed to support Drupal 10 readiness of contributed projects

Patches will periodically be added to this issue that remove Drupal 10 deprecated API uses. To stop further patches from being posted, change the status to anything other than Active, Needs review, Needs work or Reviewed and tested by the community. Alternatively, you can remove the "ProjectUpdateBotD10" tag from the issue to stop the bot from posting updates.

The patches will be posted by the Project Update Bot official user account. This account will not receive any issue credit contributions for itself or any company.

Proposed resolution

You have a few options for how to use this issue:

  1. Accept automated patches until this issue is closed

    If this issue is left open (status of Active, Needs review, Needs work or Reviewed and tested by the community) and the "ProjectUpdateBotD10" tag is left on this issue, new patches will be posted periodically if new deprecation fixes are needed.

    As the Drupal Rector project improves and is able to fix more deprecated API uses, the patches posted here will cover more of the deprecated API uses in the module.

    Patches and/or merge requests posted by others are ignored by the bot, and general human interactions in the issue do not stop the bot from posting updates, so feel free to use this issue to refine bot patches. The bot will still post new patches then if there is a change in the new generated patch compared to the patch that the bot posted last. Those changes are then up to humans to integrate.

  2. Leave open but stop new automated patches.

    If you want to use this issue as a starting point to remove deprecated API uses but then don't want new automated patches, remove the "ProjectUpdateBotD10" tag from the issue and use it like any other issue (the status does not matter then). If you want to receive automated patches again, add back the "ProjectUpdateBotD10" tag.

  3. Close it and don't use it

    If the maintainers of this project don't find this issue useful, they can close this issue (any status besides Active, Needs review, Needs work and Reviewed and tested by the community) and no more automated patches will be posted here.

    If the issue is reopened, then new automated patches will be posted.

    If you are using another issue(s) to work on Drupal 10 compatibility it would be very useful to other contributors to add those issues as "Related issues" when closing this issue.

Remaining tasks

Using the patches

  1. Apply the latest patch in the comments by Project Update Bot or human contributors that made it better.
  2. Thoroughly test the patch. These patches are automatically generated so they haven't been tested manually or automatically.
  3. Provide feedback about how the testing went. If you can improve the patch, post an updated patch here.

Providing feedback

If there are problems with one of the patches posted by the Project Update Bot, such as it does not correctly replace a deprecation, you can file an issue in the Drupal Rector issue queue. For other issues with the bot, for instance if the issue summary created by the bot is unclear, use the Project analysis issue queue.

Issue fork rollbar-3289422

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:

Comments

Project Update Bot created an issue. See original summary.

project update bot’s picture

Status: Active » Needs review
StatusFileSize
new639 bytes

This is an automated patch generated by Drupal Rector. Please see the issue summary for more details.

It is important that any automated tests available are run with this patch and that you manually test this patch.

Drupal 10 Compatibility

According to the Upgrade Status module this patch makes this module compatible with Drupal 10! 🎉
This patch updates the info.yml file for Drupal 10 compatibility.

Leaving this issue open, even after committing the current patch, will allow the Project Update Bot to post additional Drupal 10 compatibility fixes as they become available in Drupal Rector.

Debug info

Bot run #127

This patch was created using these packages:

  1. mglaman/phpstan-drupal: 1.1.9
  2. palantirnet/drupal-rector: 0.12.0
pavel.bulat’s picture

Issue summary: View changes
Issue tags: +Drupal 10 porting day

Tested the patch. Couldn't install the module to Drupal 10.
Currently, Drupal 10 has dependency on psr/log package ver 3 and rollbar/rollbar package should be updated to use the same version: Once the issue is fixed (https://github.com/rollbar/rollbar-php/issues/570) the module will be compatible with Drupal 10

kristen pol’s picture

Sounds like this is postponed based on #3 but we don't want to mark postponed in case the bot has more patches. I guess leaving as Needs review is okay but it shouldn't be tested again. Just need to continue to check the status of the issue. It's currently still open.

mmjvb’s picture

This shouldn't be postponed based on #3. It should be committed asap and set to Active or Fixed as per maintainer desire.

The release of a D10 compatible version of this module could be postponed as it can't be installed due to version constraints on par/log.

No idea how realistic these constraints are, only drush (consolidation/log) and core seem to insist on ^3.

docker@d10a5:/var/www$ composer depends psr/log
chi-teck/drupal-code-generator  2.5.3        requires psr/log (^1.1 || ^2.0 || ^3.0)
consolidation/annotated-command 4.5.6        requires psr/log (^1|^2|^3)
consolidation/log               2.x-dev      requires psr/log (^3)
drupal/core                     10.0.0-beta1 requires psr/log (^3.0)
grasmash/expander               2.0.3        requires psr/log (^1 | ^2 | ^3)
symfony/error-handler           v6.1.3       requires psr/log (^1|^2|^3)
symfony/http-kernel             v6.1.4       requires psr/log (^1|^2|^3)
docker@d10a5:/var/www$

Turns out core is the problem. For installation to succeed you need an inline alias for psr/log:

docker@d10a5:/var/www$ composer require drupal/rollbar
Using version ^2.0 for drupal/rollbar
./composer.json has been updated
Running composer update drupal/rollbar
Loading composer repositories with package information
Updating dependencies
Lock file operations: 3 installs, 0 updates, 0 removals
  - Locking drupal/rollbar (2.0.1)
  - Locking monolog/monolog (2.8.0)
  - Locking rollbar/rollbar (v3.1.3)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 3 installs, 0 updates, 0 removals
  - Downloading monolog/monolog (2.8.0)
  - Downloading rollbar/rollbar (v3.1.3)
  - Downloading drupal/rollbar (2.0.1)
  - Installing monolog/monolog (2.8.0): Extracting archive
  - Installing rollbar/rollbar (v3.1.3): Extracting archive
  - Installing drupal/rollbar (2.0.1): Extracting archive
10 package suggestions were added by new dependencies, use `composer suggest` to see details.
Package webmozart/path-util is abandoned, you should avoid using it. Use symfony/filesystem instead.
Generating autoload files
41 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
Found 1 security vulnerability advisory affecting 1 package.
Run composer audit for a full list of advisories.
docker@d10a5:/var/www$
kristen pol’s picture

Since it couldn’t be tested before, then I wouldn’t suggest committing the changes based on that. But, it looks like you figured out a way to install so it can be tested. Thanks!

project update bot’s picture

elaman made their first commit to this issue’s fork.

keshavv’s picture

Issue summary: View changes
Status: Needs review » Reviewed & tested by the community
StatusFileSize
new59.92 KB

Screenshot
I have tested the MR and confirmed that it is working perfectly in Drupal 10.
I also checked the code deprecation. So there is no deprecation.
We can go with it.
Thank you.

elaman’s picture

Version: 2.x-dev » 2.0.x-dev
spleshka’s picture

Title: Automated Drupal 10 compatibility fixes » Drupal 10 compatibility fixes

Thanks Elaman, great job. Tested on our website, works well.

intrafusion’s picture

Status: Reviewed & tested by the community » Fixed
spleshka’s picture

Thank you so much @intrafusion for such quick action! Would you be so kind to create a new release for the version supporting Drupal 10 please?

intrafusion’s picture

The change to the function signature in this issue actually breaks backwards compatibility as per #3379795: Rollbar is not compatible with Drupal 10 again

dagmar’s picture

@intrafusion I created issue #3379795 with the intention of not committing it. If you apply my fix the module won't be compatible with D10. This is why I mentioned it is something hard to fix, you can't be compatible with the 2 PSR3 signatures at the same time.

intrafusion’s picture

New release 2.1.0 which is for Drupal 10 only

Status: Fixed » Closed (fixed)

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