-
-
Notifications
You must be signed in to change notification settings - Fork 119
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
Log the content when unsupported token error throws on composer.compose() #367
Comments
Would you have some example of the input that's causing this issue? The tracking and logging for this should already be in place. |
we don't have the exact input which causes the issue as YAML having sensitive user information. So we does not log the same. |
The upstream error is being thrown here: yaml/src/compose/compose-node.ts Lines 61 to 63 in 8f38c6a
It's probably caused by invalid input YAML, but it really shouldn't throw even then. If you have access to the console logs from around the error, that could reveal a bit more information? I'll stop the error from throwing, but I would be really rather interested in getting a sample input that's causing this, as I can't even figure out how to test this. |
Closing as presumably resolved. |
Is your feature request related to a problem? Please describe.
As we need to fix the redhat-developer/yaml-language-server#654 issue on our side, but unable to get the content what causes this error.
Describe the solution you'd like
It would be great if you log the content on your side which cause this error.
The text was updated successfully, but these errors were encountered: