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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#227 fixed Retrieve global ERA5 data anphi ahilboll
#225 invalid flex_extract v7.0.4 anphi anphi
#224 fixed on ecgate, ECCODES ERRORS : Maximum value out of range: inf anphi bsteil
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 156)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#227 fixed Retrieve global ERA5 data anphi ahilboll
Description

I'm having trouble retrieving hemispheric (i.e., northern hemisphere) ERA5 data using flex_extract version 7.0.4. I'm using the GATEWAY mode, i.e., I have flex_extract installed on my local system to submit jobs to the ECGATE queue.

Installation works fine, and I can retrieve non-hemispheric ERA5 data just fine. E.g., this COMMAND file works fine:

DAY1
DAY2
DTIME 1
TYPE AN AN AN AN AN AN AN AN AN AN AN AN AN AN AN AN AN AN AN AN AN AN AN AN
TIME 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23
STEP 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ACCTYPE FC
ACCTIME 06/18
ACCMAXSTEP 12
M_CLASS EA
M_STREAM OPER
M_NUMBER OFF
M_EXPVER 1
M_GRID 250  
M_LEFT -170000
M_LOWER 10000
M_UPPER 80000
M_RIGHT 170000
M_LEVELIST 1/to/137
M_RESOL 799
M_GAUSS 0
M_ACCURACY 24
M_OMEGA 0
M_OMEGADIFF 0
M_ETA 1
M_ETADIFF 0
M_DPDETA 1
M_SMOOTH 0
M_FORMAT GRIB2
M_ADDPAR /186/187/188/235/139/39
PREFIX EA
ECSTORAGE 0
ECTRANS 1
ECFSDIR ectmp:/${USER}/econdemand/
MAILOPS hilboll@uni-bremen.de
MAILFAIL hilboll@uni-bremen.de
EOF

However, this here does *not* work:

DAY1
DAY2
DTIME 1
TYPE AN AN AN AN AN AN AN AN AN AN AN AN AN AN AN AN AN AN AN AN AN AN AN AN
TIME 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23
STEP 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ACCTYPE FC
ACCTIME 06/18
ACCMAXSTEP 12
M_CLASS EA
M_STREAM OPER
M_NUMBER OFF
M_EXPVER 1
M_GRID 250  
M_LEFT -180000
M_LOWER 00000
M_UPPER 90000
M_RIGHT 180000
M_LEVELIST 1/to/137
M_RESOL 799
M_GAUSS 0
M_ACCURACY 24
M_OMEGA 0
M_OMEGADIFF 0
M_ETA 1
M_ETADIFF 0
M_DPDETA 1
M_SMOOTH 0
M_FORMAT GRIB2
M_ADDPAR /186/187/188/235/139/39
PREFIX EA
ECSTORAGE 0
ECTRANS 1
ECFSDIR ectmp:/${USER}/econdemand/
MAILOPS hilboll@uni-bremen.de
MAILFAIL hilboll@uni-bremen.de
EOF

I tried already different left/right combinations, like -180/180, -179750/180, -180/179750, -179875/179875, and the like.

The error message I'm getting is this:

Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

Backtrace for this error:
#0  0x3dd543250f in ???
#1  0x3dd54896f6 in ???
#2  0x40a1c5 in __rwgrib2_MOD_readlatlon
	at /home/ms/datex/gdmv/flexpart/scripts_gateway/flex_extract_v7.0.4/src/rwGRIB2.f90:72
#3  0x41240b in preconvert
	at /home/ms/datex/gdmv/flexpart/scripts_gateway/flex_extract_v7.0.4/src/preconvert.f90:402
#4  0x418c6d in main
	at /home/ms/datex/gdmv/flexpart/scripts_gateway/flex_extract_v7.0.4/src/preconvert.f90:53
#225 invalid flex_extract v7.0.4 anphi anphi
Description

Dear FLEXPART users,

we prepared a bugfix version for flex_extract v7.0.3 used for retrieving ECMWF input data for FLEXPART. This was necessary since there were errors in ERA5 and CERA retrievals. Also, there were some other problems.

NEW FEATURES:

  • This version can now retrieve ERA5 and CERA data.
  • It can retrieve public datasets by using the command line parameter public
  • It can write an extra file mars_requests.csv which contains all mars request parameters for each request. Use the command line pararmeter request
  • It can retrieve analysis and forecast ensembles efficiently e.g. by setting number=0/to/9. In this case output files get an additional suffix for the ensemble member number.

MODULE PACKAGE CONDITIONS:

On ecgate we use the following module packages:

  • jasper/1.900.1(default)
  • eccodes/2.9.2(nov18:default)
  • ecfs/2.2.5(nov18:test:new:prodn:default)
  • python/2.7.12-01(may18:new:default)
  • ecaccess/4.0.2(default)
  • fftw/3.3.4(default)
  • emos/455-r64

Please be aware that all of the above packages are the current default versions except for emos! This is important since emos/458 does not work!

DOWNLOAD

The tarball that includes a Software Installation Protocol and a Software User Tutorial can be downloaded here flex_extract v7.0.4

With best regards,

Anne Philipp and Leopold Haimberger

#224 fixed on ecgate, ECCODES ERRORS : Maximum value out of range: inf anphi bsteil
Description

Dear Flex_EXTRACT developers or users,

I'm trying to extract fields at ECMWF on ecgate. flex_extract_v7.0.4 or flex_extract_v7.0.3 always produce the same error:

ECCODES ERROR   :  Maximum value out of range: inf.

This happens, when submit.py executes prepareFLEXPART.py. The downloading of the data from MARS archive works without problems. The error Maximum value out of range: inf also occurs, if I use the module grip_api instead of eccodes. What I'm doing wrong?

My installation process : I have installed flex_extract_v7.0.4 directly on ecgate and I directly execute it there. The gfortran I'm using is: /usr/local/apps/gcc/6.3.0/bin/gfortran

I have loaded the required modules in this order: python 2.7.12-01 , jasper 1.900.1 , eccodes 2.9.2 , fftw 3.3.4 , emos 458

I have compiled the code in the subdirectory python with: ./install.py --target=local --makefile=Makefile.gfortran Compilation is successful, no problems, no warnings here.

After inserting DAY1 20180711 and DAY2 20180711 in CONTROL.temp, I run the model on ecgate with following command:

./submit.py --controlfile CONTROL.temp --inputdir /scratch/ms/datex/dw0/FLEXPART/INPUT --outputdir / scratch/ms/datex/dw0/FLEXPART/OUTPUT

After the successful download of the data from MARS-archive and the creation of a lot of flux and fort files the process crashes with the following error message:

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

ECCODES ERROR   :  unable to set double array codedValues (Encoding invalid)
ECCODES ERROR   :  set: values Encoding invalid
Traceback (most recent call last):
  File "./submit.py", line 115, in <module>
    main()
  File "./submit.py", line 59, in main
    prepareFLEXPART(args,c)
  File "/home/ms/datex/dw0/FLEXPART/flex_extract_v7.0.4/flex_extract/python/prepareFLEXPART.py", line  96, in prepareFLEXPART    flexpart.create(inputfiles, c) # produce FLEXPART-ready GRIB files
  File "/home/ms/datex/dw0/FLEXPART/flex_extract_v7.0.4/flex_extract/python/FlexpartTools.py", line    1468, in create
    p=subprocess.check_call([os.path.expandvars(os.path.expanduser(c.exedir))+'/CONVERT2'],shell=True)
  File "/usr/local/apps/python/2.7.12-01/lib/python2.7/subprocess.py", line 541, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/home/ms/datex/dw0/FLEXPART/flex_extract_v7.0.4/flex_extract/python/../src//CONVERT2']' returned non-zero exit status 242

The same happens using flex_extract_v7.0.3. I have also tested other control files. Always the same error.

Thank you very much, with kind regards,

Benedikt Steil

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