Error on browsing Plone collective

[enzo.cesanelli@…]

If you try to browse the collective sorted by reversed date order on:
​http://dev.plone.org/collective/browser/?order=date&desc=1

This error is generated:

Python Traceback

Traceback (most recent call last):
  File "/usr/local/lib/python2.4/site-packages/trac/web/main.py", line 406, in dispatch_request
    dispatcher.dispatch(req)
  File "/usr/local/lib/python2.4/site-packages/trac/web/main.py", line 237, in dispatch
    resp = chosen_handler.process_request(req)
  File "/usr/local/lib/python2.4/site-packages/trac/versioncontrol/web_ui/browser.py", line 143, in process_request
    self._render_directory(req, repos, node, rev)
  File "/usr/local/lib/python2.4/site-packages/trac/versioncontrol/web_ui/browser.py", line 189, in _render_directory
    info = sorted(info, key=browse_order, reverse=desc)
  File "/usr/local/lib/python2.4/site-packages/trac/versioncontrol/web_ui/browser.py", line 188, in browse_order
    return a['is_dir'] and dir_order or 0, file_order(a)
  File "/usr/local/lib/python2.4/site-packages/trac/versioncontrol/web_ui/browser.py", line 176, in file_order
    return changes[a['rev']]['date_seconds']
KeyError: 'date_seconds' 

[Christian Boos]

Another symptom of the changeset info being used but not provided (probably due to a permission check).

Note: see get_changes in trac/versioncontrol/web_ui/util.py​.

[Christian Boos]

Actually this is problem that can be located to ​http://dev.plone.org/collective/browser/root/EasyShop/branches/diefenbach-3.0 and the fact that there's a missing changeset ​[51954].

Probably consecutive to another occurrence of the issue #5440.

[enzo.cesanelli@…]

I've noted the issue to Kai, the mantainer of EasyShop. He fixed it and now the Plone Collective by date works again!

[Christian Boos]

Replying to enzo.cesanelli@gmail.com:

I've noted the issue to Kai, the mantainer of EasyShop. He fixed it …

I'm curious how. Did something had to be done at the SVN level or was it only a matter of doing the resync (full or for that revision only)?

[enzo.cesanelli@…]

Same issue, again… :( Does not exist any way to prevent it? Thanks,

Enzo

[Christian Boos]

This time it's PloneServicesCenter/trunk/i18n and r74514 which didn't "sync". As usual, no idea why…

Is that changeset "normal" at the svn level? i.e. does a svn log --xml --verbose -r74514 work? (what's the svn URL by the way?)

[Christian Boos]

Looks like some changesets are available through the command line, some others not. Those which create problems in Trac are not, but some which are not available publicly are nevertheless reachable in Trac. Is there some svn_authz issue going on here?

[Christian Boos]

No feedback, closing again.