On Thu, May 30, 2024 at 07:43:30PM +0800, Qian Yun wrote:
>
>
> On 5/29/24 22:51, Waldek Hebisch wrote:
> >
> > first build went fine, but a few later failed. Actually, it looks
> > worse than previous version where probability of success looked
> > higher.
> >
> > Yes, problem is because some .tex files are truncated. In one run it
> > was 'ug10.tex', in few cases it was 'SEGBIND.tex'. In other cases
> > I did not check the files but LaTeX error messuge indicated truncation.
>
> Can you try my patch from yesterday and see if this one helps.
I could, but it takes time. And such tweaking is risky, while it
may solve problem on my machine we risk breaking other. I would
prefer to get closer to reasons so that we can be confident that
book build really works.
> > > Do you think this is a problem that needs to be fixed before commit?
> >
> > We should understand what is happening. As I wrote, HyperDoc and
> > graphics protocal is inherently racy, but in previously it worked
> > relatively well. Ocasional hangs did happen. But truncated files
> > is a new thing.
>
> I do not think this "truncated file" problem is a new thing.
> We simply did not test it before, so it was not noticed until now.
Well, I check HyperDoc pages, it is extremally unlikely that
breakge would be not detected in long time. More precisely
I run diff between versions and most of the time it is trivial
(just some semi-random numbers differ). Since pages did not
change in unexpected ways potential breakge would be _very_
repreateable (and current truncation clearly have random behaviour)
and stay the same for long time. HyperDoc parses pages, so truncation
likely would give errors from HyperDoc when vieved. Since I look at pages
(and I think other folks also look at them) it is extremaly unlikely
that such gross error would be missed.
Concerning book, I did a few trials with version in the trunk, and
it worked fine on each trial. That is too little to be sure,
but is strong indication that trouble is due to recent changes.
> The "sman -paste" invocation of "hypertex" does not have this problem
> because it uses only socket IO to FRICASsys, it's purely sequential.
Yes, socket I/O is free from worst races. Pure use of stdio also
should be good.
> While the "usage of sman/FRICASsys in pipe" is more complex, it involves
> both socket IO and stdio, so the race happens there.
Well, clearly we should try to limit simultaneous use of socket IO
and stdio.
--
Waldek Hebisch
--
You received this message because you are subscribed to the Google Groups
"FriCAS - computer algebra system" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/fricas-devel/Zlirdx0-N_erwFlL%40fricas.org.
