-
Notifications
You must be signed in to change notification settings - Fork 3.2k
[HOLD for payment 2025-02-04] [HOLD for payment 2025-01-21][$250] Fix Proposal Police from commenting unexpected things on issues / Update to use JSON formatting #54980
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
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! 🚀 |
@thienlnam Will try a few test proposals here to see what's happening in the actions. |
This comment has been minimized.
This comment has been minimized.
PR is merged, and since it's an action it is already taking effect. So considering 7 days from today as the payment date |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.85-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2025-01-22. 🎊 For reference, here are some details about the assignees on this issue:
|
@ikevin127 @JmillsExpensify @ikevin127 The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button] |
cc @JmillsExpensify for visibility |
Payment summary: $250 to @ikevin127 for PR. |
All paid out. I paid the difference from the earlier amount via a bonus in Upwork. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.89-8 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2025-02-04. 🎊 For reference, here are some details about the assignees on this issue:
|
@ikevin127 @JmillsExpensify @ikevin127 The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button] |
❌ No need for additional payment here, as this was a follow-up PR. |
Uh oh!
There was an error while loading. Please reload this page.
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: @JmillsExpensifyThe text was updated successfully, but these errors were encountered: