-
Notifications
You must be signed in to change notification settings - Fork 198
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
[FIX] Visualizations are not built due a Types was not set error in a production package #4200
Merged
AlexRuiz7
merged 2 commits into
4.3-7.10
from
fix/4199-visualization-types-was-not-set-error
Jun 6, 2022
Merged
[FIX] Visualizations are not built due a Types was not set error in a production package #4200
AlexRuiz7
merged 2 commits into
4.3-7.10
from
fix/4199-visualization-types-was-not-set-error
Jun 6, 2022
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…in a production package - fix `Types was not set` error appearing in production package More information in: #4199 (comment)
|
asteriscos
approved these changes
Jun 3, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Machi3mfl
approved these changes
Jun 6, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CR ✅
Test ✅
AlexRuiz7
approved these changes
Jun 6, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
github-actions bot
pushed a commit
that referenced
this pull request
Jun 6, 2022
… 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)
github-actions bot
pushed a commit
that referenced
this pull request
Jun 6, 2022
… 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)
github-actions bot
pushed a commit
that referenced
this pull request
Jun 6, 2022
… 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)
Desvelao
added a commit
that referenced
this pull request
Jun 7, 2022
… 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 <[email protected]>
Desvelao
added a commit
that referenced
this pull request
Jun 7, 2022
…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 <[email protected]>
Desvelao
added a commit
that referenced
this pull request
Jun 7, 2022
… 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 <[email protected]>
This was
linked to
issues
Jun 8, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR fixes an error that appears in the production package when building the visualizations. The problem doesn't appear in development mode, as they are rendered correctly.
Changes
Screenshots
Test
Evolution
visualization ofAgents
section is displayed with the expected colors for the status labels.Closes #4199