-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Merge rc/1.19 into master #662
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
Closed
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… to be 1 byte"" This commit was reverted on `master` but should remain on `next`, so I'm reverting the revert before merging `master` into `next`. This reverts commit adda4c9.
Approved by adityasharad
Merge rc/1.18 into next.
This reverts commit ab2bec7.
Merge master to next
C++: support for clang `__builtin_addressof` and GNU vector fill operations
Merge rc/1.18 into next.
C++: support clang's __builtin_convertvector
Merge master to next
C++: add Class::isStandardLayout()
JavaScript: Fix expected output due to qltest change.
Merge rc/1.18 into next.
Master-to-next merge
These two queries have the `security` tag in the `.ql` file, but it was missing in the change note.
C++: Update security tag in change note
New query to check for making a request without cert verification.
Python: Implement check for flask debug mode.
…reporting. This query now only flags user-controlled property and header writes, method calls are handled by the new unsafe/unvalidated method call queries.
Approved by xiemaisi
…-call Approved by esben-semmle
adityasharad
requested changes
Dec 11, 2018
Collaborator
adityasharad
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At this point we should not be merging 1.19 into master, but into next.
Contributor
Author
|
Ah, that explains it. Thanks. |
Contributor
|
This pull request introduces 160 alerts when merging 20ffdf4 into a4b3b1e - view on LGTM.com new alerts:
Comment posted by LGTM.com |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Merges the right child of #503 and #561 into master.