App

Tangent about open source development As a person that tried the Pine64 ecosystem and not being able to will drivers/C++ apps into existence (like I can with web/cross platform), I did not contribute much other than buying the device/doing some videos on YT. (I bought: PP, PPP, PineBook, PineNote, PineTab) It depended on few people working on it eg. through Discord communities Anyway point is I saw Expensify I think they have these GitHub PRs which have $ values on them, would be interesting to take that approach, just pay for it literally eg. a GoFundMe for a feature. ex. https://github.com/Expensify/App/issues/73681

So it's much worse than I assumed from paper and repo overview? For further clarification: 1. See the issue example #14268 https://github.com/openai/SWELancer-Benchmark/tree/08b5d3dff.... It has a patch that is supposed to "reintroduce" the bug into the codebase (note the comments): + // Intentionally use raw character count instead of HTML-converted length + const validateCommentLength = (text: string) => { + // This will only check raw character count, not HTML-converted length + return text.length <= CONST.MAX_COMMENT_LENGTH; + }; Also, the patch is supposedly applied over commit da2e6688c3f16e8db76d2bcf4b098be5990e8968 - much later than original fix, but also a year ago, not sure why, might be something to do with cut off dates. 2. Proceed to https://github.com/Expensify/App/issues/14268 to see the ac

First time commenter - I was so triggered by this benchmark, so I just had to come out of lurking. I've spent time going over the description and the cases and its an misrepresented travesty. The benchmark takes existing cases from Upwork, then reintroduces the problems back in the code and then asks the LLM to fix them testing against newly written 'comprehensive tests'. Lets look at some of the cases: 1. The regex zip code validation problem Looking at the Upwork problem - https://github.com/Expensify/App/issues/14958 it was mainly that they were using a common regex to validate across all countries, so the solution had to introduce country specific regex etc. The "reintroduced bug" - https://github.com/openai/SWELancer-Benchmark/blob/main/issu... is just taking that new code and adding , to two countries.... 2. Room showing empty - 148

Pay successful bounty submissions on a faster than net 180 time frame. A friend was interested in the rather extensive Expensify bug bounty programme [0], but the red tape involved created far too long a turnaround time between claiming a ticket and receiving compensation. [0] https://github.com/Expensify/App/issues?q=is%3Aopen+is%3Aiss...