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 4812)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#6344 fixed DNXHD parser regression causes lost frames cus
#6340 fixed utvideo: fix gradient prediction for interlaced video ami_stuff
#6336 invalid No Way to Cleanly Terminate ffmpeg.exe while capturing screen dbareis
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 4812)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#6344 fixed DNXHD parser regression causes lost frames cus
Description

Summary of the bug: A user in ticket #6318 uploaded DNXHD file which contains 36 frames, but since e1940d2458353943e2fab6bdb87d2278077e22a5 only one frame is decoded.

Sample is here: https://mega.nz/#!lpoDSQQb!A1YmzIAIC6osbPS3u0boIbwa1Ys0JN6LtvNcNOkslZU

How to reproduce:

% ffprobe -count_frames -select_streams v -show_entries stream=nb_read_frames DNxHD.mxf
ffprobe version N-85607-g5b281b476b Copyright (c) 2007-2017 the FFmpeg developers
  built with gcc 4.8 (SUSE Linux)
  configuration: --disable-vaapi --enable-vdpau --enable-gpl --enable-libfreetype --enable-libzvbi --enable-libass --enable-frei0r --enable-openssl --enable-nonfree --enable-libx264 --enable-libfdk-aac --enable-nonfree --enable-libvorbis --enable-decklink --enable-libmp3lame --enable-openal --enable-libiec61883 --assert-level=2
  libavutil      55. 61.100 / 55. 61.100
  libavcodec     57. 93.100 / 57. 93.100
  libavformat    57. 72.101 / 57. 72.101
  libavdevice    57.  7.100 / 57.  7.100
  libavfilter     6. 86.100 /  6. 86.100
  libswscale      4.  7.101 /  4.  7.101
  libswresample   2.  8.100 /  2.  8.100
  libpostproc    54.  6.100 / 54.  6.100
[mxf @ 0x3f443c0] Stream #0: not enough frames to estimate rate; consider increasing probesize
Input #0, mxf, from 'DNxHD.mxf':
  Metadata:
    project_name    : 52 PALOMBES 2017
    uid             : b2ddeb1d-1eca-f843-909b-f298e1a5a709
    generation_uid  : b6bcfcab-70ff-7331-1aa2-6f7e69de11d2
    application_platform: AAFSDK (MacOS X)
    modification_date: 2017-03-03T09:18:45.000000Z
    product_uid     : acfbf03a-4f42-a231-d0b7-c06ecd3d4ad7
    product_version : Unknown version
    product_name    : Avid Media Composer 8.4.5.38655
    company_name    : Avid Technology, Inc.
    material_package_umid: 0x060A2B340101010101010F001300000058B934F57C1B0045060E2B347F7F2A80
    material_package_name: 00009.new.01
    comment_Video File Format: .MTS
    comment_Video   : H.264 (1080i 50)
    comment_Audio Format: Dolby AC-3 256kb/s
  Duration: 00:00:01.44, start: 0.000000, bitrate: 123793 kb/s
    Stream #0:0: Video: dnxhd (DNXHD), yuv422p(bt709/unknown/unknown, top first), 1920x1080, SAR 1:1 DAR 16:9, 25 tbr, 25 tbn, 25 tbc
    Metadata:
      file_package_umid: 0x060A2B340101010101010F001300000058B934F57C1E0045060E2B347F7F2A80
      file_package_name: 00009
      track_name      : V1
      reel_umid       : 0x060A2B340101010101010F0013A1000023083DE5957DCEDE3D381353A1B80836
      reel_name       : 00009
      timecode        : 00:04:59:01
    Stream #0:1: Data: none
    Metadata:
      file_package_umid: 0x060A2B340101010101010F001300000058B934F57C1F0045060E2B347F7F2A80
      track_name      : A1
      data_type       : audio
    Stream #0:2: Data: none
    Metadata:
      file_package_umid: 0x060A2B340101010101010F001300000058B934F57C200045060E2B347F7F2A80
      track_name      : A2
      data_type       : audio
Unsupported codec with id 0 for input stream 1
Unsupported codec with id 0 for input stream 2
[STREAM]
nb_read_frames=1
[/STREAM]

#6340 fixed utvideo: fix gradient prediction for interlaced video ami_stuff
Description

decodes bit-exact with vfw codec

https://files.fm/u/8ebkzaug

C:\>ffmpeg -i utv_rgb_int_gradient_8.avi out.avi
ffmpeg version 3.3.git Copyright (c) 2000-2017 the FFmpeg developers
  built with gcc 4.6.2 (GCC)
  configuration: --disable-asm --disable-pthreads --enable-gpl --disable-ffprobe

  libavutil      55. 61.100 / 55. 61.100
  libavcodec     57. 93.100 / 57. 93.100
  libavformat    57. 72.101 / 57. 72.101
  libavdevice    57.  7.100 / 57.  7.100
  libavfilter     6. 85.100 /  6. 85.100
  libswscale      4.  7.101 /  4.  7.101
  libswresample   2.  8.100 /  2.  8.100
  libpostproc    54.  6.100 / 54.  6.100
[utvideo @ 0222cd78] Warning: not compiled with thread support, using thread emu
lation
Input #0, avi, from 'utv_rgb_int_gradient_8.avi':
  Duration: 00:00:03.20, start: 0.000000, bitrate: 10899 kb/s
    Stream #0:0: Video: utvideo (ULRG / 0x47524C55), rgb24, 500x500, 11227 kb/s,
 10 fps, 10 tbr, 10 tbn, 10 tbc
[utvideo @ 0233aba8] Warning: not compiled with thread support, using thread emu
lation
Stream mapping:
  Stream #0:0 -> #0:0 (utvideo (native) -> mpeg4 (native))
Press [q] to stop, [?] for help
[mpeg4 @ 0233c1f0] Warning: not compiled with thread support, using thread emula
tion
Output #0, avi, to 'out.avi':
  Metadata:
    ISFT            : Lavf57.72.101
    Stream #0:0: Video: mpeg4 (FMP4 / 0x34504D46), yuv420p, 500x500, q=2-31, 200
 kb/s, 10 fps, 10 tbn, 10 tbc
    Metadata:
      encoder         : Lavc57.93.100 mpeg4
    Side data:
      cpb: bitrate max/min/avg: 0/0/200000 buffer size: 0 vbv_delay: -1
frame=   32 fps=0.0 q=31.0 Lsize=     317kB time=00:00:03.20 bitrate= 812.7kbits
/s speed=6.61x
video:311kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing o
verhead: 2.030940%
#6336 invalid No Way to Cleanly Terminate ffmpeg.exe while capturing screen dbareis
Description

This is on Windows 7/10 64 bit (but would at least be the same on all Windows computers), using this command line:

ffmpeg -y -f gdigrab -i desktop -r 10 -vcodec libx264 -pix_fmt yuv420p 10fps.mp4

You can manually terminate the program with CTRL+BREAK which is better than nothing but if you use the command (in a batch/automated process):

TaskKill /im ffmpeg.exe /F

then the result is an unusable and corrupted video.

The program already handles CTRL+BREAK, it should probably be simple to enhance this for the sigterm signal. But it would be nice to be able to cleanly do this with something like:

ffmpeg.exe /STOP 

or perhaps:

ffmpeg.exe /STOP [AliasDefinedOnExistingCommandLineToAllowSpecificTaskTermination]
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 22 months ago Last modified on Jul 6, 2015, 10:44:56 PM