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.

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

os: The result of UserHomeDir and User.HomeDir is inconsistent. #31070

Closed
Dreamacro opened this issue Mar 27, 2019 · 6 comments
Closed

os: The result of UserHomeDir and User.HomeDir is inconsistent. #31070

Dreamacro opened this issue Mar 27, 2019 · 6 comments
Labels
FrozenDueToAge

Comments

@Dreamacro
Copy link

What version of Go are you using (go version)?

$ go version
go version go1.12 darwin/amd64

Does this issue reproduce with the latest release?

yes.

What did you do?

Before go 1.12, I used os/user to get homedir.

current, _ := user.Current()
current.HomeDir

After new release, I used new function UserHomeDir

homeDir, _ := os.UserHomeDir()

However, they may return different values under same environment. For example, when I used termux on android, the former returns $HOME while the latter returns /.

The root case because of the UserHomeDir returns / directly but user.Current() read env "$HOME" first.

I prefer the previous implementation. So how do you plan to deal with the inconsistency between the two implementation?
@cuonglm
Copy link
Member

cuonglm commented Mar 27, 2019 •
edited

With commit bedb6a1 , the result is now consistent. But not when HOME is not set.:

  • current.HomeDir is /sdcard
  • os.UserHomeDir() returns /

@Dreamacro
Copy link
Author

Great! But will this patch be released on 1.12.2? this is a long time for me to wait until 1.13 release 🤔

@gopherbot
Copy link

Change https://golang.org/cl/169540 mentions this issue: os/user: keep user.HomeDir sync with os.UserHomeDir when HOME not set

@cuonglm
Copy link
Member

cuonglm commented Mar 27, 2019

@Dreamacro I don't know, you should ask the core team cc @bradfitz @mvdan

Not sure this issue is urgent for a cherry pick.

@bradfitz
Copy link
Contributor

/cc @eliasnaur

@mvdan
Copy link
Member

mvdan commented Mar 27, 2019

But will this patch be released on 1.12.2? this is a long time for me to wait until 1.13 release

Cherry-picks are generally reserved for regressions, security bugs, or really bad bugs like runtime crashes, so I don't think this qualifies. If anyone really wants the fix before 1.13 is released, copy-pasting a bit of code from master should be pretty easy.

I think what @Gnouc said in his first comment makes sense. os/user depends on os, so perhaps we could even make it call os.UserHomeDir to deduplicate the logic.

@letompouce letompouce mentioned this issue Aug 3, 2019
Closed
@a-tommyyy a-tommyyy mentioned this issue Jan 25, 2020
Closed
@golang golang locked and limited conversation to collaborators Mar 27, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@bradfitz @mvdan @cuonglm @gopherbot @Dreamacro