-
Notifications
You must be signed in to change notification settings - Fork 28
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
Code scanning alerts #406
Code scanning alerts #406
Conversation
…to code_scanning_alerts
…to code_scanning_alerts
…to code_scanning_alerts
…to code_scanning_alerts
…to code_scanning_alerts
…99 Maximum Number Of Host Parameters In A Single SQL Statement is not reached
…to code_scanning_alerts
…nct code and ensure test case is built
…yVVUQ into code_scanning_alerts
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.
Since we are trying to fix problems reported by the code scanner, we need the old reports refreshed by these fixes. So I think we should go ahead and attempt to merge these with the develop branch ...
…pt structure so that assertion failures don't prevent returning the rest of the statistical data
…ate uq.campaign to uq.Campaign; add the 'sqlite:///' prefix to the db_location
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.
Looks good to me.
More work needs to be done on this, but I'm creating a pull request to see how the integration tests respond.