fix: Fix potential deadlock in Snowflake destination#5553
fix: Fix potential deadlock in Snowflake destination#5553kodiakhq[bot] merged 2 commits intomainfrom
Conversation
erezrokah
left a comment
There was a problem hiding this comment.
This looks good, but do we want to do something with the error returned? We can do this in a follow up PR
|
@erezrokah Maybe I'm missing something, but the error should get returned by the call to |
You're right, I missed that. No need for a follow up |
🤖 I have created a release *beep* *boop* --- ## [1.0.6](plugins-destination-snowflake-v1.0.5...plugins-destination-snowflake-v1.0.6) (2022-12-13) ### Bug Fixes * **deps:** Update module github.com/cloudquery/plugin-sdk to v1.11.2 ([#5497](#5497)) ([c1876cf](c1876cf)) * **deps:** Update module github.com/cloudquery/plugin-sdk to v1.12.0 ([#5539](#5539)) ([fb71293](fb71293)) * Fix potential deadlock in Snowflake destination ([#5553](#5553)) ([ebf0eb8](ebf0eb8)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
(Similar to: #5550)
If a worker returns an error, it will no longer be consuming from its
writeChan, and in this case we should exit the loop early to avoid deadlock.