some date modified searches not working

[jimspoon]

Some date-modified searches aren't working on my desktop. Running 1.5.0.1371a.

For example, I've tried some of the examples shown at viewtopic.php?t=10176 - including:
dm:today - not working
dm:2024 - not working
dm:10mins - not working
When I do these searches, no files are filtered out by this function.
However, this one does work:
dm:2024-04-01..2024-04-04

I've also tried some date-modified syntax options listed in the Help > Search Syntax window, under Date Syntax: and Date Constants:

Under Tools > Options > Indexes, I do have "Index date modified" and "Fast date modified sort" checked.

I do have an enormous Everything index, over 32 million files and folders indexed. My Everything-1.5a.db is over 1.7GB.

Any ideas about this?

[void]

There might be a dm macro defined?

See if the following work:

date-modified:today
date-modified:2024
date-modified:10mins



Could you please send some debug output?

• Clear your search.
• From the Tools menu, under the Debug submenu, click Start Debug Logging...
• Set your search to:
  dm:today
• From the Tools menu, under the Debug submenu, click Stop Debug Logging...
  ---This will open your Everything Debug Log.txt in Notepad.
• Could you please reply with the contents of this file.

Please check the time and timezone is correct on your Desktop PC.
Copy and paste the following into your Everything search box:
/=FORMATFILETIME(NOW())
Press ENTER in your Everything search box.
The search should be replaced with the current date and time.
Please make sure this is correct.

[jimspoon]

Thank you Void I will do as you have suggested. For right now however I just want to report that the dm: function seems to be working just fine on my laptop. dm: searches that did not work on my desktop are working on the laptop. I will get back with you with debug info for the desktop. On the desktop I did remove a bunch of offline volume indexes from the database but that didn't solve the problem.

[ChrisGreaves]

Some date-modified searches aren't working on my desktop. Running 1.5.0.1371a.

To me a fascinating use of the date-modified search is to enter simple "C:" without quotes, in the search bar, and then sort by date-modified descending.

Untitled3.png (262.81 KiB) Viewed 758 times

The screen display updates every second or so as Everything re-samples its environment. The screenshot shown here indicates the file activity on the boot drive over the past six or seven minutes.
I walk away from the laptop to wash dishes or sieve soil, and return to see just how busy a laptop can be when not in use.
Cheers, Chris

[jimspoon]

Hi Void, the date-modified searches didn't work on my desktop - didn't filter out any files. I generated the debug log and it is attached. Also I entered the "/=FORMATFILETIME(NOW())" command and the following appears in the search box: "2024.04.06 10:57:17" (without the quotes). Maybe my unusual date/time format is causing the problem?

[NotNull]

Took a quick look at you debug log.
What stood out to me that while you were typing 'dm:today', when the 'd' was keyed in, not a single result was found.
I would at least expect c:\windows or D:\ to show up.

So it looks like there is more going on here...


Do you get results if you (temporary) stop indexing updates and retry your searches?:

• Menu => Index => Stop Updating
  STOPPED will be shown in the Everything statusbar
• Retry your search(es)
• Double-click STOPPED in the statusbar to resume processing updates
  (or Menu => Index => Update Indexes )

[void]

Thank you for the logs.

I would at least expect c:\windows or D:\ to show up.

The d search is cancelled due to the dm search and
the dm search is canceled due to the dm: search and so on..
Only the dm:today search completes.
-I'll make this easier to see from the logs in the next alpha update.



Everything finds 26 million files and 2 million folders modified today.
The search takes 75 seconds.

Is this unexpected? -Could you please expand on the 'not working' -Is Everything not showing these files for you after 75 seconds?
-What is shown in the status bar? 0 items or Querying...?

