Javascript errors in PixInsight 1.8.1 Linux 64 version.

[leeasle]

I'm getting some javascript errors in a few of the scripts in PixInsight 1.8.1 running under Mint 16, haven't had any issues until the 1.8.1 version.
The affected scripts are (so far) are AperturePhotometry and ImageSolver. I know just enough programming to be dangerous! Any suggestions to fix these?

Thanks
Lynn

Message logs as follows:

/opt/PixInsight/src/scripts/AdP/AperturePhotometry.js
** Warning [267]: /opt/PixInsight/src/scripts/AdP/SpectrophotometricCatalogs.js, line 33: in strict mode code, functions may be declared only at top level or immediately within another function
function III_126_Catalog()
.........^
*** Error [073]: /opt/PixInsight/src/scripts/AdP/AperturePhotometry.js, line 3383: SyntaxError: missing } after function body


Processing script file: /opt/PixInsight/src/scripts/AdP/ImageSolver.js
** Warning [267]: /opt/PixInsight/src/scripts/AdP/SearchCoordinatesDialog.js, line 33: in strict mode code, functions may be declared only at top level or immediately within another function
function fieldLabel(parent, text, width)
.........^
*** Error [073]: /opt/PixInsight/src/scripts/AdP/ImageSolver.js, line 2585: SyntaxError: missing } after function body

[Andres.Pozo]

I don't get those warnings. I haven't test them on Mint (only in Fedora 18), but it should work the same way.

You can try to reset the Javascript engine (Script editor\EXECUTE\Reset JavaScript Runtime) or restart PixInsight. If this fixes the warnings, then the problem would probably be in another script that you executed before ImageSolver or AperturePhotometry that corrupted the state of the Javascript engine. If the warnings persist I will need to study this more carefully. I have checked the functions that you said but they seem ok.

[leeasle]

It persists after a shutdown and restart, and I've tried the java engine reset. In addition I wiped the directory and re-installed. I wonder why its complaining about the missing closing bracket, that seems to be killing the scripts.

I might try bringing up a VM and installing it there to see if it will run there. But seems like so far I'm the only one having that issue, and the 1.8.0 version ran fine.

Never a dull moment!
Thanks
Lynn

[Juan Conejero]

I can confirm this problem. Interestingly and surprisingly, it only happens when PixInsight is installed on a system protected directory (/opt/PixInsight by default). It doesn't happen on local user installations—which explains why I haven't detected it before.

I am investigating this too. For now, a simple workaround is just running PixInsight from a sub-directory under $HOME, or from any place where the current user has read/write access. Be sure this will be fixed real fast.

[leeasle]

I'm still coming up with the same errors, originally tried just changing the /opt/PixInsight to my user and granting R/W access, didn't help, so installed a copy under home in my user directory. I'll try some other things, but running out of time for today.

Thanks
Lynn

[Juan Conejero]

Hi,

This bug is now fixed. However, after a thorough analysis, the cause of this problem is potentially much more serious than what it seems from its current manifestation.

Since solving this issue requires a full rebuild of the whole platform, I'm preparing a new release. Hopefully I'll have all installation packages ready today-tomorrow.

Sorry for the trouble.

[leeasle]

Thanks for the quick responses.

For what its worth, tried it in a fresh install in a VM, has the same errors, I'll wait till the rebuild comes out. I still consider PI one of my best upgrades in my astro-photogaphy  attempts.

Thanks.

[Juan Conejero]

This problem has been fixed in the new build 1083 of the PixInsight Core application. Sorry for the trouble.

[leeasle]

Scripts ran without any errors on the new build.
Thanks for the quick fix.

Lynn