VirtualBox

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.

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.

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:

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

Ticket Resolution Summary Owner Reporter
#14047 duplicate chromium browser version 41.x -> duplicate of #13984 -- Gerry73

Reported by Gerry73, 6 days ago.

Description

I'm using virtual box 4.3.26. I have a vm with xubuntu 14.04.2 LTS. I have installed chromium: until version 40.x it works fine. If I update to newer version (exactly 41.0.2272.76 ubuntu 14.04 64bit), chromium stop to work properly. For example, if i try to change order of tabs it doesn't works. If I open developer tools (with ctrl+shift+i) I can't resize area. Before upgrading to version 41.x of chromium everything works properly. I also had the same problems with the version 4.3.12 of virtualbox.

#14046 invalid VirtualBox Mac-version-10.10.3 (Yosemite), NAT network issue -- ranjan242526

Reported by ranjan242526, 6 days ago.

Description

I have recently bought a MACBook, running with 10.10.3 (Yosemite). I want to install Vagrant to run parallel systems. Vagrant uses VirtualBox to spin multiple VMs. While doing so I have two observation which is blocking me to proceed further.

# Issues:

1. The Acquired ip through DHCP (NAT) is "10.0.2.15". All the new VM under NAT, acquire the same ip ("10.0.2.15")

  1. The Guest VM is not ping able from my Host Machine.

NOTE: I am using Ubuntu-Server 14.04 for my guest VM setup.

# Approach:

# 1 : [FAILED ..] Manually tried creating a VM (instead Vagrant ) I have also tried with all the provided virtual adaptor with NAT mode, unfortunately there is no difference. PCNet PCI II (Am79C970A); PCNet FAST III (Am79C973, the default); Intel PRO/1000 MT Desktop (82540EM); [Default one] Intel PRO/1000 T Server (82543GC); Intel PRO/1000 MT Server (82545EM); Paravirtualized network adapter (virtio-net).

# 2 : [Working] Tried downloading a Box from Vagrant and tried to run, it works perfect.

# 3 : [Working] I have created a the same VM under bridge networking, it is working by acquire the ip from my physical network. and accessible from my Host machine.

# User Story:

I want to create a Base Vagrant VM with custom configuration for my CI setup.

# Reference:

My Host Network configuration:

Soumyas-MacBook-Pro:RawMachine1 soumya$ ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
options=3<RXCSUM,TXCSUM>
inet6 ::1 prefixlen 128 
inet 127.0.0.1 netmask 0xff000000 
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 
nd6 options=1<PERFORMNUD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 6c:40:08:9e:d0:5a 
inet6 fe80::6e40:8ff:fe9e:d05a%en0 prefixlen 64 scopeid 0x4 
inet 192.168.1.7 netmask 0xffffff00 broadcast 192.168.1.255
nd6 options=1<PERFORMNUD>
media: autoselect
status: active
en1: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
options=60<TSO4,TSO6>
ether 72:00:06:43:af:80 
media: autoselect <full-duplex>
status: inactive
en2: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
options=60<TSO4,TSO6>
ether 72:00:06:43:af:81 
media: autoselect <full-duplex>
status: inactive
bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=63<RXCSUM,TXCSUM,TSO4,TSO6>
ether 6e:40:08:e9:57:00 
Configuration:
id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
ipfilter disabled flags 0x2
member: en1 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 5 priority 0 path cost 0
member: en2 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 6 priority 0 path cost 0
nd6 options=1<PERFORMNUD>
media: <unknown type>
status: inactive
p2p0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2304
ether 0e:40:08:9e:d0:5a 
media: autoselect
status: inactive
awdl0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1452
ether 8e:5f:a4:16:d5:3b 
inet6 fe80::8c5f:a4ff:fe16:d53b%awdl0 prefixlen 64 scopeid 0x9 
nd6 options=1<PERFORMNUD>
media: autoselect
status: active
vboxnet0: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 0a:00:27:00:00:00 
Soumyas-MacBook-Pro:RawMachine1 soumya$ ping 10.0.2.15
PING 10.0.2.15 (10.0.2.15): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
^C
--- 10.0.2.15 ping statistics ---
7 packets transmitted, 0 packets received, 100.0% packet loss
Soumyas-MacBook-Pro:RawMachine1 soumya$

I have also attached the screenshot of VirtualBox Guest VM, Please have a look.

Please let us know, If more info is required for analyse the issue.

NOTE: I have also tried looking to the defect #13104: But couldn't find any relation or clue.

#14043 invalid Machine starts, but can only see a black screen -> not a bug -- hoiho

Reported by hoiho, 8 days ago.

Description

Hello.

My system Linux x86_64 (Beyond Linux® From Scratch with systemd). VirtualBox version 4.3.27 r99379

VirtualBox installed from VirtualBox-4.3.27-99379-Linux_amd64.run

to /opt/VirtualBox

Output of ls -dl /opt/VirtualBox:

$ ls -dl /opt/VirtualBox
drwxr-xr-x 1 root root 2244 Apr 11 06:50 /opt/VirtualBox

Output of lsmod:

$ lsmod
Module                  Size  Used by
vboxpci                14291  0
vboxnetadp             18163  0
vboxnetflt             16740  0
vboxdrv               329553  3 vboxnetadp,vboxnetflt,vboxpci
nf_log_ipv4             4125  1
nf_log_common           2738  1 nf_log_ipv4
iptable_nat             1775  0
nf_nat_ipv4             4899  1 iptable_nat
nf_nat                 11474  1 nf_nat_ipv4
xt_LOG                  1303  1
ext4                  483094  2
jbd2                   76851  1 ext4
mbcache                 6771  1 ext4
kvm_amd                48933  0
kvm                   396827  1 kvm_amd

Vmdk image:  http://cl.ly/Oeo3/download/BareMetal-0.6.0.zip (0.3 MiB). Previously, I ran this image on another system.

Before starting:

$ sudo /etc/init.d/vboxdrv start
Starting VirtualBox kernel modules ...done.
$ sudo /etc/init.d/vboxautostart-service start
$ sudo /etc/init.d/vboxballoonctrl-service start
$ sudo /etc/init.d/vboxweb-service start

Log attached.

The VM runs fine but after starting writes that it works. But I can only see a black screen.

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

www.oracle.com
ContactPrivacy policyTerms of Use