TypeError: iteration over non-sequence

[kveretennicov@…]

Oops...

Trac detected an internal error:

iteration over non-sequence
Traceback (most recent call last):
  File "C:\python\2.4.0\Lib\site-packages\trac\web\standalone.py", line 302, in _do_trac_req
    dispatch_request(path_info, req, env)
  File "C:\python\2.4.0\Lib\site-packages\trac\web\main.py", line 139, in dispatch_request
    dispatcher.dispatch(req)
  File "C:\python\2.4.0\Lib\site-packages\trac\web\main.py", line 80, in dispatch
    req.perm = PermissionCache(self.env, req.authname)
  File "C:\python\2.4.0\Lib\site-packages\trac\perm.py", line 276, in __init__
    self.perms = PermissionSystem(env).get_user_permissions(username)
  File "C:\python\2.4.0\Lib\site-packages\trac\perm.py", line 132, in get_user_permissions
    for perm in self.store.get_user_permissions(username):
  File "C:\python\2.4.0\Lib\site-packages\trac\perm.py", line 218, in get_user_permissions
    for user, action in rows:
TypeError: iteration over non-sequence

Steps to reproduce:

• Initialize fresh trac environment
• Remove all permissions via trac-admin ("permission remove")
• Open project in browser (http://<host>/<short-project-name>)

Using tracd.

[gerber@…]

ran into the same problem today.

using trac 0.9 via cgi.

No details yet.

[anonymous]

same thing here…

[mgood]

What database driver & version are you using?

[fanch]

same thing here.

sqlite 3.2.1, pysqlite 2.0.5, tracd 0.9.5 (latest gentoo/amd64 testing version)

[eblot]

(clean up milestone)

[mgood]

fanch: are you just seeing the "TypeError?: iteration over non-sequence", or can you reproduce the same stack trace using the same steps described in the original description? I've tried it with those same versions and cannot reproduce the problem.
Please make sure that you're not just seeing a similar error message that is actually occurring in another part of the system. This appears to be a problem with a DB driver that misimplemented the DB-API and is returning None instead of an empty list when the query did not return any rows. However, pysqlite implements this correctly, so I don't think that the original error will occur with pysqlite.

[fanch]

sorry for the milestone :-/

reproducing exactly the same steps, I can reproduce exactly the same stack trace.

[cboos]

Can't reproduce with either trunk or 0.10-stable.