-
Notifications
You must be signed in to change notification settings - Fork 6
Feature/v2/train #67
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
base: docker/2025/03/26
Are you sure you want to change the base?
Feature/v2/train #67
Conversation
…onment variables since no settings exported, and Solve the problem of the isTransferContent judgment logic.
feat: ELI2-107/cli-improve-plugin-install-and-github-auth-ux
…entions-option feat: Add shouldRespondOnlyToMentions option for discord
fix: handle whitespace issue in GUI name field
fix: gui text animation
fix: room status
| } catch (error) { | ||
| handleError(error); | ||
| } | ||
| //try { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Commenting out error handling blocks (try-catch) without replacing them with an alternative can lead to unhandled exceptions, which might cause the application to crash unexpectedly.
| const packageJsonPath = path.join(cwd, 'package.json'); | ||
| if (!existsSync(packageJsonPath)) { | ||
| logger.error('No package.json found in current directory.'); | ||
| // try { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The try block is commented out, which means exceptions during the publish process are not caught, potentially causing the application to crash without proper logging or cleanup.
Pull request summary
|
Relates to
Risks
Background
What does this PR do?
What kind of change is this?
Documentation changes needed?
Testing
Where should a reviewer start?
Detailed testing steps