LSP features does not work in another directory

Describe the bug

Our product is an LSP server for COBOL language. Theia editor usually opens in ./projects folder and our LSP features work normally, nothing new so far. The problem is when you open a file that is sitting in another directory located at top level from ./projects. Example: I have the following directories structure bin boot dev entrypoint.sh etc home lib lib64 media mnt opt plugins proc projects root run sbin srv sys tmp usr var workspace_logs

if I will open the file under .tmp some of our features stop working. Please take a look at the following gif:

This behavior is not present on Theia vanilla and it is reproducible for HLASM, COBOL, JAVA LSPs. Can not reproduce it on che-theia:7.3.3.

This error I am getting in the console log:

Che version

• latest
• nightly
• other: please specify

Steps to reproduce

Expected behavior

Runtime

• kubernetes (include output of kubectl version)
• Openshift (include output of oc version)
• minikube (include output of minikube version v1.6.2 and chectl version chectl/0.0.20200214-next.75e7903 win32-x64 node-v10.19.0)
• minishift (include output of minishift version and oc version)
• docker-desktop + K8S (include output of docker version and kubectl version)
• other: (please specify)

Installation method

• chectl <!–(–installer=operator --platform=minikube ) -->
• che-operator
• minishift-addon
• I don’t know

Environment

• my computer
  • Windows
  • Linux
  • macOS
• Cloud
  • Amazon
  • Azure
  • GCE
  • other (please specify)
• other: please specify

[tsmaeder]

Ok, I see it now. Unfortunately, the production versions of Che don’t have source map info, so it’s not trivial to analyze. The way I’m reproducing it is like so:

1. Open a Java-based workspace, open a Java file and make sure VS Code Java is running
2. Open a terminal in the theia ide container
3. `touch /tmp/Foo.java"
4. Open the file in the IDE using “File->Open”
5. Open the browser developer console
6. Do ctrl-space in the file
7. Observe: you get There are no document for file:///tmp/Foo.java in the browser console

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.