-
Notifications
You must be signed in to change notification settings - Fork 301
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"change(s) detected" on console #1952
Comments
It looks like Fava's using |
Yes, these are the logs of watchfiles. I think these logs are somewhat useful (to see that files changed which should trigger a reload) and don't necessarily see the need to disable them. Do they bother you? |
Yeah, it does. 😁 I usually have two instances of Fava running in the background of one terminal window while I do other Beancount-related things and it can get pretty noisy in there.
—
Brian Lalor (he/him)
***@***.***
… On Feb 9, 2025, at 6:15 AM, Jakob Schnitzer ***@***.***> wrote:
Yes, these are the logs of watchfiles. I think these logs are somewhat useful (to see that files changed which should trigger a reload) and don't necessarily see the need to disable them. Do they bother you?
—
Reply to this email directly, view it on GitHub <#1952 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAA22WZWIILUL55BOU3RAM32O42GVAVCNFSM6AAAAABWHU2GW2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBWGE4DEMJRG4>.
You are receiving this because you authored the thread.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Fava 1.30, Beancount 3.0.0
I see these messages on the console when Fava's running and I make changes to beancount files:
I looked for those strings in the Fava source and don't see them, so I suspect it's from an included library. Maybe there's some logging that needs to be configured?
The text was updated successfully, but these errors were encountered: