-
Notifications
You must be signed in to change notification settings - Fork 5.5k
Fireflies - error handling #16024
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
Fireflies - error handling #16024
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 3 Skipped Deployments
|
WalkthroughThis pull request enhances error handling in several fireflies actions by validating the presence of required parameters and checking API responses for errors. The Changes
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
Warning There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure. 🔧 ESLint
components/fireflies/actions/find-meeting-by-id/find-meeting-by-id.mjsOops! Something went wrong! :( ESLint: 8.57.1 Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs components/fireflies/actions/find-recent-meeting/find-recent-meeting.mjsOops! Something went wrong! :( ESLint: 8.57.1 Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs components/fireflies/fireflies.app.mjsOops! Something went wrong! :( ESLint: 8.57.1 Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (5)
✅ Files skipped from review due to trivial changes (2)
🚧 Files skipped from review as they are similar to previous changes (2)
⏰ Context from checks skipped due to timeout of 90000ms (2)
🔇 Additional comments (2)
✨ Finishing Touches
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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.
Hi @michelle0927 lgtm! Ready for QA!
components/fireflies/actions/find-recent-meeting/find-recent-meeting.mjs
Outdated
Show resolved
Hide resolved
@@ -26,6 +31,11 @@ export default { | |||
}, | |||
}, | |||
}); | |||
|
|||
if (meeting.errors?.length) { |
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.
So, minor coding style nit here, but rather than requiring all callers of proxy
handle these errors, which can be error prone, it might be more consistent to have the base function detect an error response (e.g. by finding an error
key in the json response), and raising the ConfigurationError
at that point. That way upload-audio
any future actions, as well as async options can all benefit from the same error handling. Does that make sense?
components/fireflies/actions/find-recent-meeting/find-recent-meeting.mjs
Outdated
Show resolved
Hide resolved
components/fireflies/actions/find-recent-meeting/find-recent-meeting.mjs
Outdated
Show resolved
Hide resolved
Hi everyone, all test cases are passed! Ready for release! Test report |
/approve |
Add configuration errors to Fireflies actions.
Summary by CodeRabbit
Bug Fixes
Chores