[wp-meta] [Making WordPress.org] #7662: Long Trac queries showing 403 error

[Making WordPress.org]

#7662: Long Trac queries showing 403 error
-----------------------------+---------------------
 Reporter:  desrosj          |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:
Component:  Trac             |  Resolution:
 Keywords:  pending-systems  |
-----------------------------+---------------------
Changes (by dd32):

 * keywords:   => pending-systems


Comment:

 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

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/7662#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org