Skip to content

Conversation

@SteveL-MSFT
Copy link
Member

@SteveL-MSFT SteveL-MSFT commented Jul 10, 2020

PR Summary

When constructing PSModulePath, the code checks if one of user path, shared path, or $PSHome path is already part of PSModulePath. The code that does the check trims whitespace and trailing path separator. So if one of those paths match, but actually has whitespace or trailing separator, then the index doesn't take that into account and subsequent paths are inserted in the wrong location creating an invalid path.

The fix is if one of those paths are found, then find the next index of the path separator and insert at that index. If there is no path separator after that index, then it just gets appended to the end.

Spent too much time trying to add a test. The repro requires changing the system environment variable for PSModulePath and a new process to be started so that it's not inherited from an existing PowerShell process. Validated manually.

PR Context

Fix #13025

PR Checklist

@SteveL-MSFT SteveL-MSFT requested a review from rjmholt July 10, 2020 01:20
@ghost ghost assigned rjmholt Jul 10, 2020
@rjmholt
Copy link
Collaborator

rjmholt commented Jul 10, 2020

@SteveL-MSFT are you planning on re-adding a new test?

@rjmholt rjmholt requested review from daxian-dbw and iSazonov July 10, 2020 16:04
@SteveL-MSFT
Copy link
Member Author

I might have to use a test hook to be able to add a test, need to think more about this.

@rjmholt rjmholt marked this pull request as draft July 10, 2020 22:12
@ghost ghost added the Waiting on Author The PR was reviewed and requires changes or comments from the author before being accept label Jul 14, 2020
@ghost ghost removed the Waiting on Author The PR was reviewed and requires changes or comments from the author before being accept label Jul 23, 2020
@iSazonov
Copy link
Collaborator

I suggest add xUnit test. It is more fast and simple.

Copy link
Collaborator

@iSazonov iSazonov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Downloaded artifact works well.

@SteveL-MSFT SteveL-MSFT marked this pull request as ready for review July 23, 2020 14:07
@rjmholt
Copy link
Collaborator

rjmholt commented Jul 23, 2020

I'm hoping @daxian-dbw will also have a chance to review this this week

@iSazonov iSazonov added the CL-General Indicates that a PR should be marked as a general cmdlet change in the Change Log label Jul 24, 2020
@rjmholt
Copy link
Collaborator

rjmholt commented Jul 27, 2020

@PoshChan please remind me in 10 days

@rjmholt rjmholt added the Review - Needed The PR is being reviewed label Jul 28, 2020
@rjmholt
Copy link
Collaborator

rjmholt commented Aug 4, 2020

@daxian-dbw please take a moment to review this if you have time

@rjmholt rjmholt added Waiting on Author The PR was reviewed and requires changes or comments from the author before being accept and removed Review - Needed The PR is being reviewed labels Sep 1, 2020
@ghost ghost added the Stale label Sep 16, 2020
@ghost
Copy link

ghost commented Sep 16, 2020

This pull request has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 15 days. It will be closed if no further activity occurs within 10 days of this comment.

@ghost ghost closed this Sep 27, 2020
@SteveL-MSFT SteveL-MSFT reopened this Oct 2, 2020
@ghost ghost removed the Waiting on Author The PR was reviewed and requires changes or comments from the author before being accept label Oct 2, 2020
@ghost ghost removed the Stale label Oct 2, 2020
@ghost ghost added the Review - Needed The PR is being reviewed label Oct 10, 2020
@ghost
Copy link

ghost commented Oct 10, 2020

This pull request has been automatically marked as Review Needed because it has been there has not been any activity for 7 days.
Maintainer, please provide feedback and/or mark it as Waiting on Author

@daxian-dbw daxian-dbw assigned TravisEz13 and unassigned rjmholt Nov 3, 2021
@ghost ghost removed the Review - Needed The PR is being reviewed label Nov 3, 2021
@ghost ghost added the Review - Needed The PR is being reviewed label Nov 10, 2021
@ghost
Copy link

ghost commented Nov 10, 2021

This pull request has been automatically marked as Review Needed because it has been there has not been any activity for 7 days.
Maintainer, please provide feedback and/or mark it as Waiting on Author

@TravisEz13
Copy link
Member

@SteveL-MSFT If this is still needed, can you resolve the conflicts

@ghost ghost removed the Review - Needed The PR is being reviewed label May 1, 2023
@pull-request-quantifier-deprecated

This PR has 29 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!


Quantification details

Label      : Extra Small
Size       : +19 -10
Percentile : 11.6%

Total files changed: 2

Change summary by file extension:
.cs : +10 -10
.ps1 : +9 -0

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

  • Fast and predictable releases to production:
    • Optimal size changes are more likely to be reviewed faster with fewer
      iterations.
    • Similarity in low PR complexity drives similar review times.
  • Review quality is likely higher as complexity is lower:
    • Bugs are more likely to be detected.
    • Code inconsistencies are more likely to be detected.
  • Knowledge sharing is improved within the participants:
    • Small portions can be assimilated better.
  • Better engineering practices are exercised:
    • Solving big problems by dividing them in well contained, smaller problems.
    • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

  • Use the PullRequestQuantifier to quantify your PR accurately
    • Create a context profile for your repo using the context generator
    • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
    • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
    • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
  • Change your engineering behaviors
    • For PRs that fall outside of the desired spectrum, review the details and check if:
      • Your PR could be split in smaller, self-contained PRs instead
      • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

  • One line was added: +1 -0
  • One line was deleted: +0 -1
  • One line was modified: +1 -1 (git diff doesn't know about modified, it will
    interpret that line like one addition plus one deletion)
  • Change percentiles: Change characteristics (addition, deletion, modification)
    of this PR in relation to all other PRs within the repository.


Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

@TravisEz13 TravisEz13 merged commit 8135167 into PowerShell:master May 2, 2023
@ghost
Copy link

ghost commented Jun 29, 2023

🎉v7.4.0-preview.4 has been released which incorporates this pull request.:tada:

Handy links:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CL-General Indicates that a PR should be marked as a general cmdlet change in the Change Log Extra Small

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Concatenated PSModulePath values for PS7 module paths

6 participants