Opened 18 years ago
Closed 16 years ago
#5052 closed enhancement (worksforme)
Attempt to load SilverCity once per session
| Reported by: | Owned by: | Christian Boos | |
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | wiki system | Version: | |
| Severity: | minor | Keywords: | mimeview renderer macro |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Is it possible to only attempt to load SilverCity once per session?
I get a million traceback warnings in my trac log file because every render call attempts to load SilverCity, then falls back to enscript.
It would also be more efficient to only attempt to load it once.
Regards, Karl
Attachments (1)
Change History (6)
comment:1 by , 18 years ago
comment:2 by , 18 years ago
| Component: | general → wiki |
|---|---|
| Keywords: | mimeview renderer macro added |
| Milestone: | → 1.0 |
| Owner: | changed from to |
| Priority: | normal → low |
Agreed, we could be a bit smarter here.
follow-up: 4 comment:3 by , 18 years ago
Perhaps log level INFO would be more appropriate until the code is changed to check less frequently.
I'm attaching a simple patch I've applied to log these at INFO.
by , 18 years ago
| Attachment: | loader.py.diff added |
|---|
Patch for loader.py to reduce errors on load failures
comment:4 by , 18 years ago
Replying to dharris <dharris+trac@gmail.com>:
Perhaps log level INFO would be more appropriate until the code is changed to check less frequently.
I think this is more a piece of information for developers or admins who wish to debug their installation, so DEBUG seems more appropriate here, especially if the same information keeps being printed with no added value.
comment:5 by , 16 years ago
| Milestone: | 1.0 |
|---|---|
| Resolution: | → worksforme |
| Status: | new → closed |
This is no longer an issue.
Another approach would be to change the log level to DEBUG.