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

Fix nil pointer dereference error when parsing config map #1095

Merged
merged 1 commit into from
May 22, 2024

Conversation

izabelacg
Copy link
Member

Changes

  • 🐛 Fix nil pointer dereference error when parsing the cors-policy field config-contour config map

PS: Error found while investigating issues in serving tests:

/kind bug

Release Note

Resolved a nil pointer exception triggered by the cors-policy field being set to an empty value.

@knative-prow knative-prow bot added the kind/bug Categorizes issue or PR as related to a bug. label May 22, 2024
@knative-prow knative-prow bot requested review from dprotaso and ReToCode May 22, 2024 21:20
@knative-prow knative-prow bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label May 22, 2024
Copy link

codecov bot commented May 22, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.92%. Comparing base (28e07b4) to head (67ffd7c).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1095   +/-   ##
=======================================
  Coverage   93.92%   93.92%           
=======================================
  Files          11       11           
  Lines         708      708           
=======================================
  Hits          665      665           
  Misses         22       22           
  Partials       21       21           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@dprotaso
Copy link
Contributor

/lgtm
/approve

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label May 22, 2024
Copy link

knative-prow bot commented May 22, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dprotaso, izabelacg

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 knative-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 22, 2024
@dprotaso
Copy link
Contributor

Was there some malformed config in the serving tests?

@knative-prow knative-prow bot merged commit 1416c53 into knative-extensions:main May 22, 2024
24 checks passed
@izabelacg
Copy link
Member Author

Was there some malformed config in the serving tests?

in the serving e2e script, I set the cors-policy field to empty to disable the feature, which should result in a parsing error. That's why the subsequent tests fail, since the net-contour pod enters in an error state and doesn't recover. I'm waiting on the test PR to confirm if I'm properly removing the field instead of setting it to empty

@dprotaso
Copy link
Contributor

/cherry-pick release-1.14

@knative-prow-robot
Copy link
Contributor

@dprotaso: new pull request created: #1096

In response to this:

/cherry-pick release-1.14

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-sigs/prow repository.

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. kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants