Opened 12 years ago
Closed 12 years ago
#3327 closed Bug (fixed)
IntegrityError: duplicate key value violates unique constraint "session_attribute_pk"
Reported by: | stephane | Owned by: | titer |
---|---|---|---|
Priority: | Low | Milestone: | |
Component: | Website | Version: | 2.00 |
Severity: | Normal | Keywords: | trac error |
Cc: |
Description
How to Reproduce
While doing a GET operation on /report/7, Trac issued an internal error.
I created a new account, logged in, send a ticket and I wanted to see "My ticket" page to check my patch submission was okay. I get this error instead.
Request parameters:
{'id': u'7'}
System Information
Trac | 0.12dev-r9372 |
Genshi | 0.6dev-r1096 |
psycopg2 | 2.0.7 |
Python | 2.5.2 (r252:60911, Jan 24 2010, 14:53:14) [GCC 4.3.2] |
setuptools | 0.6c8 |
Subversion | 1.5.1 (r32289) |
Enabled Plugins
Python Traceback
Traceback (most recent call last): File "build/bdist.linux-i686/egg/trac/web/main.py", line 504, in _dispatch_request dispatcher.dispatch(req) File "build/bdist.linux-i686/egg/trac/web/main.py", line 259, in dispatch req.session.save() File "build/bdist.linux-i686/egg/trac/web/session.py", line 89, in save @with_transaction(self.env) File "build/bdist.linux-i686/egg/trac/db/util.py", line 36, in transaction_wrapper fn(dbtmp) File "build/bdist.linux-i686/egg/trac/web/session.py", line 118, in delete_session_cookie """, attrs) File "build/bdist.linux-i686/egg/trac/db/util.py", line 106, in executemany return self.cursor.executemany(sql_escape_percent(sql), args) IntegrityError: duplicate key value violates unique constraint "session_attribute_pk"
Change History (4)
comment:1 Changed 12 years ago by titer
- Owner changed from John Clay to titer
comment:2 Changed 12 years ago by titer
comment:3 Changed 12 years ago by charles
stephane: ping
comment:4 Changed 12 years ago by charles
- Milestone None Set deleted
- Resolution set to fixed
- Status changed from new to closed
I'm not able to trigger the error message for report 7, either when logged in or logged out, and the OP hasn't reported back, so I'm going to assume titer's upgrade to trac 0.12 fixed the problem.
stephane: If this problem persists, please reopen this ticket. Thanks!
Note: See
TracTickets for help on using
tickets.
We upgraded Trac to 0.12 stable - is the error still happening?