-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Infra] Refactor ML job ID state management #171913
Labels
Comments
miltonhultgren
added
Team:obs-ux-logs
Observability Logs User Experience Team
Team:obs-knowledge
Observability Experience Knowledge team
labels
Nov 24, 2023
Pinging @elastic/obs-ux-logs-team (Team:obs-ux-logs) |
Pinging @elastic/obs-knowledge-team (Team:obs-knowledge) |
dej611
pushed a commit
that referenced
this issue
Nov 24, 2023
These tests rely on using browser performance timings to extract URLs used when resolving ML job IDs to check if the right format is used and updated when migrating to the new format. Because this change is transparent to the user there isn't any way to test the behaviour through UI elements and due to the structure of the state management it's not straight forward to test it in isolation. #171913 has been opened to refactor the state management which should allow for this tests to be updated and re-enabled.
emma-raffenne
removed
the
Team:obs-knowledge
Observability Experience Knowledge team
label
Jan 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#168234 introduced a new part of the state used to generate the ID for the ML jobs for logs. This proved hard to test in an easy way so the tests introduced in that PR have been disabled.
Most likely the best solution to the issue is the refactor the state management used for the ML job IDs.
Rather than storing the ID format, the log view ID and the space ID and using those pieces to generate the ID in multiple places, we would store a full version of the ID or even the full ML job object and use that across the UI and the API requests.
Once that is done, the tests would need to be refactored but the same test cases should be easier to express in that world without having to rely on capturing network traffic.
The text was updated successfully, but these errors were encountered: