A new build, 0.2.0, is available. A new startup Control Panel and a lot of internal changes. See a summary of the changes here What's New in V0.2.0 Alpha
I have finally found the time to play around again with this against QSD. First, small sized app with relatively tidy data model, which worked really well.
Then I tried two of our messy applications with lot of comments and medium sized complexity in data model. However, both apps seem to have failed at the parsing phrase right at the end. I haven’t taken a detailed look at the error logs, but at a quick glace, it looks like long expressions with comments and lots of variables might have been the culprits. I am attaching the error logs, that might help. Let me know if you need the apps with no data, I can try to strip them of data and see if we can share them to help with your development.
PS: Cant attached log files in here. This is the link to the dropbox
I don’t think the parsing is the culprit, it’s another issue. I have another tester reporting a similar null pointer exception. I can’t seem to recreate so would very much like to have a copy of the app without data or obfuscated data.
Hi Kab,
0.2.2 fixes the QCS connection. I’ve also added quite a bit of diagnostic logging to help pin down errors. Can you try analyzing your big app again and if fails post the log/qsda-YYYY-MM-DD.log?
hmm getting new issue with the new built, I removed the old version and deleted the installation folders etc, cleared the browser cache too. Then proceeded with the installation of the new version. And now I can’t save my connection details. The buttons are disabled, I am putting the same information as yesterday. Both buttons are disabled for all options.
PS: I changed the host name there to something generic for the screen shot.
I will check with work to make sure they are ok with me sharing the app as its not an internal application. Meanwhile I will run it against some internal app tomorrow morning.
I found some time in between meetings, so quickly installed it. Good news, it worked with only 2 errors this time. I haven’t taken a look at the errors, I think it’s the expression used in the variable is wrong, not QSDA issue. But I have uploaded the logs so you can take a look.
What I can’t tell from the logs is if the remaining viz expressions were parsed or the expression processing stopped there. it looks like it may have stopped prematurely. If you looks at the fields page, do all expressions show Fields and Variables values?