-
Notifications
You must be signed in to change notification settings - Fork 3
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
Jang lookup indicator exception bugfix #5
Jang lookup indicator exception bugfix #5
Conversation
Thank you for your submission! We have a total of 29 PRs open right now, and we are working hard on all of them! We will take a look as soon as we can. |
@jang-splunk Static Tests results for commit bd7fdc0 - https://drive.google.com/file/d/1u3MrrK7x-h5opmg9X2hUAMO8Qfzf_Mby/view?usp=drivesdk |
@jang-splunk Compile Tests results for commit bd7fdc0 - https://drive.google.com/file/d/1NcPE-PlmTUtZWmDK-2PHwJUXoj85zIPi/view?usp=drivesdk |
@achandya-crest Static Tests results for commit a779b2a - https://drive.google.com/file/d/1x9iu0iD-g0SBaaXq-FxREY-9dzYvR5Ww/view?usp=drivesdk |
@achandya-crest Compile Tests results for commit a779b2a - https://drive.google.com/file/d/1rxgXKP76_eJDfHwnTLVhc4YNWkkYHt3S/view?usp=drivesdk |
@achandya-crest Static Tests results for commit 19facc8 - https://drive.google.com/file/d/1Z4CiCkuf_RsVYkolHME8Q2cBi3TNqSMC/view?usp=drivesdk |
@achandya-crest Compile Tests results for commit 19facc8 - https://drive.google.com/file/d/1GsKWzlzA9HF5IXvieqxLVYnQSRMTvI9R/view?usp=drivesdk |
@achandya-crest Static Tests results for commit 0d7fc9c - https://drive.google.com/file/d/1raL01w8rKNx8ttOUzY1Zk1nkn5RPaoiG/view?usp=drivesdk |
@achandya-crest Compile Tests results for commit 0d7fc9c - https://drive.google.com/file/d/1AW0rUchFtbfAEUl4yCFwUq4-vj_V_yTd/view?usp=drivesdk |
Hello @jang-splunk, The static pipeline in this PR shows a vulnerability in autoescape used in HTML files. Could you please change it? |
not my code. In fact, it was probably written by crest folks.
…-James
On Oct 10, 2023, at 02:20, achandya-crest ***@***.***> wrote:
External sender. Exercise caution.
Hello @jang-splunk <https://github.com/jang-splunk>, The static pipeline in this PR shows a vulnerability in autoescape used in HTML files. Could you please change it?
<https://user-images.githubusercontent.com/70213464/273796360-a5897e67-39c4-4ff6-b5b9-264edb953e6a.png>
—
Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMMGCKQKCKKL4LHZ2YZWMH3X6TSMHAVCNFSM6AAAAAA5BV4NGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJUGQ3TQNZXGU>.
You are receiving this because you were mentioned.
|
@achandya-crest Static Tests results for commit bc28de8 - https://drive.google.com/file/d/1lNFYQao9JD6dQkIXwd1k8RiAOYdFCbG7/view?usp=drivesdk |
@achandya-crest Compile Tests results for commit bc28de8 - https://drive.google.com/file/d/1aqMna2yO5yLzWmsErO7_p-7-ftNYuS7_/view?usp=drivesdk |
@achandya-crest Static Tests results for commit 2d71486 - https://drive.google.com/file/d/1Trsg_uZGweAdSX_caF8o9zWWqNrgD6Ek/view?usp=drivesdk |
@achandya-crest Compile Tests results for commit 2d71486 - https://drive.google.com/file/d/1DZu7wJS66E0C1ukGhrfSLgGFjaz6CJnj/view?usp=drivesdk |
Hello @jang-splunk, Could you please test the changes I made from autoescape to |safe. If it works fine, we can proceed with the release. |
Hello @jang-splunk, Did you get a chance to test the changes? |
@achandya-crest Static Tests results for commit 46fc2df - https://drive.google.com/file/d/1ALMd9eFDXPybeGLTdReUnmGoZCzpyEaF/view?usp=drivesdk |
@achandya-crest Compile Tests results for commit 46fc2df - https://drive.google.com/file/d/1wr4pKq6ncX-RN3Rjp8xLXqa94Mlj-Ehh/view?usp=drivesdk |
@achandya-crest Static Tests results for commit 8ebe473 - https://drive.google.com/file/d/1Ux5cgPf-_5ofIlHgPjPaBiUuQzV7Ncws/view?usp=drivesdk |
@achandya-crest Compile Tests results for commit 8ebe473 - https://drive.google.com/file/d/1sxx_IjmO5TcXnT4eSNWkhrkTCQCWPq3Q/view?usp=drivesdk |
Please ensure your pull request (PR) adheres to the following guidelines:
Pull Request Checklist
Please check if your PR fulfills the following requirements:
<App Name>: <PR Type> - <PR Description>
next
branch of the forked repo. Create separate feature branch for raising the PR.Pull Request Type
Please check the type of change your PR introduces:
Security Considerations (REQUIRED)
please document them in the
manual_readme_content.md
.manual_readme_content.md
all methods (eg, OAuth) used to authenticatewith the service that the connector is integrating with.
manual_readme_content.md
.the Vault API.
nosemgrep
?If yes, please provide justification in an additional comment next to the ignored code.
Release Notes (REQUIRED)
What is the current behavior? (OPTIONAL)
What is the new behavior? (OPTIONAL)
Other information (OPTIONAL)
Pay close attention to (OPTIONAL)
Screenshots (if relevant)
Thanks for contributing!