#1590 closed defect (fixed)
printing to stderr causes svn post-commit hook to crash
| Reported by: | Owned by: | daan | |
|---|---|---|---|
| Priority: | high | Component: | GeneralLinkSyntaxPlugin |
| Severity: | normal | Keywords: | |
| Cc: | Trac Release: | 0.10 |
Description
In the function update_burndown_data, lines 291 and 294, printing to stderr causes svn post-commit hook to crash.
Attachments (1)
Change History (6)
comment:1 Changed 17 years ago by
| Status: | new → assigned |
|---|
comment:2 Changed 17 years ago by
I'm suffering from this bug too. Any guess as to when it might be fixed?
comment:3 Changed 16 years ago by
| Owner: | changed from Sam Bloomquist to daan |
|---|---|
| Status: | assigned → new |
comment:4 Changed 16 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
(In [4736]) Release of version 1.9 of the Trac Scrum burndown plugin. See http://stuq.nl/weblog/2008-11-04/scrum-burndown-plugin-19-released for more information.
The Scrum burndown plugin is currently compatible and tested with Trac 0.10.5, Trac 0.11.1, Python 2.4 and Python 2.5.
Issues fixed: Fixed #3498 Incompatible with Genshi 0.5 Fixed #1743 No support for 0.11 version on trac Fixed #2330 How to enable ScrumBurndownPlugin in 0.11b1 Fixed #1590 printing to stderr causes svn post-commit hook to crash Fixed #1510 Porting to Trac 0.11 and Genshi templates Fixed #2936 problem installing plugin Fixed #1668 Environment Not Found Fixed #1472 URL Not Found when click Burndown menu Fixed #3017 Trac 0.11 - Burndown Chart does not show tickets with status 'accepted'
comment:5 Changed 13 years ago by
| Component: | ScrumBurndownPlugin → GeneralLinkSyntaxPlugin |
|---|
http://forums.westhost.com/member.php?143125-maxwellgutie13 Antivirus, Anti spyware, Firewall, etc.
Oh yeah, sorry. The stderr statements are leftover from when this was run as a separate python script by a cron job. I'll try to get them taken out this afternoon.