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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#7269 duplicate ffmpeg-vaapi hevc vbr encode can not control the output bitrate focusluo
#7262 fixed ffmpeg automatically add "handler_name" to track metadata joshuaavalon
#7259 duplicate Failed to inject frame into filter network: Out of memory when video has metadata "rotate : 90" bolds
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 5446)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#7269 duplicate ffmpeg-vaapi hevc vbr encode can not control the output bitrate focusluo
Description

ffmpeg -hwaccel vaapi -vaapi_device /dev/dri/renderD128 -v verbose -f rawvideo -s:v 1920x1080 -i ./1080p_blue_sky.yuv -vf format=nv12,hwupload -c:v hevc_vaapi -g 12 -bf 0 -b:v 4M -quality 4 -y ./hevce_vbr_1920x1080_gop12_refdist0_bitrate4M.h265

My input is 4M bitrate, but the output is bitrate=3480.3kbits/s, which is out of the 10% range

some log of output: [hevc_vaapi @ 0x5654f5b96240] Input 1920x1080 -> Surface 1920x1088 -> CTU 60x34. Output #0, hevc, to './hevce_vbr_1920x1080_gop12_refdist0_bitrate4M.h265':

Metadata:

encoder : Lavf58.17.100 Stream #0:0: Video: hevc (hevc_vaapi) (Main), 1 reference frame, vaapi_vld, 1920x1080, q=2-31, 4000 kb/s, 25 fps, 25 tbn, 25 tbc Metadata:

encoder : Lavc58.20.101 hevc_vaapi

No more output streams to write to, finishing.e=00:00:07.92 bitrate=3442.3kbits/s speed=3.12x frame= 217 fps= 78 q=-0.0 Lsize= 3688kB time=00:00:08.68 bitrate=3480.3kbits/s speed=3.11x video:3688kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.000000% Input file #0 (/root/media_streamsencoderbitstreams1080p_blue_sky.yuv):

Input stream #0:0 (video): 217 packets read (674956800 bytes); 217 frames decoded; Total: 217 packets (674956800 bytes) demuxed

Output file #0 (./hevce_vbr_1920x1080_gop12_refdist0_bitrate4M.h265):

Output stream #0:0 (video): 217 frames encoded; 217 packets muxed (3776077 bytes); Total: 217 packets (3776077 bytes) muxed

#7262 fixed ffmpeg automatically add "handler_name" to track metadata joshuaavalon
Description

Summary of the bug: Inputting a mp4 without handler_name and does not specify it in the command, ffmpeg add "handler_name" not matter what.

In the log below, video track and audio track of 1.mp4 creation_time in their metadata and -map_metadata -1 should remove all metadata. However, "handler_name" was added to 2.mp4 by ffmpeg.

How to reproduce:

% ffmpeg -i in.mp4 -map_metadata -1 -codec copy out.mp4
ffmpeg version 3.4
built with gcc 6.4.0 (Alpine 6.4.0)

Log:

$ ffmpeg -i 1.mp4 -map_metadata -1 -codec copy 2.mp4

ffmpeg version 3.4 Copyright (c) 2000-2017 the FFmpeg developers
  built with gcc 6.4.0 (Alpine 6.4.0)
  configuration: --prefix=/usr --enable-avresample --enable-avfilter --enable-gnutls --enable-gpl --enable-libmp3lame --enable-librtmp --enable-libvorbis --enable-libvpx --enable-libxvid --enable-libx264 --enable-libx265 --enable-libtheora --enable-libv4l2 --enable-postproc --enable-pic --enable-pthreads --enable-shared --enable-libxcb --disable-stripping --disable-static --enable-vaapi --enable-vdpau --enable-libopus --disable-debug
  libavutil      55. 78.100 / 55. 78.100
  libavcodec     57.107.100 / 57.107.100
  libavformat    57. 83.100 / 57. 83.100
  libavdevice    57. 10.100 / 57. 10.100
  libavfilter     6.107.100 /  6.107.100
  libavresample   3.  7.  0 /  3.  7.  0
  libswscale      4.  8.100 /  4.  8.100
  libswresample   2.  9.100 /  2.  9.100
  libpostproc    54.  7.100 / 54.  7.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '1.mp4':
  Metadata:
    major_brand     : isom
    minor_version   : 1
    compatible_brands: isomavc1
    creation_time   : 2018-06-16T17:18:50.000000Z
  Duration: 00:24:00.04, start: 0.000000, bitrate: 1549 kb/s
    Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p(tv, bt709), 1280x720, 1341 kb/s, 23.98 fps, 23.98 tbr, 24k tbn, 47.95 tbc (default)
    Metadata:
      creation_time   : 2018-06-16T17:18:50.000000Z
    Stream #0:1(jpn): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 204 kb/s (default)
    Metadata:
      creation_time   : 2018-06-16T17:11:42.000000Z
