sf project deploy start resets the parent shell that called the sf command

[licensing-intrax]

Summary

When I run sf project deploy start -x manifest/package.xml -o myorg

I see the summary of changes, and then I get the system login message and I get sent back to $HOME. It's almost as if the sf cli actively kills itself.

Steps To Reproduce:

1. create a salesforce org
2. install nodejs
3. install the salesforce cli
4. authenticate to your org using the salesforce cli
5. run the project retrieve start command

Expected result

The command should either succeed or fail, but it should not exit the directory I called it from.

Actual result

I get a login message, my shell resets, and I get kicked back to my $HOME directory

System Information

shell: GNU bash, version 5.1.16(1)-release (x86_64-pc-linux-gnu)

sf version:
{
"cliVersion": "@salesforce/cli/1.74.7",
"architecture": "linux-x64",
"nodeVersion": "node-v18.16.0",
"osVersion": "Linux 5.15.0-1031-aws",
"shell": "bash",
"rootPath": "/opt/nodejs/lib/node_modules/@salesforce/cli",
"pluginVersions": [
"@oclif/plugin-autocomplete 2.1.8 (core)",
"@oclif/plugin-commands 2.2.13 (core)",
"@oclif/plugin-help 5.2.9 (core)",
"@oclif/plugin-not-found 2.3.23 (core)",
"@oclif/plugin-plugins 2.4.4 (core)",
"@oclif/plugin-search 0.0.15 (core)",
"@oclif/plugin-update 3.1.10 (core)",
"@oclif/plugin-version 1.3.2 (core)",
"@oclif/plugin-warn-if-update-available 2.0.33 (core)",
"@oclif/plugin-which 2.2.18 (core)",
"@salesforce/cli 1.74.7 (core)",
"apex 2.2.12 (core)",
"auth 2.7.12 (core)",
"data 2.3.10 (core)",
"deploy-retrieve 1.8.11 (core)",
"info 2.6.6 (core)",
"limits 2.3.12 (core)",
"login 1.2.5 (core)",
"org 2.6.10 (core)",
"schema 2.3.7 (core)",
"settings 1.4.4 (core)",
"sobject 0.1.16 (core)",
"source 2.9.5 (core)",
"telemetry 2.1.3 (core)",
"templates 55.4.7 (core)",
"trust 2.4.7 (core)",
"user 2.3.8 (core)"
]
}

[github-actions]

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

[licensing-intrax]

This appears to be an aws issue. Closing.