Ticket #8451 (closed defect: duplicate)
Opened 3 years ago
Last modified 3 years ago
"TypeError: iteration over non-sequence" if you empty the permission list
| Reported by: | bugs@… | Owned by: | rblank |
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | general | Version: | 0.9.3 |
| Severity: | minor | Keywords: | |
| Cc: | |||
| Release Notes: | |||
| API 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
Change History
comment:1 Changed 3 years ago by rblank
- Milestone set to 0.11.6
- Owner set to rblank
- Severity changed from normal to minor
comment:2 Changed 3 years ago by bugs@…
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 Changed 3 years ago by osimons
- Milestone 0.11.6 deleted
- Resolution set to duplicate
- Status changed from new to 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.