Version 2 (modified by trac, 2 years ago) ( diff )

--

TicketQuery Wiki Macro

The TicketQuery macro lets you display ticket information anywhere that accepts WikiFormatting. The query language used by the [[TicketQuery]] macro is described in the TracQuery page.

Usage

[[TicketQuery]]

Wiki macro listing tickets that match certain criteria.

This macro accepts a comma-separated list of keyed parameters, in the form "key=value".

If the key is the name of a field, the value must use the syntax of a filter specifier as defined in TracQuery#QueryLanguage. Note that this is not the same as the simplified URL syntax used for query: links starting with a ? character. Commas (,) can be included in field values by escaping them with a backslash (\).

Groups of field constraints to be OR-ed together can be separated by a literal or argument.

In addition to filters, several other named parameters can be used to control how the results are presented. All of them are optional.

The format parameter determines how the list of tickets is presented:

  • list -- the default presentation is to list the ticket ID next to the summary, with each ticket on a separate line.
  • compact -- the tickets are presented as a comma-separated list of ticket IDs.
  • count -- only the count of matching tickets is displayed
  • rawcount -- only the count of matching tickets is displayed, not even with a link to the corresponding query (since 1.1.1)
  • table -- a view similar to the custom query view (but without the controls)
  • progress -- a view similar to the milestone progress bars

The max parameter can be used to limit the number of tickets shown (defaults to 0, i.e. no maximum).

The order parameter sets the field used for ordering tickets (defaults to id).

The desc parameter indicates whether the order of the tickets should be reversed (defaults to false).

The group parameter sets the field used for grouping tickets (defaults to not being set).

The groupdesc parameter indicates whether the natural display order of the groups should be reversed (defaults to false).

The verbose parameter can be set to a true value in order to get the description for the listed tickets. For table format only. deprecated in favor of the rows parameter

The rows parameter can be used to specify which field(s) should be viewed as a row, e.g. rows=description|summary

The col parameter can be used to specify which fields should be viewed as columns. For table format only.

For compatibility with Trac 0.10, if there's a last positional parameter given to the macro, it will be used to specify the format. Also, using "&" as a field separator still works (except for order) but is deprecated.

Examples

Example Result Macro
Number of Triage tickets: 523 [[TicketQuery(status=new&milestone=,count)]]
Number of new tickets: 523 [[TicketQuery(status=new,count)]]
Number of reopened tickets: 0 [[TicketQuery(status=reopened,count)]]
Number of assigned tickets: 543 [[TicketQuery(status=assigned,count)]]
Number of invalid tickets: 5306 [[TicketQuery(status=closed,resolution=invalid,count)]]
Number of worksforme tickets: 1089 [[TicketQuery(status=closed,resolution=worksforme,count)]]
Number of duplicate tickets: 4423 [[TicketQuery(status=closed,resolution=duplicate,count)]]
Number of wontfix tickets: 4254 [[TicketQuery(status=closed,resolution=wontfix,count)]]
Number of fixed tickets: 19134 [[TicketQuery(status=closed,resolution=fixed,count)]]
Number of untriaged tickets (milestone unset): 1066 [[TicketQuery(status!=closed,milestone=,count)]]
Total number of tickets: 36282 [[TicketQuery(count)]]
Number of tickets reported or owned by current user: 1488 [[TicketQuery(reporter=$USER,or,owner=$USER,count)]]
Number of tickets created this month: 52 [[TicketQuery(created=thismonth..,count)]]
Number of closed Firefox tickets: 8 [[TicketQuery(status=closed,keywords~=firefox,count)]]
Number of closed Opera tickets: 26 [[TicketQuery(status=closed,keywords~=opera,count)]]
Number of closed tickets affecting Firefox and Opera: 0 [[TicketQuery(status=closed,keywords~=firefox opera,count)]]
Number of closed tickets affecting Firefox or Opera: 34 [[TicketQuery(status=closed,keywords~=firefox|opera,count)]]
Number of tickets that affect Firefox or are closed and affect Opera: 34 [[TicketQuery(status=closed,keywords~=opera,or,keywords~=firefox,count)]]
Number of closed Firefox tickets that don't affect Opera: 0 [[TicketQuery(status=closed,keywords~=firefox -opera,count)]]
Last 3 modified tickets: #37069, #35857, #37068 [[TicketQuery(max=3,order=modified,desc=1,compact)]]

Details of ticket #1:

[[TicketQuery(id=1,col=id|owner|reporter,rows=summary,table)]]

Ticket Owner Reporter
#1 Jacob Adrian Holovaty
Summary Create architecture for anonymous sessions

Format: list

[[TicketQuery(version=0.6|0.7&resolution=duplicate)]]

This is displayed as:

No results 

[[TicketQuery(id=123)]]

This is displayed as:

#123
Typo in the model_api/#field-types

Format: compact

[[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]]

This is displayed as:

No results

Format: count

[[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]]

This is displayed as:

0

Format: progress

[[TicketQuery(milestone=0.12.8&group=type,format=progress)]]

This is displayed as:

Uncategorized

2044 / 2044
Bug

10564 / 10924
New feature

3865 / 4253
Cleanup/optimization

5528 / 5845

Format: table

You can choose the columns displayed in the table format (format=table) using col=<field>. You can specify multiple fields and the 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 specify full rows 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 35216)

1 2 3 4 5 6 7 8 9 10 11 →
Ticket Resolution Summary Owner Reporter
#37064 invalid SimpleTestCase._remove_databases_failures() crashes on un-wrapped connection methods Rio Weber
Description

