Closed (fixed)
Project:
Legal
Version:
3.0.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
1 Sep 2024 at 20:04 UTC
Updated:
21 Jan 2026 at 17:11 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #3
john franklin commentedThere is one test failing in the pipelines. The same test fails in other recent MRs.
Comment #5
john franklin commentedThe "test-pipelines" MR is 3.0.x, minus the LICENSE.txt file. The unit tests fail in exactly the same way when running against 3.0.x as they do the fix-phpcs-issues MR, so I consider the MR to be valid.
Comment #6
riddhi.addweb commentedI tried to apply both MR [22, 23] and it applied cleanly, but still, the errors are displayed. Still, PHPCS errors are there and not resolved. Attaching the SS for the same.
Comment #8
john franklin commentedMR 22 is the correct one. I've hidden 23 and deleted the branch from git. MR 22 passed PHPCS in the pipelines. I'll rerun it and see what comes back.
Edit: Gitlab won't allow me to delete the MR 23 branch.
Comment #10
kul.pratap commentedWorking on it.
Comment #11
kul.pratap commentedPipeline passed with no warning and errors.
Comment #12
john franklin commentedThanks for the updates @kul.pratap. A completely green pipeline is a lovely thing to see! I updated the cspell handling to inject unknown words in the `.gitlab-ci.yml` file instead of recreating the whole .cspell.json file, and backported the changes to the 3.x branch.
@robert castelo, there are two MRs attached here:
MR 22 - Applies updates to fix the "validate" class of tests in the pipeline for 3.0.x. This is as close as we're going to get to green until that last phpunit test is fixed in 3.0.x.
MR-24 - Applies updates to fix the "validate" class of tests in the pipeline for 4.0.x. This brings the pipeline to full green.
I don't think it's appropriate for me to RTBC this as I'm one of the people contributing the fixes. @riddhi.addweb, can you check on 3.x or 4.x?
Comment #13
arunsahijpal commentedGreat Work @kul.pratap and @john-franklin,
I've tested MR!22 and MR!24 on my local and phpcs doesn't reports any error, and phpcs is passing in the pipeline too!
Hence moving it to RTBC.
Comment #14
john franklin commented@robert-castelo, can you review and merge these two MRs, one each for the 3.x and 4.x branches, please?
Comment #15
orkutmuratyilmazany chance for merge?
Comment #18
robert castelo commentedComment #19
robert castelo commentedWhy is "behaviour" (UK spelling) being changed to "behavior" (US spelling)?
Not going to hold up merging, but feel like both should be allowed.
Comment #21
robert castelo commentedComment #22
orkutmuratyilmaz@robert castelo thank you:)
Comment #24
john franklin commentedBecause Drupal uses American spelling rules. It does feel rather arbitrary.
Comment #25
mxh commentedThe commit into 3.0.x breaks the admin settings form. Was AI used to produce this "cleanup"?
https://git.drupalcode.org/project/legal/-/blame/3.0.x/src/Form/LegalAdm...
- "entity_type.manage" does not exist as a service (typo)
- "role" entity type does not exist. Correct entity type ID is "user_role".
Such changes should have at least been manually tested one time before setting RTBC.