Clojurians Log v2
cursive 2026-01-16
I felt like I was losing my mind, but, nope, it’s Cursive. 😉 Top is a file in cursive, bottom is the same file cat’d in terminal. Line 5 is different. There are no uncommitted changes in the repo, file is not marked unsaved in the IDE (I can cmd+s all I want). What is … happening!? Oh, and the fie compiles in the repl in Cursive, but throws a compiler error if I kick off tests from the CLI.
actually making a change to the file myself and saving it updates it with the “hidden” change, too.;
this is the stuff of nightmares
how much time did it take to find this?
I imagine an "invalidate caches" would take care of this(?)
About 15 minutes. Too long. ;)
not too bad. I could see this sneaking into prod and just being impossible to find.
My test runner job in GitHub was throwing the compiler error- I would look in my IDE, compile it, shrug, and then kick off the job in GitHub again.
Trust nothing!
feelsbadman
you try invalidate caches?
I have had bizarre syncing issues like this with another IntelliJ product called Datagrip. Seemed like they had some strange ideas around caching, source of truth, etc.
is this parinfer? 😞
I'm going to CYA here and say that I think this is IntelliJ, not Cursive, but yeah, feelsbadman for sure.
What I think it looks like is a bug in IntelliJ's virtual file system. I'm sure they have their reasons for it, but it's frequently a real problem where the IDE sees some changes that haven't been synced to disk. But if you're explicitly saving, or swapping to another app and back (usually auto-saves on loss of focus) then it looks like a bug in IntelliJ's VFS dirty detection. Unfortunately it's not something I can help with, sorry 😞
Thanks for all the responses- I’m just glad I wasn't going crazy. ;)