Opened 5 years ago

Closed 4 years ago

#4737 closed defect (worksforme)

searching with the sensitive tickets plugin in version 0.11 creates a

Reported by: anonymous Owned by: obs
Priority: normal Component: SensitiveTicketsPlugin
Severity: normal Keywords:
Cc: k0s, m.a.swertz@… Trac Release: 0.11


Trac detected an internal error:

RuntimeError: maximum recursion depth exceeded

see attached for traceback (only the first part is included) The error directly points to sensitivetickets

Attachments (1)

tracbug.txt (16.6 KB) - added by myrond@… 5 years ago.
traceback for sensitive tickets bug in if 'SENSITIVE_VIEW' not in perm

Download all attachments as: .zip

Change History (6)

Changed 5 years ago by myrond@…

traceback for sensitive tickets bug in if 'SENSITIVE_VIEW' not in perm

comment:1 Changed 5 years ago by k0s

  • Cc k0s added

comment:2 Changed 5 years ago by k0s

this is hard to debug with so little information. what were you doing to get this error? did you have the SENSITIVE_VIEW permission? verbose reproduction steps needed

comment:3 Changed 4 years ago by obs

  • Owner changed from sbenthall to obs

comment:4 Changed 4 years ago by anonymous

  • Cc m.a.swertz@… added

I have the same problem, caused by the combined use of SensitiveTicketsPlugin with PrivateTicketsPlugin.
It seems the PrivateTicketsPolicy and SensitiveTicketsPolicy recursively call each other.

Why both?

  • I want to hide sensitive tickets in anonymous view and
  • limit the visibility of these tickets to particular groups in authenticated view

A solution seems to merge the two plugins but that is not trivial (for a non python programmer at least).

comment:5 Changed 4 years ago by obs

  • Resolution set to worksforme
  • Status changed from new to closed

Cannot replicate issue.

Add Comment

Modify Ticket

as closed .
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from obs. Next status will be 'closed'.
The resolution will be deleted. Next status will be 'reopened'.

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.