-
Notifications
You must be signed in to change notification settings - Fork 490
[Amazon.Lambda.RuntimeSupport] fix: Find header key with insensitive comparison #2094
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
base: dev
Are you sure you want to change the base?
[Amazon.Lambda.RuntimeSupport] fix: Find header key with insensitive comparison #2094
Conversation
The change looks good but can you rebase the PR to the Also the PR needs a change file to take care of change log and versioning. Can you add the following content, feel free to change the change log messages, in the following file:
|
Hey @normj, Thanks for the review, I'll rebase from the |
8af8033
to
950a7df
Compare
I rebased your changes on top of dev @duncanista |
Hey @GarrettBeatty, Thanks – sorry for taking a while, had a busy last week. I appreciate the modifications! |
running integration tests on latest commits https://github.com/aws/aws-lambda-dotnet/actions/runs/16121546157 |
hi @duncanista i ran the tests locally and it looks like the unit tests are failing related to the change. are you able to take a look? looks like most of them have the same error message |
@GarrettBeatty updated the code to instead of checking a key on every Get, now an internal case insensitive headers dictionary is generated during the constructor. Let me know if this is better, it should pass now. Sorry for taking so long. On another note, do you want me to add unit tests for the |
thanks i will rerun your changes through the test pipeline tomorrow morning < On another note, do you want me to add unit tests for the RuntimeApiHeaders file? There seems to be none, I know it's kinda trivial, but still. I think the other tests cases probably cover RuntimeApiHeaders indirectly, but if you would like to add more test cases feel free. I will approve it in its current state assuming the current tests pass anyway |
essentially creating a case insensitive header dictionary
0951630
to
0ef4dff
Compare
rebased your changes on top of dev (which has a fix in the unit tests) |
rerunning the tests - they are a little flaky and failing due to some unrelated issues. will try and get this merged in today |
Issue
Idea for #2093
Changes
Looks up for headers without any case restrictions by creating a
caseInsensitiveHeaders
dictionary from the start, so lookups are O(1)By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.