TicketQuery Wiki Macro
The TicketQuery macro lets you display ticket information anywhere that accepts WikiFormatting.
The query language used by the [[TicketQuery]] macro is described in the TracQuery page.
Usage
[[TicketQuery]]
Wiki macro listing tickets that match certain criteria.
This macro accepts a comma-separated list of keyed parameters, in the form "key=value".
If the key is the name of a field, the value must use the syntax
of a filter specifier as defined in TracQuery#QueryLanguage.
Note that this is not the same as the simplified URL syntax
used for query: links starting with a ? character. Commas (,)
can be included in field values by escaping them with a backslash (\).
Groups of field constraints to be OR-ed together can be separated by a
literal or argument.
In addition to filters, several other named parameters can be used to control how the results are presented. All of them are optional.
The format parameter determines how the list of tickets is
presented:
- list -- the default presentation is to list the ticket ID next to the summary, with each ticket on a separate line.
- compact -- the tickets are presented as a comma-separated list of ticket IDs.
- count -- only the count of matching tickets is displayed
- rawcount -- only the count of matching tickets is displayed, not even with a link to the corresponding query (since 1.1.1)
- table -- a view similar to the custom query view (but without the controls)
- progress -- a view similar to the milestone progress bars
The max parameter can be used to limit the number of tickets shown
(defaults to 0, i.e. no maximum).
The order parameter sets the field used for ordering tickets
(defaults to id).
The desc parameter indicates whether the order of the tickets
should be reversed (defaults to false).
The group parameter sets the field used for grouping tickets
(defaults to not being set).
The groupdesc parameter indicates whether the natural display
order of the groups should be reversed (defaults to false).
The verbose parameter can be set to a true value in order to
get the description for the listed tickets. For table format only.
deprecated in favor of the rows parameter
The rows parameter can be used to specify which field(s) should
be viewed as a row, e.g. rows=description|summary
The col parameter can be used to specify which fields should
be viewed as columns. For table format only.
For compatibility with Trac 0.10, if there's a last positional parameter
given to the macro, it will be used to specify the format.
Also, using "&" as a field separator still works (except for order)
but is deprecated.
Examples
| Example | Result | Macro |
|---|---|---|
| Number of Triage tickets: | 2188 | [[TicketQuery(status=new&milestone=,count)]]
|
| Number of new tickets: | 2188 | [[TicketQuery(status=new,count)]]
|
| Number of reopened tickets: | 166 | [[TicketQuery(status=reopened,count)]]
|
| Number of assigned tickets: | 0 | [[TicketQuery(status=assigned,count)]]
|
| Number of invalid tickets: | 1711 | [[TicketQuery(status=closed,resolution=invalid,count)]]
|
| Number of worksforme tickets: | 261 | [[TicketQuery(status=closed,resolution=worksforme,count)]]
|
| Number of duplicate tickets: | 554 | [[TicketQuery(status=closed,resolution=duplicate,count)]]
|
| Number of wontfix tickets: | 274 | [[TicketQuery(status=closed,resolution=wontfix,count)]]
|
| Number of fixed tickets: | 4903 | [[TicketQuery(status=closed,resolution=fixed,count)]]
|
| Number of untriaged tickets (milestone unset): | 3040 | [[TicketQuery(status!=closed,milestone=,count)]]
|
| Total number of tickets: | 11346 | [[TicketQuery(count)]]
|
| Number of tickets reported or owned by current user: | 0 | [[TicketQuery(reporter=$USER,or,owner=$USER,count)]]
|
| Number of tickets created this month: | 36 | [[TicketQuery(created=thismonth..,count)]]
|
| Number of closed Firefox tickets: | 0 | [[TicketQuery(status=closed,keywords~=firefox,count)]]
|
| Number of closed Opera tickets: | 0 | [[TicketQuery(status=closed,keywords~=opera,count)]]
|
| Number of closed tickets affecting Firefox and Opera: | 0 | [[TicketQuery(status=closed,keywords~=firefox opera,count)]]
|
| Number of closed tickets affecting Firefox or Opera: | 0 | [[TicketQuery(status=closed,keywords~=firefox|opera,count)]]
|
| Number of tickets that affect Firefox or are closed and affect Opera: | 0 | [[TicketQuery(status=closed,keywords~=opera,or,keywords~=firefox,count)]]
|
| Number of closed Firefox tickets that don't affect Opera: | 0 | [[TicketQuery(status=closed,keywords~=firefox -opera,count)]]
|
| Last 3 modified tickets: | #11220, #11283, #11364 | [[TicketQuery(max=3,order=modified,desc=1,compact)]]
|
Details of ticket #1: |
| |
| ||
Format: list
[[TicketQuery(version=0.6|0.7&resolution=duplicate)]]
This is displayed as:
No results
[[TicketQuery(id=123)]]
This is displayed as:
- #123
- Fuzzed sample crashes ffplay
Format: compact
[[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]]
This is displayed as:
No results
Format: count
[[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]]
This is displayed as:
Format: progress
[[TicketQuery(milestone=0.12.8&group=type,format=progress)]]
This is displayed as:
defect
7230 / 9477
enhancement
1004 / 1713
task
44 / 63
license violation
11 / 72
art
13 / 15
sponsoring request
4 / 6
Format: table
You can choose the columns displayed in the table format (format=table) using col=<field>. You can specify multiple fields and the order they are displayed in by placing pipes (|) between the columns:
[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter)]]
This is displayed as:
Results (1 - 3 of 8306)
Full rows
In table format you can specify full rows using rows=<field>:
[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter,rows=description)]]
This is displayed as:
Results (1 - 3 of 8306)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #11364 | invalid | µ-law: pcm_mulaw files incorrectly shown as "s16", actually 8 bit per sample | ||
| Description |
Summary of the bug: ffprobe (6.1.2)/ffplay/ffmpeg incorrectly show Stream #0:0: Audio: pcm_mulaw ([7][0][0][0] / 0x0007), 48000 Hz, 1 channels, s16, 384 kb/s when inspecting a µ-law PCM file. If you divide 384 kb/s / (48000 Hz), you get the actual (and correct for G.711 µ-law) 8 b per sample. How to reproduce: # get some example linear pcm curl https://opus-codec.org/static/examples/samples/speech_orig.wav > orig.wav ffmpeg -i orig.wav -c:a pcm_mulaw mulaw.wav ffprobe -show_entries stream=sample_fmt -hide_banner mulaw.wav # gives: # Input #0, wav, from 'mulaw.wav': # Metadata: # encoder : Lavf60.16.100 # Duration: 00:00:10.80, bitrate: 384 kb/s # Stream #0:0: Audio: pcm_mulaw ([7][0][0][0] / 0x0007), 48000 Hz, 1 channels, s16, 384 kb/s ###### PROBLEM HERE: ######-----------------------------------------------------^^^ # [STREAM] # sample_fmt=s16 # [/STREAM]
The |
|||
| #11362 | invalid | memory leaks error at __interceptor_malloc | ||
| Description |
Summary of the bug: Hello ,Dear developers, I have encountered a memory leak issue while using ffmpeg version n7.2-dev and version 7.1.git. When I execute configure, if I enable -- enable-libx264 and -- enable gpl, the issue will be triggered. If I do not enable these two options, there will be no problem. Please confirm How to reproduce: unzip FFmpeg-n7.2-dev.zip cd FFmpeg-n7.2-dev ./configure --enable-libx264 --enable-gpl --cc=clang --cxx=clang++ --toolchain=clang-asan --enable-cross-compile ./ffmpeg -i pocffmpeg test.mp4 crash log: ================================================================= ==1590113==ERROR: LeakSanitizer: detected memory leaks Direct leak of 136 byte(s) in 1 object(s) allocated from:
Indirect leak of 30 byte(s) in 2 object(s) allocated from:
SUMMARY: AddressSanitizer: 166 byte(s) leaked in 3 allocation(s). ffmpeg version: $ ./ffmpeg -version ffmpeg version 7.1.git Copyright (c) 2000-2024 the FFmpeg developers built with Ubuntu clang version 14.0.0-1ubuntu1.1 configuration: --enable-libx264 --cc=clang --cxx=clang++ --enable-gpl --toolchain=clang-asan libavutil 59. 51.100 / 59. 51.100 libavcodec 61. 27.101 / 61. 27.101 libavformat 61. 9.101 / 61. 9.101 libavdevice 61. 4.100 / 61. 4.100 libavfilter 10. 6.101 / 10. 6.101 libswscale 8. 12.100 / 8. 12.100 libswresample 5. 4.100 / 5. 4.100 libpostproc 58. 4.100 / 58. 4.100 ubuntu version: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.3 LTS Release: 22.04 Codename: jammy $ uname -r 6.8.0-49-generic libx264 version: $ dpkg -s libx264-dev Package: libx264-dev Status: install ok installed Priority: optional Section: libdevel Installed-Size: 2761 Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> Architecture: amd64 Multi-Arch: same Source: x264 Version: 2:0.163.3060+git5db6aa6-2build1 Depends: libx264-163 (= 2:0.163.3060+git5db6aa6-2build1) Description: development files for libx264
Original-Maintainer: Debian Multimedia Maintainers <debian-multimedia@lists.debian.org> Homepage: https://www.videolan.org/developers/x264.html |
|||
| #11354 | invalid | Certain PlayStation STR complained "Invalid data" | ||
| Description |
Summary of the bug: How to reproduce: use Avanti GUI (v0.9.2) to try and covert Sony PlayStation 1 .STR movie files.. I get the error message below. ffmpeg version: FFmpeg-2024-12-14-win64-static I tried the latest build from the built on ... idk? error message: Input #0, not reported and process canceled by FFmpeg with the message: [in#0 @ 000001a21d256c00] Error opening input: Invalid data found when processing input Error opening input file Tales of Destiny 1 -- Opening.STR. Error opening input files: Invalid data found when processing input --- https://github.com/BtbN/FFmpeg-Builds/releases http://www.avanti.arrozcru.org/ I will try a newer up to date encoder called VidCoder not sure if it will help. |
|||
See also: TracQuery, TracTickets, TracReports
