wiki:

TracQuery

Trac Ticket Queries

In addition to reports, Trac provides support for custom ticket queries, used to display lists of tickets meeting a specified set of criteria.

To configure and execute a custom query, switch to the View Tickets module from the navigation bar, and select the Custom Query link.

Filters

When you first go to the query page the default filter will display tickets relevant to you:

  • If logged in then all open tickets it will display open tickets assigned to you.
  • If not logged in but you have specified a name or email address in the preferences then it will display all open tickets where your email (or name if email not defined) is in the CC list.
  • If not logged and no name/email defined in the preferences then all open issues are displayed.

Current filters can be removed by clicking the button to the left with the minus sign on the label. New filters are added from the pulldown lists at the bottom corners of the filters box ('And' conditions on the left, 'Or' conditions on the right). Filters with either a text box or a pulldown menu of options can be added multiple times to perform an or of the criteria.

You can use the fields just below the filters box to group the results based on a field, or display the full description for each ticket.

Once you've edited your filters click the Update button to refresh your results.

Clicking on one of the query results will take you to that ticket. You can navigate through the results by clicking the Next Ticket or Previous Ticket links just below the main menu bar, or click the Back to Query link to return to the query page.

You can safely edit any of the tickets and continue to navigate through the results using the Next/Previous/Back to Query links after saving your results. When you return to the query any tickets which were edited will be displayed with italicized text. If one of the tickets was edited such that it no longer matches the query criteria the text will also be greyed. Lastly, if a new ticket matching the query criteria has been created, it will be shown in bold.

The query results can be refreshed and cleared of these status indicators by clicking the Update button again.

Saving Queries

Trac allows you to save the query as a named query accessible from the reports module. To save a query ensure that you have Updated the view and then click the Save query button displayed beneath the results. You can also save references to queries in Wiki content, as described below.

Note: one way to easily build queries like the ones below, you can build and test the queries in the Custom report module and when ready - click Save query. This will build the query string for you. All you need to do is remove the extra line breaks.

Note: you must have the REPORT_CREATE permission in order to save queries to the list of default reports. The Save query button will only appear if you are logged in as a user that has been granted this permission. If your account does not have permission to create reports, you can still use the methods below to save a query.

You may want to save some queries so that you can come back to them later. You can do this by making a link to the query from any Wiki page.

[query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0]

Which is displayed as:

Active tickets against 1.0

This uses a very simple query language to specify the criteria (see Query Language).

Alternatively, you can copy the query string of a query and paste that into the Wiki link, including the leading ? character:

[query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner]

Which is displayed as:

Assigned tickets by owner

Using the [[TicketQuery]] Macro

The TicketQuery macro lets you display lists of tickets matching certain criteria anywhere you can use WikiFormatting.

Example:

[[TicketQuery(version=0.6|0.7&resolution=duplicate)]]

This is displayed as:

No results

Just like the query: wiki links, the parameter of this macro expects a query string formatted according to the rules of the simple ticket query language. This also allows displaying the link and description of a single ticket:

[[TicketQuery(id=123)]]

This is displayed as:

#123
Fuzzed sample crashes ffplay

A more compact representation without the ticket summaries is also available:

[[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]]

This is displayed as:

No results

Finally, if you wish to receive only the number of defects that match the query, use the count parameter.

[[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]]

This is displayed as:

0

Customizing the table format

You can also customize the columns displayed in the table format (format=table) by using col=<field> - you can specify multiple fields and what order they are displayed by placing pipes (|) between the columns like below:

[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter)]]

This is displayed as:

Results (1 - 3 of 5835)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#7743 duplicate [git master] Build error: ‘tcuGetErrorName’ undeclared (and others) bermond
#7739 fixed Explain stream specifier usage for codec and other global options Gyan UlfZibis
#7736 duplicate Incorrect video start time when muxing with opus audio jstrot123
1 2 3 4 5 6 7 8 9 10 11

Full rows

In table format you can also have full rows by using rows=<field> like below:

