feat: allow returning error from adlib actions in blueprints#1638
feat: allow returning error from adlib actions in blueprints#1638anteeek wants to merge 5 commits intoSofie-Automation:mainfrom
Conversation
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 19 minutes and 16 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (6)
✨ 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 |
b2484b1 to
545404c
Compare
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
f806f8d to
58c6a68
Compare
About the Contributor
This PR is made on behalf of the BBC
Type of Contribution
This is a:
Feature
Current Behavior
Currently, there's no way to return a meaningful error message (other than just 500 - failed) from running an adlib action
New Behavior
This PR builds upon #1643 to allow an adlib-action to return a more generic form of error that will be propagated to callers.
This does break the api from #1643, but it loosens the api to allow for any 4xx failure reason to be given, instead of just 'validation failed'.
Note that in this example screenshot, my blueprints have assigned a stack trace to details, that field is a user owned json blob and could contain any additional details needed
Testing
Affected areas
Blueprints integration
Time Frame
Other Information
Status