Opened 15 years ago
Closed 15 years ago
#8451 closed defect (duplicate)
"TypeError: iteration over non-sequence" if you empty the permission list
Reported by: | Owned by: | Remy Blank | |
---|---|---|---|
Priority: | low | Milestone: | |
Component: | general | Version: | 0.9.3 |
Severity: | minor | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
I created a new trac project and purged the permission list so no user was left in the list.
If you open the created project in your browser, then the following error is shown:
Oops... Trac detected an internal error: iteration over non-sequence Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/trac/web/modpython_frontend.py", line 206, in handler dispatch_request(mpr.path_info, mpr, env) File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 139, in dispatch_request dispatcher.dispatch(req) File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 80, in dispatch req.perm = PermissionCache(self.env, req.authname) File "/usr/lib/python2.4/site-packages/trac/perm.py", line 276, in __init__ self.perms = PermissionSystem(env).get_user_permissions(username) File "/usr/lib/python2.4/site-packages/trac/perm.py", line 132, in get_user_permissions for perm in self.store.get_user_permissions(username): File "/usr/lib/python2.4/site-packages/trac/perm.py", line 218, in get_user_permissions for user, action in rows: TypeError: iteration over non-sequence
I know a project with no permissions set isn't very useful, but nonetheless it's an error.
Attachments (0)
Change History (3)
comment:1 by , 15 years ago
Milestone: | → 0.11.6 |
---|---|
Owner: | set to |
Severity: | normal → minor |
comment:2 by , 15 years ago
Yes, I use version 0.9.3, because it's the stable version in Ubuntu Dapper LTS Server Edition… I don't know if it's the case on 0.11.
comment:3 by , 15 years ago
Milestone: | 0.11.6 |
---|---|
Resolution: | → duplicate |
Status: | new → closed |
Duplicate of #2862.
BTW, 0.9.x versions are no longer supported. We won't be handling new issues from such old versions unless they are clearly reproduceable also with newer and supported versions.
Did you set the version field correctly? 0.9.3?
I'll check if this is still the case on 0.11-stable.