Author Topic: B4 error on first run  (Read 5047 times)

jporkkahtc

  • Senior Community Member
  • Posts: 2620
  • Hero Points: 210
  • Text
B4 error on first run
« on: September 19, 2019, 05:37:44 PM »
---------------------------
SlickEdit Pro
---------------------------
Restore: Access denied
---------------------------
OK   
---------------------------


Bug#1: Access denied on which file?
I had to resort to using PROCMON.exe to figure this out.

This is just as bad as the occasional "File Not Found" box that doesn't identify the file.
Turns out, it wasn't a Slick configuration file that I initially thought it must be

Bug#2: Slick finished opening, but didn't restore the editor windows -- toolbars and such are OK, but no editor windows opened.

Also, it seems to stop restoring the rest of the files that should have been restored.


Bug #3: The dialog is unclear.
I thought Slick had a problem with some slick config file - especially since this was the first run of B4.
Turns out, it just couldn't access a file that had been open last time I ran slick.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 6823
  • Hero Points: 526
Re: B4 error on first run
« Reply #1 on: September 19, 2019, 08:30:16 PM »
Any idea how I can reproduce this specific error?

Auto-restore seems to handle file not found well. It just continues without prompting.

Another common problem is a network directory which is no longer accessible. This will cause a long delay (like 30 seconds on Windows). auto-restore just stops after displaying a message box. This could be improved. We need to avoid lots of long delays.

jporkkahtc

  • Senior Community Member
  • Posts: 2620
  • Hero Points: 210
  • Text
Re: B4 error on first run
« Reply #2 on: September 19, 2019, 08:41:49 PM »
The file in question was
C:\src\foo\bar\.vs\myVS2017Project\v15\Server\sqlite3\db.lock

In Slick, open that file plus a bunch of other files.
Close slick.

Open "myVS2017Project.sln" in VisualStudio2017.
Start debugging.
devenv will now be holding a lock on that file.

Start Slickedit.
It fails during restore.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 6823
  • Hero Points: 526
Re: B4 error on first run
« Reply #3 on: September 20, 2019, 07:56:14 PM »
Thanks. I should be able to reproduce that even without Visual Studio.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 6823
  • Hero Points: 526
Re: B4 error on first run
« Reply #4 on: September 23, 2019, 04:33:56 PM »
Fixed for next build. SlickEdit will just continue auto-restore when there is a failure restoring a file.

jporkkahtc

  • Senior Community Member
  • Posts: 2620
  • Hero Points: 210
  • Text
Re: B4 error on first run
« Reply #5 on: September 23, 2019, 05:10:25 PM »
In the failed to load a buffer case, does slick check for specific error codes to ignore, or just ignore all?

In most cases I think it is a bad practice to look at specific error codes, but in this case there is a terrible one to ignore -- the case where the file is not found because a file share is not available.

If the saved state has 10 files on some file share, then just ignoring these errors when trying to restore will cause slick to hang for a *really* long time. (Unless of course, slick is doing async IO to open all the files at the same time :-) ).

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 6823
  • Hero Points: 526
Re: B4 error on first run
« Reply #6 on: September 24, 2019, 12:17:57 AM »
Code has been added to reduce the amount of time spent waiting for access to some network. SlickEdit will wait 2 seconds and then force the fail. Previously, this time could be as long as 30 seconds and was OS and Network dependent.

All errors are handle the same. Just continue to restore the files you can.

jporkkahtc

  • Senior Community Member
  • Posts: 2620
  • Hero Points: 210
  • Text
Re: B4 error on first run
« Reply #7 on: September 26, 2019, 05:36:59 PM »
Another case I found:
---------------------------
SlickEdit Pro
---------------------------
Restore: gzip program not found in PATH
---------------------------
OK   
---------------------------


If I have 3 *.GZ files to be restored and gzip is not in my path, how many times will I see this popup error?

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 6823
  • Hero Points: 526
Re: B4 error on first run
« Reply #8 on: September 26, 2019, 09:50:39 PM »
No popup message are displays for errors unless you are restoring from an auto-save crash restore file.