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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

s3_endpoint: log ID of new connection_manager instead of nil #201

Merged
merged 2 commits into from
Sep 2, 2022

Conversation

grrtrr
Copy link
Contributor

@grrtrr grrtrr commented Aug 20, 2022

Due to the way the function is called, endpoint->http_connection_manager is always NULL here, since nothing has been assigned yet.

Hence the log statement consistently prints nil, as in

[DEBUG] 2022-08-19 12:19:06.073 S3Endpoint [140627654626880] id=0x7fe63ff2b8e0: Created connection manager (nil) for endpoint

The absence of the ID makes it hard to trace problems in allocating/releasing the http_connection_manager.
Print its address instead, consistent with other output.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Due to the way the function is called, `endpoint->http_connection_manager` is `NULL`,
since nothing has been assigned yet.

Hence the statement always prints `nil`, as in
```
[DEBUG] 2022-08-19 12:19:06.073 S3Endpoint [140627654626880] id=0x7fe63ff2b8e0: Created connection manager (nil) for endpoint
```
The absence of the ID makes it hard to trace problems in allocating/releasing the `http_connection_manager`.
Print its address instead, consistent with other output.
@TingDaoK TingDaoK enabled auto-merge (squash) September 2, 2022 21:20
@TingDaoK TingDaoK merged commit c8025c8 into awslabs:main Sep 2, 2022
@grrtrr grrtrr deleted the print_connection_manager_id branch September 2, 2022 21:42
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.

None yet

2 participants