-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[$250] Fix Proposal Police from commenting unexpected things on issues / Update to use JSON formatting #54980
Comments
Job added to Upwork: https://www.upwork.com/jobs/~021877133911642803604 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ZhenjaHorbach ( |
Triggered auto assignment to @JmillsExpensify ( |
Upwork job price has been updated to $125 |
📣 @ikevin127 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
Kevin is working on this - slack discussion here |
Upwork job price has been updated to $250 |
♻️ Plan
|
Updates
Here's the test repository to get an Idea of action response after the 3 changes mentioned above were implemented: ikevin127/expensify-proposal-testing#1 (comment) ♻️ Tomorrow will proceed with |
♻️ Did some more testing and looks like the o1-mini model is not available with AI assistants. I started testing the different cases and neither gpt-4o-mini nor gpt-4o seem to follow the instructions when it comes to wrong proposal template case, even though it does return structured format, it doesn't seem to understand the context when it comes to the proposal template and the mandatory / optional sections. The only one that's working as expected is the gpt-4-1106-preview model, which is what I use on my side for testing and what proposal police was based on from the beginning. ↪️ I will continue to test on my side with gpt-4-1106-preview, then I'll move forward with to the GH action code changes part. When I'm done I'll report on the testing and we can decide whether :expensify: wants to stay on the gpt-4-1106-preview model given the pricing or explore other alternatives. After further discussions I'll do some prompt engineering to try and have it work on gpt-4o-mini or gpt-4o because otherwise the costs would be too high. |
cc @thienlnam @marcochavezf PR is ready for review! 🚀 |
Example here: #54905 (comment)
The ProposalPolice bot commented something unexpected and this was due to the API call returning something unexpected which was not handled.
Solution:
Update the API to use structured responses which will ensure that the returned parameter is in a format we expect which should prevent situations like this in the future
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @ZhenjaHorbachThe text was updated successfully, but these errors were encountered: