-
Notifications
You must be signed in to change notification settings - Fork 228
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
Upgrade Oboe to latest commit to fix CodeQL errors #2545
Comments
Hrm, this would be very good to have. Current master has a large amount of changes compared to the last released version (which we currently use):
Backporting would imply including the source instead of using a submodule, I guess? Not nice either :( |
Can you list the merges, rather than the diff? That might be a quick start. |
No merges there, therefore, a one-line log: ~/Projects/jamulus/libs/oboe$ git log --format=one HEAD..origin/main
|
According to this comment google/oboe#1506 (comment) the master branch of oboe is clean |
What is the current behaviour and why should it be changed?
Currently CodeQL fails due to Oboe issues. Since google/oboe#1507 got merged they should be fixed
Describe possible approaches
Wait for official release and live with warnings
backport changes
pin the current master commit
Has this feature been discussed and generally agreed?
No
The text was updated successfully, but these errors were encountered: