After launching of Everything i can see in the lower left: "Index cancelled."
Current version: 1.5.0.1402a (x64)
this also happens with 1.5.0.1401a.
With previous versions i always saw: "Querying ..." for a few seconds before files begin to appear in the Everything window.
Now, after launching of Everything, i see "Index cancelled." before files begin to appear in the window.
"Querying ..." also appears quickly, but "Index cancelled." is appearing afterwards.
I have downgraded to 1.5.0.1400a and it is showing correctly showing "Querying ..." and then displays the file list.
After launching of Everything 1.5.0.1402a: "Index cancelled."
Re: After launching of Everything 1.5.0.1402a: "Index cancelled."
Thank you for the issue report stef,
I am unsure what the issue could be at this stage.
This message is shown when you cancel the initial index with Ctrl + Break or right click the Indexing progress bar and click Cancel.
Please upload your Help -> Troubleshooting Information in a bug report
I am unsure what the issue could be at this stage.
This message is shown when you cancel the initial index with Ctrl + Break or right click the Indexing progress bar and click Cancel.
Please upload your Help -> Troubleshooting Information in a bug report
Re: After launching of Everything 1.5.0.1402a: "Index cancelled."
I didn't press Ctrl + Break and didn't right-clicked the Indexing Progress Bar.
For a few seconds "Querying..." appears in the statusbar, with 1.5.0.14021 and newer "Index cancelled." appears in the statusbar.
previous versions: Querying...
1.5.0.1400a :Querying...
1.5.0.1401a: Querying...
1.5.0.1402a: Index cancelled.
everything seems to be running fine. nothing wrong in the index journal and it is correctly indexing files.
-----
After doing some intensive testing i think i found something.
I have switched to a different tab and suddenly "Index cancelled." doesn't appeared anymore after i have launched Everything.
I have made a backup of the file Session-1.5.a.json and compared it to a previous backup.
The only change was what tab has been selected.
If the last tab has been selected (in the case of 25 tabs = "tab_cursel":24), everything is fine if i launch Everything.
But if i select any other tab, "Index cancelled." always appears if i launch Everything.
So, it depends on the tab which has been selected.
I have prepared some verbose debug-logs with some session-1.5a.json-files. I will send them later today.
For a few seconds "Querying..." appears in the statusbar, with 1.5.0.14021 and newer "Index cancelled." appears in the statusbar.
previous versions: Querying...
1.5.0.1400a :Querying...
1.5.0.1401a: Querying...
1.5.0.1402a: Index cancelled.
everything seems to be running fine. nothing wrong in the index journal and it is correctly indexing files.
-----
After doing some intensive testing i think i found something.
I have switched to a different tab and suddenly "Index cancelled." doesn't appeared anymore after i have launched Everything.
I have made a backup of the file Session-1.5.a.json and compared it to a previous backup.
The only change was what tab has been selected.
If the last tab has been selected (in the case of 25 tabs = "tab_cursel":24), everything is fine if i launch Everything.
But if i select any other tab, "Index cancelled." always appears if i launch Everything.
So, it depends on the tab which has been selected.
I have prepared some verbose debug-logs with some session-1.5a.json-files. I will send them later today.
Re: After launching of Everything 1.5.0.1402a: "Index cancelled."
Thank you for the logs and sessions stef,
I was able to reproduce the issue from your session.
There's a bug when requesting the folders first status and the database is busy.
The wrong event gets put on the queue.
Once the database loads, you'll see the incorrect Index Cancelled message.
Unfortunately, there's no way to prevent this in builds 1401/1402.
I will post a fix soon.
I was able to reproduce the issue from your session.
There's a bug when requesting the folders first status and the database is busy.
The wrong event gets put on the queue.
Once the database loads, you'll see the incorrect Index Cancelled message.
Unfortunately, there's no way to prevent this in builds 1401/1402.
I will post a fix soon.
Re: After launching of Everything 1.5.0.1402a: "Index cancelled."
Everything 1.5.0.1403a fixes an issue with Everything firing an indexed cancelled event when requesting the folders first status.