To me the query time is unexpected.
-This query should only be taking ~0.36 seconds. (32 million files and 4 threads) -Check your CPU is not throttled.
(on my PC, I'm seeing: ~0.045 seconds per 1 million files and one thread at ~4ghz)

The query is most likely bottle necking your RAM. -please also check your RAM, make sure it's using dual channel or quad channel.
Maybe Everything is being paged-to/unpaged-from disk..

Enable virtual_lock to help keep Everything in RAM.

/=FORMATFILETIME(NOW())" command and the following appears in the search box: "2024.04.06 10:57:17" (without the quotes). Maybe my unusual date/time format is causing the problem?

The format doesn't matter.
Was the date and time correct?

[jimspoon]

Away from my desktop for a day or two but I can answer some questions I think.

Everything finds 26 million files and 2 million folders modified today.
The search takes 75 seconds.

Is this unexpected?

Yes very! There's no way there were that many files and folders modified today (see below about how the files are not being filtered according to the dm condition). Regarding the delay, usually my Everything searches return results immediately. Sometimes Everything appears to freeze for awhile before it finally returns a result. But on this desktop I have other programs freezing, especially my xplorer2 file manager. I thought the huge size of my Everything database might be a problem for my system. But today I discovered my Manictime (time logger) database is 500+MB so now I wonder if that could be causing my "not responding" problems.

-Could you please expand on the 'not working' -Is Everything not showing these files for you after 75 seconds?

As far as the "dm:today" and other dm commands, what I mean by "not working" is that the results are not being filtered according to the specified date condition, it's as if the "dm:today" were not there at all. For example I had "ext:jpg" in the same search, and Everything showed all my jpg files (millions). And even with "date-modfied:today" entered in the search box, those same jpgs were displayed, from all dates, not just those for today. Oddly enough a date-modified condition entered in the format "dm:2024-04-01..2024-04-05" DID filter the results to show only files modified on those dates. And the number of files shown for this search is very modest, nothing like the 26 million indicated above.

-What is shown in the status bar? 0 items or Querying...?

To me the query time is unexpected.
-This query should only be taking ~0.36 seconds. (32 million files and 4 threads) -Check your CPU is not throttled.
(on my PC, I'm seeing: ~0.045 seconds per 1 million files and one thread at ~4ghz)

The query is most likely bottle necking your RAM. -please also check your RAM, make sure it's using dual channel or quad channel.
Maybe Everything is being paged-to/unpaged-from disk..

Enable virtual_lock to help keep Everything in RAM.

Will do when I can access the desktop again within the next couple of days. In case it's pertinent, it's an old system, it's got 24GB DDR3 RAM, I think 2x8GB + 2x4GB modules. Thanks for your help!

[void]

2024-04-06 10:51:55.728: 0000000110002358 20e01104 M 0000000000dee600 N 0000000000dee720 OP 739 today

Ah ha!

I know what the issue is..

It's the new ISO8601 wildcards.
I'm not initializing a value correctly and Everything is thinking this is a complex date-modified range.
Everything is converting all filetimes to local time to do the range comparison.
This is extremely CPU expensive.

I will have a fix soon.
For now, you'll need to specify a full range to get the expected results: dm:2024-04-01..2024-04-04

[jimspoon]

Great! I'm curious why dm:today worked on my desktop while it failed on my desktop, I guess it was because of the very much higher number of files on my desktop? (32 million files/folders).

And now I'm wondering - if I had preceded dm:today with other filters that would have reduced the number of files to be processed by dm:today, maybe it would have worked? Will try that when I can get back to my desktop.

[void]

it will randomly work or not work due to a wildcard value not being initialized correctly.

[NotNull]

The d search is cancelled due to the dm search and
the dm search is canceled due to the dm: search and so on..
Only the dm:today search completes.
-I'll make this easier to see from the logs in the next alpha update.

Thanks for explaining. While you're at it ..
saw a typo: prIOrity vs. prOIrity or similar (context was something like "set UI priority to high")
The earth might stop spinning if this does not get fixed within 3 months! This should be your top proirity from now on!

[void]

saw a typo: prIOrity vs. prOIrity or similar (context was something like "set UI priority to high")

Thank you for the typo report.
I had already removed these lines

[NotNull]

Thanks for saving the planet!

[void]

Everything 1.5.0.1372a fixes an issue with Everything using ISO8601 wildcard date/time searches instead of regular date/time searches.

dm:today should now be instant.

[anmac1789]

Everything 1.5.0.1372a fixes an issue with Everything using ISO8601 wildcard date/time searches instead of regular date/time searches.

dm:today should now be instant.

When I search for dm:10mins I get results from october...it's april 2024

[void]

I get results from october

Is the date in the future?



dm:10mins will look for files with a date modified timestamp in the range from 10 mins ago until the end of time..



To make Everything instead search for the range from 10 mins ago until now:

• In Everything 1.5, from the Tools menu, click Options.
• Click the Advanced tab on the left.
• To the right of Show settings containing, search for:
  now
• Select: date_cutoff_now
• Set the value to: true
• Click OK.

Please note: when enabled, you will not see any new results when using dm:10mins until you change your search.

[anmac1789]

I get results from october

Is the date in the future?

yes, its in date 2032...which is so wierd..

[void]

To set the date modified to now:

• Select the files from the future.
• From the Edit menu, under the Advanced submenu, click Set File time....
• Change Set date modified to: Now.
• Click OK.

[anmac1789]

To set the date modified to now:

• Select the files from the future.
• From the Edit menu, under the Advanced submenu, click Set File time....
• Change Set date modified to: Now.
• Click OK.

But this would reset the time to the current time but it won't reflect the true file date and time within the C drive

[NotNull]

but it won't reflect the true file date and time within the C drive

whereas a file date from the distant future (2032 !) does?

[anmac1789]

but it won't reflect the true file date and time within the C drive

whereas a file date from the distant future (2032 !) does?

uhh I didn't understand...

[ChrisGreaves]

To set the date modified to now:

Thank You!
And it works on a Selection of multiple files, too.
Cheers, Chris