Gitpod: Cannot create new files

[stefdworschak]

Hi all,

Some of our students have reported issues in creating new files in their workspaces' directories.

Does not work:

• Use the "File" - "New File" menu
• Right-click "New File"

Does work:

• Using touch from the terminal

Could you please have a look at this issue as soon as possible?

Thanks,
Stefan

[bravoalpha79]

Possibly related, a suddenly not-working HTML tag auto-complete has been reported by at least two users in the same timeframe as the above issues.

[Saharalnoor]

Hi! I am experiencing the same issue in gitpod. I can´t create a New file or New folder

[irinatu17]

I have the same issue, as well as not able to create a new folder.

[Decline-of-Mind]

I am unable to create any new files or folders, as well as HTML autocomplete not working. If I type .thisclass and press tab, it only indents me further. It doesn't create the div with my class.

[Sparkplug84]

I also had similar issues today. Unable to create new files or folders using the menu. Also my environment problems and warnings were not visible any more.

[AlexiaDelorme]

I am currently experiencing an issue with the "Format document" command that is no longer working on any of my gitpod workspaces.

[corneliusludmann]

Thanks you all for reporting. Unfortunately, I'm not able to reproduce this. Could you please provide some more information:

1. Was it a newly created workspace or did you re-start an existing workspace? In case of the latter: When was the workspace created (see https://gitpod.io/workspaces/ – top right corner of the workspace item)?
2. Could you provide a workspace instance ID where this happens (the thing at the beginning of the URL in the browser like af4bcca2-87ad-4223-be37-66c7dc79cf02)?
3. Could you probably share a workspace snapshot where this happens (e.g. via [email protected] as long as here are no confidential information in this workspace)?

[AlexiaDelorme]

Hi Cornelius,

Thanks for getting back to us.

1. I re-started an existing workspace. My workspace was created 3 months ago.
2. My workspace instance ID: da314b55-5d5b-43c9-86b7-56ec4a4196d4
3. I have sent the screenshot by email.

Thanks and regards,
Alexia

[GlobetrotterG]

Same here. I am trying to add a folder, and wouldn't let me. Also, when I try to use the auto-tag feature, it wouldn't let either. So I had to write the whole code.

[NgiapPuoyKoh]

Gitpod workspace not behaving consistently (files not saved and browser run behavioir not consistent) during the past 10 hours. Very frustrating had to stop and restart several times. https://d552dc35-3c89-47ef-abb1-2f9bf4495be5.ws-eu01.gitpod.io/ finally unable to start the workspace.

[eldowling]

I don't know if this issue I'm having is related, but when I try to test my login page by using an invalid password I get this error:
jinja2.exceptions.UndefinedError: 'form' is undefined

This used to work without issue, so when I look at my app.py I have seen lots of imports have failed, like this:

[stefdworschak]

@corneliusludmann is there any update on this issue and do we have an ETA for when this might be fixed? Or do you need any additional information?

[corneliusludmann]

@jankeromnes has taken over the investigation. Since we are not able to reproduce this we need someone who can share his/her workspace with us, I guess. @jankeromnes can tell more ...

[jankeromnes]

Ok, it seems that all affected workspaces are based on repositories created from this template:

https://github.com/Code-Institute-Org/gitpod-full-template

Is that correct? (If you're seeing this issue, and did not use this template, please let me know.)

[jankeromnes]

I'm able to create files without issues.

(@AlexiaDelorme Note that these files are not unnecessary, as they properly configure your dev environment for Code Institute based projects in Gitpod. Without these files, you get an unconfigured, clean Gitpod environment, without any of the configurations / extensions pre-installed by Code Institute.)

[jankeromnes]

If someone has a workspace where this bug happens, could you please share a snapshot here?

• In the IDE top menu bar, there is a "Workspace" menu
• In that menu, there is a "Share Workspace Snapshot" item
• This will give you a snapshot URL, which can be used to start a clone of your workspace (which hopefully allows reproducing the bug)

[AlexiaDelorme]

@jankeromnes Thanks for getting back, I think I deleted them when I started working on my project, this is not what causing my issue I suppose.

[AlexiaDelorme]

@jankeromnes Yes, on my side I used the Code Institute template you mentioned in your previous comment, I think this is probably the case of most students reporting on this issue.

Let me share the markdown button for my workspace snapshot:

It's not visible on the screenshot but on my side it's just the "format document" option that is no longer working when I right click on my file content to format it.

[jankeromnes]

I think I deleted them when I started working on my project, this is not what causing my issue I suppose.

@AlexiaDelorme Good point, if it worked well before, but now not anymore, that's probably unrelated to the deleted files.

Still (on a side note), by removing the .gitpod.yml, you've uninstalled these VSCode extensions from Gitpod:

• ms-python.python (no more advanced Python linting / debugging)
• formulahendry.auto-close-tag (no more auto-closing HTML/XML tags)
• mkaufman.HTMLHint (no more advanced HTML linting)
• eventyret.bootstrap-4-cdn-snippet (no more !bcdn)

That's totally fine, just wanted to explain why some features may not be available for you even though they work for others.

Let me share the markdown button for my workspace snapshot:

That's awesome, thank you so much. I'll see if this helps me reproduce the various problems mentioned above.

[AlexiaDelorme]

@jankeromnes Thanks! Indeed I think I'll add them back anyway, especially for the HTML auto-closing tags option :)

[jankeromnes]

In the provided snapshot, I'm able to create files & folders without issue:

• Use the "File" - "New File" menu
• Right-click "New File"
• Right-click "New Folder"

I'm also able to:

• Auto-complete HTML tags (but this is very basic, i.e. <sp can auto-complete to <span, but it doesn't auto-close the tag -- I guess that's because the formulahendry.auto-close-tag extension is not installed)
• Typing .thisclass and then [Tab] gives me <div class="thisclass"></div>
• Right-click "Format Document" works (in HTML files, this can fix the indentation, but the feature is greyed out in Python files)
• Save files fast without issues

[GlobetrotterG]

Hi @jankeromnes - This is the workspace I'm experiencing issues where I can't add a folder and I can't auto tag as well. Please help! Thanks!

[AlexiaDelorme]

@jankeromnes Thanks a lot for checking, as you suggested I've added back the two files (.gitpod.yml & .gitpod.dockerfile) and I can now re-use the format command (either by right clicking or with the shortcut). This solved my issue, I don't know why the command stopped working only yesterday even though I deleted these files 3 months ago! Thanks a lot for your patience and I hope you'll be able to help the other students :)

[jankeromnes]

Thanks a lot for checking, as you suggested I've added back the two files (.gitpod.yml & .gitpod.dockerfile) and I can now re-use the format command (either by right clicking or with the shortcut).

@AlexiaDelorme Wow, that's great news, thanks. Personally I've tried manually installing the Python extension into your workspace, but for some reason I still couldn't get Format Document to be re-enabled. I'm a bit puzzled by why this workspace behaves differently than brand new workspaces I create for other projects, so I'll continue investigating, but meanwhile it's super cool that your problem is now solved. 👍

This solved my issue, I don't know why the command stopped working only yesterday even though I deleted these files 3 months ago!

That is a bit surprising to me as well. FYI, we've released an update to Gitpod yesterday (as we do about every 2 weeks), and in this update we've upgraded the IDE and a few built-in VSCode extensions. Maybe that had something to do with it? Not sure. Needs more investigation.

Thanks a lot for your patience and I hope you'll be able to help the other students :)

You're very welcome! Sorry again for the awkward experience, and I also hope to be able to solve the other problems as well.

This is the workspace I'm experiencing issues where I can't add a folder and I can't auto tag as well. Please help! Thanks!

@GlobetrotterG Many thanks for the snapshot! Taking a look to see if I can finally reproduce this annoying bug.

[jankeromnes]

I'm experiencing issues where I can't add a folder

@GlobetrotterG What folder are you trying to add, and where?

In your snapshot, I'm to right-click in the file explorer, then click "New Folder", then choose "test" as a name, and that works. It doesn't for you?

and I can't auto tag as well

Now that I can reproduce. I see in your Extensions panel (in IDE left vertical bar) that Auto Close Tag 0.5.6 is installed, but indeed typing <span> does not automatically add </span> behind (however, hitting Ctrl+Space after a <span> proposes to close the tag, but you probably expect that to happen automatically).

This could be a new bug in Theia, the IDE used by Gitpod. I'll investigate this further.

[jankeromnes]

Ha, now what's really strange: if I go into the Extensions panel, and uninstall the "Auto Close Tag" extension (and then click on the Reload button), I'm able to type <p> and the editor automatically adds </p> behind.

So maybe the "Auto Close Tag" extension conflicts with something that the IDE already does on its own?

[GlobetrotterG]

@jankeromnes - Thank you for looking into this. I was going to add a folder called 'CV' from 'assets' but it doesn't work for me. I tried using 'test' but no luck unfortunately.

For the auto-tag, still no luck. Say for example, I use .class to auto tag a div, it still doesn't for me.

Yes, I agree there's a bug in Theia, because it was fine a week ago.

[jankeromnes]

@GlobetrotterG Many thanks for explaining all the steps you tried in details.

Unfortunately, I'm still unable to reproduce these bugs, even with your snapshot:

https://youtu.be/1AutsBWIxI4

As a workaround, do you think you could commit & push your current changes to GitHub, and then try to create a brand new Gitpod workspace for the repository? (E.g. by typing gitpod.io/# in front of your repository URL.) With a little luck, the bugs are caused because the workspace is too old, and they won't reproduce again in a fresh workspace.

(Side note: You can create as many Gitpod workspaces as you want, and we generally consider it good practice to create a fresh workspace every time you resume working on a project, even if that's multiple times per day.)

[GlobetrotterG]

@jankeromnes - Thank you once again for your help and for showing me a video shot on Youtube.

I might have to try and do a git commit and push to github and create a new workspace. I hope that works. I'll let you know.

Thank you! :)

[jankeromnes]

@GlobetrotterG Well, I'm sorry about these awkward problems. I have a hard time understanding why you're getting them and I don't (after all, it's supposed to be a feature of Gitpod that we can all use the exact same coding environments and stop saying "it works on my machine"!)

What web browser are you using, by the way?

Also, please let me know if the fresh workspace also has that bug. That would be very unfortunate.

[GlobetrotterG]

@jankeromnes - That's absolutely fine, it's not your fault. I guess Gitpod is being temperamental on me! lol! I'm using Chrome browser.

[GlobetrotterG]

@jankeromnes - So I pushed this repo to my github and opened it as a different workspace, and it seems to be working fine now. I can add a folder and I can auto tag as well!

Thank you for your help! You're a lifesaver! :)

[jankeromnes]

Alright, these issues seemed to be caused by too old workspaces, and I'm happy that everyone successfully resolved them by simply creating new workspaces.

Please feel free to create new Gitpod workspaces all the time (there is no limit, and Gitpod was even designed to support "disposable workspaces", where you just push your work at the end of a coding session and then forget about your workspace -- in general, creating a fresh workspace will typically work better than always restarting the same old workspace, which may get stale at some point).

If you're still seeing problems in Gitpod, please open new dedicated GitHub issues (ideally one GitHub issue per Gitpod bug, or per symptom if you don't know exactly what the bug is). Thanks again!