You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Eirik Bjorsnos (JIRA)" <ji...@apache.org> on 2008/02/13 17:57:09 UTC

[jira] Created: (INFRA-1523) Corrupted revision 625025 in SVN

Corrupted revision 625025 in SVN
--------------------------------

                 Key: INFRA-1523
                 URL: https://issues.apache.org/jira/browse/INFRA-1523
             Project: Infrastructure
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: Subversion
            Reporter: Eirik Bjorsnos
            Priority: Critical



The JspWiki Subversion revisions that were recently imported into the ASF SVN seems to contain a corrupted revision:

$ svn log -r 625025 http://svn.apache.org/repos/asf/ svn: REPORT request failed on '/repos/asf/!svn/bc/625025'
svn: REPORT of '/repos/asf/!svn/bc/625025': 200 OK (http://svn.apache.org)

The same revision seems to be shown ok in ViewVC:

http://svn.apache.org/viewvc?view=rev&revision=625025

JavaSVN gives me "MalformedByteSequenceException: Invalid byte 2 of 3-byte UTF-8 sequence" from the Xerces XML parser, so my guess is that this is related to an encoding problem with the log message introduced by running cvs2svn.

Trying to propedit the svn:log revprop gives me this:

$ svn propedit svn:log  --revprop   -r 625025 http://svn.apache.org/repos/asf/ 
svn: Valid UTF-8 data
(hex: 69 6e 67 20 74 68 65 20 65 72 72 6f 72 2e 20 43 72 65 64 69 74 3a 20 4a)
followed by invalid UTF-8 sequence
(hex: 9f 72 67 65)

while running just propget gives me this:

$ svn propget  svn:log  --revprop   -r 625025 http://svn.apache.org/repos/asf/ 
WebContainerAuthorizer now throws a RuntimeException if it cannot somehow parse the web.xml. This isn't ideal, but it's better than ignoring the error. Credit: J?\159rgen Weber.

My guess is that doing a propedit on the svn:log revprop will fix this issue. 

I've reported similar issues before and remember Justin Erenkrantz fixing it by doing a propedit.

Thanks,
Eirik.




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (INFRA-1523) Corrupted revision 625025 in SVN

Posted by "Eirik Bjorsnos (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569077#action_12569077 ] 

Eirik Bjorsnos commented on INFRA-1523:
---------------------------------------


Found one more corrupt revision:

626835


> Corrupted revision 625025 in SVN
> --------------------------------
>
>                 Key: INFRA-1523
>                 URL: https://issues.apache.org/jira/browse/INFRA-1523
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Subversion
>            Reporter: Eirik Bjorsnos
>            Priority: Critical
>
> The JspWiki Subversion revisions that were recently imported into the ASF SVN seems to contain a corrupted revision:
> $ svn log -r 625025 http://svn.apache.org/repos/asf/ svn: REPORT request failed on '/repos/asf/!svn/bc/625025'
> svn: REPORT of '/repos/asf/!svn/bc/625025': 200 OK (http://svn.apache.org)
> The same revision seems to be shown ok in ViewVC:
> http://svn.apache.org/viewvc?view=rev&revision=625025
> JavaSVN gives me "MalformedByteSequenceException: Invalid byte 2 of 3-byte UTF-8 sequence" from the Xerces XML parser, so my guess is that this is related to an encoding problem with the log message introduced by running cvs2svn.
> Trying to propedit the svn:log revprop gives me this:
> $ svn propedit svn:log  --revprop   -r 625025 http://svn.apache.org/repos/asf/ 
> svn: Valid UTF-8 data
> (hex: 69 6e 67 20 74 68 65 20 65 72 72 6f 72 2e 20 43 72 65 64 69 74 3a 20 4a)
> followed by invalid UTF-8 sequence
> (hex: 9f 72 67 65)
> while running just propget gives me this:
> $ svn propget  svn:log  --revprop   -r 625025 http://svn.apache.org/repos/asf/ 
> WebContainerAuthorizer now throws a RuntimeException if it cannot somehow parse the web.xml. This isn't ideal, but it's better than ignoring the error. Credit: J?\159rgen Weber.
> My guess is that doing a propedit on the svn:log revprop will fix this issue. 
> I've reported similar issues before and remember Justin Erenkrantz fixing it by doing a propedit.
> Thanks,
> Eirik.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Reopened: (INFRA-1523) Corrupted revision 625025 in SVN

Posted by "Eirik Bjorsnos (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/INFRA-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eirik Bjorsnos reopened INFRA-1523:
-----------------------------------


Thanks Joe,

Could you take a look at revision 622169 as well?

That revision produces invalid XML using the svn command line client:

svn log --xml -v -r 622169  http://svn.apache.org/repos/asf/ > file.xml

Parsing file.xml with Xerces gives me this:

org.xml.sax.SAXParseException: Invalid byte 2 of 3-byte UTF-8 sequence

Thanks,
Eirik.

> Corrupted revision 625025 in SVN
> --------------------------------
>
>                 Key: INFRA-1523
>                 URL: https://issues.apache.org/jira/browse/INFRA-1523
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Subversion
>            Reporter: Eirik Bjorsnos
>            Priority: Critical
>
> The JspWiki Subversion revisions that were recently imported into the ASF SVN seems to contain a corrupted revision:
> $ svn log -r 625025 http://svn.apache.org/repos/asf/ svn: REPORT request failed on '/repos/asf/!svn/bc/625025'
> svn: REPORT of '/repos/asf/!svn/bc/625025': 200 OK (http://svn.apache.org)
> The same revision seems to be shown ok in ViewVC:
> http://svn.apache.org/viewvc?view=rev&revision=625025
> JavaSVN gives me "MalformedByteSequenceException: Invalid byte 2 of 3-byte UTF-8 sequence" from the Xerces XML parser, so my guess is that this is related to an encoding problem with the log message introduced by running cvs2svn.
> Trying to propedit the svn:log revprop gives me this:
> $ svn propedit svn:log  --revprop   -r 625025 http://svn.apache.org/repos/asf/ 
> svn: Valid UTF-8 data
> (hex: 69 6e 67 20 74 68 65 20 65 72 72 6f 72 2e 20 43 72 65 64 69 74 3a 20 4a)
> followed by invalid UTF-8 sequence
> (hex: 9f 72 67 65)
> while running just propget gives me this:
> $ svn propget  svn:log  --revprop   -r 625025 http://svn.apache.org/repos/asf/ 
> WebContainerAuthorizer now throws a RuntimeException if it cannot somehow parse the web.xml. This isn't ideal, but it's better than ignoring the error. Credit: J?\159rgen Weber.
> My guess is that doing a propedit on the svn:log revprop will fix this issue. 
> I've reported similar issues before and remember Justin Erenkrantz fixing it by doing a propedit.
> Thanks,
> Eirik.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (INFRA-1523) Corrupted revision 625025 in SVN

Posted by "Eirik Bjorsnos (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568635#action_12568635 ] 

Eirik Bjorsnos commented on INFRA-1523:
---------------------------------------

Same  problem applies to revision 626654

$ svn log -r 626654  http://svn.apache.org/repos/asf/ 
svn: REPORT request failed on '/repos/asf/!svn/bc/626654'
svn: REPORT of '/repos/asf/!svn/bc/626654': 200 OK (http://svn.apache.org)

$ svn propget  svn:log  --revprop   -r 626654  http://svn.apache.org/repos/asf/ 
P?\138ivitetty




> Corrupted revision 625025 in SVN
> --------------------------------
>
>                 Key: INFRA-1523
>                 URL: https://issues.apache.org/jira/browse/INFRA-1523
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Subversion
>            Reporter: Eirik Bjorsnos
>            Priority: Critical
>
> The JspWiki Subversion revisions that were recently imported into the ASF SVN seems to contain a corrupted revision:
> $ svn log -r 625025 http://svn.apache.org/repos/asf/ svn: REPORT request failed on '/repos/asf/!svn/bc/625025'
> svn: REPORT of '/repos/asf/!svn/bc/625025': 200 OK (http://svn.apache.org)
> The same revision seems to be shown ok in ViewVC:
> http://svn.apache.org/viewvc?view=rev&revision=625025
> JavaSVN gives me "MalformedByteSequenceException: Invalid byte 2 of 3-byte UTF-8 sequence" from the Xerces XML parser, so my guess is that this is related to an encoding problem with the log message introduced by running cvs2svn.
> Trying to propedit the svn:log revprop gives me this:
> $ svn propedit svn:log  --revprop   -r 625025 http://svn.apache.org/repos/asf/ 
> svn: Valid UTF-8 data
> (hex: 69 6e 67 20 74 68 65 20 65 72 72 6f 72 2e 20 43 72 65 64 69 74 3a 20 4a)
> followed by invalid UTF-8 sequence
> (hex: 9f 72 67 65)
> while running just propget gives me this:
> $ svn propget  svn:log  --revprop   -r 625025 http://svn.apache.org/repos/asf/ 
> WebContainerAuthorizer now throws a RuntimeException if it cannot somehow parse the web.xml. This isn't ideal, but it's better than ignoring the error. Credit: J?\159rgen Weber.
> My guess is that doing a propedit on the svn:log revprop will fix this issue. 
> I've reported similar issues before and remember Justin Erenkrantz fixing it by doing a propedit.
> Thanks,
> Eirik.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (INFRA-1523) Corrupted revision 625025 in SVN

Posted by "Joe Schaefer (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/INFRA-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joe Schaefer closed INFRA-1523.
-------------------------------

    Resolution: Fixed

Corrected svn:log for both r625025
and r626654.

> Corrupted revision 625025 in SVN
> --------------------------------
>
>                 Key: INFRA-1523
>                 URL: https://issues.apache.org/jira/browse/INFRA-1523
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Subversion
>            Reporter: Eirik Bjorsnos
>            Priority: Critical
>
> The JspWiki Subversion revisions that were recently imported into the ASF SVN seems to contain a corrupted revision:
> $ svn log -r 625025 http://svn.apache.org/repos/asf/ svn: REPORT request failed on '/repos/asf/!svn/bc/625025'
> svn: REPORT of '/repos/asf/!svn/bc/625025': 200 OK (http://svn.apache.org)
> The same revision seems to be shown ok in ViewVC:
> http://svn.apache.org/viewvc?view=rev&revision=625025
> JavaSVN gives me "MalformedByteSequenceException: Invalid byte 2 of 3-byte UTF-8 sequence" from the Xerces XML parser, so my guess is that this is related to an encoding problem with the log message introduced by running cvs2svn.
> Trying to propedit the svn:log revprop gives me this:
> $ svn propedit svn:log  --revprop   -r 625025 http://svn.apache.org/repos/asf/ 
> svn: Valid UTF-8 data
> (hex: 69 6e 67 20 74 68 65 20 65 72 72 6f 72 2e 20 43 72 65 64 69 74 3a 20 4a)
> followed by invalid UTF-8 sequence
> (hex: 9f 72 67 65)
> while running just propget gives me this:
> $ svn propget  svn:log  --revprop   -r 625025 http://svn.apache.org/repos/asf/ 
> WebContainerAuthorizer now throws a RuntimeException if it cannot somehow parse the web.xml. This isn't ideal, but it's better than ignoring the error. Credit: J?\159rgen Weber.
> My guess is that doing a propedit on the svn:log revprop will fix this issue. 
> I've reported similar issues before and remember Justin Erenkrantz fixing it by doing a propedit.
> Thanks,
> Eirik.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (INFRA-1523) Corrupted revision 625025 in SVN

Posted by "Joe Schaefer (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/INFRA-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joe Schaefer closed INFRA-1523.
-------------------------------

    Resolution: Fixed

Repaired.

> Corrupted revision 625025 in SVN
> --------------------------------
>
>                 Key: INFRA-1523
>                 URL: https://issues.apache.org/jira/browse/INFRA-1523
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Subversion
>            Reporter: Eirik Bjorsnos
>            Priority: Critical
>
> The JspWiki Subversion revisions that were recently imported into the ASF SVN seems to contain a corrupted revision:
> $ svn log -r 625025 http://svn.apache.org/repos/asf/ svn: REPORT request failed on '/repos/asf/!svn/bc/625025'
> svn: REPORT of '/repos/asf/!svn/bc/625025': 200 OK (http://svn.apache.org)
> The same revision seems to be shown ok in ViewVC:
> http://svn.apache.org/viewvc?view=rev&revision=625025
> JavaSVN gives me "MalformedByteSequenceException: Invalid byte 2 of 3-byte UTF-8 sequence" from the Xerces XML parser, so my guess is that this is related to an encoding problem with the log message introduced by running cvs2svn.
> Trying to propedit the svn:log revprop gives me this:
> $ svn propedit svn:log  --revprop   -r 625025 http://svn.apache.org/repos/asf/ 
> svn: Valid UTF-8 data
> (hex: 69 6e 67 20 74 68 65 20 65 72 72 6f 72 2e 20 43 72 65 64 69 74 3a 20 4a)
> followed by invalid UTF-8 sequence
> (hex: 9f 72 67 65)
> while running just propget gives me this:
> $ svn propget  svn:log  --revprop   -r 625025 http://svn.apache.org/repos/asf/ 
> WebContainerAuthorizer now throws a RuntimeException if it cannot somehow parse the web.xml. This isn't ideal, but it's better than ignoring the error. Credit: J?\159rgen Weber.
> My guess is that doing a propedit on the svn:log revprop will fix this issue. 
> I've reported similar issues before and remember Justin Erenkrantz fixing it by doing a propedit.
> Thanks,
> Eirik.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.