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
bwd runs and receptor output

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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#212 fixed Bug in flex_extract v7.0.3 Fortran program "CONVERT2" anphi anphi
#208 fixed WRF specific files pesei mitchekc
#207 fixed Error running FLEXPART pesei mitchekc
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 149)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#212 fixed Bug in flex_extract v7.0.3 Fortran program "CONVERT2" anphi anphi
Description

During a test with ERA5 and CERA with the gateway version (submitting the jobscript to the ecgate server) I had problems in the CONVERT2 Fortran program.

I received the following error with grib_api:

grib_ieee_to_long: Number is too large: x=3.35531257646599394446e+44 > xmax=3.40282346638528859812e+38
/scratch/ma/deploy/metabuilds/ecflow-metab_5062/ecgb/GNU.63/grib_api/grib_api/src/grib_ieeefloat.c at line 147: assertion failure Assert(0)

Program received signal SIGABRT: Process abort signal.

Backtrace for this error:
#0  0x3dd543250f in ???
#1  0x3dd5432495 in ???
#2  0x3dd5433c74 in ???
#3  0x7ffff7b38a42 in grib_fail
    at /scratch/ma/deploy/metabuilds/ecflow-metab_5062/ecgb/GNU.63/grib_api/grib_api/src/grib_errors.c:111
#4  0x7ffff7b2241b in grib_ieee_to_long
    at /scratch/ma/deploy/metabuilds/ecflow-metab_5062/ecgb/GNU.63/grib_api/grib_api/src/grib_ieeefloat.c:147
#5  0x7ffff7b226c7 in grib_ieee_nearest_smaller_to_long
    at /scratch/ma/deploy/metabuilds/ecflow-metab_5062/ecgb/GNU.63/grib_api/grib_api/src/grib_ieeefloat.c:237
#6  0x7ffff7b2283e in grib_nearest_smaller_ieee_float
    at /scratch/ma/deploy/metabuilds/ecflow-metab_5062/ecgb/GNU.63/grib_api/grib_api/src/grib_ieeefloat.c:280
#7  0x7ffff7b01b1e in pack_double
    at /scratch/ma/deploy/metabuilds/ecflow-metab_5062/ecgb/GNU.63/grib_api/grib_api/src/grib_accessor_class_data_simple_packing.c:678
#8  0x7ffff7b0627d in pack_double
    at /scratch/ma/deploy/metabuilds/ecflow-metab_5062/ecgb/GNU.63/grib_api/grib_api/src/grib_accessor_class_data_g2simple_packing.c:206
#9  0x7ffff7b3726a in _grib_set_double_array_internal
    at /scratch/ma/deploy/metabuilds/ecflow-metab_5062/ecgb/GNU.63/grib_api/grib_api/src/grib_value.c:559
#10  0x7ffff7b3731b in _grib_set_double_array
    at /scratch/ma/deploy/metabuilds/ecflow-metab_5062/ecgb/GNU.63/grib_api/grib_api/src/grib_value.c:586
#11  0x7ffff7b373e0 in grib_set_double_array_internal
    at /scratch/ma/deploy/metabuilds/ecflow-metab_5062/ecgb/GNU.63/grib_api/grib_api/src/grib_value.c:608
#12  0x7ffff7b0ef3a in pack_double
    at /scratch/ma/deploy/metabuilds/ecflow-metab_5062/ecgb/GNU.63/grib_api/grib_api/src/grib_accessor_class_data_apply_bitmap.c:311
#13  0x7ffff7b3726a in _grib_set_double_array_internal
    at /scratch/ma/deploy/metabuilds/ecflow-metab_5062/ecgb/GNU.63/grib_api/grib_api/src/grib_value.c:559
#14  0x7ffff7b3731b in _grib_set_double_array
    at /scratch/ma/deploy/metabuilds/ecflow-metab_5062/ecgb/GNU.63/grib_api/grib_api/src/grib_value.c:586
#15  0x7ffff7b37474 in __grib_set_double_array
    at /scratch/ma/deploy/metabuilds/ecflow-metab_5062/ecgb/GNU.63/grib_api/grib_api/src/grib_value.c:679
#16  0x7ffff7deec6c in grib_f_set_real8_array_
    at /scratch/ma/deploy/metabuilds/ecflow-metab_5062/ecgb/GNU.63/grib_api/grib_api/fortran/grib_fortran.c:2619
#17  0x7ffff7df067a in __grib_api_MOD_grib_set_real8_array
    at /scratch/ma/deploy/metabuilds/ecflow-metab_5062/ecgb/GNU.63/grib_api/builds/fortran/grib_f90.f90:2953
#18  0x409733 in __rwgrib2_MOD_writelatlon
    at /home/ms/at/km4a/flex_extract_v7.1/source/fortran/rwGRIB2.f90:154
#19  0x417b61 in preconvert
    at /home/ms/at/km4a/flex_extract_v7.1/source/fortran/preconvert.f90:682
#20  0x418bf9 in main
    at /home/ms/at/km4a/flex_extract_v7.1/source/fortran/preconvert.f90:53 

and the following error while using eccodes:

ECCODES ERROR   :  Maximum value out of range: -nan
ECCODES ERROR   :  unable to compute packing parameters

ECCODES ERROR   :  unable to set double array codedValues (Encoding invalid)
ECCODES ERROR   :  set: values Encoding invalid
 readspectral:            1  records read
 readlatlon:           76  records read
STATISTICS:  97406.7212 97402.4837   908.5665
 readlatlon:           38  records read
 readlatlon:           38  records read
 readlatlon:           38  records read 
#208 fixed WRF specific files pesei mitchekc
Description

Does FLEXWRF v3.2 use the namelist.input or namelist.wps files? Should copies of these files be placed in any particular folder? Is there a FLEXWRF sub-routine that compares the meteorological fields defined in the namelist files with the field defined in the flexwrf.input file?

#207 fixed Error running FLEXPART pesei mitchekc
Description

Hi there, My job output file contains the following error text when I attempt to run FLEXPART. I don't know what the error means. I have checked the values for each variable in my flexwrf.input file and they appear to be set using the correct type. What can I do to further troubleshoot the issue?

Thank you

the input file used is flexwrf.input in the local folder of the executable

Pre-generating random numbers Calling readinput Opening ' flexwrf.input

' for reading

Reading pathnames

forrtl: severe (59): list-directed I/O syntax error, unit 1, file /project/6006014/kcmrowse/FLEX/flexpart_wrf-3.3/flexwrf.input Image PC Routine Line Source libifcoremt.so.5 00002ACB5B91CDF2 forio_return Unknown Unknown libifcoremt.so.5 00002ACB5B96582F for_read_seq_lis_ Unknown Unknown flexwrf32_intel_o 00000000004C35CA Unknown Unknown Unknown flexwrf32_intel_o 00000000004607E7 Unknown Unknown Unknown flexwrf32_intel_o 000000000040327E Unknown Unknown Unknown libc-2.24.so 00002ACB5DB8B2E0 libc_start_main Unknown Unknown flexwrf32_intel_o 000000000040317A Unknown Unknown Unknown

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 15, 2015, 7:11:51 AM
hosted by ZAMG