Closed gauravpant1306 closed 4 months ago
This pull request introduces 2 alerts when merging 291d388b397254ad7a27f7577f92060566285a78 into a9fe840aaad6f523faa5d06c0e7b6244e82712e0 - view on LGTM.com
new alerts:
Heads-up: LGTM.com's PR analysis will be disabled on the 5th of December, and LGTM.com will be shut down ⏻ completely on the 16th of December 2022. Please enable GitHub code scanning, which uses the same CodeQL engine :gear: that powers LGTM.com. For more information, please check out our post on the GitHub blog.
This pull request introduces 2 alerts when merging ffc4b0b963ef3e6c9119865ed81175e2c9984aea into a9fe840aaad6f523faa5d06c0e7b6244e82712e0 - view on LGTM.com
new alerts:
Heads-up: LGTM.com's PR analysis will be disabled on the 5th of December, and LGTM.com will be shut down ⏻ completely on the 16th of December 2022. Please enable GitHub code scanning, which uses the same CodeQL engine :gear: that powers LGTM.com. For more information, please check out our post on the GitHub blog.
Looks like you modified compiled typescript code.
Please open a issue to describe the motivation for this feature/change
response interceptor to handle streams if stream is encrypted by custom algorithm
Description
Changed response-interceptor interceptor definition and implementation
Motivation and Context
If stream is encrypted and chunks are of different size, we need to handle those streams, decode and combine
How has this been tested?
Yes, we can use it like this
Types of changes
Checklist:
edit: code formatting