[Infra UI] Fix live tailing with the graphql api

[weltenwort]

Rename slice target to logPosition

The slice name target was seriously lacking in the desciptiveness department so I renamed it to logPosition. It contains the desired log position (as selected by the datepicker) as well as the reported log position. The polling state for "live streaming" (see below) is also managed by this slice.

Live streaming

This changes the live streaming functionality to poll the log entry and summary graphql endpoints. It is started and stopped using the startAutoReload and stopAutoReload action creators of the logPosition slice. These are used by the streaming toggle button besides the date picker to toggle a 5s polling interval:

idle

streaming

While streaming is enabled, the log text jumps to the bottom and a loading indicator is displayed, which contains the time since the last polling cycle to indicate the age of the currently displayed data.

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[weltenwort]

jenkins, test this

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[skh]

I tested this by starting, stopping, and restarting live streaming on several logs. I could trigger Maximum call stack size exceeded errors but not consistently.

Stack traces from the console:

and from the error page:

Uncaught RangeError: Maximum call stack size exceeded (:1)
Version: 7.0.0-alpha1
Build: 9007199254740991
Error: Uncaught RangeError: Maximum call stack size exceeded (:1)
    at window.onerror (http://localhost:5601/bundles/commons.bundle.js:199111:32)
    at Object.invokeGuardedCallbackDev (http://localhost:5601/bundles/commons.bundle.js:211853:16)
    at Object.invokeGuardedCallback (http://localhost:5601/bundles/commons.bundle.js:211902:29)
    at Object.invokeGuardedCallbackAndCatchFirstError (http://localhost:5601/bundles/commons.bundle.js:211916:43)
    at executeDispatch (http://localhost:5601/bundles/commons.bundle.js:212181:19)
    at executeDispatchesInOrder (http://localhost:5601/bundles/commons.bundle.js:212203:5)
    at executeDispatchesAndRelease (http://localhost:5601/bundles/commons.bundle.js:212301:5)
    at executeDispatchesAndReleaseTopLevel (http://localhost:5601/bundles/commons.bundle.js:212312:10)
    at forEachAccumulated (http://localhost:5601/bundles/commons.bundle.js:212282:8)
    at runEventsInBatch (http://localhost:5601/bundles/commons.bundle.js:212443:5)
    at runExtractedEventsInBatch (http://localhost:5601/bundles/commons.bundle.js:212452:3)
    at handleTopLevel (http://localhost:5601/bundles/commons.bundle.js:215916:5)
    at batchedUpdates (http://localhost:5601/bundles/commons.bundle.js:224252:14)
    at batchedUpdates (http://localhost:5601/bundles/commons.bundle.js:213654:12)
    at dispatchEvent (http://localhost:5601/bundles/commons.bundle.js:215997:5)
    at interactiveUpdates (http://localhost:5601/bundles/commons.bundle.js:224307:14)

Uncaught RangeError: Maximum call stack size exceeded (http://localhost:5601/bundles/commons.bundle.js:211955)
Version: 7.0.0-alpha1
Build: 9007199254740991
Error: Uncaught RangeError: Maximum call stack size exceeded (http://localhost:5601/bundles/commons.bundle.js:211955)
    at window.onerror (http://localhost:5601/bundles/commons.bundle.js:199111:32)

I was looking at the logs from demo-stack-apache-01 when this happened but can't immediately reproduce.

---

I also saw those in the browser console, but also not consistently:

warning.js:33 Warning: This synthetic event is reused for performance reasons. If you're seeing this, you're accessing the method `relatedTarget` on a released/nullified synthetic event. This is a no-op function. If you must keep the original synthetic event around, use event.persist(). See https://fb.me/react-event-pooling for more information.

(They appeared for several (all?) properties on the synthetic event, I only pasted one above.)

---

Are these known problems?

[weltenwort]

I came across that too, but it only happened to me with the redux devtools extension active. Something about the way it hooks into the store causes things to go wrong. Does the problem occur for you without the devtools active?

[skh]

No, I couldn't reproduce without redux devtools active either.

[weltenwort]

@skh I found the reason for the devtools problem and fixed it (an accidental event object passed to the stopAutoReload action creator). Thanks for bringing it up again 👍

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[skh]

Looks good, I can't reproduce the error anymore!