Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ISSUE #6830] Bump salesforce CDK dependency and patch version #36937

Merged
merged 2 commits into from Apr 9, 2024

Conversation

strosek
Copy link
Contributor

@strosek strosek commented Apr 9, 2024

Bump Salesforce source connector version (to 2.4.4) and CDK dependency (0.79.2) to include issue fixes in #36901

What

Some exceptions raised are logged with an internal_message field empty in the concurrent CDK. This makes it hard to categorize and solve problems. issue 6830

Fixed empty internal_message fields when an ExceptionWithDisplayMessage is raised.

How

A __str__() implementation was added to ExceptionWithDisplayMessage to avoid empty internal_message fields
Added relevant unit test, which catches unhandled exceptions and traces them with the correct internal message.

馃毃 User Impact 馃毃

No breaking changes
Changes can be reverted

@strosek strosek requested a review from maxi297 April 9, 2024 18:16
@strosek strosek self-assigned this Apr 9, 2024
Copy link

vercel bot commented Apr 9, 2024

The latest updates on your projects. Learn more about Vercel for Git 鈫楋笌

1 Ignored Deployment
Name Status Preview Comments Updated (UTC)
airbyte-docs 猬滐笍 Ignored (Inspect) Visit Preview Apr 9, 2024 7:11pm

Copy link
Contributor

@maxi297 maxi297 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Before you merge, can you add a bit more meat to the PR description? I usually like to use this kind of template where I explicitly mentioned what was done and how (which you have done) but also to describe 馃毃 User Impact 馃毃 i.e. how can we know the change worked, is the change breaking and can it be reverted if there is an issue. Note that there should always be a user impact as when we do a change, we expect it to deliver value.

Another note: I'm not the best to document PR as well so please keep me accountable on that as well.

@strosek strosek merged commit f29f7bb into master Apr 9, 2024
30 checks passed
@strosek strosek deleted the strosek/salesforce-bump-36901 branch April 9, 2024 20:22
@strosek strosek changed the title Bump salesforce CDK dependency and patch version [ISSUE #6830] Bump salesforce CDK dependency and patch version Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/connectors Connector related issues area/documentation Improvements or additions to documentation connectors/source/salesforce
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants