You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@harmony.apache.org by Tim Ellison <t....@gmail.com> on 2008/03/28 12:24:45 UTC
[classlib][archive] Non-UTF8 character in manifest during confluence
startup (HARMONY-5662)
I just committed code in this area (at r641928) so it may indeed be a
regression. Looking...
Regards,
Tim
Alexei Zakharov (JIRA) wrote:
> [ https://issues.apache.org/jira/browse/HARMONY-5662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582976#action_12582976 ]
>
> Alexei Zakharov commented on HARMONY-5662:
> ------------------------------------------
>
> I far as I understand it doesn't like Windows end of line symbol 0D0A in "nekohtml-0.9.5,jar"'s manifest. BTW there were no such problem couple of months ago so this looks like a regression. Keep investigating...
>
>> Non-UTF8 character in manifest during confluence startup
>> --------------------------------------------------------
>>
>> Key: HARMONY-5662
>> URL: https://issues.apache.org/jira/browse/HARMONY-5662
>> Project: Harmony
>> Issue Type: Sub-task
>> Environment: Debian Linux IA32, confluence 2.7.1
>> Reporter: Alexei Zakharov
>>
>> I encounter the follwoing exception while trying to run confluence on the latest Harmony (r640865):
>> Throwable occurred: java.io.IOException: Input at 22 does not match UTF8 Specification
>> at java.util.jar.InitManifest.addLine(InitManifest.java:109)
>> at java.util.jar.InitManifest.nextChunk(InitManifest.java:181)
>> at java.util.jar.InitManifest.<init>(InitManifest.java:55)
>> at java.util.jar.Manifest.read(Manifest.java:169)
>> at java.util.jar.Manifest.<init>(Manifest.java:93)
>> at java.util.jar.JarInputStream.<init>(JarInputStream.java:66)
>> at java.util.jar.JarInputStream.<init>(JarInputStream.java:89)
>> at org.apache.catalina.util.ExtensionValidator.getManifest(ExtensionVali dator.java:373)
>> at org.apache.catalina.util.ExtensionValidator.validateApplication(Exten sionValidator.java:184)
>> at org.apache.catalina.core.StandardContext.start(StandardContext.java:4 064)
>> at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014)
>> at org.apache.catalina.core.StandardHost.start(StandardHost.java:736)
>> at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014)
>> at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443 )
>> at org.apache.catalina.core.StandardService.start(StandardService.java:4 48)
>> at org.apache.catalina.core.StandardServer.start(StandardServer.java:700 )
>> at org.apache.catalina.startup.Catalina.start(Catalina.java:552)
>> at java.lang.reflect.VMReflection.invokeMethod(VMReflection.java)
>> at java.lang.reflect.Method.invoke(Method.java:317)
>> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295)
>> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433)
>
Re: [classlib][archive] Non-UTF8 character in manifest during confluence startup (HARMONY-5662)
Posted by Alexei Zakharov <al...@gmail.com>.
Yes Tim, I've also noticed this your commit (that was AFAIU a part of
HARMONY-4569). So here comes an updated stack trace :-)
SEVERE: Error in dependencyCheck
Throwable occurred: java.io.IOException: NUL character in a manifest
at java.util.jar.InitManifest.readValue(InitManifest.java:173)
at java.util.jar.InitManifest.readHeader(InitManifest.java:117)
at java.util.jar.InitManifest.<init>(InitManifest.java:56)
at java.util.jar.Manifest.read(Manifest.java:211)
at java.util.jar.Manifest.<init>(Manifest.java:115)
at java.util.jar.JarInputStream.<init>(JarInputStream.java:66)
at java.util.jar.JarInputStream.<init>(JarInputStream.java:89)
at org.apache.catalina.util.ExtensionValidator.getManifest(ExtensionValidator.java:373)
at org.apache.catalina.util.ExtensionValidator.validateApplication(ExtensionValidator.java:184)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4064)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:736)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at org.apache.catalina.core.StandardService.start(StandardService.java:448)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:700)
at org.apache.catalina.startup.Catalina.start(Catalina.java:552)
at java.lang.reflect.VMReflection.invokeMethod(VMReflection.java)
at java.lang.reflect.Method.invoke(Method.java:317)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433)
Mar 28, 2008 3:04:08 PM org.apache.catalina.core.StandardContext start
I'm currently looking for the jar file and its manifest that caused the problem.
Regards,
Alexei
2008/3/28, Tim Ellison <t....@gmail.com>:
> Tim Ellison wrote:
> > I just committed code in this area (at r641928) so it may indeed be a
> > regression. Looking...
>
>
> Sorry Alexei, just noticed that your version under test was r640865.
>
> Given the recent changes is it possible for you to retry on a later
> version >r641928 since the failing code has been replaced.
>
> Thanks,
>
> Tim
>
>
Re: [classlib][archive] Non-UTF8 character in manifest during confluence startup (HARMONY-5662)
Posted by Alexei Zakharov <al...@gmail.com>.
Seems my attachment was lost. Please it attached to HARMONY-5662.
Thanks,
Alexei
2008/3/28, Alexei Zakharov <al...@gmail.com>:
> Looks like I found the guilty manifest, please see attached. It is
> from "concurrent-1.3.4-patched.jar" that is part of confluence 2.7.1
> distribution. You may notice that this manifest was created via gcc
> (?) and follows best practices for all strings in C language - ends
> with '\0'. So we get a null-terminated manifest here. :-/
>
> Can we avoid throwing exception in such cases?
>
>
> Regards,
> Alexei
>
> 2008/3/28, Alexei Fedotov <al...@gmail.com>:
> > Alexei,
> > Could you please dump "buf" buffer from InitManifest constructor to
> > check if it really contains a null character? If it does, we should
> > think how to ignore it smoothly.
> >
> > Thank you in advance.
> >
> >
> > On Fri, Mar 28, 2008 at 3:15 PM, Alexei Zakharov
> > <al...@gmail.com> wrote:
> > > I'd like to note here that I don't remember any problems with
> > > manifests loading during confluence startup a couple of months ago
> > > (however, there were other problems). It looks like manifest parsing
> > > routines were significantly updated since then.
> > >
> > > Regards,
> > > Alexei
> > >
> > > 2008/3/28, Alexei Fedotov <al...@gmail.com>:
> > >
> > >
> > > > Alexei's problem (introduced by a patch from [1]) is fixed in my code.
> > > > He faced another one though.
> > > >
> > > > [1] http://issues.apache.org/jira/browse/HARMONY-5473
> > > >
> > > >
> > > >
> > > >
> > > > On Fri, Mar 28, 2008 at 2:41 PM, Tim Ellison <t....@gmail.com> wrote:
> > > > > Tim Ellison wrote:
> > > > > > I just committed code in this area (at r641928) so it may indeed be a
> > > > > > regression. Looking...
> > > > >
> > > > > Sorry Alexei, just noticed that your version under test was r640865.
> > > > >
> > > > > Given the recent changes is it possible for you to retry on a later
> > > > > version >r641928 since the failing code has been replaced.
> > > > >
> > > > > Thanks,
> > > > > Tim
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > With best regards,
> > > >
> > > > Alexei
> > > >
> > >
> >
> >
> >
> >
> > --
> > With best regards,
> >
> > Alexei
> >
>
>
Re: [classlib][archive] Non-UTF8 character in manifest during confluence startup (HARMONY-5662)
Posted by Alexei Fedotov <al...@gmail.com>.
Thank you Alexei!
On Mon, Mar 31, 2008 at 1:14 PM, Alexei Zakharov
<al...@gmail.com> wrote:
> Thanks Alexei, I've just committed your patch. However, I've changed
> the cut&paste manifest a little bit to avoid all possible legal
> issues.
>
> Regards,
> Alexei
>
> 2008/3/29, Alexei Fedotov <al...@gmail.com>:
>
>
> > Hello Alexei, Tim,
> >
> > I chose not using byte buffers since renaming was suggested first. I
> > agree that these buffers are easy to be fixed during the next step.
> > See a solution at [1]. I hope "0.92-gcc" in my test won't be
> > considered as a cut&paste from the original code, but rather as a
> > reference to the problematic environment.
> >
> > [1] http://issues.apache.org/jira/browse/HARMONY-5662
> >
> >
> >
> >
> > On Sat, Mar 29, 2008 at 1:30 AM, Tim Ellison <t....@gmail.com> wrote:
> > > Alexei Fedotov wrote:
> > > > Ok, I found a way to localize this hack in one place. This requires my
> > > > ByteBuffer to return an actual ByteBuffer instead of byte[]. This may
> > > > be an answer to Tim's naming concern.
> > >
> > > Care to share it with us?
> > >
> > > Tim
> > >
> > >
> >
> >
> >
> >
> > --
> > With best regards,
> >
> > Alexei
> >
>
--
With best regards,
Alexei
Re: [classlib][archive] Non-UTF8 character in manifest during confluence startup (HARMONY-5662)
Posted by Alexei Zakharov <al...@gmail.com>.
Thanks Alexei, I've just committed your patch. However, I've changed
the cut&paste manifest a little bit to avoid all possible legal
issues.
Regards,
Alexei
2008/3/29, Alexei Fedotov <al...@gmail.com>:
> Hello Alexei, Tim,
>
> I chose not using byte buffers since renaming was suggested first. I
> agree that these buffers are easy to be fixed during the next step.
> See a solution at [1]. I hope "0.92-gcc" in my test won't be
> considered as a cut&paste from the original code, but rather as a
> reference to the problematic environment.
>
> [1] http://issues.apache.org/jira/browse/HARMONY-5662
>
>
>
>
> On Sat, Mar 29, 2008 at 1:30 AM, Tim Ellison <t....@gmail.com> wrote:
> > Alexei Fedotov wrote:
> > > Ok, I found a way to localize this hack in one place. This requires my
> > > ByteBuffer to return an actual ByteBuffer instead of byte[]. This may
> > > be an answer to Tim's naming concern.
> >
> > Care to share it with us?
> >
> > Tim
> >
> >
>
>
>
>
> --
> With best regards,
>
> Alexei
>
Re: [classlib][archive] Non-UTF8 character in manifest during confluence startup (HARMONY-5662)
Posted by Alexei Fedotov <al...@gmail.com>.
Hello Alexei, Tim,
I chose not using byte buffers since renaming was suggested first. I
agree that these buffers are easy to be fixed during the next step.
See a solution at [1]. I hope "0.92-gcc" in my test won't be
considered as a cut&paste from the original code, but rather as a
reference to the problematic environment.
[1] http://issues.apache.org/jira/browse/HARMONY-5662
On Sat, Mar 29, 2008 at 1:30 AM, Tim Ellison <t....@gmail.com> wrote:
> Alexei Fedotov wrote:
> > Ok, I found a way to localize this hack in one place. This requires my
> > ByteBuffer to return an actual ByteBuffer instead of byte[]. This may
> > be an answer to Tim's naming concern.
>
> Care to share it with us?
>
> Tim
>
>
--
With best regards,
Alexei
Re: [classlib][archive] Non-UTF8 character in manifest during confluence
startup (HARMONY-5662)
Posted by Tim Ellison <t....@gmail.com>.
Alexei Fedotov wrote:
> Ok, I found a way to localize this hack in one place. This requires my
> ByteBuffer to return an actual ByteBuffer instead of byte[]. This may
> be an answer to Tim's naming concern.
Care to share it with us?
Tim
Re: [classlib][archive] Non-UTF8 character in manifest during confluence startup (HARMONY-5662)
Posted by Alexei Fedotov <al...@gmail.com>.
Ok, I found a way to localize this hack in one place. This requires my
ByteBuffer to return an actual ByteBuffer instead of byte[]. This may
be an answer to Tim's naming concern.
On Fri, Mar 28, 2008 at 6:57 PM, Alexei Fedotov
<al...@gmail.com> wrote:
> Yes, it is possible to avoid throwing exception for such case, though
> it would be clearly a hack. Before hacking the code I want to
> understand why should not we fix the root of the problem, i.e. the
> buggy manifest.
>
> On Fri, Mar 28, 2008 at 5:06 PM, Alexei Zakharov
>
>
> <al...@gmail.com> wrote:
> > Looks like I found the guilty manifest, please see attached. It is
> > from "concurrent-1.3.4-patched.jar" that is part of confluence 2.7.1
> > distribution. You may notice that this manifest was created via gcc
> > (?) and follows best practices for all strings in C language - ends
> > with '\0'. So we get a null-terminated manifest here. :-/
> >
> > Can we avoid throwing exception in such cases?
> >
> >
> >
> > Regards,
> > Alexei
> >
> > 2008/3/28, Alexei Fedotov <al...@gmail.com>:
> > > Alexei,
> > > Could you please dump "buf" buffer from InitManifest constructor to
> > > check if it really contains a null character? If it does, we should
> > > think how to ignore it smoothly.
> > >
> > > Thank you in advance.
> > >
> > >
> > > On Fri, Mar 28, 2008 at 3:15 PM, Alexei Zakharov
> > > <al...@gmail.com> wrote:
> > > > I'd like to note here that I don't remember any problems with
> > > > manifests loading during confluence startup a couple of months ago
> > > > (however, there were other problems). It looks like manifest parsing
> > > > routines were significantly updated since then.
> > > >
> > > > Regards,
> > > > Alexei
> > > >
> > > > 2008/3/28, Alexei Fedotov <al...@gmail.com>:
> > > >
> > > >
> > > > > Alexei's problem (introduced by a patch from [1]) is fixed in my code.
> > > > > He faced another one though.
> > > > >
> > > > > [1] http://issues.apache.org/jira/browse/HARMONY-5473
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Fri, Mar 28, 2008 at 2:41 PM, Tim Ellison <t....@gmail.com> wrote:
> > > > > > Tim Ellison wrote:
> > > > > > > I just committed code in this area (at r641928) so it may indeed be a
> > > > > > > regression. Looking...
> > > > > >
> > > > > > Sorry Alexei, just noticed that your version under test was r640865.
> > > > > >
> > > > > > Given the recent changes is it possible for you to retry on a later
> > > > > > version >r641928 since the failing code has been replaced.
> > > > > >
> > > > > > Thanks,
> > > > > > Tim
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > With best regards,
> > > > >
> > > > > Alexei
> > > > >
> > > >
> > >
> > >
> > >
> > >
> > > --
> > > With best regards,
> > >
> > > Alexei
> > >
> >
>
>
>
> --
> With best regards,
> Alexei
>
--
With best regards,
Alexei
Re: [classlib][archive] Non-UTF8 character in manifest during confluence
startup (HARMONY-5662)
Posted by Tim Ellison <t....@gmail.com>.
Alexei Fedotov wrote:
> Yes, it is possible to avoid throwing exception for such case, though
> it would be clearly a hack. Before hacking the code I want to
> understand why should not we fix the root of the problem, i.e. the
> buggy manifest.
The simple answer is to be compatible with the way the RI behaves.
Also, we don't control the source of this manifest.
Regards,
Tim
Re: [classlib][archive] Non-UTF8 character in manifest during confluence startup (HARMONY-5662)
Posted by Alexei Fedotov <al...@gmail.com>.
Yes, it is possible to avoid throwing exception for such case, though
it would be clearly a hack. Before hacking the code I want to
understand why should not we fix the root of the problem, i.e. the
buggy manifest.
On Fri, Mar 28, 2008 at 5:06 PM, Alexei Zakharov
<al...@gmail.com> wrote:
> Looks like I found the guilty manifest, please see attached. It is
> from "concurrent-1.3.4-patched.jar" that is part of confluence 2.7.1
> distribution. You may notice that this manifest was created via gcc
> (?) and follows best practices for all strings in C language - ends
> with '\0'. So we get a null-terminated manifest here. :-/
>
> Can we avoid throwing exception in such cases?
>
>
>
> Regards,
> Alexei
>
> 2008/3/28, Alexei Fedotov <al...@gmail.com>:
> > Alexei,
> > Could you please dump "buf" buffer from InitManifest constructor to
> > check if it really contains a null character? If it does, we should
> > think how to ignore it smoothly.
> >
> > Thank you in advance.
> >
> >
> > On Fri, Mar 28, 2008 at 3:15 PM, Alexei Zakharov
> > <al...@gmail.com> wrote:
> > > I'd like to note here that I don't remember any problems with
> > > manifests loading during confluence startup a couple of months ago
> > > (however, there were other problems). It looks like manifest parsing
> > > routines were significantly updated since then.
> > >
> > > Regards,
> > > Alexei
> > >
> > > 2008/3/28, Alexei Fedotov <al...@gmail.com>:
> > >
> > >
> > > > Alexei's problem (introduced by a patch from [1]) is fixed in my code.
> > > > He faced another one though.
> > > >
> > > > [1] http://issues.apache.org/jira/browse/HARMONY-5473
> > > >
> > > >
> > > >
> > > >
> > > > On Fri, Mar 28, 2008 at 2:41 PM, Tim Ellison <t....@gmail.com> wrote:
> > > > > Tim Ellison wrote:
> > > > > > I just committed code in this area (at r641928) so it may indeed be a
> > > > > > regression. Looking...
> > > > >
> > > > > Sorry Alexei, just noticed that your version under test was r640865.
> > > > >
> > > > > Given the recent changes is it possible for you to retry on a later
> > > > > version >r641928 since the failing code has been replaced.
> > > > >
> > > > > Thanks,
> > > > > Tim
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > With best regards,
> > > >
> > > > Alexei
> > > >
> > >
> >
> >
> >
> >
> > --
> > With best regards,
> >
> > Alexei
> >
>
--
With best regards,
Alexei
Re: [classlib][archive] Non-UTF8 character in manifest during confluence startup (HARMONY-5662)
Posted by Alexei Zakharov <al...@gmail.com>.
Looks like I found the guilty manifest, please see attached. It is
from "concurrent-1.3.4-patched.jar" that is part of confluence 2.7.1
distribution. You may notice that this manifest was created via gcc
(?) and follows best practices for all strings in C language - ends
with '\0'. So we get a null-terminated manifest here. :-/
Can we avoid throwing exception in such cases?
Regards,
Alexei
2008/3/28, Alexei Fedotov <al...@gmail.com>:
> Alexei,
> Could you please dump "buf" buffer from InitManifest constructor to
> check if it really contains a null character? If it does, we should
> think how to ignore it smoothly.
>
> Thank you in advance.
>
>
> On Fri, Mar 28, 2008 at 3:15 PM, Alexei Zakharov
> <al...@gmail.com> wrote:
> > I'd like to note here that I don't remember any problems with
> > manifests loading during confluence startup a couple of months ago
> > (however, there were other problems). It looks like manifest parsing
> > routines were significantly updated since then.
> >
> > Regards,
> > Alexei
> >
> > 2008/3/28, Alexei Fedotov <al...@gmail.com>:
> >
> >
> > > Alexei's problem (introduced by a patch from [1]) is fixed in my code.
> > > He faced another one though.
> > >
> > > [1] http://issues.apache.org/jira/browse/HARMONY-5473
> > >
> > >
> > >
> > >
> > > On Fri, Mar 28, 2008 at 2:41 PM, Tim Ellison <t....@gmail.com> wrote:
> > > > Tim Ellison wrote:
> > > > > I just committed code in this area (at r641928) so it may indeed be a
> > > > > regression. Looking...
> > > >
> > > > Sorry Alexei, just noticed that your version under test was r640865.
> > > >
> > > > Given the recent changes is it possible for you to retry on a later
> > > > version >r641928 since the failing code has been replaced.
> > > >
> > > > Thanks,
> > > > Tim
> > > >
> > > >
> > >
> > >
> > >
> > >
> > > --
> > > With best regards,
> > >
> > > Alexei
> > >
> >
>
>
>
>
> --
> With best regards,
>
> Alexei
>
Re: [classlib][archive] Non-UTF8 character in manifest during confluence startup (HARMONY-5662)
Posted by Alexei Fedotov <al...@gmail.com>.
Alexei,
Could you please dump "buf" buffer from InitManifest constructor to
check if it really contains a null character? If it does, we should
think how to ignore it smoothly.
Thank you in advance.
On Fri, Mar 28, 2008 at 3:15 PM, Alexei Zakharov
<al...@gmail.com> wrote:
> I'd like to note here that I don't remember any problems with
> manifests loading during confluence startup a couple of months ago
> (however, there were other problems). It looks like manifest parsing
> routines were significantly updated since then.
>
> Regards,
> Alexei
>
> 2008/3/28, Alexei Fedotov <al...@gmail.com>:
>
>
> > Alexei's problem (introduced by a patch from [1]) is fixed in my code.
> > He faced another one though.
> >
> > [1] http://issues.apache.org/jira/browse/HARMONY-5473
> >
> >
> >
> >
> > On Fri, Mar 28, 2008 at 2:41 PM, Tim Ellison <t....@gmail.com> wrote:
> > > Tim Ellison wrote:
> > > > I just committed code in this area (at r641928) so it may indeed be a
> > > > regression. Looking...
> > >
> > > Sorry Alexei, just noticed that your version under test was r640865.
> > >
> > > Given the recent changes is it possible for you to retry on a later
> > > version >r641928 since the failing code has been replaced.
> > >
> > > Thanks,
> > > Tim
> > >
> > >
> >
> >
> >
> >
> > --
> > With best regards,
> >
> > Alexei
> >
>
--
With best regards,
Alexei
Re: [classlib][archive] Non-UTF8 character in manifest during confluence
startup (HARMONY-5662)
Posted by Tim Ellison <t....@gmail.com>.
Alexei Zakharov wrote:
> I'd like to note here that I don't remember any problems with
> manifests loading during confluence startup a couple of months ago
> (however, there were other problems). It looks like manifest parsing
> routines were significantly updated since then.
Yes, and I guess it means that we need to improve our unit tests in this
area if we were able to introduce a regression.
Thanks for your help in finding this problem quickly. I'm sure we'll
soon get it worked out.
Regards,
Tim
Re: [classlib][archive] Non-UTF8 character in manifest during confluence startup (HARMONY-5662)
Posted by Alexei Zakharov <al...@gmail.com>.
I'd like to note here that I don't remember any problems with
manifests loading during confluence startup a couple of months ago
(however, there were other problems). It looks like manifest parsing
routines were significantly updated since then.
Regards,
Alexei
2008/3/28, Alexei Fedotov <al...@gmail.com>:
> Alexei's problem (introduced by a patch from [1]) is fixed in my code.
> He faced another one though.
>
> [1] http://issues.apache.org/jira/browse/HARMONY-5473
>
>
>
>
> On Fri, Mar 28, 2008 at 2:41 PM, Tim Ellison <t....@gmail.com> wrote:
> > Tim Ellison wrote:
> > > I just committed code in this area (at r641928) so it may indeed be a
> > > regression. Looking...
> >
> > Sorry Alexei, just noticed that your version under test was r640865.
> >
> > Given the recent changes is it possible for you to retry on a later
> > version >r641928 since the failing code has been replaced.
> >
> > Thanks,
> > Tim
> >
> >
>
>
>
>
> --
> With best regards,
>
> Alexei
>
Re: [classlib][archive] Non-UTF8 character in manifest during confluence startup (HARMONY-5662)
Posted by Alexei Fedotov <al...@gmail.com>.
Alexei's problem (introduced by a patch from [1]) is fixed in my code.
He faced another one though.
[1] http://issues.apache.org/jira/browse/HARMONY-5473
On Fri, Mar 28, 2008 at 2:41 PM, Tim Ellison <t....@gmail.com> wrote:
> Tim Ellison wrote:
> > I just committed code in this area (at r641928) so it may indeed be a
> > regression. Looking...
>
> Sorry Alexei, just noticed that your version under test was r640865.
>
> Given the recent changes is it possible for you to retry on a later
> version >r641928 since the failing code has been replaced.
>
> Thanks,
> Tim
>
>
--
With best regards,
Alexei
Re: [classlib][archive] Non-UTF8 character in manifest during confluence
startup (HARMONY-5662)
Posted by Tim Ellison <t....@gmail.com>.
Tim Ellison wrote:
> I just committed code in this area (at r641928) so it may indeed be a
> regression. Looking...
Sorry Alexei, just noticed that your version under test was r640865.
Given the recent changes is it possible for you to retry on a later
version >r641928 since the failing code has been replaced.
Thanks,
Tim