Diagnosis Warning - Fixed but...

[BanjoTom]

Running a routine Database Diagnosis I repeatedly got this "warning":

Checking Annotation Objects:
      Warning: Container with invalid dimensions found for file [202656]. Fixed.
Completed.

It says "fixed," but the warning persists.  How do I identify the file 202656 (which I'm guessing is a D&P template,  since it refers to a container) so I can fix this?

[Tveloso]

File 202656 should actually be one of the Files indexed in IMatch.

You can use the File Finder App to identify it...(one of the options there is to search by OID, and that's where you should enter 202656)

[Mario]

Each file in the database has one container, the container contains one or more layers, and a layer contains one or more annotation objects.

Invalid dimensions means that the size of the container did not match the size of the image. This has been corrected.
Not sure how this can happen. If you can recall what you did since the last diagnosis or you find some steps to reproduce this, let me know.

The main purpose of the database diagnosis is to detect issues I did not think of (yet) and to ensure everything IMatch does is valid. When I add a new suitable feature, the first thing is add some more tests, then the feature then add diagnosis routines to ensure the new feature behaves.

[BanjoTom]

I ran FileFinder with the OID of the file that generated a warning, and it pointed to a .txt file.  How do I fix the container or layer or annotation problem that keeps generating the same warning after each Database Diagnostic run?

[BanjoTom]

That .txt file had a linked person.  When I deleted that person-link, the Diagnostics for the database ran with NO warning!  So it seems that fixed it...

[Mario]

Linking a person to a text file...hm, I would never have thought users would so something like this.

But it explains that IMatch considered the dimensions of the container wonky, because a text file has no width or height.
I shall think about how to detect and handle this in the diagnosis.

[Mario]

I have fixed this false warning for the next release.