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

Logging #109

Closed
Tracked by #240
bouncepaw opened this issue Oct 27, 2021 · 5 comments
Closed
Tracked by #240

Logging #109

bouncepaw opened this issue Oct 27, 2021 · 5 comments

Comments

@bouncepaw
Copy link
Owner

Currently, out logging is a mess.

We want to clean up this mess.

How?

@bouncepaw
Copy link
Owner Author

The question has been asked:

Do we need structured logging?

To which I say: we don't really.

@bouncepaw
Copy link
Owner Author

A recent code scan has revealed a vulnerability in the logging system. 12 vulnerabilities, in fact. GitHub has notified about it.

Снимок экрана 2021-12-15 в 21 12 31

Yep, thanks a lot.

I guess we should do something about it. On the other hand, why

🌾

@handlerug
Copy link
Contributor

golang/go#54763

@bouncepaw
Copy link
Owner Author

Since 2022, slog started existing. That's what ought to be used one day.

@bouncepaw bouncepaw mentioned this issue Jun 28, 2024
12 tasks
bouncepaw added a commit that referenced this issue Sep 7, 2024
* Migrate httpd.go

* Migrate history and main

* Migrate hypview

* Migrate interwiki

* Migrate misc

* Migrate utils

* Migrate backlinks

* Migrate categories

* Reformat some imports

* Migrate hyphae

* Migrate migration

* Reformat more imports

* Migrate user

* Migrate shroom

* Migrate viewutil

* Migrate web

* Migrate others

* Migrate main

* Wording concerns
@bouncepaw
Copy link
Owner Author

bouncepaw commented Sep 7, 2024

In a two-hour rush, implemented. I like it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants