fix(otelgorm): Make metric reporting work with prepared statements #182
Annotations
1 error and 3 warnings
You have commit messages with errors
⧗ input: fix(otelgorm): Make metric reporting work with prepared statements
Previously we only initialized metrics reporting by calling
otelsql.ReportDBStatsMetrics if the gorm.DB.ConnPool interface
pointer we received happened to be a *sql.DB. This was often
the case, but not if prepared statements were enabled (and
possibly in other circumstances too). This caused metrics
reporting to be silently disabled. We fix this by calling
gorm.DB.DB whose sole purpose is to extract the underlying
*sql.DB.
✖ subject must not be sentence-case, start-case, pascal-case, upper-case [subject-case]
✖ found 1 problems, 0 warnings
ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint
|
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
This job failed
Loading