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

No logging to debug what is communicated #12

Open
ManufactoryOfCode opened this issue Apr 19, 2022 · 0 comments
Open

No logging to debug what is communicated #12

ManufactoryOfCode opened this issue Apr 19, 2022 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@ManufactoryOfCode
Copy link

It is common practice to have some kind of logging to be able to debug the communication. This will require to introduce a logging interceptor right after the actually used AuthenticationInterceptor. However in order to not close the underlying buffers, it is good to upgrade retrofit2 version (currently 2.9.0), so that response.body().source().peek() function will be introduced in class RealBufferedSource. This function allows to clone the source and that way preserve the source for later use yet be able to log the response body at the same time.

ManufactoryOfCode added a commit to ManufactoryOfCode/kucoin-futures-java-sdk that referenced this issue Apr 19, 2022
@ISAAC-XXYYZZ ISAAC-XXYYZZ self-assigned this Aug 12, 2024
@ISAAC-XXYYZZ ISAAC-XXYYZZ added the enhancement New feature or request label Aug 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants