Skip to content
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

TEMP environment variable is 8.3 Path on some systems #532

Closed
ferventcoder opened this issue Jan 11, 2016 · 0 comments
Closed

TEMP environment variable is 8.3 Path on some systems #532

ferventcoder opened this issue Jan 11, 2016 · 0 comments
Assignees
@ferventcoder
Labels
5 - Released Bug
Milestone
0.9.10

Comments

@ferventcoder
Copy link
Member

Related to #415 - Do not provide $env:TEMP as an 8.3 variable.
@ferventcoder ferventcoder self-assigned this Jan 11, 2016
@ferventcoder ferventcoder added this to the 0.9.10 milestone Jan 11, 2016
ferventcoder added a commit that referenced this issue Jan 11, 2016
@ferventcoder
(GH-532) Fix - Temp uses 8.3 Path
76ae7e2 
When determining the cache location and using the `TEMP` environment
variable, ensure that it is coming back as a Full Path and not as an
8.3 path. This happens on some systems when you simply call for the
Environment Variable. However `Path.GetTempPath()` provides a fully
qualified path instead of a shortened path. Use that instead.
ferventcoder added a commit that referenced this issue Jan 11, 2016
@ferventcoder
Merge branch 'stable'
0328603 
* stable:
  (GH-526) Fix: The handle is invalid
  (GH-532) Fix - Temp uses 8.3 Path
  (maint) update binroot deprecation
@ferventcoder ferventcoder mentioned this issue Jan 11, 2016
Closed
This was referenced Apr 1, 2016
Closed
Closed
@ferventcoder ferventcoder mentioned this issue Jun 23, 2016
Closed
ferventcoder added a commit that referenced this issue Jun 23, 2016
@ferventcoder
(GH-826) SYSTEM user always uses machine TEMP
b9d8759 
Using `Path.GetTempPath()` instead of
`Environment.GetEnvironmentVariable("TEMP")` in 76ae7e2 for GH-532
has caused the SYSTEM user to return one of the following:

 * `c:\windows\system32\config\systemprofile\appdata\local\temp`
 * `c:\windows\syswow64\config\systemprofile\appdata\local\temp`

These folders seem to cause issues with accessing files, causing all
kinds of fun issues, such as "Not able to read package from path" and
not able to find executables being downloaded to these folders.

If one of these two folders is detected, ensure that the folder
structure is `%SystemRoot%\TEMP`.
@ferventcoder ferventcoder mentioned this issue Jun 29, 2016
Closed
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ferventcoder ferventcoder

Labels
5 - Released Bug
Projects
None yet
Milestone
0.9.10
Development

No branches or pull requests
2 participants
@ferventcoder @gep13