Making WordPress.org

Opened 6 weeks ago

Closed 5 weeks ago

#7662 closed defect (bug) (fixed)

Long Trac queries showing 403 error

Reported by: desrosj's profile desrosj Owned by:
Milestone: Priority: normal
Component: Trac Keywords: pending-systems
Cc:

Description

It seems that long queries in Trac are being blocked from displaying.

I discovered this when clicking on the links in the "0 Replies" column on the Core Components page, which links to a query for open tickets within the component and a static list of ticket IDs.

The failures seem to begin around the 65 ticket mark. For example, the Taxonomy component has 56 tickets at the time of creating this ticket and the report works, but the Users component has 68 and shows the 403 error.

Change History (4)

#1 @desrosj
6 weeks ago

I'm guessing this is an upper limit put in place to prevent abuse.

It would be nice to link to a report containing all 0 reply tickets for a given component more easily without the need to include ticket IDs. That would probably solve this issue and make have the added benefit of being dynamic instead of static based on the query. But I'm not sure how feasible that is.

#2 @dd32
6 weeks ago

  • Keywords pending-systems added

I've passed this onto Systems: https://make.wordpress.org/systems/2024/05/31/increase-query-params-length-for-trac/

I expect systems will make a change to resolve the trac report.

It would be nice to link to a report containing all 0 reply tickets for a given component more easily without the need to include ticket IDs. That would probably solve this issue and make have the added benefit of being dynamic instead of static based on the query. But I'm not sure how feasible that is.

I agree, I think it'd be possible, but there's a report for noreply-tickets which appears to have been disabled: https://core.trac.wordpress.org/report/41 so I'm guessing the reason that this is using an ID query is that querying for tickets with no replies in Trac is not performant..

I've tried to resurect that report, and it is indeed slow when querying for a specific component, so querying all components probably wouldn't have been great.

I've added a new report, 66, which is minimal and seems to be more performant.. in my testing..
It pulls up tickets in a component with no comments from the reporter or any user named '%bot', I didn't add any workflow stuff, can you play with that @desrosj?

Eg; https://core.trac.wordpress.org/report/66?COMPONENT=Users

#3 @dd32
6 weeks ago

There's a pretty slow no-replies report on meta.trac too.. https://meta.trac.wordpress.org/report/18

#4 @dd32
5 weeks ago

  • Resolution set to fixed
  • Status changed from new to closed

Systems have made some adjustments which appears to result in these links now being operational.

Note: See TracTickets for help on using tickets.