empty timeline after upgrading Trac and relocating repository

27 views
Skip to first unread message

Stefan

unread,
Feb 6, 2020, 10:57:40 AM2/6/20
to Trac Users
Hi,

we recently updated our trac installation from 0.12.7 to 1.0.19 as well as the SVN installation (1.9.7 -> 1.10.6). Initially everything worked fine. However, after we relocated the SVN repository (from one drive to another one on the same machine) Trac failed to show the new commits in the timeline.

I then realized I forgot to update the repository path in trac.ini, adjusted it there and ran trac-admin [env-loc] repository resync. Ever since, the timeline is completely empty and doesn't show any revisions anymore.

I enabled DEBUG level logging in trac and didn't see any obvious pointers to what is going wrong there. When I do a commit the expected log message is put on record:

[api] DEBUG: Event changeset_added on repository 'P:\SVN\Repositories\[NAME]' for changesets (u'383178',)
[svn_fs] DEBUG: Subversion bindings imported
[cache] INFO: repos rev [383178] != cached rev [383177] in '[name]'
[cache] INFO: Trying to sync revision [383178] in '[name]'
[cache] DEBUG: Caching node change in [383178] in '[name]': (u'[...]/X4/universe/navigation.cpp', 'file', 'edit', u'[...]/X4/universe/navigation.cpp', 380945)

looking at the trac.db using sqlite I see proper entries for all revisions in the revision table. I also tried to disable two additional filter plugins we use (TimelineCheckinFilter and TimelineUserFilter) without much luck (the timeline was still not showing any recent commits.

Any pointers to what might be going wrong would be much appreciated.

Regards,
Stefan

Stefan Hett

unread,
Feb 6, 2020, 11:20:40 AM2/6/20
to trac-...@googlegroups.com
Ok, no clue how this finally works now again. I switched the timeline
settings for my current profile (to ISO-8601 and then back again to
"Default date format") and suddenly everything is working again.

So from my side: pls disregard this post (can provide further feedback
if s/o feels like investigating the issue for a potential bug in Trac).

Regards,
Stefan

Reply all
Reply to author
Forward
0 new messages