What version was the last that was NOT affected by this change?

On Nov 18, 8:29 am, Daniel Hommel <[EMAIL PROTECTED]>
wrote:
> The problem seems to be related to the code that changed when we removed
> the ProcessReader. There is an event handler that (asynchronously!)
> reads the standardoutputof the process into a string builder and the
> Run() method of the ProcessExecutor seems to finish before this handler
> has read all the data. The event handler is also doing the logging and
> when you set the log level to WARN it has less to write and so it is
> faster and may finish on time... If i put a Tread.Sleep() before the
> last line of the Run() method in ProcessExecutor the problem disappears,
> but that is clearly not a solution. I'll try to provide a fix ASAP.
>
> Daniel Hommel writes:
> > Robert Pickering writes:
> >> I too experienced this issue, it seemed to be related the upgrade from
> >> 1.3 to 1.4.1 (which otherwise worked quite well). It's on an english
> >> computer but using the french version ofsvn(the installer forsvn
> >> seems very aggressive about localisation giving you little choice
> >> about what language it uses). Changing from DEBUG to WARN cured the
> >> problem.
>
> > I tried to switch to WARN but it didn't work for me. I still get an
> > exception.
>
> >> CCNET seemed to be trying to parse half the log message. You'd see
> >> half a log message then error from CCNET complaining about an unclosed
> >> element and then the rest of log message. I could probably post an
> >> example if that would be helpful.
>
> > Sounds exactly like the problem i'm seeing here. Looking into the
> > changes that were made to the Subversion source control since 1.3
> > doesn't give me any ideas... I guess it's debugging time.
>
> > regards,
>
> > Daniel

Reply via email to