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:

Results (1 - 3 of 2537)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#2857 fixed win32 wndproc errors causing tray, opengl and clipboard problems Antoine Martin Antoine Martin
#2856 fixed xpra list to list client sockets Antoine Martin Antoine Martin
#2851 worksforme segfault in motion.pyx:match_distance() Ian Collier Ian Collier
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>:

[[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 2537)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#2857 fixed win32 wndproc errors causing tray, opengl and clipboard problems Antoine Martin Antoine Martin
Description

Reported privately.

  • tray:
    2020-08-05 09:26:23,843 win32NotifyIcon: app_id=0, title='Xpra'
    2020-08-05 09:26:23,843 create_tray_window()
    2020-08-05 09:26:23,843 NotifyIconWndProc(657358, 36, 0, 420183257504) instance=None, message(36)=None
    Exception ignored on calling ctypes callback function: <function NotifyIconWndProc at 0x000001e4a6be3550>
    Traceback (most recent call last):
      File "E:\Xpra\trunk\src/xpra/platform/win32/win32_NotifyIcon.py", line 480, in NotifyIconWndProc
    ctypes.ArgumentError: argument 4: <class 'OverflowError'>: int too long to convert
    2020-08-05 09:26:23,843 NotifyIconWndProc(657358, 129, 0, 420183257456) instance=None, message(129)=None
    Exception ignored on calling ctypes callback function: <function NotifyIconWndProc at 0x000001e4a6be3550>
    Traceback (most recent call last):
      File "E:\Xpra\trunk\src/xpra/platform/win32/win32_NotifyIcon.py", line 480, in NotifyIconWndProc
    ctypes.ArgumentError: argument 4: <class 'OverflowError'>: int too long to convert
    
  • clipboard:
    Exception ignored on calling ctypes callback function: <bound method Win32Clipboard.wnd_proc of ClipboardProtocolHelperCore>
    Traceback (most recent call last):
      File "E:\Xpra\trunk\src/xpra/platform/win32/clipboard.py", line 256, in wnd_proc
    ctypes.ArgumentError: argument 4: <class 'OverflowError'>: int too long to convert
    Exception ignored on calling ctypes callback function: <bound method Win32Clipboard.wnd_proc of ClipboardProtocolHelperCore>
    Traceback (most recent call last):
      File "E:\Xpra\trunk\src/xpra/platform/win32/clipboard.py", line 256, in wnd_proc
    ctypes.ArgumentError: argument 4: <class 'OverflowError'>: int too long to convert
    2020-08-05 09:26:27,338 Error: cannot instantiate <class 'xpra.platform.win32.clipboard.Win32Clipboard'>
    Traceback (most recent call last):
      File "E:\Xpra\trunk\src/xpra/client/mixins/clipboard.py", line 219, in make_clipboard_helper
      File "E:\Xpra\trunk\src/xpra/client/gtk_base/gtk_client_base.py", line 1268, in setup_clipboard_helper
      File "E:\Xpra\trunk\src/xpra/client/mixins/clipboard.py", line 315, in setup_clipboard_helper
      File "E:\Xpra\trunk\src/xpra/platform/win32/clipboard.py", line 228, in __init__
      File "E:\Xpra\trunk\src/xpra/platform/win32/clipboard.py", line 250, in init_window
    FileNotFoundError: [WinError 3] The system cannot find the path specified.
    2020-08-05 09:26:27,338 Warning: no clipboard support
    
  • opengl
    do_run_glcheck(.., False)
    get_gl_client_window_module()
    parse_padding_colors(None)=(0, 0, 0)
    increase_fraction(20, 1, 10)
    check_support() GetModuleHandleW()=0x400000
    check_support() RegisterClassExW()=0xc362
    Exception ignored on calling ctypes callback function: <function DefWndProc at 0x000001fe5f8b7af0>
    Traceback (most recent call last):
      File "E:\Xpra\trunk\src/xpra/platform/win32/gl_context.py", line 33, in DefWndProc
    ctypes.ArgumentError: argument 4: <class 'OverflowError'>: int too long to convert
    Exception ignored on calling ctypes callback function: <function DefWndProc at 0x000001fe5f8b7af0>
    Traceback (most recent call last):
      File "E:\Xpra\trunk\src/xpra/platform/win32/gl_context.py", line 33, in DefWndProc
    ctypes.ArgumentError: argument 4: <class 'OverflowError'>: int too long to convert
    check_support() CreateWindowExW()=0x0
    check_support(False)={'info': 'disabled: failed to create temporary window, The operation completed successfully.'}
    do_run_glcheck() opengl_props={'info': 'disabled: failed to create temporary window, The operation completed successfully.'}, gl_client_window_module=<module 'xpra.client.gl.gtk3.nativegl_client_window' from 'C:\\Program Files\\Xpra\\lib\\xpra\\client\\gl\\gtk3\\nativegl_client_window.pyc'>
    
#2856 fixed xpra list to list client sockets Antoine Martin Antoine Martin
Description

See #2743

#2851 worksforme segfault in motion.pyx:match_distance() Ian Collier Ian Collier
Description

I use xpra for several hours a day, and the server crashes maybe every 1-2 weeks. So this one is tricky to reproduce, and I think if I turn debugging on the log will fill up way before the crash happens. But still, when it does happen it's annoying. There also isn't anything particular I can do to trigger the crash, although my window manager (fvwm1) does weird stuff sometimes, and the crashes have tended to happen during WM operations (although one happened when I dismissed xscreensaver by pressing a key just as it was starting to engage).

The xpra version is 4.0.2 using the distro package from Fedora 32 (both client and server). The previous 3.x version of xpra seemed stable.

The crash is happening in the match_distance function of motion.pyx, here:

        for i1 in range(rstart, rend):
            i2 = i1+distance
            v = a1[i1]       <----CRASH

By analysing a core file I've managed to ascertain that 'distance' is zero, line_state is a list of 970 zero-bytes, and 'self' has the following value:

{ob_base = {ob_refcnt = 4,                                                         
    ob_type = 0x7f0f86a329e0 <__pyx_type_4xpra_6server_6window_6motion_ScrollData>}, __pyx_vtab =
    0x7f0f86a33040 <__pyx_vtable_4xpra_6server_6window_6motion_ScrollData>,                
  __weakref__ = 0x0, distances = 0x0, a1 = 0x0, a2 = 0x0, matched = 0 '\000',              
  x = 211, y = 44, width = 1542, height = 970}

So the crash is happening because self.a1 is null.

This is called from get_scroll_values() here:

            for i in reversed(sorted(scroll_hits.keys())):
                v = scroll_hits[i]
                for scroll in v:
                    #find matching lines:
                    line_defs = self.match_distance(line_state, scroll, MIN_LINE_COUNT)

It looks like 'i' is pointing to the 9th element of the sorted list when this happens, although this is difficult to say because of the various layers of translation and optimisation. The puzzle is that this function starts with

        if self.a1==NULL or self.a2==NULL:
            return None

and so self.a1 and self.a2 should be guaranteed non-null, right? So something must be nullifying them after the function has started. I have no clue as to what, because I don't actually understand the code. I am imagining that distance shouldn't really be zero here, but don't know whether that's anything to do with it. I guess the hack fix would be to return early from match_distance if a1 or a2 are null, but this wouldn't get to the root cause.

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 4 years ago Last modified on 11/23/16 15:37:19