Notice: We have migrated to GitLab launching 2024-05-01 see here:

#3386 closed defect (invalid)

Trac's git changeset browsing is suspect.

Reported by: Chris Johns Owned by: Amar Takhar
Priority: high Milestone: 5.1
Component: admin Version: 5
Severity: critical Keywords:
Cc: Blocked By:


It is critical this interface works because we have moved to Trac for release notes and the release notes contain links to the changesets because we reference the tickets in the commits.

Some requests work:

  1. [changeset:"900c40730dbee34cd7a6f1c03c80896951bf1b9c/rtems" 900c40730dbee34cd7a6f1c03c80896951bf1b9c/rtems]
  2. [changeset:"d8de6b9dbe4ab1ef375ecce55e8bfb1028c5dd13/rtems" d8de6b9dbe4ab1ef375ecce55e8bfb1028c5dd13/rtems]
  3. [changeset:"9704efb4ec088a472842cbc9bc46392685ebc806/rtems" 9704efb4ec088a472842cbc9bc46392685ebc806/rtems]

and others do not:

  1. [changeset:"2afb22b7e1ebcbe40373ff7e0efae7d207c655a9/rtems" 2afb22b7e1ebcbe40373ff7e0efae7d207c655a9/rtems]


  • items 2. and 3. are either side of the changeset a. in the commit history of RTEMS.
  • Clicking on 3. and then the Next Changeset link also fails.

Change History (1)

comment:1 Changed on 10/20/18 at 21:15:43 by Amar Takhar

Resolution: invalid
Status: assignedclosed

This is a known issue and will only be fixed by upgrading to Trac 1.3 The diff is just too large and Apache times out before it's done. You can use to view it as it's written in C and not some kludgy python:

Note: See TracTickets for help on using tickets.