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

Log errors to a file #88

Open
2 tasks done
Jacalz opened this issue May 16, 2023 · 1 comment
Open
2 tasks done

Log errors to a file #88

Jacalz opened this issue May 16, 2023 · 1 comment
Labels
enhancement New feature or request
Milestone

Comments

@Jacalz
Copy link
Owner

Jacalz commented May 16, 2023

Checklist

  • I have searched the issue tracker for open issues that relate to the same feature, before opening a new one.
  • This issue only relates to a single feature. I will open new issues for any other features.

Is your feature request related to a problem?

On crashing, it would be good to see any errors that occurred even when not running Rymdport from a terminal. Always logging output to a log file should solve this.

Describe the solution you'd like to see.

Use a logger that prints to a file.

@Jacalz Jacalz added the enhancement New feature or request label May 16, 2023
@Jacalz Jacalz added this to the Undecided milestone Jun 22, 2023
@Jacalz
Copy link
Owner Author

Jacalz commented Jun 22, 2023

It might be nice to do this once we have Go 1.21 as the base and thus can use the new log/slog package. There will however be quite some time until we can use that as a base (currently just considering moving to Go 1.18 has minimum for v3.5.0) so we might have to either wait a long time or find a temporary solution.

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

No branches or pull requests

1 participant