wiki:TracQuery

Version 3 (modified by trac, 6 years ago) (diff)

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:

No results

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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#2669 worksforme stopping https tunnel will lead to stopping http tunnel anonymous maybe
#2662 fixed I2PSnark opens tunnels at startup when no torrents are running zzz Reportage
#2661 fixed PeerState.java: remove _currentReceiveSecond zzz jogger
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 1845)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#2669 worksforme stopping https tunnel will lead to stopping http tunnel anonymous maybe
Description

i went to http://127.0.0.1:7657/i2ptunnelmgr and i stopped https tunnel since it doesnt provide any further usability but when i turned it off , http tunnel also went off. Not sure if its related but here is my logs:

  • I2P Version and Running Environment
I2P version:	0.9.43-0-1~disco+1
Java version:	Debian 11.0.5 (OpenJDK Runtime Environment 11.0.5+10-post-Debian-1deb10u1)
Wrapper version:	3.5.30
Server version:	9.4.15.v20190215
Servlet version:	Jasper JSP 2.3 Engine
JSTL version:	standard-taglib 1.2.5
Platform:	Linux amd64 4.19.81-1.pvops.qubes.x86_64
Processor:	Haswell Core i3/i5/i7 model 60 (coreihwl)
JBigI status:	Locally optimized library libjbigi-linux-coreihwl_64.so loaded from file
GMP version:	6.1.2
JBigI version:	4
JCpuId version:	3
Encoding:	UTF-8
Charset:	UTF-8
Built By:	Undefined
  • Critical Logs (all red color)
    Nov 19, 2019, 10:15:11 PM CRIT [JobQueue 3/5] net.i2p.router.JobQueueRunner : Error processing job [Outbound client message delayed send] on thread 2: java.lang.IllegalArgumentException: Bad public key type ECIES_X25519
         java.lang.IllegalArgumentException: Bad public key type ECIES_X25519
         at net.i2p.router.crypto.TransientSessionKeyManager.createAndReturnSession(TransientSessionKeyManager.java:333)
         at net.i2p.router.crypto.TransientSessionKeyManager.getCurrentOrNewKey(TransientSessionKeyManager.java:303)
         at net.i2p.router.message.GarlicMessageBuilder.buildMessage(GarlicMessageBuilder.java:151)
         at net.i2p.router.message.OutboundClientMessageJobHelper.createGarlicMessage(OutboundClientMessageJobHelper.java:126)
         at net.i2p.router.message.OutboundClientMessageOneShotJob.send(OutboundClientMessageOneShotJob.java:639)
         at net.i2p.router.message.OutboundClientMessageOneShotJob.access$300(OutboundClientMessageOneShotJob.java:105)
         at net.i2p.router.message.OutboundClientMessageOneShotJob$SendJob.runJob(OutboundClientMessageOneShotJob.java:365)
         at net.i2p.router.JobQueueRunner.runCurrentJob(JobQueueRunner.java:110)
         at net.i2p.router.JobQueueRunner.run(JobQueueRunner.java:66)
    Nov 19, 2019, 10:36:47 PM CRIT [JobQueue 4/5] net.i2p.router.JobQueueRunner : Error processing job [Outbound client message delayed send] on thread 3: java.lang.IllegalArgumentException: Bad public key type ECIES_X25519
         java.lang.IllegalArgumentException: Bad public key type ECIES_X25519
         at net.i2p.router.crypto.TransientSessionKeyManager.createAndReturnSession(TransientSessionKeyManager.java:333)
         at net.i2p.router.crypto.TransientSessionKeyManager.getCurrentOrNewKey(TransientSessionKeyManager.java:303)
         at net.i2p.router.message.GarlicMessageBuilder.buildMessage(GarlicMessageBuilder.java:151)
         at net.i2p.router.message.OutboundClientMessageJobHelper.createGarlicMessage(OutboundClientMessageJobHelper.java:126)
         at net.i2p.router.message.OutboundClientMessageOneShotJob.send(OutboundClientMessageOneShotJob.java:639)
         at net.i2p.router.message.OutboundClientMessageOneShotJob.access$300(OutboundClientMessageOneShotJob.java:105)
         at net.i2p.router.message.OutboundClientMessageOneShotJob$SendJob.runJob(OutboundClientMessageOneShotJob.java:365)
         at net.i2p.router.JobQueueRunner.runCurrentJob(JobQueueRunner.java:110)
         at net.i2p.router.JobQueueRunner.run(JobQueueRunner.java:66)
    Nov 19, 2019, 10:36:52 PM CRIT [nal Reader 5] 2p.data.i2cp.I2CPMessageReader: Uncaught I2CP error
         java.lang.IllegalArgumentException: Bad public key type ECIES_X25519
         at net.i2p.router.crypto.TransientSessionKeyManager.createAndReturnSession(TransientSessionKeyManager.java:333)
         at net.i2p.router.crypto.TransientSessionKeyManager.getCurrentOrNewKey(TransientSessionKeyManager.java:303)
         at net.i2p.router.message.GarlicMessageBuilder.buildMessage(GarlicMessageBuilder.java:151)
         at net.i2p.router.message.OutboundClientMessageJobHelper.createGarlicMessage(OutboundClientMessageJobHelper.java:126)
         at net.i2p.router.message.OutboundClientMessageOneShotJob.send(OutboundClientMessageOneShotJob.java:639)
         at net.i2p.router.message.OutboundClientMessageOneShotJob.access$300(OutboundClientMessageOneShotJob.java:105)
         at net.i2p.router.message.OutboundClientMessageOneShotJob$SendJob.runJob(OutboundClientMessageOneShotJob.java:365)
         at net.i2p.router.message.OutboundClientMessageOneShotJob.runJob(OutboundClientMessageOneShotJob.java:305)
         at net.i2p.router.ClientMessagePool.add(ClientMessagePool.java:77)
         at net.i2p.router.client.ClientManager.distributeMessage(ClientManager.java:472)
         at net.i2p.router.client.ClientConnectionRunner.distributeMessage(ClientConnectionRunner.java:735)
         at net.i2p.router.client.ClientMessageEventListener.handleSendMessage(ClientMessageEventListener.java:451)
         at net.i2p.router.client.ClientMessageEventListener.messageReceived(ClientMessageEventListener.java:131)
         at net.i2p.internal.QueuedI2CPMessageReader$QueuedI2CPMessageReaderRunner.run2(QueuedI2CPMessageReader.java:56)
         at net.i2p.data.i2cp.I2CPMessageReader$I2CPMessageReaderRunner.run(I2CPMessageReader.java:164)
         at java.base/java.lang.Thread.run(Thread.java:834)
         at net.i2p.util.I2PThread.run(I2PThread.java:103)

  • Router Logs
    Nov 19, 2019, 10:45:27 PM DEBUG [t Runner 108] .i2ptunnel.I2PTunnelHTTPClient: Before selecting outproxy for location.services.mozilla.com:443
    Nov 19, 2019, 10:45:27 PM DEBUG [t Runner 108] .i2ptunnel.I2PTunnelHTTPClient: After selecting outproxy for location.services.mozilla.com:443: null
    Nov 19, 2019, 10:45:27 PM WARN [t Runner 108] .i2ptunnel.I2PTunnelHTTPClient: No outproxy configured for request: https://location.services.mozilla.com:443/
    Nov 19, 2019, 10:45:27 PM DEBUG [t Runner 108] .i2ptunnel.I2PTunnelHTTPClient: HTTPClient[3/126]: Line=[CONNECT firefox.settings.services.mozilla.com:443 HTTP/1.1]
    Nov 19, 2019, 10:45:27 PM DEBUG [t Runner 108] .i2ptunnel.I2PTunnelHTTPClient: HTTPClient[3/126]: First line [CONNECT firefox.settings.services.mozilla.com:443 HTTP/1.1]
    Nov 19, 2019, 10:45:27 PM DEBUG [t Runner 108] .i2ptunnel.I2PTunnelHTTPClient: Before selecting outproxy for firefox.settings.services.mozilla.com:443
    Nov 19, 2019, 10:45:27 PM DEBUG [t Runner 108] .i2ptunnel.I2PTunnelHTTPClient: After selecting outproxy for firefox.settings.services.mozilla.com:443: null
    Nov 19, 2019, 10:45:27 PM WARN [t Runner 108] .i2ptunnel.I2PTunnelHTTPClient: No outproxy configured for request: https://firefox.settings.services.mozilla.com:443/
    Nov 19, 2019, 10:45:28 PM DEBUG [t Runner 108] .i2ptunnel.I2PTunnelHTTPClient: HTTPClient[3/127]: Line=[CONNECT firefox.settings.services.mozilla.com:443 HTTP/1.1]
    Nov 19, 2019, 10:45:28 PM DEBUG [t Runner 108] .i2ptunnel.I2PTunnelHTTPClient: HTTPClient[3/127]: First line [CONNECT firefox.settings.services.mozilla.com:443 HTTP/1.1]
    Nov 19, 2019, 10:45:28 PM DEBUG [t Runner 108] .i2ptunnel.I2PTunnelHTTPClient: Before selecting outproxy for firefox.settings.services.mozilla.com:443
    Nov 19, 2019, 10:45:28 PM DEBUG [t Runner 108] .i2ptunnel.I2PTunnelHTTPClient: After selecting outproxy for firefox.settings.services.mozilla.com:443: null
    Nov 19, 2019, 10:45:28 PM WARN [t Runner 108] .i2ptunnel.I2PTunnelHTTPClient: No outproxy configured for request: https://firefox.settings.services.mozilla.com:443/
    Nov 19, 2019, 10:45:28 PM DEBUG [t Runner 108] .i2ptunnel.I2PTunnelHTTPClient: HTTPClient[3/128]: Line=[CONNECT shavar.services.mozilla.com:443 HTTP/1.1]
    Nov 19, 2019, 10:45:28 PM DEBUG [t Runner 108] .i2ptunnel.I2PTunnelHTTPClient: HTTPClient[3/128]: First line [CONNECT shavar.services.mozilla.com:443 HTTP/1.1]
    Nov 19, 2019, 10:45:28 PM DEBUG [t Runner 108] .i2ptunnel.I2PTunnelHTTPClient: Before selecting outproxy for shavar.services.mozilla.com:443
    Nov 19, 2019, 10:45:28 PM DEBUG [t Runner 108] .i2ptunnel.I2PTunnelHTTPClient: After selecting outproxy for shavar.services.mozilla.com:443: null
    Nov 19, 2019, 10:45:28 PM WARN [t Runner 108] .i2ptunnel.I2PTunnelHTTPClient: No outproxy configured for request: https://shavar.services.mozilla.com:443/
    Nov 19, 2019, 10:46:32 PM ERROR [Queue Pumper] net.i2p.router.JobQueue : Job ReadJob: Job 19: DB Read Job out of order with job TestJob: Job 515525: Test tunnel difference of 75s
    Nov 19, 2019, 10:46:38 PM WARN [Reseed ] uter.networkdb.reseed.Reseeder: EepGet failed on https://download.xxlspeed.com/i2pseeds.su3?netid=2 : java.net.ConnectException: Connection timed out (Connection timed out)

  • Service (Wrapper) Logs
