-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Visualizations are not displayed cause to Types was not set
error
#4199
Comments
ResearchThis problem was introduced when replacing the way to build the visualizations in this PR. The related logic is https://github.com/wazuh/wazuh-kibana-app/pull/4166/files#diff-42e6e019bbfdef197e9fa0e231f0018792ce92f8fa2db530e5c506beef79ceb4R287-R294. This builds the visualization and apply the defined colors in the visualization correctly only in development mode. With the built package, it appears the RemediationRevert how the visualization was created using the Bug in .createVis method of
|
…in a production package - fix `Types was not set` error appearing in production package More information in: #4199 (comment)
… production package (#4200) * fix: fix an error that avoids the visualizations are built correctly in a production package - fix `Types was not set` error appearing in production package More information in: #4199 (comment) * changelog: add PR entry
… production package (#4200) * fix: fix an error that avoids the visualizations are built correctly in a production package - fix `Types was not set` error appearing in production package More information in: #4199 (comment) * changelog: add PR entry (cherry picked from commit e8c4815)
… production package (#4200) * fix: fix an error that avoids the visualizations are built correctly in a production package - fix `Types was not set` error appearing in production package More information in: #4199 (comment) * changelog: add PR entry (cherry picked from commit e8c4815)
… production package (#4200) * fix: fix an error that avoids the visualizations are built correctly in a production package - fix `Types was not set` error appearing in production package More information in: #4199 (comment) * changelog: add PR entry (cherry picked from commit e8c4815)
… was not set error in a production package (#4213) [FIX] Visualizations are not built due a Types was not set error in a production package (#4200) * fix: fix an error that avoids the visualizations are built correctly in a production package - fix `Types was not set` error appearing in production package More information in: #4199 (comment) * changelog: add PR entry (cherry picked from commit e8c4815) Co-authored-by: Antonio <34042064+Desvelao@users.noreply.github.com>
…pes was not set error in a production package (#4214) [FIX] Visualizations are not built due a Types was not set error in a production package (#4200) * fix: fix an error that avoids the visualizations are built correctly in a production package - fix `Types was not set` error appearing in production package More information in: #4199 (comment) * changelog: add PR entry (cherry picked from commit e8c4815) Co-authored-by: Antonio <34042064+Desvelao@users.noreply.github.com>
… not built due a Types was not set error in a production package (#4215) [FIX] Visualizations are not built due a Types was not set error in a production package (#4200) * fix: fix an error that avoids the visualizations are built correctly in a production package - fix `Types was not set` error appearing in production package More information in: #4199 (comment) * changelog: add PR entry (cherry picked from commit e8c4815) Co-authored-by: Antonio <34042064+Desvelao@users.noreply.github.com>
Description
In Kibana 7.10.2 appears an error in the visualizations that avoid hey are built and rendered correctly.
Screenshots
The text was updated successfully, but these errors were encountered: