Skip to main content

Known Issues

Feature release status badge: PriPrev
PriPrev

Find below some common issues in cloud development environments that are not critical or pressing defects in the system:

  • The setup job for a workspace may have some harmless error messages at the top:

    jq: error: Could not open file /workspace/.vscode-remote/data/Machine/.tmp: No such file or directory
    jq: error (at /workspace/.vscode-remote/data/Machine/.tmp:0): object ({"python.de...) and null (null) cannot be multiplied
    rm: cannot remove '/workspace/.vscode-remote/data/Machine/.tmp': No such file or directory
    jq: error: Could not open file /home/gitpod/.vscode-server/data/Machine/.tmp: No such file or directory
    jq: error (at /home/gitpod/.vscode-server/data/Machine/.tmp:0): object ({"python.de...) and null (null) cannot be multiplied
    rm: cannot remove '/home/gitpod/.vscode-server/data/Machine/.tmp': No such file or directory
  • If you are in the DataOps UI and navigated to a file where the filename or the path contains a ., e.g.:

    file invalid name __shadow__

    When opening the DataOps CDE, you may get an error like the one below:

    error for file invalid name __shadow__

    Just go back in your browser, move up in the directory structure and then click to reopen the DataOps CDE.

  • The setup job for a new workspace can take approximately 10 seconds to run and get the environment fully ready. During this time, extensions may not fully load or work correctly.

  • The Preview Results button:

    Preview Results tab __shadow__

    Preview Results tab __shadow__

    Even though it returns results, sometimes the timer continues to tick up. This has no adverse effect.

  • Occasionally, the following error message will appear:

    This is the result of a race condition and can be ignored.
  • If you leave a workspace open and it times out, you may see:

    cloud environment timeout __shadow__

    This can be ignored, and you can still click Open Workspace to access anew your workspace with your changes — until the workspace is automatically deleted.

  • Variable scope

    If you are using subgroups within DataOps, there is a known issue with GitPod that doesn't always get the correct scope. We believe we have addressed this within the DataOps workspace image, but if you see this problem, please report it.