xpra icon
Bug tracker and wiki

Trac Ticket Queries

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 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 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.

Some shortcuts can be used to manipulate checkbox filters.

  • Clicking on a filter row label toggles all checkboxes.
  • Pressing the modifier key while clicking on a filter row label inverts the state of all checkboxes.
  • Pressing the modifier key while clicking on a checkbox selects the checkbox and deselects all other checkboxes in the filter.

The modifier key is platform and browser dependent. On Mac the modified key is Option/Alt or Command. On Linux the modifier key is Ctrl + Alt. Opera on Windows seems to use Ctrl + Alt, while Alt is effective for other Windows browsers.

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

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:

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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#1769 fixed Getting Occasional OpenGL Tracebacks J. Max Mena J. Max Mena
Description

My server and client are both Fedora 26 machines running trunk r18446 built from source.

My client machine has an Nvidia GPU (a GTX 745 to be specific), and occasionally I will get this traceback (usually while running Firefox - as far as I can tell it's not specific to any sites, I've gotten it on Wikipedia before). Normally I frown upon writing "Weird errors in the logs" tickets without thoroughly understanding what's going on first, but OpenGL isn't my forte and usually when I see this traceback in the log the paints go a little weird. The last couple times I saw it, Firefox stopped painting altogether until I re-attached.

Here's the traceback:

2018-02-16 11:21:28,675  flush=2, image=ImageWrapper(YUV420P:(0, 0, 1244, 1, 24):PACKED), coords=(0, 325, 1244, 1), size=1244x1
2018-02-16 12:49:45,405 Error painting planar update
Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/xpra/client/gl/gl_window_backing_base.py", line 988, in gl_paint_planar
    self.update_planar_textures(x, y, enc_width, enc_height, img, pixel_format, scaling=(enc_width!=width or enc_height!=height))
  File "/usr/lib64/python2.7/site-packages/xpra/client/gl/gl_window_backing_base.py", line 1054, in update_planar_textures
    glTexSubImage2D(target, 0, 0, 0, width//div_w, height//div_h, GL_LUMINANCE, GL_UNSIGNED_BYTE, pixel_data)
  File "latebind.pyx", line 32, in OpenGL_accelerate.latebind.LateBind.__call__ (src/latebind.c:989)
  File "wrapper.pyx", line 318, in OpenGL_accelerate.wrapper.Wrapper.__call__ (src/wrapper.c:6561)
GLError: GLError(
	err = 1281,
	description = 'invalid value',
	baseOperation = glTexSubImage2D,
	pyArgs = (
		GL_TEXTURE_RECTANGLE_ARB,
		0,
		0,
		0,
		622,
		0,
		GL_LUMINANCE,
		GL_UNSIGNED_BYTE,
		<memory at 0x7f914813c938>,
	),
	cArgs = (
		GL_TEXTURE_RECTANGLE_ARB,
		0,
		0,
		0,
		622,
		0,
		GL_LUMINANCE,
		GL_UNSIGNED_BYTE,
		<memory at 0x7f914813c938>,
	),
	cArguments = (
		GL_TEXTURE_RECTANGLE_ARB,
		0,
		0,
		0,
		622,
		0,
		GL_LUMINANCE,
		GL_UNSIGNED_BYTE,
		<memory at 0x7f914813c938>,
	)
)
2018-02-16 12:49:45,406  flush=0, image=ImageWrapper(YUV420P:(0, 0, 1244, 1, 24):PACKED), coords=(0, 547, 1244, 1), size=1244x1
#1768 invalid Replace CODEC_FLAG2_FAST with AV_CODEC_FLAG2_FAST Antoine Martin Leo Izen
Description

FFmpeg replaced CODEC_FLAG2_FAST with AV_CODEC_FLAG2_FAST two years ago and left CODEC_FLAG2_FAST as a deprecated alias. This deprecated alias has finally been removed two years later, so it needs to be switched over to AV_CODEC_FLAG2_FAST or Xpra won't compile with a recent version of FFmpeg. This doesn't break compatibility with stable systems, since AV_CODEC_FLAG2_FAST has existed for more than two years. This change was already made in the Xpra codebase for CODEC_ID_H264 -> AV_CODEC_ID_H264 and similar changes, but not for AV_CODEC_FLAG2_FAST.

#1766 fixed no longer control encoding in config file (macos/OS X client) sto6 sto6
Description

Using macOS-10.13.3 client to display a linux (centos 6.6 or 6.9) server, mode=ssh exclusively. Previously while using client Xpra 2.0.2, my client config file could specify encoding=rgb (and it worked). After upgrading to client 2.2.4, same file yields encoding of auto (checked while connection is active).

The goal is (as worked using 2.0.2), to start the client-GUI with a predefined config file, and just hit Connect (without editing any GUI fields) and achieve encoding=rgb. The GUI is capable of achieving encoding=rgb, but incapable (it seems now) of saving a config file to reproduce same. I have not tried if explicitly assigning other encodings do work (i.e. it may not be specific to only rgb).

  1. Issue persists in both server (linux) versions I've tried: xpra v1.0.6-r15846, xpra v1.0.9-r17257
  2. Using the launcher GUI, I can hit "Advanced Encoding Options" and play with it (change to other than Raw RGB..., then change back), and then hit Connect and thereby sometimes achieve encoding=rgb (checked while connection is active).
  3. In the server log when it's working I see: "using rgb as primary encoding" instead of "automatic picture encoding enabled". Also the client menu's Encoding item (while connected) confirms same: either automatic (it failed) or "Raw RGB..." (it works) has a check-mark.

Because of above #1-3 I conclude it's a client-specific issue. It demos the server is still capable of rgb. But I did not nail down an exact 100% reliable way to "play" with advanced enc. options to always achieve the rbg. And every time I think I found a play-sequence that works, if I repeat same but Save those settings to a file (instead of Connect), then try and launch from that file, it returns to encoding=auto.

I also tried to explore many variations in the config file just using an editor (including encoding=rgb24, or rgb32), with no success. Somehow I thought perhaps omitting quality=... or some special value of quality (0, -1, 100, auto, Auto, none...) might get it to work, but no success yet. Note when you play with advanced enc. options, select other encodings, then reselect original desired encoding, often the initially displayed speed=Auto, quality=Auto GUI fields don't both come back (i.e. quality tends to be omitted; prob. unrelated issue, though it was leading me to try to drop quality or define it "specially" in the config file).

From a client terminal I can reproduce the problem this way:

% open /Applications/Xpra.app myconfig.xpra

but if I start it this way it works (gives rgb):

% /Applications/Xpra.app/Contents/MacOS/Launcher myconfig.xpra

I've associated (in macos Finder) the Xpra.app as the app to "open-with" for files of type *.xpra. Maybe that was a mistake, and I need to figure out how to associate them with the path to the .../Launcher instead (though the app worked in 2.0.2)? When I use above Launcher the GUI window is initially iconified (I want it either open instead of iconified, as the app does; or an option to tell .../Launcher to just auto-Connect: by-pass the GUI). (Also unrelated, I didn't find the way yet to start multiple unrelated Xpra clients). Thanks.

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. 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

Last modified 15 months ago Last modified on 11/23/16 15:37:19