Skip to content
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

Control frequency of logging info #47

Open
Anangaya opened this issue Feb 11, 2024 · 5 comments
Open

Control frequency of logging info #47

Anangaya opened this issue Feb 11, 2024 · 5 comments
Assignees
Labels
stale Maybe not now

Comments

@Anangaya
Copy link

I want to keep log level as info, but increase the time between the logs so I can see some action.

@YamiOdymel YamiOdymel self-assigned this Feb 11, 2024
@YamiOdymel
Copy link
Member

YamiOdymel commented Feb 11, 2024

You want the INFO message to be slowed down? well, but it's a bit hard because it logs everytime something happened 🤔

@Anangaya
Copy link
Author

option to only display the latest info log would work as well. warnings and errors should create new lines though

@YamiOdymel
Copy link
Member

Are you talking about the logs in Terminal or Web UI?

It sounds like you want the INFO message to be appeared in it's own line,
and the new INFO message will replace the old one.

But logs is something that keeps printing/appending, it's impossible to replace the old line with a new message.

I want to keep log level as info, increase the time between the logs so I can see some action.

Perhaps you can have a explain the "action" you were trying to achieve,
so we can have a solution for the original problem.

Maybe some INFO messages are too meaningless, so "segment 1# inserted"- thing should be DEBUG?

@Anangaya
Copy link
Author

Anangaya commented Feb 11, 2024

I'm looking to make INFO logs in the terminal less cluttered, similar to how progress bars update by replacing old output. This would help in focusing on significant actions without the terminal getting overwhelmed. Ideally, INFO messages would update in place, while warnings and errors would still log as new entries.

This or reduce the frequency of the INFO logs for every 10 segments or something.

@YamiOdymel
Copy link
Member

YamiOdymel commented Feb 11, 2024

I see now, but it sounds difficult to replace INFO message inline meanwhile WARN/ERROR has it's own line 💀

Just let me-, let me think about it.

@YamiOdymel YamiOdymel added the stale Maybe not now label Feb 17, 2024
J0nDoe added a commit to J0nDoe/chaturbate-dvr that referenced this issue Oct 22, 2024
Channel_file.go - fix issue with segments not correctly ending when they were supposed to

Log_type.go - moved log type to it's own file, setup global logging (touches on issue teacat#47)

Main.go - added update_log_level handler, setting global log level

Channel.go, channel_internal.go, channel_util.go - updated to use new log_type

Manager.go - updated to use new log_type, update from .com to .global (issue teacat#74)

Channel_update.go, create_channel.go, delete_channel.go, get_channel.go, get_settings.go, listen_update.go, pause_channel.go, resume_channel.go, terminal_program.go - go fmt / go vet

Chaturbate_channels.json.sample - added sample json of the channels file, for mapping in docker config

List_channels.go - refactored to sort by online status, so online is always at the first ones you see

Script.js - adjust default settings, added pagination, added global log logic

Index.html - updated to use online version of tocas ui, added pagination, added global log logic, visual improvements

Removal of local tocas folder since using online version
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Maybe not now
Projects
None yet
Development

No branches or pull requests

2 participants