Skip to content
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

Spelling #9778

Merged
merged 46 commits into from
Oct 16, 2020
Merged

Spelling #9778

merged 46 commits into from
Oct 16, 2020

Conversation

jsoref
Copy link
Contributor

@jsoref jsoref commented Oct 11, 2020

This PR corrects misspellings identified by the check-spelling action.

The misspellings have been reported at jsoref@6819186#commitcomment-43154265

The action reports that the changes in this PR would make it happy: jsoref@d52634d

Note: this PR does not include the action. If you're interested in running a spell check on every PR and push, that can be offered separately.

Spelling errors make code harder to read, they lead to various other kinds of bugs, they make it harder to search for tokens, ...
I can file an issue for this if requested.

Proposed Changes

  • spelling

Release Note

NONE

@knative-prow-robot knative-prow-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Oct 11, 2020
@knative-prow-robot knative-prow-robot added area/API API objects and controllers area/autoscale labels Oct 11, 2020
@knative-prow-robot
Copy link
Contributor

Welcome @jsoref! It looks like this is your first PR to knative/serving 🎉

@knative-prow-robot
Copy link
Contributor

Hi @jsoref. Thanks for your PR.

I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@knative-prow-robot knative-prow-robot added area/networking needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. area/test-and-release It flags unit/e2e/conformance/perf test issues for product features labels Oct 11, 2020
@google-cla google-cla bot added the cla: yes Indicates the PR's author has signed the CLA. label Oct 11, 2020
Copy link
Contributor Author

@jsoref jsoref left a comment

Choose a reason for hiding this comment

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

Note: Spelling corrections were mostly picked automatically by Google Sheets, it's quite possible I've messed up, but I try to review before submitting...

@@ -83,7 +83,7 @@ data:
logging.request-log-template: '{"httpRequest": {"requestMethod": "{{.Request.Method}}", "requestUrl": "{{js .Request.RequestURI}}", "requestSize": "{{.Request.ContentLength}}", "status": {{.Response.Code}}, "responseSize": "{{.Response.Size}}", "userAgent": "{{js .Request.UserAgent}}", "remoteIp": "{{js .Request.RemoteAddr}}", "serverIp": "{{.Revision.PodIP}}", "referer": "{{js .Request.Referer}}", "latency": "{{.Response.Latency}}s", "protocol": "{{.Request.Proto}}"}, "traceId": "{{index .Request.Header "X-B3-Traceid"}}"}'

# If true, the request logging will be enabled.
# NB: up to and including Knative version 0.18 if logging.requst-log-template is non-empty, this value
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Google says that this is not present beyond one gist

