Modify ↓
Opened 15 years ago
Last modified 14 months ago
#9140 new defect
patch renderer should handle added binary files in GIT binary diffs
Reported by: | Christian Boos | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | next-stable-1.6.x |
Component: | rendering | Version: | 0.12dev |
Severity: | minor | Keywords: | patch diff |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
2010-03-15 22:05:19,147 Trac[api] WARNING: HTML preview using <trac.mimeview.patch.PatchRenderer object at 0x2693850> failed ( Traceback (most recent call last): File "build/bdist.linux-x86_64/egg/trac/mimeview/api.py", line 759, in render rendered_content, filename, url) File "build/bdist.linux-x86_64/egg/trac/mimeview/patch.py", line 51, in render Mimeview(self.env).tab_width) File "build/bdist.linux-x86_64/egg/trac/mimeview/patch.py", line 118, in _diff_to_hdf oldrev, newrev = index_line.split()[-1].split('..') ValueError: need more than 1 value to unpack)
for attachment:8216-textarea-resize-r8859.patch:ticket:8721.
This is an issue with GIT binary diffs: for a new binary there's a new file mode 100644
line, which is not currently expected by the code.
94 diff --git a/trac/htdocs/grip.png b/trac/htdocs/grip.png 95 new file mode 100644 96 index 0000000000000000000000000000000000000000..6524d4167d2d6e3939cfcf3111ce520acd66bc21 97 GIT binary patch 98 literal 162 99 zc%17D@N?(olHy`uVBq!ia0vp^(m>40!3-puuch|@DVB6cUq=Rp^(V|(yIunMk|nMY 100 zCBgY=CFO}lsSJ)O`AMk?p1FzXsX?iUDV2pMQ*D5X*aCb)TzBu@{r~^}iVZzqfg(&L 101 zL4Lvi8J=!8@B;EgJY5_^DsCku9AK6xWM-3k!OUU6z#qV1KKathOF(%BPgg&ebxsLQ 102 E0Ke)mAOHXW 103
Attachments (0)
Change History (5)
comment:1 by , 10 years ago
Milestone: | next-minor-0.12.x → next-stable-1.0.x |
---|
comment:2 by , 9 years ago
Keywords: | patch added |
---|
comment:3 by , 8 years ago
Milestone: | next-stable-1.0.x → next-stable-1.2.x |
---|
comment:4 by , 5 years ago
Milestone: | next-stable-1.2.x → next-stable-1.4.x |
---|
Note:
See TracTickets
for help on using tickets.
Moved ticket assigned to next-stable-1.0.x since maintenance of 1.0.x is coming to a close. Please move the ticket back if it's critical to fix on 1.0.x.