SNOW-892592: Fix panic when SF_OCSP_RESPONSE_CACHE_SERVER_ENABLED=false #883
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.
Description
https://github.com/snowflakedb/snowflake-sdks-drivers-issues-teamwork/issues/608
When testing for https://github.com/snowflakedb/snowflake-sdks-drivers-issues-teamwork/issues/593 I found a panic when SF_OCSP_RESPONSE_CACHE_SERVER_ENABLED is false. The initOcspCache() function initializes a mutex lock on the ocsp response cache. If SF_OCSP_RESPONSE_CACHE_SERVER_ENABLED=false it exits the init function before the lock is initialized. The driver tries to access it later and it causes a panic during connection.
This change is to initialize the lock first and then check for SF_OCSP_RESPONSE_CACHE_SERVER_ENABLED.
Checklist
make fmt
to fix inconsistent formatsmake lint
to get lint errors and fix all of them