You've missed to follow mate. What started this discussion is the way Taiga is mounted with Cloudron technology, we don't have access to these files. 🙂
Your feedback is very welcome, particularly while we are designing the next major Taiga release. Welcoming feedback doesn't mean blindly accepting it. We have our own research and our metrics after 5 years or running this beautiful open source platform and we need to put together all those inputs.
I was not expecting you accept things blindly. These metrics you are talking about are certainly not coming from the branded taiga links in its email templates. And this is what I'm talking about only, emails. Branding emails from the settings inside the app.
I was privileged enough to enjoy early access to the Internet as back as 1995, went into open source in 1996, SuSE 5.1) and I made my career in open source since 2002.
And obviously we both haven't been developing in the same market at all. You, operating systems and in the like. Me, Marketing Technology. For example, I've running one of the first aurotesponders service online, look for "Autoresponse Magic" in Internet Way Back Machine archives. And many more in the like. I'm not saying to brag, only to show we have been online both of us long enough but we have touched two completely different worlds and markets, and approach to the Online Market, which has now become the Market Online. (no kidding)
I've seen quite some stuff over the past 19 years and what you say is true, but may I say I don't like that truth? I mean, white-labeling Taiga is not something that excites me.
Hopefully not and let's hope noone would expect that from you. Me I did not talk about white-labelling Taiga at all, and was talking about having emails of the app to be FREE of Taiga branding.
Mate you need to follow, do not bring me where I haven't touched a word. Thanks 😉
16/07/2021 17:58:24 :: [console] Error writing to collectd.localhost.df-sdc1.df_complex-used: Unable to read header (/var/lib/graphite/whisper/collectd/localhost/df-sdc1/df_complex-used.wsp)
16/07/2021 17:58:24 :: [console] Unhandled Error
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/twisted/python/threadpool.py", line 266, in <lambda>
inContext.theWork = lambda: context.call(ctx, func, *args, **kw)
File "/usr/lib/python3/dist-packages/twisted/python/context.py", line 122, in callWithContext
return self.currentContext().callWithContext(ctx, func, *args, **kw)
File "/usr/lib/python3/dist-packages/twisted/python/context.py", line 85, in callWithContext
File "/usr/lib/python3/dist-packages/carbon/writer.py", line 189, in writeForever
--- <exception caught here> ---
File "/usr/lib/python3/dist-packages/carbon/writer.py", line 165, in writeCachedDataPoints
File "/usr/lib/python3/dist-packages/carbon/database.py", line 124, in write
File "/usr/lib/python3/dist-packages/whisper.py", line 740, in update_many
return file_update_many(fh, points, now)
File "/usr/lib/python3/dist-packages/whisper.py", line 747, in file_update_many
header = __readHeader(fh)
File "/usr/lib/python3/dist-packages/whisper.py", line 294, in __readHeader
raise CorruptWhisperFile("Unable to read header", fh.name)
whisper.CorruptWhisperFile: Unable to read header (/var/lib/graphite/whisper/collectd/localhost/df-sdc1/df_complex-free.wsp)
The last line gives a hint that the graphite file is corrupt. So, I removed all the whisper files in /home/yellowtent/platformdata/graphite/whisper/collectd/localhost/df-sdc1 and graphs seems to work after that.
@atridad Maybe a good idea to check the health of the hard disk ? Also, since we hit the systemd issue on the same server.
The latest version has fixed a few issues related login session and shows now the default welcome screen if requireAuthentication is false
I have added a login button on the top right though for users to authenticate and thus have a list of their own pads
@jdaviescoates There's two levels of retry - things like network errors, transient api errors etc are retried immediately. The other retry is in the next scheduled backup time. There is no other retry between scheduled backup time.
@nebulon Thanks for clarifying that and will re-enable the automatic updates. Was just checking to see if there was a seperate channel for those and why I constantly saw the message saying that it was pre-release and not considered stable.
I’ll stick to the automatic updates as that follows the schedule of controlled updates from Cloudron, and I completely understand that some people would be willing to get the latest paches and releases for dev environments (for example).
Although maybe expanding the update options to include weeks and months might be good as some people/companies might prefer an patch management and update schedule each month rather than each week (just an idea but happy for your team to focus on more important features and bugs).
@nj yes with the folder in place there adding the -r to solve this makes sense, however the initial issue is that this folder should not be there in the first place. As the name already suggests, I guess this was just some intermediate manual action to stash certs. Essentially if you don't actively use files in that folder then just delete it to solve this for future releases.