-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Go 1.23 fixups #17341
base: mbg/go/1.23
Are you sure you want to change the base?
Go 1.23 fixups #17341
Conversation
6074085
to
f18a83a
Compare
Previously we had structs with different trap labels (because the labels already included the tags, which make structs non-identical), but no way to distinguish them in QL.
…on extracting an alias
…exported methods defined in different packages
…eType deep-unalias bug
f18a83a
to
0d3a0d9
Compare
This means that there is a target for defs and refs to refer to after the original fields go away because their corresponding structs have also gone away on a database downgrade.
Positive DCA results: https://github.com/github/codeql-dca-main/issues/23447 Now running QA: https://github.com/github/codeql-qa-ops/issues/191 |
…if they are variadic)
Did you see that https://github.com/bazelbuild/rules_go/releases/tag/v0.50.0 was released? That way, we should be able to fully rely on upstream again. |
Thanks, commented there instead! |
For future reference: DCA results were good, but with the addition of the stats commit they are terrible. A stats update really ought to happen due to adding a new table, but evidently it has caused a bad join order somewhere important. This will also apply to smaller PRs that are adding tables |
No description provided.