Problem with grid data synchronization and call stack error in Dev Console with 10.0

[senordhuff]

Hello,

I'm seeing a problem in your latest 10.0 nightly from 9/25/14 where adding a new record to one ListGrid is not automatically adding the record to another ListGrid that shares the same datasource. This exact operation is working with smartclient 9.1. I tried to find a suitable Feature Explorer demo to test this out and couldn't find one. Any suggestions?

In the past when i try to debug issues like this, I can review the dev console output by putting ResultSet into Debug. However, when I do that I get an error in the Dev console like this with Google Chrome:

Uncaught RangeError: Maximum call stack size exceeded ISC_Core.js?isc_version=v10.0p_2014-09-25.js:285isc_c_Class_fireCallback ISC_Core.js?isc_version=v10.0p_2014-09-25.js:285isc_c_Timer__fireTimeout ISC_Core.js?isc_version=v10.0p_2014-09-25.js:1259(anonymous function)

We've had similar issues in the past because of nested Datasources. The top level datasource for this grid has several nested Datasources attached to it including references to the top-level Datasource.

Suggestions on how to figure this out? I'm wondering if this call stack error is contributing to the problem with grid synchronization.

[claudiobosticco]

Hi senordhuff , please verify if you're having the same problem I've got:
http://forums.smartclient.com/showth...t=31148&page=2

[senordhuff]

Claudio, I'm guessing it is a different problem since they said they fixed your problem in last night's build?

[claudiobosticco]

Sorry, I've just replied: the problem seems still there: http://forums.smartclient.com/showpost.php?p=124637&postcount=21

[Isomorphic]

Grid synchronization and log level setting in the Developer Console is working in general.

As far as troubleshooting your grid synchronization problem given your odd issue with the Developer Console, you should be able to programmatically change the ResultSet log level, without opening the Developer Console, by calling Log.setLogPriority(). You can also obtain the current log messages as one big string via Log.getMessages() if you end up even more broken somehow.

As far as your issue with the Developer Console, are you able to get any more information than that? You're showing "Maximum call stack size exceeded" with a stack only a few levels deep. Did you perhaps trim the output?

[Isomorphic]

This issue may be fixed by the upcoming 10/15 build. Please give it a shot.

[Isomorphic]

To clarify - the fixes in the 10/15 build will likely resolve the stack overflow that you're seeing when attempting to debug this. But they may not fix the grid synchronization issue. Let us know how it goes please!

[senordhuff]

Thank you. Both grid synchronization and resultset debug logging are now working with the 10/15 build.

[Isomorphic]

Good to hear - thanks for the confirmation