mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-26 06:35:59 +03:00
[GH-ISSUE #178] floccus.log size and name #171
Labels
No labels
browser-specific
bug
correctness issues
enhancement
feature: Google Drive
feature: Linkwarden
feature: git
feature: nextcloud-bookmarks
feature: tabs
feature: webdav
help wanted
native-app
priority: high
priority: low
priority: medium
pull-request
question
question
stale
upstream
waiting for more information
wontfix
🙁 Not following issue template
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/floccus#171
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @lightdot on GitHub (Oct 2, 2018).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/178
Just noticed that the floccus.log:
Well, perhaps I just haven't used Floccus long enough to see the log recycled or limited in size... In this case please disregard this part, naturally.
I also suggest appending a browser name and a timestamp to the filename when saving the log trough the UI.
I tested Floccus in several different browsers on the same machine and this would have simplified it.
Eventually, turning the log off by default and having an on/off switch would probably be a good idea.
@marcelklehr commented on GitHub (Oct 4, 2018):
Hey! Thanks for your feedback! :)
Perhaps I'll have to reduce the rotation size. Chrome simply stops allowing writes at some point, so I'd like to avoid that, of course.
That's a good idea! :)
mmh. I'd rather have the log always available in case something unexpected happens. It doesn't hit performance too hard, I think.
@github-actions[bot] commented on GitHub (Mar 21, 2023):
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.