archive/tar: add FileInfoNames interface

[qiulaidongfeng]

An optional interface FileInfoNames has been added.

If the parameter fi of FileInfoHeader implements the interface
the Gname/Uname of the return value Header
are provided by the method of the interface.

Also added testing.

Fixes #50102

[gopherbot]

This PR (HEAD: 292ab66) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/558355.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account to log in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

[gopherbot]

Message from Gopher Robot:

Patch Set 1:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

This PR (HEAD: 124d651) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/558355.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account to log in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

[gopherbot]

Message from Kirill Kolyshkin:

Patch Set 3:

(3 comments)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

This PR (HEAD: a91a7a6) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/558355.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account to log in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

[gopherbot]

Message from qiulaidongfeng:

Patch Set 4: Run-TryBot+1

(4 comments)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Gopher Robot:

Patch Set 4:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Gopher Robot:

Patch Set 4:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Gopher Robot:

Patch Set 4: TryBot-Result-1

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from qiulaidongfeng:

Patch Set 4: -Run-TryBot

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

This PR (HEAD: e080379) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/558355.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account to log in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

[gopherbot]

Message from qiulaidongfeng:

Patch Set 5: Run-TryBot+1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Gopher Robot:

Patch Set 5:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Gopher Robot:

Patch Set 5: TryBot-Result+1

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from qiulaidongfeng:

Patch Set 5: -Run-TryBot

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

This PR (HEAD: 34b2feb) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/558355.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account to log in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

[gopherbot]

Message from qiulaidongfeng:

Patch Set 6: Run-TryBot+1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Gopher Robot:

Patch Set 6:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Gopher Robot:

Patch Set 6:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Gopher Robot:

Patch Set 6: TryBot-Result-1

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

This PR (HEAD: a25a4d5) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/558355.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account to log in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

[gopherbot]

Message from qiulaidongfeng:

Patch Set 7: Run-TryBot+1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Gopher Robot:

Patch Set 7:

(2 comments)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from qiulaidongfeng:

Patch Set 7: -Run-TryBot

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

This PR (HEAD: 08f7daa) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/558355.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account to log in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

[gopherbot]

Message from qiulaidongfeng:

Patch Set 8: Run-TryBot+1

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Gopher Robot:

Patch Set 8:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Gopher Robot:

Patch Set 8: TryBot-Result+1

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from qiulaidongfeng:

Patch Set 8: -Run-TryBot

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from qiulaidongfeng:

Patch Set 13: Commit-Queue+1

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from qiulaidongfeng:

Patch Set 13: -Commit-Queue

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 13:

CV cannot start a Run for [email protected] because the user is neither the CL owner nor a committer nor a dry-runner.

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 13: LUCI-TryBot-Result-1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from qiulaidongfeng:

Patch Set 13: Commit-Queue+1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 13:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-03-12T09:18:05Z","revision":"0c085606198adfc57b025734bc1e0f5fe659a480"}

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from qiulaidongfeng:

Patch Set 13: -Commit-Queue

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 13:

This CL has passed the run

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 13: LUCI-TryBot-Result+1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Ian Lance Taylor:

Patch Set 13: Auto-Submit+1 Code-Review+2 Commit-Queue+1

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 13:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-03-12T22:47:18Z","revision":"0c085606198adfc57b025734bc1e0f5fe659a480"}

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Ian Lance Taylor:

Patch Set 13: -Commit-Queue

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 13:

This CL has failed the run. Reason:

Tryjob golang/try/gotip-linux-amd64-race has failed with summary (view all results):

---

FAILURE

• go on master (change 558355)

Tests failed. See all test results.

Error:
shard 2: failed to run "go tool dist test -json": exit status 1

Links:

• shard 2 build page
• shard 2 test results
• shard 2 "go tool dist test -json" (combined output)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 13: LUCI-TryBot-Result-1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from qiulaidongfeng:

Patch Set 13: Commit-Queue+1

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 13:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-03-13T08:34:35Z","revision":"0c085606198adfc57b025734bc1e0f5fe659a480"}

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from qiulaidongfeng:

Patch Set 13: -Commit-Queue

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 13:

This CL has passed the run

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 13: LUCI-TryBot-Result+1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Cherry Mui:

Patch Set 13: Code-Review+1

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

This PR (HEAD: a213613) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/558355.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account to log in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

[gopherbot]

Message from qiulaidongfeng:

Patch Set 14: Commit-Queue+1

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 14:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-03-15T10:43:39Z","revision":"921bc6ec77b8be689727d8e5f866941480f9f1ef"}

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from qiulaidongfeng:

Patch Set 14: -Commit-Queue

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 14:

This CL has passed the run

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 14: LUCI-TryBot-Result+1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/558355.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

This PR is being closed because golang.org/cl/558355 has been merged.