UI sometimes shows an incorrect "old" version of a table

[rbasralian]

Sometimes, when working on queries in a code studio, it's possible to wind up in a state where a UI panel is incorrectly pointing to an old version of a table that used the same variable name.

For example, in the screenshot below, if you look at t5 on the left (the old/bad version of t5) vs. the t5 on the right (the new/good version of t5), you can clearly see from the "ModTime2" column that they are actually different tables.

This is with Version 1.20230511.106 (29a6afd7).

Here is an easy way to reproduce this:

1. Run any simple query (e.g. t = db.i("DbInternal", "ProcessEventLog").where().sort("Timestamp"))
2. Click the button to show the table (e.g. the t button):
3. Run another query using the same table variable (e.g. t = db.i("DbInternal", "QueryPerformanceLog").where())
4. Now you have two different tables called t: . (The one on the left is wrong; it should have updated to show the QuryPerformanceLog.)
5. If you disconnect the code studio, the first panel (the wrong one) stays around, even with "Close tables on disconnect" checked:

[rbasralian]

One other detail — when this happens, the "old, broken" tab still hangs around after I restart my console session, even though I have "Close Panels on Disconnect" checked

I also have these warnings/errors in the browser:

LogProxy.js:87 Failed to apply filters: [Id == "9056cafb-8e02-4df4-bf0b-6be4582d8885"] Table was changed before request completed, this can be safely ignored.
isEnabled.console.error @ LogProxy.js:87
LogProxy.js:87 Failed to apply filters: [Id == "ce34460a4-c9b0-47e5-9073-8bcea167872d"] Table was changed before request completed, this can be safely ignored.
irisapi.nocache.js:56030 WebSocket is already in CLOSING or CLOSED state.
$lambda$1_17 @ irisapi.nocache.js:56030
irisapi.nocache.js:56030 WebSocket is already in CLOSING or CLOSED state.
$lambda$1_17 @ irisapi.nocache.js:56030
b9fab0f5-89de-488c-bfd1-1590c687b0bd:1 Uncaught (in promise) Table was changed before request completed, this can be safely ignored.

[rbasralian]

This also happens if you right-click a tab and select "Copy panel". In that case, the copy won't update when you redefine the table: