Skip to content
This repository was archived by the owner on Mar 11, 2026. It is now read-only.

refactor: clean up types and imports#409

Merged
JustinBeckwith merged 2 commits intomasterfrom
fixy
Mar 9, 2019
Merged

refactor: clean up types and imports#409
JustinBeckwith merged 2 commits intomasterfrom
fixy

Conversation

@JustinBeckwith
Copy link
Copy Markdown
Contributor

Fixes #<issue_number_goes_here> (it's a good idea to open an issue first for discussion)

  • Tests and linter pass
  • Code coverage does not decrease (if any source code was changed)
  • Appropriate docs were updated (if necessary)

@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Mar 1, 2019
@codecov
Copy link
Copy Markdown

codecov Bot commented Mar 1, 2019

Codecov Report

Merging #409 into master will decrease coverage by 0.04%.
The diff coverage is 86%.

Impacted file tree graph

@@            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
Impacted Files Coverage Δ
src/sink.ts 96.42% <ø> (ø) ⬆️
src/index.ts 99.44% <100%> (-0.01%) ⬇️
src/entry.ts 100% <100%> (ø) ⬆️
src/log.ts 80% <82.92%> (-0.24%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9a2884e...9a19288. Read the comment docs.

@jkwlui
Copy link
Copy Markdown
Contributor

jkwlui commented Mar 4, 2019

@stephenplusplus are you able to look into why system tests are failing here?

@AVaksman AVaksman added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Mar 5, 2019
@kokoro-team kokoro-team removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Mar 5, 2019
@stephenplusplus stephenplusplus self-assigned this Mar 6, 2019
@stephenplusplus stephenplusplus added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Mar 6, 2019
@stephenplusplus
Copy link
Copy Markdown
Contributor

I can't reproduce locally. Let's try a rebuild!

@kokoro-team kokoro-team removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Mar 6, 2019
@stephenplusplus
Copy link
Copy Markdown
Contributor

stephenplusplus commented Mar 6, 2019

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?

@JustinBeckwith
Copy link
Copy Markdown
Contributor Author

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.

@googlebot
Copy link
Copy Markdown

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 cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

ℹ️ Googlers: Go here for more info.

@googlebot googlebot added cla: no This human has *not* signed the Contributor License Agreement. and removed cla: yes This human has signed the Contributor License Agreement. labels Mar 6, 2019
@stephenplusplus
Copy link
Copy Markdown
Contributor

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!

@JustinBeckwith
Copy link
Copy Markdown
Contributor Author

@jkwlui is on the other issues

@JustinBeckwith JustinBeckwith added cla: yes This human has signed the Contributor License Agreement. and removed cla: no This human has *not* signed the Contributor License Agreement. labels Mar 7, 2019
@googlebot
Copy link
Copy Markdown

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.

@JustinBeckwith JustinBeckwith added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Mar 7, 2019
@kokoro-team kokoro-team removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Mar 7, 2019
Comment thread src/index.ts Outdated
callback?: CreateSinkCallback): Promise<[Sink, LogSink]>|void {
const self = this;
if (!is.string(name)) {
if (typeof name !== 'string') {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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]

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Happy to :) So question tho - would you prefer a total drop of is, a move to the other is, or keeping this as is 🥁

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No objections to dropping is as semver-major. If the argument is that it is not breaking, it needs to be made.

@googlebot
Copy link
Copy Markdown

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

@yoshi-automation yoshi-automation added the 🚨 This issue needs some love. label Mar 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

cla: yes This human has signed the Contributor License Agreement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants