Project Load Error with property id="XISF:..."

[frant]

I had to reboot my PC this afternoon, so saved everything to a new project, to reopen it all later. I didn't change any options in the property save dialog.
Upon re-opening the project I saw several errors in the console log regarding invalid property identifiers.

*** Error: Invalid property identifier: XISF:BlockAlignmentSize (line=1946,column=88)
*** Error: Invalid property identifier: XISF:CreationTime (line=1947,column=74)
*** Error: Invalid property identifier: XISF:CreatorApplication (line=1950,column=80)
*** Error: Invalid property identifier: XISF:CreatorModule (line=1953,column=75)
*** Error: Invalid property identifier: XISF:CreatorOS (line=1956,column=71)
*** Error: Invalid property identifier: XISF:ImageIdentifier (line=1959,column=77)
*** Error: Invalid property identifier: XISF:LoadTime (line=1962,column=70)
*** Error: Invalid property identifier: XISF:MaxInlineBlockSize (line=1965,column=88)
*** Error: Invalid property identifier: XISF:OutputHints (line=1966,column=73)
*** Error: Invalid property identifier: XISF:ResourceURL (line=1969,column=73)

The project continued to load fine, and the image corresponding to the errors also seems ok, at least as far as I can tell.

I'm running PixInsight Core 01.08.03.1123 Ripley (x64) on a Windows 7 (64-bit) PC.
I have attached the log output from the console: Project_Load_Error_Console_Log.txt
The project file was too large to attach, it can be found here: https://www.dropbox.com/s/m7ogm348lm2z0ze/all_wip.xosm?dl=0

The project data itself is huge, 5.9GB so not really practical to upload anywhere. I made an attempt to save another project with only the image in question to see if I could produce something smaller that replicated the issue, but to no avail.

Please let me know if there's any more info you need, happy to help the PixInsight project any way I can.

Regards,
Richard

[Juan Conejero]

Hi Richard,

Those errors are completely harmless. They happen because the current core application still isn't ready for some advanced features of the XISF format. I'll release a temporary version of the XISF module which does not propagate these properties to shut up these errors, until we release a new version of PixInsight in January.

You can simply ignore these errors. Sorry for the inconvenience.

[frant]

Hi Juan,

Not an inconvenience, and no need to apologise, I'm a software developer too and I know how these things go
Just thought I'd report it, in case there was an issue and it'd help improve the platform for everyone.
I love PixInsight, and thanks for all your hard work.

Regards,
Richard