On Thursday, September 19, 2019 at 5:02:54 PM UTC-5, SegundoBob wrote: This bug may be in my code or in Leo-Editor code. I have been seeing > occurrences for at least two weeks. > > The bug occurs when I run my unit tests for my program that compares two > Leo-Editor files. I have 41 unit tests. The bug occurs about once every > 30 tests. >
Sounds like a worthy bug. Thanks for sharing it with us. I don't have any ideas about causes. My strategy would be to insert traces in Leo as follows: I would trace fast.readFile in leoFileCommands.py. This is the code that reads .leo files. If your .leo files contain external files, I would also trace fast_at.scan_lines in leoAtFile.py. My goal would be to have the traces fire only in unexpected situations, so I don't get overwhelmed with data. If you can get that to happen you will likely have a handle on what is going on. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/53dfa78f-acb5-43a2-bfb5-a6e080f038f6%40googlegroups.com.
