On 9/21/2017 4:13 PM, Richard Hipp wrote:
> I think you can omit the IOERR_RETRY now. I believe I have fixed that
> problem in the Windows VFS of SQLite. At least, it works for me on my
> Win10 laptop when I set the repository file to read-only. Please try
> it and let me know either way.
Oh go
On 9/21/17, Andy Goth wrote:
> On 9/21/2017 3:48 PM, Richard Hipp wrote:
>> The latest check-in
>> (https://www.fossil-scm.org/fossil/info/e97d4443d5628702) loads a new
>> version of SQLite which should address the issues of trying to open a
>> read-only database file. Please try it and let me kn
On 9/21/2017 3:51 PM, Richard Hipp wrote:
> Your fix to the /doc webpage was also helpful, Andy. I had seen that
> error before but then it went away mysteriously and I was wondering
> what happened. Apparently I pulled in your fix while testing my
> changes, without realizing it. :-)
When test
On 9/21/2017 3:48 PM, Richard Hipp wrote:
> The latest check-in
> (https://www.fossil-scm.org/fossil/info/e97d4443d5628702) loads a new
> version of SQLite which should address the issues of trying to open a
> read-only database file. Please try it and let me know.
Looks good to me, provided I co
On 9/21/17, Richard Hipp wrote:
> On 9/21/17, Andy Goth wrote:
>>
>>> As an interim fix, can you recompile with -DSQLITE_WIN32_IOERR_RETRY=0
>>> and let me know if that clears the problem for you?
>>
>> This improves matters but doesn't totally fix everything. Fossil starts
>> far faster and no
On 9/21/17, Andy Goth wrote:
>
>> As an interim fix, can you recompile with -DSQLITE_WIN32_IOERR_RETRY=0
>> and let me know if that clears the problem for you?
>
> This improves matters but doesn't totally fix everything. Fossil starts
> far faster and no longer has the lock/sharing conflict warn
On 9/21/2017 3:17 PM, Andy Goth wrote:
> The winOpen() function then successfully retries with flags altered to
> contain SQLITE_OPEN_READONLY instead of SQLITE_OPEN_READWRITE, and this
> succeeds. Trouble is, winLog() was already called, and the error
> message propagated back to Fossil and event
On 9/21/2017 1:18 PM, Richard Hipp wrote:
> The problem is that the Windows VFS has logic that retries failed I/O
> operations repeatedly before giving up. This is a work-around to the
> common issue of anti-virus software holding files hostage while they
> are being scanned.
It was a mistake to
On Sep 21, 2017, at 11:16 AM, Andy Goth wrote:
>
> xyzzy...Nothing happens.
You win 10 geek points today.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
On 9/21/17, Andy Goth wrote:
>
> To reproduce, all that's needed is to set the repository file read-only in
> Windows, then run "fossil ui".
>
So it is. You can also repro by running a plain old "sqlite3.exe"
command-line shell. Start the shell with no argument, then type ".log
stdout" to cause
Nothing happens.
By which I mean Fossil refuses to start, saying it sees no xyzzy here. So,
twice as much happens.
Therefore it is honoring my VFS change, and picking win32-none is not the
solution to my problem.
To reproduce, all that's needed is to set the repository file read-only in
Windows,
On 9/21/17, Andy Goth wrote:
> I added "set FOSSIL_VFS=win32-none" to my documentation viewer batch file.
> This had no apparent effect. Is there another value I can give it that will
> have a more dramatic effect to confirm it's being seen by Fossil?
set FOSSIL_VFS=xyzzy
Then run: fossil statu
I added "set FOSSIL_VFS=win32-none" to my documentation viewer batch file.
This had no apparent effect. Is there another value I can give it that will
have a more dramatic effect to confirm it's being seen by Fossil?
On Sep 21, 2017 8:08 AM, "Richard Hipp" wrote:
> On 9/20/17, Andy Goth wrote:
On 9/20/17, Andy Goth wrote:
> I'm fine in Linux working from a loopback-mounted ISO9660 disc image,
> but in Windows 8.1 doing the same nets me the following:
>
> SQLITE_NOTE: delayed 1375ms for lock/sharing conflict at line 43312
> SQLITE_CANTOPEN: os_win.c:43319:(5) winOpen(E:\repo.fossil) - Ac
Okay cool, I'll tell the Air Force that's what they need to do.
On Thu, Sep 21, 2017 at 7:13 AM, Roy Keene wrote:
> Quit using Windows ?
>
>
> On Wed, 20 Sep 2017, Andy Goth wrote:
>
> I'm fine in Linux working from a loopback-mounted ISO9660 disc image,
>> but in Windows 8.1 doing the same nets
Quit using Windows ?
On Wed, 20 Sep 2017, Andy Goth wrote:
I'm fine in Linux working from a loopback-mounted ISO9660 disc image,
but in Windows 8.1 doing the same nets me the following:
SQLITE_NOTE: delayed 1375ms for lock/sharing conflict at line 43312
SQLITE_CANTOPEN: os_win.c:43319:(5) winO
I'm fine in Linux working from a loopback-mounted ISO9660 disc image,
but in Windows 8.1 doing the same nets me the following:
SQLITE_NOTE: delayed 1375ms for lock/sharing conflict at line 43312
SQLITE_CANTOPEN: os_win.c:43319:(5) winOpen(E:\repo.fossil) - Access is
denied.
Followed by what appea
17 matches
Mail list logo
