-
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
Update @elastic/elasticsearch to v8.2.0-canary.2 #128633
Update @elastic/elasticsearch to v8.2.0-canary.2 #128633
Conversation
Pinging @elastic/kibana-core (Team:Core) |
@@ -111,6 +111,7 @@ export function modelsProvider(client: IScopedClusterClient, mlClient: MlClient) | |||
* Provides the ML nodes overview with allocated models. | |||
*/ | |||
async getNodesOverview(): Promise<NodesOverviewResponse> { | |||
// @ts-expect-error typo in type definition: MlGetMemoryStatsResponse.cluser_name |
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.
This will be fixed in the next canary version
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.
Core changes LGTM
// @ts-expect-error 'properties' does not exist on type 'MappingMatchOnlyTextProperty' | ||
isECS: !!indexMappings[name]?.mappings?.properties?.ecs?.properties?.version?.type, |
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.
😢
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.
Yes, even if this is a proper type fix (not all mapping types accepts a properties
property) this is actually a 'terrible' change for us.
TBH I blame TS a bit about this behavior:
type A = { foo: string; }
type B = { bar: string; }
type Composite = A | B;
const test: Composite = { foo: 'hello' };
// error 'foo' does not exist on type B
test.foo
I would love to have a way for TS to consider typeof test.foo
as being string | undefined
, but undeclared
and undefined
are two very distinct concepts for typescript...
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.
Deployment management changes LGTM - only 1 change in fetch_indices.ts
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.
ML changes LGTM
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.
Enterprise Search changes LGTM
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.
enterprise search changes LGTM
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.
Infra changes LGTM
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.
security solution changes LGTM.
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.
security solution changes LGTM.
@elasticmachine merge upstream |
2162407
to
55bba66
Compare
💛 Build succeeded, but was flakyTest Failures
Metrics [docs]Public APIs missing exports
History
To update your PR or re-run it, just comment with: |
* Update @elastic/elasticsearch to v8.2.0-canary.2 * fix core violation * add optional properties to our type * update generated doc * add another ts-ignore * remove unused ts-expect-error * add ts-expect-error for type typo * add ts-expect-error infra code * fix more errors (cherry picked from commit 158c617)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
* Update @elastic/elasticsearch to v8.2.0-canary.2 * fix core violation * add optional properties to our type * update generated doc * add another ts-ignore * remove unused ts-expect-error * add ts-expect-error for type typo * add ts-expect-error infra code * fix more errors (cherry picked from commit 158c617) Co-authored-by: Pierre Gayvallet <pierre.gayvallet@elastic.co>
Summary
Bump
@elastic/elasticsearch
to versionv8.2.0-canary.2
and adapt associated TS failures and violations