Output #0, mp4, to '2.mp4':
  Metadata:
    encoder         : Lavf57.83.100
    Stream #0:0: Video: h264 (Main) (avc1 / 0x31637661), yuv420p(tv, bt709), 1280x720, q=2-31, 1341 kb/s, 23.98 fps, 23.98 tbr, 24k tbn, 24k tbc (default)
    Stream #0:1: Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 204 kb/s (default)
Stream mapping:
  Stream #0:0 -> #0:0 (copy)
  Stream #0:1 -> #0:1 (copy)
Press [q] to stop, [?] for help
frame=34525 fps=30679 q=-1.0 Lsize=  272712kB time=00:24:00.02 bitrate=1551.4kbits/s speed=1.28e+03x
video:235787kB audio:35953kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.357371%
$ffmpeg -i 2.mp4 -map_metadata -1 -codec copy 3.mp4

ffmpeg version 3.4 Copyright (c) 2000-2017 the FFmpeg developers
  built with gcc 6.4.0 (Alpine 6.4.0)
  configuration: --prefix=/usr --enable-avresample --enable-avfilter --enable-gnutls --enable-gpl --enable-libmp3lame --enable-librtmp --enable-libvorbis --enable-libvpx --enable-libxvid --enable-libx264 --enable-libx265 --enable-libtheora --enable-libv4l2 --enable-postproc --enable-pic --enable-pthreads --enable-shared --enable-libxcb --disable-stripping --disable-static --enable-vaapi --enable-vdpau --enable-libopus --disable-debug
  libavutil      55. 78.100 / 55. 78.100
  libavcodec     57.107.100 / 57.107.100
  libavformat    57. 83.100 / 57. 83.100
  libavdevice    57. 10.100 / 57. 10.100
  libavfilter     6.107.100 /  6.107.100
  libavresample   3.  7.  0 /  3.  7.  0
  libswscale      4.  8.100 /  4.  8.100
  libswresample   2.  9.100 /  2.  9.100
  libpostproc    54.  7.100 / 54.  7.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '2.mp4':
  Metadata:
    major_brand     : isom
    minor_version   : 512
    compatible_brands: isomiso2avc1mp41
    encoder         : Lavf57.83.100
  Duration: 00:24:00.04, start: 0.000000, bitrate: 1551 kb/s
    Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p(tv, bt709), 1280x720, 1341 kb/s, 23.98 fps, 23.98 tbr, 24k tbn, 47.95 tbc (default)
    Metadata:
      handler_name    : VideoHandler
    Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 204 kb/s (default)
    Metadata:
      handler_name    : SoundHandler
Output #0, mp4, to '3.mp4':
  Metadata:
    encoder         : Lavf57.83.100
    Stream #0:0: Video: h264 (Main) (avc1 / 0x31637661), yuv420p(tv, bt709), 1280x720, q=2-31, 1341 kb/s, 23.98 fps, 23.98 tbr, 24k tbn, 24k tbc (default)
    Stream #0:1: Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 204 kb/s (default)
Stream mapping:
  Stream #0:0 -> #0:0 (copy)
  Stream #0:1 -> #0:1 (copy)
Press [q] to stop, [?] for help
frame=34525 fps=26192 q=-1.0 Lsize=  272712kB time=00:24:00.02 bitrate=1551.4kbits/s speed=1.09e+03x
video:235787kB audio:35953kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.357374%
#7259 duplicate Failed to inject frame into filter network: Out of memory when video has metadata "rotate : 90" bolds
Description

Summary of the bug:

I built ffmpeg for android, it's working fine for some videos, but it crashes on high bitrate h264 videos with rotate tag.

First let me detail the enviroment:

1- the script i used to build ffmpeg can be found at https://github.com/bolds07/ffmpeg-for-android-for-dummies/blob/master/builder.sh 2 - im testing on android emulator and also in my real phone (i686 and arm64v8-a) 3 - the command i'm running is a simple encoding command like: ffmpeg -y -i file.mp4 -c:v libx264 -crf 30 -c:a copy output.mp4 3a - I also tried to use mpeg4 and other encoders to replace libx264 but the same problem occurs 4 - all videos h264 i've with bitrate until 6.000 kbps work fine 5 - videos with bitrate 12.000kbps without the rotate metadata work fine 7 - I've tested big videos (200MB) with 5000kbps and they work fine (if the video hasn't the metadata rotate) 8 - I've tested small videos (15MB) with 12000kbps and they don't work (if it has)

I re-run tha command with the parameters -v 9 -loglevel 99 and pasted the result at: https://pastebin.com/ihawsPvZ

I will set two video samples for anyone test, one which works and one which doesn't (the only difference i see is the metadata but i might be wrong)

https://www.dropbox.com/s/pdimy5rj8lnbn56/work.mp4?dl=1 https://www.dropbox.com/s/0tpkrgdm02qzj3s/crash.mp4?dl=1

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 3 years ago Last modified on Jul 6, 2015, 10:44:56 PM