-
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
[App Search] Bugfix: Remove row from engine table after engine is deleted #94823
Conversation
c082ab1
to
9e70e0e
Compare
⏳ Build in-progress, with failures
Failed CI StepsHistory
To update your PR or re-run it, just comment with: |
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.
Ah I grabbed latest again and it's working for me now locally, sorry! QA looks great, thanks Byron. 🙏
As a total aside: while we're here, can also we add a color: 'danger'
to the trash icon to match our other tables? No worries if you'd rather handle separately (or if you want I can grab it), feel free to merge this as-is if so!
@elasticmachine merge upstream |
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: |
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Summary
Introduced a silly bug with my recent changes. I misunderstood how typescript
enums
work, and assuming that by default they used the property name as their value by default instead of an auto-incrementing integer. So while our code was fine with everything internally being integers, when it started getting data from our API, it was failing to refresh the data and remove the row. Sorry I missed this.QA
Checklist