Skip to content

Comments

cmd: fallback to parsing getent passwd output when $SHELL is not set#1760

Open
Rolv-Apneseth wants to merge 1 commit intocontainers:mainfrom
Rolv-Apneseth:fallback_shell
Open

cmd: fallback to parsing getent passwd output when $SHELL is not set#1760
Rolv-Apneseth wants to merge 1 commit intocontainers:mainfrom
Rolv-Apneseth:fallback_shell

Conversation

@Rolv-Apneseth
Copy link

As suggested in #1615, this PR just adds a fallback if $SHELL is not set for whatever reason.

Not very comfortable with Go, but hopefully the code is alright. Happy to make any changes anyway. And let me know if you want some tests added, I just wasn't sure entirely where to add that.

@gemini-code-assist
Copy link

Summary of Changes

Hello @Rolv-Apneseth, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the application's ability to reliably determine the user's default shell. It addresses scenarios where the $SHELL environment variable might be unset by introducing a new utility function that attempts to read $SHELL and, if unsuccessful, gracefully falls back to parsing the output of the getent passwd command. This change ensures that core functionalities dependent on the user's shell can proceed without error, making the application more resilient to varied environment configurations.

Highlights

  • Robust Shell Detection: Implemented a fallback mechanism to determine the user's default shell when the $SHELL environment variable is not set, improving application robustness.
  • New Utility Function: Introduced a new getUserShell utility function in src/cmd/utils.go to encapsulate the logic for retrieving the shell, first checking $SHELL and then falling back to parsing getent passwd output.
  • Refactored Shell Acquisition: Updated create.go, enter.go, and rootMigrationPath.go to utilize the new getUserShell function instead of directly relying on os.Getenv("SHELL").

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • src/cmd/create.go
    • Replaced direct os.Getenv("SHELL") call with a call to the new getUserShell() function.
  • src/cmd/enter.go
    • Replaced direct os.Getenv("SHELL") call with a call to the new getUserShell() function.
  • src/cmd/rootMigrationPath.go
    • Replaced direct os.Getenv("SHELL") call with a call to the new getUserShell() function.
  • src/cmd/utils.go
    • Added a new getUserShell() function that first checks the $SHELL environment variable.
    • Implemented fallback logic within getUserShell() to execute and parse /bin/getent passwd output if $SHELL is empty.
    • Added error handling for getent command execution and output parsing.
    • Ensured the $SHELL environment variable is set for subsequent operations if determined via getent.
Activity
  • The author initiated this pull request to address an issue identified in failed to get the current user's default shell #1615, providing an initial implementation for a shell fallback mechanism.
  • The author expressed openness to feedback and making further changes, including adding tests if deemed necessary, indicating a collaborative approach to development.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request adds a fallback mechanism to determine the user's shell by parsing getent passwd output when the $SHELL environment variable is not set. This is a good improvement for robustness. The changes are applied consistently across the create, enter, and rootMigrationPath commands. My review includes a couple of suggestions for the new getUserShell function in src/cmd/utils.go to enhance its portability and robustness. Additionally, since you've mentioned being open to adding tests, it would be great to add unit tests for the new getUserShell function to cover both the successful paths and the error cases you're handling. This would improve the long-term maintainability of this new logic.

Signed-off-by: Rolv Apneseth <rolv.apneseth@gmail.com>
Signed-off-by: Rolv-Apneseth <rolv.apneseth@gmail.com>
@softwarefactory-project-zuul
Copy link

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant