Skip to content

fix: avoid duplicate READY message when shell is already running #3462

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

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Konikz
Copy link

@Konikz Konikz commented Apr 22, 2025

This commit modifies the start.go file to check for an existing shell session (via ssh.pid) before showing the READY message. This prevents duplicate READY messages when the shell is already launched.

Fixes

#3452

This commit modifies the start.go file to check for an existing shell session (via ssh.pid) before showing the READY message. This prevents duplicate READY messages when the shell is already launched.

Signed-off-by: Konikz <konikz@github.com>
@@ -313,6 +313,13 @@ func watchHostAgentEvents(ctx context.Context, inst *store.Instance, haStdoutPat
if *inst.Config.Plain {
logrus.Infof("READY. Run `ssh -F %q %s` to open the shell.", inst.SSHConfigFile, inst.Hostname)
} else {
// Check if a shell session is already running
if _, err := os.Stat(filepath.Join(inst.Dir, "ssh.pid")); err == nil {
Copy link
Member

Choose a reason for hiding this comment

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

How did you test this PR?

Copy link
Author

Choose a reason for hiding this comment

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

Still testing, I'll revert back once fixed.

@AkihiroSuda
Copy link
Member

Konikz konikz@github.com

Is this email address correct?
Are you a GitHub staff?

@Konikz Konikz marked this pull request as draft April 22, 2025 16:08
@Konikz
Copy link
Author

Konikz commented Apr 22, 2025

@AkihiroSuda no Sir, i'm not Github staff, I just use the "Keep my email addresses private" and use this email because my college address doesn't handle CLA invocations well.

@AkihiroSuda
Copy link
Member

@AkihiroSuda no Sir, i'm not Github staff, I just use the "Keep my email addresses private" and use this email because my college address doesn't handle CLA invocations well.

Is konikz@github.com reachable?
I don't think GitHub assigns <USERNAME>@github.com for non-employees?

@jandubois
Copy link
Member

I don't think GitHub assigns <USERNAME>@github.com for non-employees?

It doesn't. It assigns an email address of <ID>@users.noreply.github.com. That email is not functional (noreply) and I think not acceptable for the purpose of the DCO.

CNCF clarified in DCO and Real Names:

The DCO requires the use of a real name that can be used to identify someone in case there is an issue about a contribution they made.

A real name does not require a legal name, nor a birth name, nor any name that appears on an official ID (e.g. a passport). Your real name is the name you convey to people in the community for them to use to identify you as you. The key concern is that your identification is sufficient enough to contact you if an issue were to arise in the future about your contribution.

Your real name should not be an anonymous id or false name that misrepresents who you are.

Since the name and email are required to contact the contributor in case there is a concern about the licensing of the contributed code, we can only accept commits that have been signed with a proper name and working email address (see above that it doesn't have to be your legal name, but it should still identify you personally).

@Konikz
Copy link
Author

Konikz commented Apr 23, 2025

@AkihiroSuda & @jandubois ,
Thank you for the clarification. For GitHub contributions, I'll create a separate email address to sign the DCO and ensure I can be contacted if needed in the future.

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.

3 participants