2019/11/19 16:30:02 | Reseeding from https://i2pseed.creativecowpat.net:8443/i2pseeds.su3?netid=2
2019/11/19 16:30:04 | INFO: 77 files extracted to /tmp/i2p-oPmYxBOF.tmp/reseeds-648232905
2019/11/19 16:30:04 | Reseed got 77 router infos from https://i2pseed.creativecowpat.net:8443/i2pseeds.su3?netid=2 with 0 errors
2019/11/19 16:30:04 | Reseed successful, fetched 143 router infos
2019/11/19 18:00:04 | Reseed start
2019/11/19 18:00:04 | Reseeding from https://netdb.i2p2.no/i2pseeds.su3?netid=2
2019/11/19 18:00:08 | INFO: 75 files extracted to /tmp/i2p-oPmYxBOF.tmp/reseeds-20597842
2019/11/19 18:00:08 | Reseed got 75 router infos from https://netdb.i2p2.no/i2pseeds.su3?netid=2 with 0 errors
2019/11/19 18:00:08 | Reseeding from https://i2p.mooo.com/netDb/i2pseeds.su3?netid=2
2019/11/19 18:00:10 | INFO: 49 files extracted to /tmp/i2p-oPmYxBOF.tmp/reseeds-659012952
2019/11/19 18:00:10 | Reseed got 49 router infos from https://i2p.mooo.com/netDb/i2pseeds.su3?netid=2 with 0 errors
2019/11/19 18:00:10 | Reseed successful, fetched 124 router infos
2019/11/19 19:30:10 | Reseed start
2019/11/19 19:30:10 | Reseeding from https://reseed.memcpy.io/i2pseeds.su3?netid=2
2019/11/19 19:30:12 | INFO: 77 files extracted to /tmp/i2p-oPmYxBOF.tmp/reseeds-297914628
2019/11/19 19:30:12 | Reseed got 77 router infos from https://reseed.memcpy.io/i2pseeds.su3?netid=2 with 0 errors
2019/11/19 19:30:12 | Reseeding from https://netdb.i2p2.no/i2pseeds.su3?netid=2
2019/11/19 19:30:13 | INFO: 75 files extracted to /tmp/i2p-oPmYxBOF.tmp/reseeds-214463758
2019/11/19 19:30:13 | Reseed got 75 router infos from https://netdb.i2p2.no/i2pseeds.su3?netid=2 with 0 errors
2019/11/19 19:30:13 | Reseed successful, fetched 152 router infos
2019/11/19 21:00:13 | Reseed start
2019/11/19 21:00:13 | Reseeding from https://i2p.mooo.com/netDb/i2pseeds.su3?netid=2
2019/11/19 21:00:14 | INFO: 49 files extracted to /tmp/i2p-oPmYxBOF.tmp/reseeds-607057824
2019/11/19 21:00:14 | Reseed got 49 router infos from https://i2p.mooo.com/netDb/i2pseeds.su3?netid=2 with 0 errors
2019/11/19 21:00:14 | Reseeding from https://i2pseed.creativecowpat.net:8443/i2pseeds.su3?netid=2
2019/11/19 21:00:16 | INFO: 77 files extracted to /tmp/i2p-oPmYxBOF.tmp/reseeds-905322061
2019/11/19 21:00:16 | Reseed got 77 router infos from https://i2pseed.creativecowpat.net:8443/i2pseeds.su3?netid=2 with 0 errors
2019/11/19 21:00:16 | Reseed successful, fetched 126 router infos
2019/11/19 22:15:37 | CRIT  [JobQueue 3/5] net.i2p.router.JobQueueRunner : Error processing job [Outbound client message delayed send] on thread 2: java.lang.IllegalArgumentException: Bad public key type ECIES_X25519
2019/11/19 22:15:37 | java.lang.IllegalArgumentException: Bad public key type ECIES_X25519
2019/11/19 22:15:37 | 	at net.i2p.router.crypto.TransientSessionKeyManager.createAndReturnSession(TransientSessionKeyManager.java:333)
2019/11/19 22:15:37 | 	at net.i2p.router.crypto.TransientSessionKeyManager.getCurrentOrNewKey(TransientSessionKeyManager.java:303)
2019/11/19 22:15:37 | 	at net.i2p.router.message.GarlicMessageBuilder.buildMessage(GarlicMessageBuilder.java:151)
2019/11/19 22:15:37 | 	at net.i2p.router.message.OutboundClientMessageJobHelper.createGarlicMessage(OutboundClientMessageJobHelper.java:126)
2019/11/19 22:15:37 | 	at net.i2p.router.message.OutboundClientMessageOneShotJob.send(OutboundClientMessageOneShotJob.java:639)
2019/11/19 22:15:37 | 	at net.i2p.router.message.OutboundClientMessageOneShotJob.access$300(OutboundClientMessageOneShotJob.java:105)
2019/11/19 22:15:37 | 	at net.i2p.router.message.OutboundClientMessageOneShotJob$SendJob.runJob(OutboundClientMessageOneShotJob.java:365)
2019/11/19 22:15:37 | 	at net.i2p.router.JobQueueRunner.runCurrentJob(JobQueueRunner.java:110)
2019/11/19 22:15:37 | 	at net.i2p.router.JobQueueRunner.run(JobQueueRunner.java:66)
2019/11/19 22:30:16 | Reseed start
2019/11/19 22:30:16 | Reseeding from https://reseed.i2p-projekt.de/i2pseeds.su3?netid=2
2019/11/19 22:30:18 | INFO: 66 files extracted to /tmp/i2p-oPmYxBOF.tmp/reseeds-546994863
2019/11/19 22:30:18 | Reseed got 66 router infos from https://reseed.i2p-projekt.de/i2pseeds.su3?netid=2 with 0 errors
2019/11/19 22:30:18 | Reseeding from https://reseed.i2p.net.in/i2pseeds.su3?netid=2
2019/11/19 22:30:50 | Reseed got no router infos from https://reseed.i2p.net.in/i2pseeds.su3?netid=2
2019/11/19 22:30:50 | Reseeding from https://download.xxlspeed.com/i2pseeds.su3?netid=2
2019/11/19 22:31:23 | Reseed got no router infos from https://download.xxlspeed.com/i2pseeds.su3?netid=2
2019/11/19 22:31:23 | Reseeding from https://netdb.i2p2.no/i2pseeds.su3?netid=2
2019/11/19 22:31:57 | Reseed got no router infos from https://netdb.i2p2.no/i2pseeds.su3?netid=2
2019/11/19 22:31:57 | Reseeding from https://i2p.novg.net/i2pseeds.su3?netid=2
2019/11/19 22:32:34 | Reseed got no router infos from https://i2p.novg.net/i2pseeds.su3?netid=2
2019/11/19 22:32:34 | Reseeding from https://i2p.mooo.com/netDb/i2pseeds.su3?netid=2
2019/11/19 22:32:35 | INFO: 49 files extracted to /tmp/i2p-oPmYxBOF.tmp/reseeds-903494641
2019/11/19 22:32:35 | Reseed got 49 router infos from https://i2p.mooo.com/netDb/i2pseeds.su3?netid=2 with 0 errors
2019/11/19 22:32:35 | Reseed successful, fetched 115 router infos
2019/11/19 22:36:52 | CRIT  [JobQueue 4/5] net.i2p.router.JobQueueRunner : Error processing job [Outbound client message delayed send] on thread 3: java.lang.IllegalArgumentException: Bad public key type ECIES_X25519
2019/11/19 22:36:52 | java.lang.IllegalArgumentException: Bad public key type ECIES_X25519
2019/11/19 22:36:52 | 	at net.i2p.router.crypto.TransientSessionKeyManager.createAndReturnSession(TransientSessionKeyManager.java:333)
2019/11/19 22:36:52 | 	at net.i2p.router.crypto.TransientSessionKeyManager.getCurrentOrNewKey(TransientSessionKeyManager.java:303)
2019/11/19 22:36:52 | 	at net.i2p.router.message.GarlicMessageBuilder.buildMessage(GarlicMessageBuilder.java:151)
2019/11/19 22:36:52 | 	at net.i2p.router.message.OutboundClientMessageJobHelper.createGarlicMessage(OutboundClientMessageJobHelper.java:126)
2019/11/19 22:36:52 | 	at net.i2p.router.message.OutboundClientMessageOneShotJob.send(OutboundClientMessageOneShotJob.java:639)
2019/11/19 22:36:52 | 	at net.i2p.router.message.OutboundClientMessageOneShotJob.access$300(OutboundClientMessageOneShotJob.java:105)
2019/11/19 22:36:52 | 	at net.i2p.router.message.OutboundClientMessageOneShotJob$SendJob.runJob(OutboundClientMessageOneShotJob.java:365)
2019/11/19 22:36:52 | 	at net.i2p.router.JobQueueRunner.runCurrentJob(JobQueueRunner.java:110)
2019/11/19 22:36:52 | 	at net.i2p.router.JobQueueRunner.run(JobQueueRunner.java:66)
2019/11/19 22:36:52 | CRIT  [nal Reader 5] 2p.data.i2cp.I2CPMessageReader: Uncaught I2CP error
2019/11/19 22:36:52 | java.lang.IllegalArgumentException: Bad public key type ECIES_X25519
2019/11/19 22:36:52 | 	at net.i2p.router.crypto.TransientSessionKeyManager.createAndReturnSession(TransientSessionKeyManager.java:333)
2019/11/19 22:36:52 | 	at net.i2p.router.crypto.TransientSessionKeyManager.getCurrentOrNewKey(TransientSessionKeyManager.java:303)
2019/11/19 22:36:52 | 	at net.i2p.router.message.GarlicMessageBuilder.buildMessage(GarlicMessageBuilder.java:151)
2019/11/19 22:36:52 | 	at net.i2p.router.message.OutboundClientMessageJobHelper.createGarlicMessage(OutboundClientMessageJobHelper.java:126)
2019/11/19 22:36:52 | 	at net.i2p.router.message.OutboundClientMessageOneShotJob.send(OutboundClientMessageOneShotJob.java:639)
2019/11/19 22:36:52 | 	at net.i2p.router.message.OutboundClientMessageOneShotJob.access$300(OutboundClientMessageOneShotJob.java:105)
2019/11/19 22:36:52 | 	at net.i2p.router.message.OutboundClientMessageOneShotJob$SendJob.runJob(OutboundClientMessageOneShotJob.java:365)
2019/11/19 22:36:52 | 	at net.i2p.router.message.OutboundClientMessageOneShotJob.runJob(OutboundClientMessageOneShotJob.java:305)
2019/11/19 22:36:52 | 	at net.i2p.router.ClientMessagePool.add(ClientMessagePool.java:77)
2019/11/19 22:36:52 | 	at net.i2p.router.client.ClientManager.distributeMessage(ClientManager.java:472)
2019/11/19 22:36:52 | 	at net.i2p.router.client.ClientConnectionRunner.distributeMessage(ClientConnectionRunner.java:735)
2019/11/19 22:36:52 | 	at net.i2p.router.client.ClientMessageEventListener.handleSendMessage(ClientMessageEventListener.java:451)
2019/11/19 22:36:52 | 	at net.i2p.router.client.ClientMessageEventListener.messageReceived(ClientMessageEventListener.java:131)
2019/11/19 22:36:52 | 	at net.i2p.internal.QueuedI2CPMessageReader$QueuedI2CPMessageReaderRunner.run2(QueuedI2CPMessageReader.java:56)
2019/11/19 22:36:52 | 	at net.i2p.data.i2cp.I2CPMessageReader$I2CPMessageReaderRunner.run(I2CPMessageReader.java:164)
2019/11/19 22:36:52 | 	at java.base/java.lang.Thread.run(Thread.java:834)
2019/11/19 22:36:52 | 	at net.i2p.util.I2PThread.run(I2PThread.java:103)
2019/11/19 22:46:04 | Reseed start
2019/11/19 22:46:04 | Reseeding from https://i2p.novg.net/i2pseeds.su3?netid=2
2019/11/19 22:46:04 | INFO: 77 files extracted to /tmp/i2p-oPmYxBOF.tmp/reseeds-108685756
2019/11/19 22:46:05 | Reseed got 77 router infos from https://i2p.novg.net/i2pseeds.su3?netid=2 with 0 errors
2019/11/19 22:46:05 | Reseeding from https://download.xxlspeed.com/i2pseeds.su3?netid=2
2019/11/19 22:46:37 | Reseed got no router infos from https://download.xxlspeed.com/i2pseeds.su3?netid=2
2019/11/19 22:46:37 | Reseeding from https://reseed.onion.im/i2pseeds.su3?netid=2
2019/11/19 22:46:38 | INFO: 77 files extracted to /tmp/i2p-oPmYxBOF.tmp/reseeds-583922662
2019/11/19 22:46:38 | Reseed got 77 router infos from https://reseed.onion.im/i2pseeds.su3?netid=2 with 0 errors
2019/11/19 22:46:38 | Reseed successful, fetched 154 router infos

#2662 fixed I2PSnark opens tunnels at startup when no torrents are running zzz Reportage
Description

I2PSnark should check if torrents are running at startup before opening tunnels; currently it opens the minimum configured number of tunnels regardless.

#2661 fixed PeerState.java: remove _currentReceiveSecond zzz jogger
Description

This is unused since long. It is also too coarse also as we use millisecond based timers everywhere else.

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