refactor: clean up types and imports#409
Conversation
Codecov Report
@@ Coverage Diff @@
## master #409 +/- ##
==========================================
- Coverage 90.49% 90.44% -0.05%
==========================================
Files 14 14
Lines 631 628 -3
Branches 34 34
==========================================
- Hits 571 568 -3
Misses 42 42
Partials 18 18
Continue to review full report at Codecov.
|
|
@stephenplusplus are you able to look into why system tests are failing here? |
|
I can't reproduce locally. Let's try a rebuild! |
|
Rebuild still failed. @jkwlui -- the error message, "Error: 3 INVALID_ARGUMENT: A monitored resource must be specified for each log entry", could relate to the logic where we find the most appropriate resource to go alongside a log entry dependent on the environment the code is in. That being said, I'm not sure how to simulate the Kokoro environment. Any ideas? |
|
Can you try something? If the grpc-js env var is set, just process.exit? I wonder if this is a race condition with system tests. |
|
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 ℹ️ Googlers: Go here for more info. |
|
I'm not 100% on what that env var is, but I went with this: 53691a1 Looks like Kokoro is having issues, though, so the suspense continues! |
|
@jkwlui is on the other issues |
|
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.) ℹ️ Googlers: Go here for more info. |
| callback?: CreateSinkCallback): Promise<[Sink, LogSink]>|void { | ||
| const self = this; | ||
| if (!is.string(name)) { | ||
| if (typeof name !== 'string') { |
There was a problem hiding this comment.
Would this be considered semver major?
[rant] Removal of is as a dependency doesn't fit into the spirit of this PR anyway. This only makes the review process more complex. Refactor PRs should be easy to review.
Open a separate PR for this change.
[/rant]
There was a problem hiding this comment.
Happy to :) So question tho - would you prefer a total drop of is, a move to the other is, or keeping this as is 🥁
There was a problem hiding this comment.
No objections to dropping is as semver-major. If the argument is that it is not breaking, it needs to be made.
|
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
Fixes #<issue_number_goes_here> (it's a good idea to open an issue first for discussion)