On 2026-03-29, Tavis Ormandy wrote: > On 2026-03-28, John Wiegley wrote: >>>>>>> "TO" == Tavis Ormandy <[email protected]> writes: >> >>> I'm currently minimizing things manually, maybe I should automate that if it >>> looks like it might be a big job... I'll wait to see if it's easy :) >> >> Minimizing? >> > > I just mean finding a minimal set of transactions that demonstrate the > problem. > >>> There are a lot of breaking changes, it might take some time to minimize >>> testcases. What is the best way to handle it? >> >> Very good question. I think first I’d like to know: Which are the ones that >> yield no differences? >>
I can't help feeling a bit frustrated with the pace and volume of AI changes, it still seems like a coin toss if if my ledger will work or not with the next `git pull` :( For example, this week claude broke `--sort date`... is this feature really so niche, or am I the only person testing? I think maybe people won't notice all the problems until the next release happens. https://github.com/ledger/ledger/issues/3126 It might be tough walking users through isolating the problematic transactions and running git bisect, and with the huge amount of code churn nobody is going to be able to guess what might have caused it... Tavis. -- _o) $ lynx lock.cmpxchg8b.com /\\ _o) _o) $ finger [email protected] _\_V _( ) _( ) @taviso -- --- You received this message because you are subscribed to the Google Groups "Ledger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/ledger-cli/10rj51u%24skl%241%40ciao.gmane.io.
