Plugin development error loop without useful feedback #48883
Labels
Team:Core
Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
triage_needed
Kibana version:
Current master
Elasticsearch version:
v8.0.0
Steps to reproduce:
This is one example of how to get the out-of-memory error loop going.
devTools
(here in searchprofiler) to a non-existent file.yarn start
Alternatively: if a non-existent module is imported into a
ts
file in combination with// @ts-ignore
the same result is achieved.Why would you ever do this? Primary reasons I can think of:
js
in newts
Expected behavior:
I would expect better feedback about the root cause. In the case described above it is the file that is not resolving correctly. Getting into this error state is very unhelpful.
Currently, for example, new platform migrations or instances of using
js
modules ints
modules can be very tricksy to debug.Logs in console:
Looks like the cause is
src/legacy/server/logging/apply_filters_to_keys.js: 27
, but this is obviously triggered by something else (see steps above)Sample of the repeating OOM exception:
The text was updated successfully, but these errors were encountered: