8000 Move-Item recursively creates "infinitely" nested directories · Issue #16089 · PowerShell/PowerShell · GitHub
[go: up one dir, main page]
Skip to content

Move-Item recursively creates "infinitely" nested directories #16089

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
5 tasks done
PAStheLoD opened this issue Sep 14, 2021 · 1 comment
Closed
5 tasks done

Move-Item recursively creates "infinitely" nested directories #16089

PAStheLoD opened this issue Sep 14, 2021 · 1 comment
Labels
Resolution-Fixed The issue is fixed.
Milestone
7.2.0-preview.10

Comments

@PAStheLoD
Copy link
PAStheLoD commented Sep 14, 2021 •
edited
Loading

Prerequisites

Steps to reproduce

mkdir test
cd test

mkdir abc
mv * abc

Don't forget to hit ctrl-c fast.

dir -Recurse t shows the created structure. I used 7zip File Manager to shift-del the nested dir structure.

Expected behavior

PS should not create the nested directory structure, it should ignore the target when expanding the wildcard into the source list, move everything else into the target directory.

In this example it should basically do a no-op, since there's nothing else to move into "abc".

Actual behavior

A directory that contains a directory, that contains a directory ... t\abc\abc\abc\abc ...

Environment data

PSVersion                      7.2.0-preview.9
PSEdition                      Core
GitCommitId                    7.2.0-preview.9
OS                             Microsoft Windows 10.0.19042
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0
@PAStheLoD PAStheLoD added the Needs-Triage The issue is new and needs to be triaged by a work group. label Sep 14, 2021
@iSazonov
Copy link
Collaborator

@PAStheLoD Thanks for reporting the issue! It was fixed in #16029. You can download latest preview build and check the scenario.

@iSazonov iSazonov added this to the 7.2.0-rc.1 milestone Sep 15, 2021
@iSazonov iSazonov closed this as completed Dec 1, 2021
@ghost ghost removed the Needs-Triage The issue is new and needs to be triaged by a work group. label Dec 1, 2021
@iSazonov iSazonov added the Resolution-Fixed The issue is fixed. label Dec 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Resolution-Fixed The issue is fixed.
Projects
None yet
Milestone
7.2.0-preview.10
Development

No branches or pull requests
2 participants
@PAStheLoD @iSazonov
0