Codespace terminal gets launched in wrong directory

[maiertech]

I noticed that since today (or maybe yesterday) freshly created codespaces launch the terminal in the wrong directory. As you can see from attached screenshot, the codespace gets launched in the workspace directory and not in the directory that actually contains the cloned project. I am basically one level too high.

Screen Shot 2020-11-16 at 10.33.00 PM2578×1378 186 KB

I can cd on the terminal and work on the project, but the issue is that being in the parent directory breaks some project configs, e.g. for ESLint. I am not sure when exactly this problem started but I think I can narrow it down to today or yesterday.

[matthewisabel]

Thanks for raising this. It’s something we’re tracking and plan to fix shortly.

[maiertech]

Is there an ETA for this? This issue seems somewhat random. Yesterday, some codespaces worked just fine, while with others I ran into this issue. Today every codespace I launch has this issue.

[jkeech]

The fix for this has been rolled out. Please let us know if you continue to see it. The issue was that the root path was being set incorrectly on resume. During creation, it was set to the repo root, but on resume, it was set one level higher. Now resume keeps it at the correct path. Both existing Codespaces and new Codespaces should be fixed now on the next resume.