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

Key diagnostic information in CloudConvertClientException not included in stack traces #45

Open
mattrussell-sonocent opened this issue Feb 28, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@mattrussell-sonocent
Copy link

When the library emits a CloudConvertClientException, it doesn't report any information about the status code or error response / code in the exception message, although these are captured on the exception object as fields. This means that by default, none of this information ends up in logs / stack traces, obscuring diagnostics. Could the message be changed to include the key information captured by these fields?

An example stack trace at present:

c.c.e.CloudConvertClientException: null
	at c.c.e.ResultExtractor.extract(ResultExtractor.java:71)
	at c.c.e.RequestExecutor.execute(RequestExecutor.java:27)
	at c.c.r.s.ImportFilesResource.upload(ImportFilesResource.java:67)
	at c.c.r.s.ImportFilesResource.upload(ImportFilesResource.java:112)
	at c.c.r.s.ImportFilesResource.upload(ImportFilesResource.java:35)
...
@josiasmontag josiasmontag added the enhancement New feature or request label Feb 28, 2022
@alialrabi
Copy link

Yes, I'm trying to use he library and I get Null exception but there are no information about this.

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

3 participants