You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Deephaven JS API expects at this time (see #188 to fix this) that subscriptions will have snapshots sent in one message, and deltas in at most two messages (one for added rows and metadata, one for modified rows).
However, for snapshots with more than 65536 rows, the server seems to split the initial snapshot into more than one FlightData payload, which causes an error in the JS API when it processes the second message:
To reproduce this, create a table with more than 65536, and try to get a full table subscription on it, such as for a scatter plot (at this time, scatter plots cannot be downsampled):
The Deephaven JS API expects at this time (see #188 to fix this) that subscriptions will have snapshots sent in one message, and deltas in at most two messages (one for added rows and metadata, one for modified rows).
However, for snapshots with more than 65536 rows, the server seems to split the initial snapshot into more than one FlightData payload, which causes an error in the JS API when it processes the second message:
To reproduce this, create a table with more than 65536, and try to get a full table subscription on it, such as for a scatter plot (at this time, scatter plots cannot be downsampled):
Next, click the downsample icon, next to the warning
!
that will appear on the chart's header, to confirm that downsampling should be disabled.Expected: data appears.
Actual: browser console shows an error message, no data appears.
The text was updated successfully, but these errors were encountered: