Closed kb-ig closed 1 year ago
Thanks for the bug report. Does it happen on all tables or just specific ones?
@rathboma It seems quite inconsistent for some tables. When I was trying to capture that recording, it was 50/50 - sometimes it would work, and others not work (always the way when trying to capture a bug!). But now, I've just tried about 50 different tables across a number of different databases (all the same postgres version) and 100% hit this issue.
It seems to happen far less often with the developer tools window open. Following the 100% reproduce rate above with the dev tools closed, I can only reproduce around 10% of the time (maybe even less) with the dev tools open.
Sorry, I know this isnt very helpful :/ At first I thought it might be something to do with the table size (i.e. number of columns, number of constraints etc) but that doesnt seem to be the case. It also doesnt seem to be related to the number of rows in the table.
Just hit the same problem. I do not see a pattern yet. Happens on a production MySQL as well as local copy - the same tables. Also on a SQL Server tables.
Just in case the call stack is helpful
The same is happening to me
Thanks all, we're looking into it. Hopefully a hotfix coming in the next couple of days
Describe the bug When I right-click on a table and select the "View Structure" option, the table columns are shown for a second or two, then vanish and the BK shows "No Columns".
Checking in the dev tools, I can see two errors occuring:
Cannot read property 'style' of null
- as soon as the structure window opens (and the columns are displayed)RangeError: Maximum call
- a couple of seconds later, and the columns are no longer displayed after thisTo Reproduce Steps to reproduce the behavior:
Expected behavior Table structure should be shown and not disappear after a couple of seconds
Screenshots / Gifs If applicable, add screenshots or GIFS to help explain your problem.
Version Information (please complete the following information):
Additional context The problem does not seem to happen every time. Sometimes, if the problem does not happen, closing and reopening Beekeeper and then following the reproduce steps will cause the error to occur.