Dotfiles install.sh script doesn't fully run

[schickling]

Bug description

I'm currently giving the new dotfiles feature (see #5198) a try and have been running into a few problems. It seems that my provided install.sh script is only partially executed. (I'm actually not sure what the problem is but would like to find out - is there a way to see the logs of the executed install.sh script?)

Steps to reproduce

• Use my dotfiles https://github.com/schickling/dotfiles
• Open any repo in a new workspace
• You should see that the install.sh script partially ran (e.g. by the renamed ~/.config/fish-backup folder)

• Running the install.sh script manually seems to work

Workspace affected

No response

Expected behavior

No response

Example repository

No response

Anything else?

Additional questions

• Will the executed result of my dotfiles be cached, so it's instantly ready when opening any kind of (new) workspace? (This is critical for me as executing my install.sh script (mostly using Nix home-manager) can take multiple minutes)
• How can I see the logs of the executed install.sh file?

[iQQBot]

You can view log in ~/.dotfiles.log

[iQQBot]

Will the executed result of my dotfiles be cached, so it's instantly ready when opening any kind of (new) workspace? (This is critical for me as executing my install.sh script (mostly using Nix home-manager) can take multiple minutes)

no cache here

[axonasif]

You can view log in ~/.dotfiles.log

I thought that's only for symlinking logs 😅
Just checked now and it seems STDOUT and STDERROR are there too, thanks for the info!

[axonasif]

@schickling basically the env profile wasn't loaded, so you need to use bash interactive mode to do that manually.
I just raised a PR schickling/dotfiles#9

[schickling]

Thanks a lot @axonasif - this indeed seems to address the initial problem of the install.sh script not running properly - it now does. However...

no cache here

This turns out to be a major problem - at least for my use case where setting up the dotfiles takes multiple minutes.
This now seems to have the result of opening any kind of workspace takes multiple minutes showing this screen (i.e. making it faster to clone a repo on my local machine etc than opening it on Gitpod)

[axonasif]

@schickling yes you are right, it seems to take a bit longer to open, probably 2 minutes. But I'm unable to reproduce the other error that you mentioned. I open my PR with Gitpod and did some activities on the workspace for the last 5 minutes but nothing wrong yet.

[axonasif]

@schickling can you please try again and let me know if it's still happening 🙏?

[axonasif]

@schickling your MakeFile changes won't be persistent since you're running it from init task of .gitpod.yml

[iQQBot]

@schickling Did you use vscode inside? you can switch to stable

[schickling]

Closing this issue as the mentioned problem is addressed via this:

#!/usr/bin/bash -I

However the lack of caching for dotfiles is still a major problem for me (which unfortunately renders Gitpod with dotfiles enabled impractical for me to use).

[axonasif]

Closing this issue as the mentioned problem is addressed via this:

#!/usr/bin/bash -I

However the lack of caching for dotfiles is still a major problem for me (which unfortunately renders Gitpod with dotfiles enabled impractical for me to use).

I would encourage you to create a separate feature request for this 🙂

[schickling]

Done: #7592