Cannot delete a directory if it WAS a 'workspace deploy location'

[edmundreinhardt]

Cannot delete a directory if it WAS a 'workspace deploy location'

[SanjulaGanepola]

@edmundreinhardt There shouldn't be any file watcher that needs to be deactivated. I tried out what you outlined and it looks like it can even be reproduced in just Code4i by simply doing the following:

1. Create a new directory in the IFS Browser.
2. Use Set Deploy Workspace Location on this new directory.
3. Deploy the project to this location.
4. Try to delete the directory using the IFS Browser and you will get the error "Device busy".

When testing, I did notice that this only happens when there is a .bashrc file. When I didn't have one, it would give the error: "Cannot remove the current directory".

My .bashrc content:

export PATH="/QOpenSys/pkgs/bin:${PATH}"

[sebjulliand]

Hey guys, I looked at the code in Code for i and rerproduced the issue as well.
However, it's not related to .bashrc, in my opinion. Why the deletion fails is simple: when deploying, the deploy location becomes the new current directory then the deployment commands and run. After that, trying to delete the deployment directory fails because you're basically trying to cut the branch you're seating on 😅

When running a command, we can see the current directory on the left side:

I'll make a note to handle this case in Code for i. In the case the user deletes the current deploy location, we'll make ~ the new current directory.

[edmundreinhardt]

Yes, Seb, I noticed that this was reproducible in Code 4 i. But I could understand at some level, that the directory was still in use. The unique issue to Project Explorer is that even after changing the deploy directory, the old directory cannot be deleted.

[sebjulliand]

@edmundreinhardt did you try do deploy again after changing the deploy dir and before trying to delete the old one? Because the current working directory is changed during the deployment, not just when you change the deployment location.

[edmundreinhardt]

Yes, you are right. I will close this issue here, since this is a Code 4 i issue
@sebjulliand should I open defect in code 4 i or do you already have something there?

[sebjulliand]

Yes, you are right. I will close this issue here, since this is a Code 4 i issue @sebjulliand should I open defect in code 4 i or do you already have something there?

Please do, I don't have anything there yet. You can assign it to me right away.