-
-
Notifications
You must be signed in to change notification settings - Fork 579
Fix logging of where application is bound #2249
Conversation
Log message is now:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the PR!
I wrote some comments so please kindly consider them.
Briefly, I would like to minimize the changes to the interface since we are now planning a next version and don't want to introduce breaking changes while I fully agreed that the wrong information should be fixed.
That's the new output. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! LGTM
Hi @paganotoni, |
Hi @hut8, I just realized that this PR is opened against the |
Absolutely. My mistake! Thanks for correcting me on that. I'll get this
done today or tomorrow
…On Fri, Apr 29, 2022, 10:17 Yonghwan SO ***@***.***> wrote:
Hi @hut8 <https://github.com/hut8>,
I just realized that this PR is opened against the main branch.
Currently, all PR requests should open to the development branch. I tried
to edit the base but it seems like it could break the commit history. Could
you please check your forked repository/branch or reopen the PR against the
development branch?
—
Reply to this email directly, view it on GitHub
<#2249 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACYZSB5WSUPFH2T7EEATULVHPVOPANCNFSM5UKCKD3Q>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
@hut8 thanks for putting together this one. I attempted to rebase it to development but seems it has some conflicts. Can you please take care of those. Thanks again! |
Makes changes backwards compatible and restores logging statement at beginning of startup
@paganotoni I think I took care of it 😄 |
Addresses #2248
This adds a method to a public interface, which isn't ideal and may technically be a breaking change. I'm open to suggestions about that.