Problem/Motivation
Closures now displays its source location, see merged PR
Steps to reproduce
Run tests using PHP 8.4
Proposed resolution
Update tests to use separate representation for closures for PHP 8.4
Remaining tasks
- review
- commit
User interface changes
Introduced terminology
API changes
Data model changes
Release notes snippet
| Comment | File | Size | Author |
|---|---|---|---|
| #25 | 3477366-nr-bot.txt | 90 bytes | needs-review-queue-bot |
Issue fork drupal-3477366
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
Comment #3
andypostComment #4
andypostComment #5
smustgrave commentedNeat trick for BC.
Reviewing the change and conditions for 8.4 make sense.
Comment #7
longwaveCommitted 97775e7 and pushed to 11.x. Thanks!
MR doesn't apply to 10.4, moving there for backport.
Comment #8
andypostRe-rolled and adjusted line numbers
Comment #10
andypostMR https://git.drupalcode.org/project/drupal/-/merge_requests/9772
Comment #12
smustgrave commentedSeems backport has test failures.
Will keep an eye out
Comment #13
andypostIt was pod's scheduling issue so retried
EntityReferenceWidgetTest- guess random failureComment #14
smustgrave commentedAppears all green now
Comment #15
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #16
andypostsome bot's error but rebased
Comment #17
andypostsomehow tests fail for 10.4 as branch tests are not green
Comment #18
andypostproper rebase
Comment #19
andypostnow it's 10.5/10.4
Comment #20
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #21
andypostfalse positive
Comment #22
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #24
andypostMR opened for 10.5 for bot as patch applicable
Comment #25
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #26
longwaveI am not sure the bot looks at the MR base or issue version, maybe it only tries to apply patches to 11.x.
Comment #27
longwavePatch is identical to 11.x version except for the line numbers in error messages.
Committed and pushed 4b3308017f0 to 10.5.x and 7fda601bd78 to 10.4.x. Thanks!
Comment #30
andypostThank you! only 2 blockers now left!