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
Message: Request textDocument/semanticTokens/full failed with message: Maximum call stack size exceeded #3268
Comments
@brianjmurrell Thank you for your bug report. Please provide an exact copy of your Dockerfile so I can try to reproduce this issue. |
I found rcjsuen/dockerfile-language-service#95 while testing some stuff. It may or may not be related. |
Dockerfile is doing it here for me.
So is the implication that there is something erroneous in my Dockerfile (that I could fix) that is causing this? |
Thank you for that. I was able to reproduce the issue. It looks different than the one I just found.
Not really. If your Dockerfile builds it should be valid. If it doesn't build...the editor still shouldn't go crazy and spam you with error messages. :) As I know how annoying the error messages can be, you can try disabling semantic highlighting in your "[dockerfile]": {
"editor.semanticHighlighting.enabled": false
} |
Excellent. Please ensure that any PR to fix references this issue so that I know when I can re-enable In fact it would be nice if the VS Code (or plugin) update that fixes this checks if the user has that setting disabled explicitly and asks them if they want to re-enable given that the issue is fixed and the OUTPUT log spamming should stop.
Thanks for that. Per the above, it would be nice to know if/when I can re-enable that without having to follow PR landings and subsequent releases, etc. |
@brianjmurrell I did some testing and the patch below should stop the error from happening. I am not sure how important your diff --git a/utils/docker/Dockerfile.centos.8 b/utils/docker/Dockerfile.centos.8
index 43cf722af..ae2d4806b 100644
--- a/utils/docker/Dockerfile.centos.8
+++ b/utils/docker/Dockerfile.centos.8
@@ -94,7 +94,7 @@ RUN for repo in $REPOS; do \
fi; \
fi; \
echo -e "[$repo:$branch:$build_number]\n\
-name=$repo:$branch:$build_number\n\
+name=$repo:$branch:$build_number \n\
baseurl=${JENKINS_URL}job/daos-stack/job/$repo/job/$branch/$build_number/artifact/artifacts/centos7/\n\
enabled=1\n\
gpgcheck=False\n" >> /etc/yum.repos.d/$repo:$branch:$build_number.repo; \ |
I have opened rcjsuen/dockerfile-language-service#96 to track this issue with variables. |
@brianjmurrell Thank you again for the bug report. I have opened #3269 to address this. |
This fix is now released in Docker extension version 1.18.0. |
Issue Type: Bug
I keep getting a constant stream of errors from the Dockerfile Language Server:
Extension version: 1.17.0
VS Code version: Code 1.61.1 (c13f1abb110fc756f9b3a6f16670df9cd9d4cf63, 2021-10-14T01:15:35.620Z)
OS version: Linux x64 5.14.9-100.fc33.x86_64
Restricted Mode: No
System Info
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
opengl: enabled_on
rasterization: disabled_software
skia_renderer: enabled_on
video_decode: disabled_software
vulkan: disabled_off
webgl: enabled
webgl2: enabled
A/B Experiments
The text was updated successfully, but these errors were encountered: