Closed memorsolutions closed 2 months ago
Thanks for the very helpful bug report! A fix is proposed in https://github.com/aws/aws-toolkit-vscode/pull/5279 . Would you mind trying it out to confirm that it fixes the issue for you?
Extensions: Install from VSIX
to install the *.vsix
file.@justinmk3 , tested and have confirmed that the errors are no longer present.
Thank you for the quick response!
This request was addressed in AWS Toolkit 3.14.0 and/or Amazon Q 1.14.0!
AWS Toolkit changelog: https://github.com/aws/aws-toolkit-vscode/blob/master/packages/toolkit/CHANGELOG.md Amazon Q changelog: https://github.com/aws/aws-toolkit-vscode/blob/master/packages/amazonq/CHANGELOG.md Release artifacts: https://github.com/aws/aws-toolkit-vscode/releases
Problem
Both the AWS Toolkit and Amazon Q extensions produce the following error when the extension is activated and the effective user account is one that is defined externally (e.g., AD, LDAP).
[error] SystemError: A system error occurred: uv_os_get_passwd returned ENOENT (no such file or directory)
This appears to have been introduced by #5215 with the addition of the call to os.userInfo in getUsername (env.ts).
In such cases, the effective user ID does not have a matching entry in /etc/passwd and userInfo throw an exception. This error is discussed in several issues in other repos such as:
Might a fallback to process.env.USER be an acceptable approach for these extensions?
NOTE: Recent restructuring in https://github.com/aws/aws-toolkit-vscode/commit/c21dce155b5b3d3cd70094c843db6e8ae5b32417 appears to retain this bug.
Steps to reproduce the issue
~/.config/Code/logs/<date and time>/window1/exthost/exthost.log