Re-filing #36942 - got closed for lack of a repro, I have one

TLDR: _remove_databases_failures blindly does method.wrapped on every connection method it visits. If the method isn't a _DatabaseFailure at that point (e.g. SQLite recycled the connection between setUpClass and tearDownClass, or the class's databases set changed after setup), teardown dies with AttributeError: 'function' object has no attribute 'wrapped'.

Repro, traceback, one-line fix (isinstance guard), and two regression tests below. Verified on 6.0.3 and on main @ 526b548c (that commit touches auth/backends.py, not test/testcases.py).

Note: between 6.0.3 and main, the list of disallowed connection methods moved from a SimpleTestCase class attribute to connection.features.disallowed_simple_test_case_connection_methods. Orthogonal to the bug - both branches still blindly access method.wrapped - but the patch surface differs slightly per branch.

Minimal repro

settings.py: 

DATABASES = {
    "default": {"ENGINE": "django.db.backends.sqlite3", "NAME": BASE_DIR / "db.sqlite3"},
    "shard_b": {"ENGINE": "django.db.backends.sqlite3", "NAME": BASE_DIR / "db_shard_b.sqlite3"},
}

tests/test_repro.py: 

from django.test import TransactionTestCase

class ReproTests(TransactionTestCase):
    # Implicit databases = {"default"} - shard_b is NOT declared
    def test_anything(self):
        assert True

Run under pytest-django; the test body doesn't need to touch the DB: 

pytest tests/test_repro.py

Traceback (abridged) 

.../django/test/testcases.py:280
    in _remove_databases_failures
        setattr(connection, name, method.wrapped)
                                  ^^^^^^^^^^^^^^
AttributeError: 'function' object has no attribute 'wrapped'

Root cause

_add_databases_failures installs _DatabaseFailure wrappers; _remove_databases_failures assumes every method it iterates is still one. That symmetry breaks most often because the SQLite backend replaces connection objects between setUpClass and tearDownClass the new connection has fresh, un-wrapped methods. Also reproducible if a subclass/fixture mutates cls.databases after setup or if a class skipped super().setUpClass() but still inherits the addClassCleanup

Proposed fix

Add an isinstance guard so teardown only touches what setup installed. On main: 

@classmethod
def _remove_databases_failures(cls):
    for alias in connections:
        if alias in cls.databases:
            continue
        connection = connections[alias]
        disallowed_methods = (
            connection.features.disallowed_simple_test_case_connection_methods
        )
        for name, _ in disallowed_methods:
            method = getattr(connection, name)
            if isinstance(method, _DatabaseFailure):
                setattr(connection, name, method.wrapped)

Backport for stable/6.0.x is identical except the iteration source stays cls._disallowed_connection_methods

isinstance is preferable to the hasattr("wrapped") approach in #20758 because it only unwraps Django's own wrapper class and won't chase third-party objects that happen to expose .wrapped

Regression tests

Two tests both scoped to teardown:

  • test_teardown_noops_when_method_is_not_wrapped - replaces a connection method with a plain function and asserts _remove_databases_failures does not raise.
  • test_teardown_still_unwraps_database_failures - installs a _DatabaseFailure manually and asserts it is restored

Full source attached as a patch

Related

  • #36942 (closed needsinfo) - same bug, no reprodce
  • ​PR #20758 by Michele Fiori uses a hasattr guard; happy to rebase onto isinstance + tests or open a fresh PR crediting the original author
#37063 duplicate PicklingError: Can't pickle Task Johannes Maron
Description

Hi there,

I am working on Django tasks executor and noticed that the current implementation has a few oddities and bugs that we might want to address in future releases.

For now, let's focus on the biggest one, Tasks, and therefore TasksResults can't be pickled. However, it is essential to use multiprocessing and to utilize the entire CPU to execute tasks. 

Traceback (most recent call last):
  File "<console>", line 1, in <module>
  File "$HOME/.local/share/uv/python/cpython-3.14.0-macos-aarch64-none/lib/python3.14/multiprocessing/reduction.py", line 51, in dumps
    cls(buf, protocol).dump(obj)
    ~~~~~~~~~~~~~~~~~~~~~~~^^^^^
_pickle.PicklingError: Can't pickle <function cpu_heavy_task at 0x10986eae0>: it's not the same object as tests.testapp.tasks.cpu_heavy_task

Of course, you can serialize and deserialize objects yourself, but that's a pretty high bar to clear. Especially since it's a fairly easy fix for Django.

Cheers! Joe

#37059 wontfix `.only(..)` does not check eagerly if the fields exists Yujin Kim Willem Van Onsem
Description

Django's QuerySets are lazy, but the checks for (most) methods are eagerly, I think. For example: 

us = User.objects.filter(bla='qux')

will raise an error.

But only(..) seems to be an exception on this. If we use: 

us = User.objects.only('bla')

it will only raise if we evaluate us (enumerate, aggregate, str/len/...).

It seems nice that .only(..) would check eagerly if the fields are available, otherwise tests might succeed if the queryset is in some cases not evaluated.

A possible problem might be that .only(..) could strictly speaking mention fields that are not *yet* defined, but later in the chain of ORM method calls.

1 2 3 4 5 6 7 8 9 10 11 →

See also: TracQuery, TracTickets, TracReports

Note: See TracWiki for help on using the wiki.
Back to Top