-
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
[packages] Move @kbn/interpreter to Bazel #101089
Conversation
Pinging @elastic/kibana-operations (Team:Operations) |
"build": "node scripts/build", | ||
"kbn:bootstrap": "node scripts/build --dev", | ||
"kbn:watch": "node scripts/build --dev --watch" | ||
"interpreter:peg": "../../node_modules/.bin/pegjs src/common/lib/grammar.peg" |
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.
can we run this as part of bootstrap ?
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.
@jbudz probably in order to accomplish this we need to do something like https://github.com/elastic/kibana/blob/master/packages/kbn-tinymath/BUILD.bazel#L33
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.
except that interpreter is not using peggy yet but still the old pegjs.
i am ok with moving to peggy in the same pr as long as it doesn't break
whats the status on this ? |
@elasticmachine merge upstream |
jenkins, test it |
seems issue still persists, grammar file can't be found .... and a bunch of types failling (maybe due to the same reason?) i guess all the type failiures can be mitigating by using ExpressionAst type from expressions plugin rather that the Ast type from the package |
@ppisljar everything is now working |
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!
@elasticmachine merge upstream |
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.
Kibana app changes LGTM, code review only
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.
Code review only, Presentation team changes LGTM!
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]Async chunks
Page load bundle
History
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.
LGTM
💔 Backport failed
To backport manually run: |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Co-authored-by: Tiago Costa <[email protected]> Co-authored-by: Kibana Machine <[email protected]> Co-authored-by: Tiago Costa <[email protected]> Co-authored-by: Kibana Machine <[email protected]>
Friendly reminder: Looks like this PR hasn’t been backported yet. |
1 similar comment
Friendly reminder: Looks like this PR hasn’t been backported yet. |
@jbudz I think this is correctly backported right? |
Part of #69706
That PR moves the @kbn/interpreter into Bazel by pushing a BUILD file for that package.
After merging this the package will be consumed from within bazel-bin folder.