You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While working on some PRs and having the cointop configuration file open in my $EDITOR I noticed that cointop made changes to the config file. Inspecting filesystem operations on config.toml using fswatch it appears the configuration file is written to around 10 times per minutes (give or take a few) when cointop is running (see code snippet below), which seems unnecessary.
Any idea where that might originate from, @miguelmota?
I'd appreciate some pointers as to where the cause may lie and am happy to look into it and provide a PR.
$ fswatch -tu file.txt
Sat 24 Apr 2021 09:49:26 PM GMT /home/mota/go/src/github.com/miguelmota/test/file.txt
Sat 24 Apr 2021 09:49:26 PM GMT /home/mota/go/src/github.com/miguelmota/test/file.txt
Sat 24 Apr 2021 09:49:27 PM GMT /home/mota/go/src/github.com/miguelmota/test/file.txt
Sat 24 Apr 2021 09:49:27 PM GMT /home/mota/go/src/github.com/miguelmota/test/file.txt
The method ct.Save() is invoked when performing actions like toggling favorites, editing portfolio, price alerts, preferred currency, etc. which causes file writes.
I wonder if the the very frequent file writes I saw possibly had to do with two running instances of cointop…
I'm going to close this issue for now and will re-open with more reproducible instructions should the issue occur again.
While working on some PRs and having the cointop configuration file open in my
$EDITOR
I noticed that cointop made changes to the config file. Inspecting filesystem operations on config.toml usingfswatch
it appears the configuration file is written to around 10 times per minutes (give or take a few) whencointop
is running (see code snippet below), which seems unnecessary.Any idea where that might originate from, @miguelmota?
I'd appreciate some pointers as to where the cause may lie and am happy to look into it and provide a PR.
The text was updated successfully, but these errors were encountered: