-
Notifications
You must be signed in to change notification settings - Fork 190
fix: resolve bot workflow runtime failure #1789
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: main
Are you sure you want to change the base?
fix: resolve bot workflow runtime failure #1789
Conversation
|
Hi @Abhijeet2409, this is **LinkBot** 👋
Linking pull requests to issues helps us significantly with reviewing pull requests and keeping the repository healthy. 🚨 This pull request does not have an issue linked. Please link an issue using the following format: 📖 Guide: If no issue exists yet, please create one: Thanks! |
8fdd975 to
6ce82ae
Compare
Signed-off-by: Abhijeet Saharan <[email protected]>
6ce82ae to
f26e953
Compare
WalkthroughRemoves the runtime character validation for the Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Actionable comments posted: 1
Signed-off-by: Abhijeet <[email protected]>
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.
Actionable comments posted: 1
| - Refactored SDK dependencies to use version ranges, moved build-only deps out of runtime, removed unused core deps and added optional extras. | ||
|
|
||
| ### Fixed | ||
| - Fixed bot workflow runtime failure caused by strict `FAILED_WORKFLOW_NAME` validation. (`#1690`) |
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.
🧹 Nitpick | 🔵 Trivial
LGTM! Spacing issue resolved.
The changelog entry accurately describes the fix and correctly addresses the previous review comment about spacing. The entry is now consistent with most other entries that include a space before the issue reference.
Optional nitpick: For maximum consistency, consider using plain parentheses (#1690) instead of backticks around the issue reference, as the majority of entries in the Fixed section use this format (e.g., lines 287-291). However, this is minor since backticks do appear elsewhere (line 285).
✨ Optional formatting adjustment for consistency
-- Fixed bot workflow runtime failure caused by strict `FAILED_WORKFLOW_NAME` validation. (`#1690`)
+- Fixed bot workflow runtime failure caused by strict `FAILED_WORKFLOW_NAME` validation. (`#1690`)📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| - Fixed bot workflow runtime failure caused by strict `FAILED_WORKFLOW_NAME` validation. (`#1690`) | |
| - Fixed bot workflow runtime failure caused by strict `FAILED_WORKFLOW_NAME` validation. (`#1690`) |
This PR resolves a runtime failure in
bot-workflows.jscaused by overly strict validation ofFAILED_WORKFLOW_NAME.Fix
Removed the strict validation block for
FAILED_WORKFLOW_NAME.This is safe because:
Testing
workflow_dispatchwithdry_run: true.https://github.com/Abhijeet2409/hiero-sdk-python/actions/runs/21918619254
Closes #1690