[[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 5835)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#7743 duplicate [git master] Build error: ‘tcuGetErrorName’ undeclared (and others) bermond
Description

I'm getting the following error when trying to build ffmpeg git master:

CC      libavfilter/vf_scale_cuda.o
In file included from libavfilter/vf_scale_cuda.c:31:
./libavutil/cuda_check.h: In function ‘ff_cuda_check’:
./libavutil/cuda_check.h:38:7: error: ‘tcuGetErrorName’ undeclared (first use in this function); did you mean ‘cuGetErrorName’?
     ((tcuGetErrorName *)cuGetErrorName_fn)(err, &err_name);
       ^~~~~~~~~~~~~~~
       cuGetErrorName
./libavutil/cuda_check.h:38:7: note: each undeclared identifier is reported only once for each function it appears in
./libavutil/cuda_check.h:38:24: error: expected expression before ‘)’ token
     ((tcuGetErrorName *)cuGetErrorName_fn)(err, &err_name);
                        ^
./libavutil/cuda_check.h:39:7: error: ‘tcuGetErrorString’ undeclared (first use in this function); did you mean ‘cuGetErrorString’?
     ((tcuGetErrorString *)cuGetErrorString_fn)(err, &err_string);
       ^~~~~~~~~~~~~~~~~
       cuGetErrorString
./libavutil/cuda_check.h:39:26: error: expected expression before ‘)’ token
     ((tcuGetErrorString *)cuGetErrorString_fn)(err, &err_string);
                          ^
make: *** [ffbuild/common.mak:60: libavfilter/vf_scale_cuda.o] Error 1
  • A git bisect shows that this is caused by commit 15c6390.
  • Possibly related ticket: #7735.

How to reproduce:

$ git clone https://git.ffmpeg.org/ffmpeg.git
$ cd ffmpeg
$ ./configure --prefix='/usr' --extra-cflags='-I/opt/cuda/include' --extra-ldflags='-L/opt/cuda/lib64' --enable-nonfree --enable-cuda-sdk
$ make -j1

System Information:

  • OS: Arch Linux x86_64
  • ffmpeg: git master
  • Compiler: gcc 8.2.1
  • CUDA: 10.0.130
#7739 fixed Explain stream specifier usage for codec and other global options Gyan UlfZibis
Description

Summary of the bug: At https://www.ffmpeg.org/ffmpeg-codecs.html#Codec-Options there is no hint that options should be postfixed by a stream specifier in case of ambiguity. An example would be helpful too. At https://www.ffmpeg.org/ffmpeg.html#AVOptions the given example doesn't reflect the statement: "... a stream specifier should be attached ...", so "... in case of ambiguity" should be amended. For https://ffmpeg.org/ffmpeg-formats.html#Format-Options the same applies. How to reproduce:

% ffmpeg -i input -level:a 5 output # avoid ambiguity with video codec level
ffmpeg version: current
#7736 duplicate Incorrect video start time when muxing with opus audio jstrot123
Description

Problem description

In its simplest form, my goal is to create an mkv by muxing a video (vp9) track and an audio (opus) track. Should be a simple task but I'm facing issues with the resulting video start time.

Due to the inherent 6.5 ms (312 * 48K) delay of the opus codec, the audio start time is expected to be -0.007ms but the video should still start at 0ms yet ffmpeg muxes with the video starting at +0.007ms:

$ ffmpeg -i track0.vp9.ivf -i track1.opus.ogg -codec copy output.mkv
ffmpeg version 4.1 Copyright (c) 2000-2018 the FFmpeg developers
  built with gcc 8 (Debian 8.2.0-10)
  configuration: --disable-decoder=amrnb --disable-decoder=libopenjpeg --disable-mips32r2 --disable-mips32r6 --disable-mips64r6 --disable-mipsdsp --disable-mipsdspr2 --disable-mipsfpu --disable-msa --disable-libopencv --disable-podpages --disable-sndio --disable-stripping --enable-libaom --enable-avfilter --enable-avresample --enable-gcrypt --enable-gnutls --enable-gpl --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libfdk-aac --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libilbc --enable-libkvazaar --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtesseract --enable-libtheora --enable-libvidstab --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libx265 --enable-libxvid --enable-libzvbi --enable-nonfree --enable-opencl --enable-opengl --enable-postproc --enable-pthreads --enable-shared --enable-version3 --enable-libwebp --incdir=/usr/include/x86_64-linux-gnu --libdir=/usr/lib/x86_64-linux-gnu --prefix=/usr --toolchain=hardened --enable-frei0r --enable-chromaprint --enable-libx264 --enable-libiec61883 --enable-libdc1394 --enable-vaapi --enable-libmfx --disable-altivec --shlibdir=/usr/lib/x86_64-linux-gnu
  libavutil      56. 22.100 / 56. 22.100
  libavcodec     58. 35.100 / 58. 35.100
  libavformat    58. 20.100 / 58. 20.100
  libavdevice    58.  5.100 / 58.  5.100
  libavfilter     7. 40.101 /  7. 40.101
  libavresample   4.  0.  0 /  4.  0.  0
  libswscale      5.  3.100 /  5.  3.100
  libswresample   3.  3.100 /  3.  3.100
  libpostproc    55.  3.100 / 55.  3.100
