Skip to content

Fix incorrect path of workspace in devcontainer setup.sh#1104

Closed
Howardisme wants to merge 2 commits intoapache:mainfrom
Howardisme:fix-devcontainer-path
Closed

Fix incorrect path of workspace in devcontainer setup.sh#1104
Howardisme wants to merge 2 commits intoapache:mainfrom
Howardisme:fix-devcontainer-path

Conversation

@Howardisme
Copy link
Contributor

Related Issues

Fix #1103

Changes

  • Bug fix
  • New feature
  • Refactoring
  • Documentation
  • Test
  • CI/CD pipeline
  • Other

Why

This PR fixes an issue where the DevContainer fails to initialize properly during a fresh build.

How

Modified .devcontainer/setup.sh line 24: cd /workspaces/mahout -> cd /workspace

Checklist

  • Added or updated unit tests for all changes
  • Added or updated documentation for all changes


# setup pre-commit hooks
cd /workspaces/mahout
cd /workspace
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you help me understand? I think it should be in mahout directory?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

Copy link
Contributor Author

@Howardisme Howardisme Mar 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @ryankert01 and @viiccwen , Thank you for the quick response. I completely understand why it feels like it should be in mahout directly. However, I found devcontainer.json cause this error happened. In devcontainer.json, the workspace is explicitly mounted to /workspace:

image

Because devcontainer.json forces the target to /workspace, when setup.sh tries to run cd /workspaces/mahout on line 24, it throws the No such file or directory error and break the initialization of setup.

We have two ways to fix it:

  1. (My current PR): Update setup.sh to use cd /workspace to match the devcontainer.json. This is often safer because we don't know what the user names their local clone directory.
  2. Update devcontainer.json to mount to /workspaces/mahout instead.

Let me know which way you think is better to this issue or any follow up questions!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pls update ur own setting file.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it! I wil update my local file to align with the script.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Closing this PR. Looking forward to contributing to other parts of this project!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice one!

Copy link
Contributor

@viiccwen viiccwen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thx for contributing, but there is no need to change.

@viiccwen
Copy link
Contributor

viiccwen commented Mar 1, 2026

If u still have any issue in building the env, pls let us know. : )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] DevContainer setup fails due to incorrect workspace path in setup.sh

3 participants