Kibana version:
7.6.1
Describe the bug:
The react-beautiful-dnd library, upgraded during the 7.6 stack release from
10.0.1 to 12.2.0, includes a breaking change to the way errors are handled
and recovered. As a result of this change, an uncaught error may trigger a
an effect that feels (from the perspective of a user) like a partial page
reload.
The most common condition where this can occur is when dragging entries to the
Timeline while data is loading, per the animated gif below:
Steps to reproduce:
- Navigate to the Hosts page
- Open the Timeline
- Drag a host to the Timeline
- While data is still loading, drag a different host to the Timeline to create an
or query
Expected Results
- The page does not appear to reload
- In development mode, a single error is logged to the JS console
Actual Results
- The page appears to reload
- In development mode, two errors are logged to the JS console
Error 1
react-beautiful-dnd
Invariant failed: Cannot find droppable entry with id [droppableId.content.event-details-value-default-draggable-plain-column-renderer-formatted-field-value-timeline-1-kLGooXABOOUskGlPiQw5-@timestamp-1583260131000]👷<200d> This is a development only message. It will be removed in production builds.
in Draggable (created by ConnectFunction)
in ConnectFunction (created by PrivateDraggable)
in PrivateDraggable (created by PublicDraggable)
in PublicDraggable (created by Droppable)
in Droppable (created by ConnectFunction)
in ConnectFunction
Error 2
react-beautiful-dnd
Invariant failed: Cannot find droppable entry with id [droppableId.content.event-details-value-default-draggable-plain-column-renderer-formatted-field-value-timeline-1-kLGooXABOOUskGlPiQw5-@timestamp-1583260131000]👷<200d> This is a development only message. It will be removed in production builds.
in ErrorBoundary (created by DragDropContext)
in DragDropContext (created by Anonymous)
in Anonymous
Kibana version:
7.6.1Describe the bug:
The
react-beautiful-dndlibrary, upgraded during the7.6stack release from10.0.1to12.2.0, includes a breaking change to the way errors are handledand recovered. As a result of this change, an uncaught error may trigger a
an effect that feels (from the perspective of a user) like a partial page
reload.
The most common condition where this can occur is when dragging entries to the
Timeline while data is loading, per the animated gif below:
Steps to reproduce:
orqueryExpected Results
Actual Results
Error 1
Error 2