Missing schema for fields and filters on views with aggregation

Steps to reproduce with Drupal core were asked for 2 years ago and haven't been supplied. Also, a view maintainer has not been able to reproduce the problem. Steps to reproduce were again asked for 9 months ago.

Since that hasn't been supplied I am closing this issue.

If you are experiencing this problem on a supported version of Drupal reopen the issue, by setting the status to 'Active', and provide complete steps to reproduce the issue → (starting from "Install Drupal core").

Still can’t replicate. If you are going to reopen could you update the steps to reproduce please.

Steps to reproduce has been update. Please check first post or https://www.drupal.org/node/3263208/revisions →

Re-roll for 10.3.3

Added MR, as expected the "test only" pipeline failed due to schema errors, otherwise the fix passes.

This is holding up a recipe for Drupal CMS that cannot pass tests until this is fixed, so hoping this can be reviewed ASAP.

Hello,
Still can’t replicate.
Need clear steps to reproduce the issue.

The steps work to replicate, but since there is an MR with a "test only" fail, they are less important now. If you really want to see it, import this view into a test site. https://git.drupalcode.org/project/drupal/-/blob/2bd05246e8bba0ff72332b0...

Aggregating with a COUNT on any entity ID (a user ID, in that example) will create a missing schema error. Look at the artifacts from the MR tests. It's right there.

Here is the "test only" run showing the missing schema errors when the test view (a simple view of users with a COUNT on user ID) is installed into a site without the accompanying schema fixes: https://git.drupalcode.org/issue/drupal-3263208/-/jobs/3498941

Left some comments and questions on the MR.

Updated the MR with a post update hook and accompanying test to ensure the hook works. Back to ready for review.

Believe feedback on this one has been addressed! Nice!

Bump

This is holding up the Events recipe for Drupal CMS that cannot pass tests until this is fixed, so hoping this can be committed ASAP.

I found one wee doc error in the MR and used the suggestion feature to fix that.

The proposed resolution should describe the change so that a reviewer/committers know what to expect in the MR.

I am among the many here, include the views maintainer, that are not able to reproduce this issue. The steps to reproduce is missing the step to install config_inspector and the link to view the report is a 404 for me. Is there other steps missing? I imported the view from #32 🐛 Missing schema for fields and filters on views with aggregation Needs work which is supposed to include the error and again, there are no errors with the config inspector.

Since this is important to Drupal CMS is there a tag to use? There is one for 'Drupal CMS release target' but I can't find an issue for the Drupal CMS release plan.

I've updated credit and leaving at RTBC due to the connection to Drupal CMS.

@quietone, are you saying you cannot view the "test-only" output here? https://git.drupalcode.org/issue/drupal-3263208/-/jobs/3498941

You don't need to reproduce the issue. The "test-only" run reproduces it for you, lines 48-54 of that job output. That's what it's there for.

@john.oltman, I am saying that the 'steps to reproduce' in the issue summary are not complete. If I start from a fresh install of Drupal and then follow those steps, then the link in step 4 is a 404. With config_inspector installed that link is still a 404. I also tried to reproduce from a fresh install of Umami, with the same results.

I do hold that is important to be able to reproduce an issue as well as have a test, both have their place and value.

@quietone, this is ready for another look - the steps to reproduce have been fixed, with two new screenshots. Thanks for your feedback!

This might have been a Drupal CMS blocker at one point but it no longer is, and certainly not for the Events recipe. Untagging!

I should have been more clear. It is the Events Registration recipe that is blocked.

https://www.drupal.org/project/events_registration →

Retagging.

Putting in needs work because the passage of time has caused the MR to become stale and have an error.