Re: [fossil-users] Delay with `fossil ui' (related to backoffice processing?)

2018-07-22 Thread Florian Balmer
Warren Young: > That’s brand new code, less than a week old. It’s not surprising it’s > not rock-solid yet. Yes, I agree, I no not expect complex new features to be flawless from the beginning. But I've stumbled into the issue while testing a fix from the current tip, and decided to report it

Re: [fossil-users] Delay with `fossil ui' (related to backoffice processing?)

2018-07-22 Thread Richard Hipp
On 7/22/18, Florian Balmer wrote: > > The Windows HTTP server (and thus `fossil ui') works by spawning > sub-processes for each individual HTTP request, right? This results in > multiple sub-processes per web page (one for the HTML page, one for > CSS, another one for JavaScript, etc.)? > Every

Re: [fossil-users] Delay with `fossil ui' (related to backoffice processing?)

2018-07-22 Thread Richard Hipp
On 7/21/18, Florian Balmer wrote: > > I see random delays for the `fossil ui' command, Please test the latest trunk version and let me know if you are still seeing issues. Anybody who has the capability, please also verify that "fossil server --scgi" is now working again. I do not have a SCGI

Re: [fossil-users] Delay with `fossil ui' (related to backoffice processing?)

2018-07-22 Thread Florian Balmer
Richard Hipp: > Hence, if the subprocess gets involves in backoffice work, that can > delay the return of content to the user. > The only comes up on Windows. I do not yet have a good work-around. I see, thank you very much for the detailed explanations. I only have the obvious (inefficient?)

Re: [fossil-users] Delay with `fossil ui' (related to backoffice processing?)

2018-07-22 Thread Florian Balmer
Thank very much for your feedback! Warren Young: > Which is it? With the random appearance of the delay, and the long duration of 60 seconds, I eventually gave up on "bisecting". But with a more systematic approach, I've now got: Last good: [06507038] First bad: [947081aa] > If the problem

Re: [fossil-users] Delay with `fossil ui' (related to backoffice processing?)

2018-07-22 Thread Florian Balmer
> ... writing to a FILE* pointing to NULL may have exactly the same > effect as writing to a FILE* pointing to "/dev/null"? Well, unless there's a directory named "dev" in the root of the current drive, which would result in creation (due to the passed "wb" mode) of a file named "null", on

Re: [fossil-users] Delay with `fossil ui' (related to backoffice processing?)

2018-07-22 Thread Warren Young
On Jul 22, 2018, at 1:18 AM, Florian Balmer wrote: > > [5544931c] src/backoffice.c:240 That’s brand new code, less than a week old. It’s not surprising it’s not rock-solid yet. I expect drh is now on the case. :) ___ fossil-users mailing list

Re: [fossil-users] Delay with `fossil ui' (related to backoffice processing?)

2018-07-22 Thread Richard Hipp
On 7/22/18, Florian Balmer wrote: > > Just a thought: would it make sense to have --nodelay as a global > option recognized by all commands, and maybe also through an > environment variable, and a CGI control option? So that any backoffice > processing could be temporarily disabled? Everything

Re: [fossil-users] Delay with `fossil ui' (related to backoffice processing?)

2018-07-22 Thread Florian Balmer
Richard Hipp: > Please test the latest trunk version and let me know if you are still > seeing issues. Thank you very much for the fix! I see no more delays with "fossil ui" on Windows. Just a thought: would it make sense to have --nodelay as a global option recognized by all commands, and