Input #0, ivf, from 'track0.vp9.ivf':
  Duration: N/A, start: 0.000000, bitrate: N/A
    Stream #0:0: Video: vp9 (Profile 0) (VP90 / 0x30395056), yuv420p(tv), 720x480, 23.98 tbr, 23.98 tbn, 23.98 tbc
[ogg @ 0x56377efc2500] 654 bytes of comment header remain
Input #1, ogg, from 'track1.opus.ogg':
  Duration: 00:10:00.49, start: 0.000000, bitrate: 409 kb/s
    Stream #1:0: Audio: opus, 48000 Hz, 5.1, fltp
    Metadata:
      ENCODER         : opusenc from opus-tools 0.1.10
      ENCODER_OPTIONS : --vbr --bitrate 448
Output #0, matroska, to 'output.mkv':
  Metadata:
    encoder         : Lavf58.20.100
    Stream #0:0: Video: vp9 (Profile 0) (VP90 / 0x30395056), yuv420p(tv), 720x480, q=2-31, 23.98 tbr, 1k tbn, 23.98 tbc
    Stream #0:1: Audio: opus ([255][255][255][255] / 0xFFFFFFFF), 48000 Hz, 5.1, fltp
    Metadata:
      ENCODER         : opusenc from opus-tools 0.1.10
      ENCODER_OPTIONS : --vbr --bitrate 448
Stream mapping:
  Stream #0:0 -> #0:0 (copy)
  Stream #1:0 -> #0:1 (copy)
Press [q] to stop, [?] for help
frame=14397 fps=0.0 q=-1.0 Lsize=   95680kB time=00:10:00.47 bitrate=1305.3kbits/s speed=1.48e+03x    
video:65466kB audio:29900kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.329659%

$ ffprobe -i output.mkv -show_streams 2>/dev/null | grep start_time
start_time=0.007000
start_time=-0.007000

$ ffprobe -i output.mkv -show_packets -of compact 2>/dev/null | head -2
packet|codec_type=audio|stream_index=1|pts=-7|pts_time=-0.007000|dts=-7|dts_time=-0.007000|duration=20|duration_time=0.020000|convergence_duration=N/A|convergence_duration_time=N/A|size=1737|pos=924|flags=K_
packet|codec_type=video|stream_index=0|pts=7|pts_time=0.007000|dts=7|dts_time=0.007000|duration=N/A|duration_time=N/A|convergence_duration=N/A|convergence_duration_time=N/A|size=10995|pos=2668|flags=K_

If instead I use an ac3 audio track (w/o delay) then all tracks are muxed withno delay, as expected:

$ ffmpeg -i track0.vp9.ivf -i track1.ac3 -codec copy output.mkv
...
Input #0, ivf, from 'track0.vp9.ivf':
  Duration: N/A, start: 0.000000, bitrate: N/A
    Stream #0:0: Video: vp9 (Profile 0) (VP90 / 0x30395056), yuv420p(tv), 720x480, 23.98 tbr, 23.98 tbn, 23.98 tbc
[ac3 @ 0x55fdae1a1500] Estimating duration from bitrate, this may be inaccurate
Input #1, ac3, from 'track1.ac3':
  Duration: 00:10:00.48, start: 0.000000, bitrate: 448 kb/s
    Stream #1:0: Audio: ac3, 48000 Hz, 5.1(side), fltp, 448 kb/s
...

$ ffprobe -i output.mkv -show_streams 2>/dev/null | grep start_time
start_time=0.000000
start_time=0.000000

