Software engineer/Web developer/Consultant/Nerd/Devops enthusiast during days | Open Sourcer/Drummer/Poet during nights | Biker on weekends | Student for life
@ICICILombard thank you for your pathetic services @ICICILombard I have raised a complaint with needed government bodies against you and your absolute bullshit services.
@ICICILombard how can you keep vehicle insurance claim pending for more than a week despite providing all the details. this is absolute fraud.
@irdaindia please look into the matter and take strict action against. their claim manager is also not giving satisfactory response.
@curiousharish I think its more about getting used to it. There is reason why so many enterprises prefer AWS. Once you get used to it you mostly will never go to their UI all will work from your helm charts
Ahhhh, Codex 5.3 (xhigh) with a vague prompt just solved a bug that I and others have been struggling to fix for over 6 months. Other reasoning levels with Codex failed, Opus 4.6 failed. Cost $4.14 and 45 minutes. Full trace plus includes original issue: https://t.co/DbBACN2HLj
I know this prompt is relatively bad. Honestly, our stable release is in a week, and I was throwing some Hail Marys at the frontier models to see if I could get a clean, understandable fix for some of these bugs. By using `gh`, it grabs much better context from the issue, so its not terrible.
The best thing that Codex did was eventually start reading GTK4 source code. That's where I ended up (see my GH issue), and I knew the answer was somewhere in there, but I didn't have the time or motivation to do it myself. The other models never went there, and lower reasoning efforts with 5.3 didn't go there either. Only xhigh went there. I think that was a critical difference.
The final fix was decent. It was small, all in a single file, and very understandable. It had one bug I identified (you can see in the trace), and then I manually cleaned up some style. But, it did a great job.
Definitely an "it's so over" moment. But at the same time, it feels amazing because now our next stable release will have this fix and I was able to spend the time working on other fixes as it went.
@bramus@SantoshYadavDev when it's completely collapsed it's difficult to click on tab. it most of the time gets clicked on tab close button. perhaps it needs some improvement. not sure what it can be. may be make close button smaller or increase the tab button size.
@jonathan_wilke would prefer tanstack cause of its react 18/19 support but wont choose it just cause I see unwanted rerender with react hook form. with formcontextprovider it can be fixed pretty easily.