-
Notifications
You must be signed in to change notification settings - Fork 94
Conversation
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the |
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.
Overall LGTM, just failing some tests.
41d0812
to
88f358b
Compare
@alexeagle @gregmagolan @filipesilva This one is ready now. Can you please have a look? thanks! |
3e99790
to
f62e6f1
Compare
@googlebot I am ok with my commits being contributed to this project. |
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, great work @devversion!
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.
Could you minimize the Delta in Go code? This runs in Google3 also. We'll need another reviewer for that part
@alexeagle Unfortunately I don't think that I can reduce the diff here. Especially because the Go code is the breaking part for the runfiles on Windows. The go code currently just assumes that all runfiles are relative to the resolved root directory. This is not the case on Windows, and therefore we now resolve through the Bazel runfile utilities from Go. Can you elaborate what specific part runs inside of Google3? the whole devserver or just the individual parts like |
4ea44e3
to
3d38e11
Compare
The failure of |
@alexeagle If you find some time, could you start the tests again? 😄 ( |
c242b94
to
1b52aa7
Compare
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.
I had two minor comments, but I don't think I'm a good reviewer for this anyway so don't let me stop you.
A Googler has manually verified that the CLAs look good. (Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.) |
b14160d
to
cc1a219
Compare
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the |
A Googler has manually verified that the CLAs look good. (Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.) |
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the |
A Googler has manually verified that the CLAs look good. (Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.) |
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the |
A Googler has manually verified that the CLAs look good. (Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.) |
Note, we didn't merge the whole change, still needs another PR to enable the test on windows, by removing: |
Both bazelbuild/rules_typescript#327 and bazelbuild/rules_typescript#378 have circleci `test` jobs being killed: ``` Server terminated abruptly (error code: 14, error message: '', log file: '/home/circleci/.cache/bazel/_bazel_circleci/cced162ff126e466524550c57f0d7df5/server/jvm.out') ``` According to the note in https://github.com/bazelbuild/rules_typescript/blob/3671b8d5b6f5731e191098b6d5243c44f474c0da/.circleci/bazel.rc#L32-L38 this means the memory limit should be reduced. Closes bazel-contrib#380 PiperOrigin-RevId: 228881108
Both bazelbuild/rules_typescript#327 and bazelbuild/rules_typescript#378 have circleci `test` jobs being killed: ``` Server terminated abruptly (error code: 14, error message: '', log file: '/home/circleci/.cache/bazel/_bazel_circleci/cced162ff126e466524550c57f0d7df5/server/jvm.out') ``` According to the note in https://github.com/bazelbuild/rules_typescript/blob/845b16ca5f8202df3c3f845df2e9629e85217397/.circleci/bazel.rc#L32-L38 this means the memory limit should be reduced. Closes bazel-contrib#380 PiperOrigin-RevId: 228881108
No description provided.