Modify ↓
Opened 7 years ago
Closed 6 years ago
#13124 closed defect (worksforme)
TicketQuery fails
| Reported by: | anonymous | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | ticket system | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description (last modified by )
[[TicketQuery(keywords~=java,keywords!~=javascript)]] fails with an error message: Error: Macro TicketQuery(keywords~=java,keywords!~=javascript) failed out of memory for query result
Maybe because it lists too many tickets (#9736) and runs out of memory?
Attachments (0)
Change History (3)
comment:1 by , 7 years ago
| Description: | modified (diff) |
|---|
comment:2 by , 7 years ago
comment:3 by , 6 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
The query seems to work fine in this Trac instance. There have been many improvements following the switch to Jinja2.
Unless another developer feels we need to implement a limit on the number of results returned (comment:1:ticket:13125), then I don't see anything to be done here.
Note:
See TracTickets
for help on using tickets.



The comments which uses
TicketQuerymacro has been removed in #9736.