Trac Ticket Queries
Table of contents
In addition to reports, Trac provides support for custom ticket queries, which can be used to display tickets that meet specified 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 in and no name/email is 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 dropdown 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 dropdown menu of options can be added multiple times to perform an Or on 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.
After you have edited your filters, click the Update button to refresh your results.
Navigating Tickets
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.
Using TracLinks
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:
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:
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 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 1539)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1599 | fixed | Decoding a Y4M encoded bitstream do not retain framerate | mindfreeze | |
| #1598 | fixed | Y4M reader not handling chroma-format `420mpeg2` correctly | mindfreeze | |
| #1597 | fixed | Incorrect parsing of nnpfc_constant_patch_size_flag | hallapur |
Full rows
In table format you can also have full rows by 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 1539)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1599 | fixed | Decoding a Y4M encoded bitstream do not retain framerate | mindfreeze | |
| Description |
When we encode which is in y4m input, the frame rate and other input metadata are present in the header. This is also expected when we decode a bitstream to y4m. Background Currently in VVC, when we try to decode a video (bitstream) to Y4M format, it suggests there is no framerate info in the bitstream and fallback to the default 50fps. This is not the correct behaviour. If it is YUV, we don't care about the frame rate inside the decoded stream, it is not the case here. Steps to reproduce
EncoderAppStatic -i FourPeople_480x270_60.y4m -c vvc-vtm/encoder_randomaccess_vtm.cfg --InputBitDepth=10 --FramesToBeEncoded=1 --QP=50 --ReconFile=Fourpeople-recon.yuv -b fourpeople.bin The sample used in this example: https://media.xiph.org/video/aomctc/test_set/a5_270p/FourPeople_480x270_60.y4m
./bin/DecoderAppStatic -b fourpeople.bin -o four.y4m
SRC: head -1 /media/aomctc-a5-270p/FourPeople_480x270_60.y4m SRC: YUV4MPEG2 W480 H270 F60:1 Ip A0:0 C420jpeg XYSCSS=420JPEG ENC_STREAM: head -1 four.y4m ENC_STREAM: YUV4MPEG2 W480 H270 F50:1 Ip A0:0 C420p10 Samples Any y4m samples would be sufficient, Workarounds If we explicitly signal HRDParameters with SEIPictureTiming and BufferPeriod, we get the approximate frame-rate (no idea why not same for all the clips) in the decoded y4m file, --HrdParametersPresent=1 --SEIPictureTiming=1 --SEIBufferingPeriod=1 --RCCpbSize=1000 YUV4MPEG2 W480 H270 F60000:1001 Ip A0:0 C420p10 It suggests 59.94 instead of 60fps for this sample clip. So I do not know if this is the correct way to handle frame-rate information in VVC, I have little idea as a whole for VVC. At the same time, for some other clips which has fractional frame rates (only tested with 2-4 clips, so not yet conclusive) it gives the correct framerate in the output y4m. Another broken example, Input: https://media.xiph.org/video/aomctc/test_set/a2_2k/MountainBike_1920x1080_30fps_8bit.y4m Encode-settings: same as above SRC: YUV4MPEG2 W1920 H1080 F30:1 Ip A1:1 C420jpeg XYSCSS=420JPEG ENC_STREAM: YUV4MPEG2 W1920 H1080 F30000:1001 Ip A0:0 C420p10 Another working example, Input: https://media.xiph.org/video/aomctc/test_set/a5_270p/Vertical_Bayshore_270x480_2997.y4m SRC: YUV4MPEG2 W270 H480 F30000:1001 Ip A0:0 C420jpeg XYSCSS=420JPEG ENC_STREAM: YUV4MPEG2 W270 H480 F30000:1001 Ip A0:0 C420p10 Question I would assume it falls back to 420p10 due to the internal 10-bit pipeline in the configuration of VVC. Would be beneficial to have a clarification for that. Best, V |
|||
| #1598 | fixed | Y4M reader not handling chroma-format `420mpeg2` correctly | mindfreeze | |
| Description |
Hi, Background We have been trying to integrate VVC into a popular compression testing framework, AreWeCompressedYet (AWCY)[1]. Typically we store the input videos as Y4M files for ease of file handling and maintainability. We have the initial support of VVC_VTM in an experimental YUV pipeline, where the videos are converted from y4m->yuv on the fly. it is problematic when we want to scale the jobs. Thus y4m is useful as other encoders are built and tested with y4m for many years. Y4M is a not-so-well-defined spec, [in fact no official spec per-se! (?)], so different authors/encoders have different implementations. Thus implementing is a bit tricky. One page which people tend to refer to as a loose spec is the multimedia wiki[2], which is obviously not fully defined, thus discrepancies are there. VVC have initial support for encoding and decoding of Y4M files, which works well for most cases. I have been testing and comparing the YUV encoding pipeline with the Y4M encoding pipeline for various videos typically available in our xiph's Media collection[2] and other public resources. In the testing, there was this edge case where the VVC-VTM is not handling c420mpeg2 Y4M files correctly. Not handling in the sense, the bitstream in a YUV pipeline is mismatched from the same file in Y4M pipeline. At the same time if hack the chroma-format to be 420 or 420jpeg it works and gives bit-identical output What is 420mpeg2? I tried to have a bit of digging into this, and it seems to be there since ~2006 in the mjpegtools[3]. And other public implementations of y4m handlers[4,5,6,7, 8] CLI from yuv4mpeg 420mpeg2 - 4:2:0 MPEG-2 (horiz. cositing) Many samples on the internet are with 420mpeg2. Proposed solution Typically in y4m readers, say HDRTools, FFmpeg or any other libraries which supports many y4m inputs, it is handles in the input parsing is the same as other 420 input formats[4,6,7,8]. So one quick fix would be handling it in the same fashion as 420jpeg in VVC-VTM[9] to mimic other public implementations. Samples https://media.xiph.org/video/aomctc/test_set/b1_syn/EuroTruckSimulator2_1920x1080p60_v2.y4m https://media.xiph.org/video/aomctc/test_set/b1_syn/STARCRAFT_1080p60.y4m https://media.xiph.org/video/aomctc/test_set/a4_360p/BlueSky_360p25_v2.y4m Sample command line EncoderAppStatic -i $INPUT.Y4M -c encoder_randomaccess_vtm.cfg --ReconFile=$INPUT-recon.yuv --QP=$X -b $INPUT-bitstream.bin EncoderAppStatic -i $INPUT.YUV -c encoder_randomaccess_vtm.cfg --ReconFile=$INPUT-recon.yuv --SourceWidth=$WIDTH --SourceHeight=$HEIGHT --FrameRate=$FPS --InputBitDepth=$DEPTH --QP=50 -b $INPUT-bitstream.bin Steps to reproduce
[1]: https://github.com/xiph/awcy [2]: https://wiki.multimedia.cx/index.php/YUV4MPEG2 [2]: https://media.xiph.org/ [3]: https://mjpeg.sourceforge.io/ [4]: https://gitlab.com/standards/HDRTools/-/blob/master/common/src/InputY4M.cpp#L209 [5]: https://github.com/xiph/daala/blob/master/tools/y4m_input.c#L180 [6]: https://github.com/image-rs/y4m/blob/58375d69120a33e2a21320e17449e84e4de9949d/src/lib.rs#L249 [7]: https://gitlab.com/AOMediaCodec/avm/-/blob/main/common/y4minput.c#L909 [8]: https://source.ffmpeg.org/?p=ffmpeg.git;a=blob;f=libavformat/yuv4mpegenc.c;h=2fa5ee2714ddba9f15c998a9295f153b26a21985;hb=HEAD#l104 [9]: https://vcgit.hhi.fraunhofer.de/jvet/VVCSoftware_VTM/-/blob/master/source/Lib/Utilities/VideoIOYuv.cpp#L233 [A.1]: Steps to modify a header echo "YUV4MPEG2 W640 H360 F25:1 Ip C420jpeg" > BlueSky_360p25_v3.y4m tail -n+2 BlueSky_360p25_v2.y4m >> BlueSky_360p25_v3.y4m Please do let me know if you have any questions, Best, V |
|||
| #1597 | fixed | Incorrect parsing of nnpfc_constant_patch_size_flag | hallapur | |
| Description |
The flag is parsed incorrectly which causes decoder crash.
Correct way to parse is as follows:
|
|||
Query Language
query: TracLinks and the [[TicketQuery]] macro both use a mini “query language” for specifying query filters. Filters are separated by ampersands (&). Each filter 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 omitted 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, TicketQuery