$ ffprobe -i output.mkv -show_packets -of compact 2>/dev/null | head -2
packet|codec_type=video|stream_index=0|pts=0|pts_time=0.000000|dts=0|dts_time=0.000000|duration=N/A|duration_time=N/A|convergence_duration=N/A|convergence_duration_time=N/A|size=10995|pos=753|flags=K_
packet|codec_type=audio|stream_index=1|pts=0|pts_time=0.000000|dts=0|dts_time=0.000000|duration=32|duration_time=0.032000|convergence_duration=N/A|convergence_duration_time=N/A|size=1792|pos=11755|flags=K_

Workaround

I tried all sorts of combinations of -itsoffset, -copyts, -start_at_zero, -avoid_negative_ts, ... the only workaround I found (by luck) was to provide a large (-10) negative itsoffset for the audio track and suddenly ffmpeg stops applying a delay to the video track.

$ ffmpeg -i track0.vp9.ivf -itsoffset -10 -i track1.opus.ogg -codec copy output.mkv
...
$ ffprobe -i output.mkv -show_streams 2>/dev/null | grep start_time
start_time=0.000000
start_time=-0.007000

$ ffprobe -i output.mkv -show_packets -of compact 2>/dev/null | head -2
packet|codec_type=video|stream_index=0|pts=0|pts_time=0.000000|dts=0|dts_time=0.000000|duration=N/A|duration_time=N/A|convergence_duration=N/A|convergence_duration_time=N/A|size=10995|pos=924|flags=K_
packet|codec_type=audio|stream_index=1|pts=-7|pts_time=-0.007000|dts=-7|dts_time=-0.007000|duration=20|duration_time=0.020000|convergence_duration=N/A|convergence_duration_time=N/A|size=1737|pos=11926|flags=K_

Other observations

  • With multiple audio tracks the -itsoffset has to be specified for each audio track.
  • Compared number of video and audio packets in ffprobe -show_packets output and all are accounted for.
  • With other itsoffset values there are weird behaviors too! With 0 to -5 it just adds a delay to the video track, with -6 to -9 it aligns both to -7ms:
with -itsoffset 0:
start_time=0.007000
start_time=-0.007000

with -itsoffset -1:
start_time=1.007000
start_time=-0.007000

with -itsoffset -2:
start_time=2.007000
start_time=-0.007000

...
with -itsoffset -5:
start_time=5.007000
start_time=-0.007000

with -itsoffset -6 to -9:
start_time=-0.007000
start_time=-0.007000

with -itsoffset -10 to -99:59:59.99999999:
start_time=0.000000
start_time=-0.007000
1 2 3 4 5 6 7 8 9 10 11

Query Language

query: TracLinks and the [[TicketQuery]] macro both use a mini “query language” for specifying query filters. Basically, the filters are separated by ampersands (&). Each filter then consists of the ticket field name, an operator, and one or more values. More than one value are separated by a pipe (|), meaning that the filter matches any of the values. To include a literal & or | in a value, escape the character with a backslash (\).

The available operators are:

= the field content exactly matches one of the values
~= the field content contains one or more of the values
^= the field content starts with one of the values
$= the field content ends with one of the values

All of these operators can also be negated:

!= the field content matches none of the values
!~= the field content does not contain any of the values
!^= the field content does not start with any of the values
!$= the field content does not end with any of the values

The date fields created and modified can be constrained by using the = operator and specifying a value containing two dates separated by two dots (..). Either end of the date range can be left empty, meaning that the corresponding end of the range is open. The date parser understands a few natural date specifications like "3 weeks ago", "last month" and "now", as well as Bugzilla-style date specifications like "1d", "2w", "3m" or "4y" for 1 day, 2 weeks, 3 months and 4 years, respectively. Spaces in date specifications can be left out to avoid having to quote the query string.

created=2007-01-01..2008-01-01 query tickets created in 2007
created=lastmonth..thismonth query tickets created during the previous month
modified=1weekago.. query tickets that have been modified in the last week
modified=..30daysago query tickets that have been inactive for the last 30 days

See also: TracTickets, TracReports, TracGuide

Last modified 4 years ago Last modified on Jul 6, 2015, 10:44:56 PM