@@ -109,7 +109,7 @@ type revisionWatcher struct {
logger *zap.SugaredLogger

// podsAddressable will be set to false if we cannot
// probe a pod directly, but its cluster IP has beeen successfully probed.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sometimes people intentionally add extra letters, this doesn't appear to be such an instance

@@ -179,7 +179,7 @@ func (r *reconcilerImpl) Reconcile(ctx context.Context, key string) error {
logger := logging.FromContext(ctx)

// Initialize the reconciler state. This will convert the namespace/name
// string into a distinct namespace and name, determin if this instance of
// string into a distinct namespace and name, determine if this instance of
Copy link
Contributor Author

Choose a reason for hiding this comment

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

It wouldn't shock me if I'm supposed to change this elsewhere, just let me know where and I should be able to eventually.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@tcnghia: there's a vendor/ directory in this repository, often those are directories that people aren't supposed to change directly, it has instances with determin -- can I just change them directly? Or is there an appropriate place to change it. Here's what my local clones have:
https://gist.github.com/jsoref/6115a4ce35488ecc6797ec3cb79563b4

Copy link
Member

Choose a reason for hiding this comment

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

don't change vendor directory, it gets auto populated with some tooling we have. is a mix of internal and external modules

@@ -44,7 +44,7 @@ func ReconcileCertificate(ctx context.Context, owner kmeta.Accessor, desired *v1

recorder := controller.GetEventRecorder(ctx)
if recorder == nil {
return nil, fmt.Errorf("recoder for reconciling Certificate %s/%s is not created", desired.Namespace, desired.Name)
return nil, fmt.Errorf("recorder for reconciling Certificate %s/%s is not created", desired.Namespace, desired.Name)
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm always worried about changes like his, but as the line above is recorder, I'm relatively confident here

pkg/reconciler/route/table_test.go Show resolved Hide resolved
// We want exactly 2. Not 1, not panicing 3, just 2.
// We want exactly 2. Not 1, not panicking 3, just 2.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I understand that the verb is panic. The English conjugation is panicking. afaik, panicing isn't commonly (ngrams, trends) used.

Copy link
Contributor

Choose a reason for hiding this comment

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

this is more like (panic)ing as in go's panic.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, I get that.

https://www.google.com/search?q=go+%22panicing%22
~298,000 results
+Did you mean: go "panicking"

https://www.google.com/search?q=go+%22panicking%22
~14,300,000 results

Copy link
Member

Choose a reason for hiding this comment

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

this looks good panicking

@tcnghia
Copy link
Contributor

tcnghia commented Oct 11, 2020

/ok-to-test

@knative-prow-robot knative-prow-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Oct 11, 2020
@tcnghia
Copy link
Contributor

tcnghia commented Oct 11, 2020

@jsoref very nice through update, thanks. Can you please rerun hack/update-codegen.sh (see https://github.com/knative/serving/pull/9778/checks?check_run_id=1239381808 )

@jsoref
Copy link
Contributor Author

jsoref commented Oct 11, 2020

@tcnghia: I don't think I have a working go install. I'll have to look later. (I'm happy to give write bits to my fork too...)

@tcnghia
Copy link
Contributor

tcnghia commented Oct 11, 2020

@tcnghia: I don't think I have a working go install. I'll have to look later. (I'm happy to give write bits to my fork too...)

@n3wscott @mattmoor I wonder if this is something we can automate so that our less-frequent contributors can just do /update-codegen and get a commit :) -- or a downloadable patch to use with git apply

@jsoref

This comment has been minimized.

@mattmoor
Copy link
Member

cc @n3wscott

I was just using his library 😉

@n3wscott
Copy link
Contributor

We never have supported bash 3, only bash 4

jsoref added 14 commits October 15, 2020 09:35
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
@csantanapr
Copy link
Member

Very nice job @jsoref 👍

@@ -20,7 +20,7 @@ metadata:
labels:
serving.knative.dev/release: devel
annotations:
knative.dev/example-checksum: "12baeac1"
knative.dev/example-checksum: "1d830d9e"
Copy link
Member

Choose a reason for hiding this comment

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

remove this change, nothing to do with the spell checking

@@ -149,7 +149,7 @@ func TestQueueTraceSpans(t *testing.T) {
h := queue.ProxyHandler(breaker, network.NewRequestStats(time.Now()), true /*tracingEnabled*/, proxy)
h(writer, req)
} else {
h := health.ProbeHandler(healthState, tc.prober, true /* isAggresive*/, true /*tracingEnabled*/, nil)
h := health.ProbeHandler(healthState, tc.prober, true /* isAggressive*/, true /*tracingEnabled*/, nil)
Copy link
Member

Choose a reason for hiding this comment

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

👍

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oh, I should point out that the first commented item has a leading space (but no trailing), whereas the second has no whitespace. I suspect the latter is the preferred style, but I'm not eager to make changes :-)

@@ -153,11 +153,11 @@ data:
# Scale to zero pod retention period defines the minimum amount
# of time the last pod will remain after Autoscaler has decided to
# scale to zero.
# This flag is for the situations where the pod starup is very expensive
# This flag is for the situations where the pod startup is very expensive
Copy link
Member

Choose a reason for hiding this comment

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

👍

// We want exactly 2. Not 1, not panicing 3, just 2.
// We want exactly 2. Not 1, not panicking 3, just 2.
Copy link
Member

Choose a reason for hiding this comment

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

this looks good panicking

@@ -20,7 +20,7 @@ metadata:
labels:
serving.knative.dev/release: devel
annotations:
knative.dev/example-checksum: "3af7fc85"
knative.dev/example-checksum: "97c1d10b"
Copy link
Member

Choose a reason for hiding this comment

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

I wonder why your tool changing yaml checking sums

@csantanapr
Copy link
Member

@jsoref the PR looks good, just a few comments
I would remove the checksum changes (2 places), don't why they are there unless I'm unaware that they are required

knative.dev/example-checksum

@csantanapr
Copy link
Member

ignore my comments to checksum I saw @julz comment

Hi @jsoref - looks like you'll need to run ./hack/update-checksums.sh following the rebase to update the checksums again

@csantanapr
Copy link
Member

/approve

Copy link
Contributor

@markusthoemmes markusthoemmes left a comment

Choose a reason for hiding this comment

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

Thanks for bearing with us through this and thanks for everybodz helping to unblock things 🎉

/lgtm
/approve

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Oct 16, 2020
@knative-prow-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: csantanapr, jsoref, markusthoemmes

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@knative-prow-robot knative-prow-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 16, 2020
@knative-prow-robot knative-prow-robot merged commit 1c8ec8f into knative:master Oct 16, 2020
@jsoref jsoref deleted the spelling branch October 16, 2020 21:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/API API objects and controllers area/autoscale area/networking area/test-and-release It flags unit/e2e/conformance/perf test issues for product features cla: yes Indicates the PR's author has signed the CLA. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants