The Needs Review Queue Bot → tested this issue. It either no longer applies to Drupal core, or fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".
Apart from a re-roll or rebase, this issue may need more work to address feedback in the issue or MR comments. To progress an issue, incorporate this feedback as part of the process of updating the issue. This helps other contributors to know what is outstanding.
Consult the Drupal Contributor Guide → to find step-by-step guides for working with issues.
- 🇺🇸United States douggreen Winchester, VA
Attached patch fixes issue raised by the bot. It also cleans up the comment a tad.
* The both complained about the
isset()
which was introduced in #28, I've replace it with a simple condition because IMO neitherisset()
nor!empty
is necessary here. - Status changed to Needs review
about 1 year ago 1:57pm 23 June 2023 - last update
about 1 year ago 29,551 pass, 2 fail The last submitted patch, 40: 3143617-40.patch, failed testing. View results →
- Status changed to Needs work
about 1 year ago 10:33pm 23 June 2023 - 🇺🇸United States neclimdul Houston, TX
Its been 3 years so its hard to remember but pretty sure the isset was the to preserve the behavior of the empty check as demonstrated by the failing tests. What was the problem with it?
- 🇮🇹Italy robertom
Attached patch fixes issues
Symfony\Component\HttpFoundation\Exception\BadRequestException: Input value "page" contains a non-scalar value.
raised by the test bot
- Status changed to Needs review
7 months ago 11:08pm 4 December 2023 - last update
7 months ago Build Successful - Status changed to Needs work
7 months ago 11:27pm 4 December 2023 The Needs Review Queue Bot → tested this issue.
While you are making the above changes, we recommend that you convert this patch to a merge request → . Merge requests are preferred over patches. Be sure to hide the old patch files as well. (Converting an issue to a merge request without other contributions to the issue will not receive credit.)
- Status changed to Needs review
7 months ago 12:00am 5 December 2023 - 🇮🇹Italy robertom
Attached a patch without the use of ->all()['page'] for avoid warning like
Undefined array key "page"
- Status changed to Needs work
7 months ago 2:12pm 5 December 2023 - 🇺🇸United States smustgrave
Issue summary should be updated to the standard issue template, even if sections don't apply leaving them with NA is easier for reviews/committers.
- Status changed to Needs review
7 months ago 2:49pm 5 December 2023 - 🇺🇸United States neclimdul Houston, TX
Updated.
Turns out its been long enough a few things have changed. Specifically, current versions of PHP throw an exception instead of a warning which makes it a bit harder to see. Specifically, real exception gets gobbled up by a more generic exception and Drupal's exception logging in watchdog doesn't show previous exceptions.
Since the actual exception is hidden and its hard to validate the root cause without hacking the exception handler or using a debugger, I've left the original trace in place. The fix is the same and the trace captures the essence of the problem.
- last update
7 months ago 30,688 pass, 1 fail - Status changed to Needs work
7 months ago 5:26pm 5 December 2023 - 🇺🇸United States smustgrave
Ran patch #47 and it has a test failure that seems legit.
Recommended to convert to MRs
- 🇺🇸United States neclimdul Houston, TX
"pretty sure the isset was the to preserve the behavior of the empty check as demonstrated by the failing tests." 🤷
Added it back because it was there to defensively handle a null value from the getPagerParameter method. Since isset is a language level feature there's no real cost to being defensive like this.
I'm already tired of the 500 remotes and all the commit juggling. I'm going to really miss the simple patch workflow. But ok, its in a MR now.
- 🇺🇸United States neclimdul Houston, TX
Turns around it was a little more complicated. I went ahead and took the opportunity to update the tests and make things a little more clear.
- Status changed to Needs review
7 months ago 3:22pm 6 December 2023 - Status changed to RTBC
7 months ago 7:30pm 6 December 2023 - last update
7 months ago 30,696 pass, 2 fail - last update
7 months ago 30,698 pass, 2 fail - last update
7 months ago 30,698 pass, 2 fail - last update
6 months ago 30,712 pass, 2 fail - last update
6 months ago 30,726 pass, 2 fail - last update
6 months ago 30,766 pass, 2 fail - last update
6 months ago 25,905 pass, 1,817 fail - last update
6 months ago 25,884 pass, 1,814 fail - last update
6 months ago 25,945 pass, 1,825 fail - last update
6 months ago 25,909 pass, 1,807 fail - last update
6 months ago 25,914 pass, 1,799 fail - Status changed to Needs work
6 months ago 3:28am 28 December 2023 - 🇳🇿New Zealand quietone New Zealand
I'm triaging RTBC issues → . I read the IS, the comments and the MR.
Thanks for updating the Issue Summary, that is always helpful! The review in #28 by @neclimdul was also useful as it explained what they were thinking and checking. That provided me with insight into understanding the issue and when else I may need to check.
The changes to getPagerQuery and getPagerParameter are changing the behavior, making it conform to the interface. So, it there any ramification for contrib/custom?
I left suggestions in the MR for coding standards and one asking for documentation.
I hide all the patches.
- last update
5 months ago Build Successful