Skip to content

Conversation

@greenstatic
Copy link

I came here after encountering an application bug where it inadvertently closed a shared SystemBus connection. I bet a common mistake that is made after glancing through past issues.

After reviewing the library documentation and similar issues reported I decided to use the SystemBusPrivate function. It was mentioned in #15 and an example was given here: #140 (ExampleSystemBusPrivate). I later realized that I was looking at go doc v4 documentation for the library (at pkg.go.dev) instead of the current latest v5 which include the Connect* methods introduced with #185.

Since @jsouthworth mentioned that we could deprecate the old-style methods in favor of the new Connect* ones (#185 (comment)) I decided to help out so that others could avoid the pitfalls I came across and to make it clear which methods they should use.

@greenstatic
Copy link
Author

@guelfey @jsouthworth - any feedback?

@greenstatic
Copy link
Author

@kolyshkin updated the docs with your suggestion.

Copy link
Contributor

@kolyshkin kolyshkin left a comment

Choose a reason for hiding this comment

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

LGTM (except commits need to be squashed).

@guelfey PTAL

@guelfey
Copy link
Member

guelfey commented Nov 14, 2025

I disagree that these functions are "deprecated". Granted, they are likely not the ones that new users want to use, but they are required if you want to use a custom authentication mechanism, and by itself there is nothing wrong with that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants