Closed
Bug 514406
Opened 16 years ago
Closed 16 years ago
ViewVC log not returning all data
Categories
(mozilla.org Graveyard :: Server Operations, task)
mozilla.org Graveyard
Server Operations
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: gerv, Unassigned)
References
()
Details
This URL:
http://viewvc.svn.mozilla.org/vc/?view=query&dir=&file=&file_match=exact&who=&who_match=exact&comment=&comment_match=exact&querysort=date&hours=&date=explicit&mindate=2009-03-03&maxdate=2009-09-03&limit_changes=1
should return all SVN changes for the past six months. But, no matter how I tweak the parameters, I can't persuade it to go back before 1st September. Is it broken, or am I doing something wrong?
I need this data because it's the alternative source for the information sought in bug 505331.
Gerv
| Reporter | ||
Comment 1•16 years ago
|
||
Note that the top of the page returned by the above URL says:
"Checkins on all branches between Mon Mar 2 16:00:00 2009 PST and Wed Sep 2 17:00:00 2009 PDT"
so it thinks that's what it's doing, it's just that it won't return any data from before a certain time. Oddly, it was September 1st yesterday, but it's 31st August today. As I write, the last checkin the above URL lists is 50564.
Having done some experimenting, it seems like the limit is around 1000 file changes. It's possible to get data from before that by changing the maxdate, so I guess I could batch it...
Gerv
| Reporter | ||
Comment 2•16 years ago
|
||
However, the RSS feed seems fixed at a limit of 20 entries :-( I guess I can get around that by creating my own using dapper.net.
Gerv
Here's why:
# Limit the number of rows returned by a given query to this number.
row_limit = 1000
This is set for performance reasons, so raising it much could bury viewvc.
| Reporter | ||
Comment 4•16 years ago
|
||
OK. I've worked around it by doing repeated date-based GETs.
Gerv
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WONTFIX
Updated•11 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•