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

Debugging/troubleshooting "System Notices" #7938

Closed
3 of 7 tasks
seanenck opened this issue Aug 22, 2019 · 4 comments
Closed
3 of 7 tasks

Debugging/troubleshooting "System Notices" #7938

seanenck opened this issue Aug 22, 2019 · 4 comments
Labels
type/enhancement An improvement of existing functionality

Comments

@seanenck
Copy link

  • Gitea version (or commit ref): 1.9.1
  • Git version: 2.20.1
  • Operating system: Debian buster
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist: n/a

Description

System notices are reporting

Error while getting .editorconfig file: reference not found...

However I have no idea how to actually troubleshoot this problem because I have no context (not the missing editorconfig but how to get more information or root cause system notices). With just the type, description, and creation date I'd have to monitor all of our users actions to try and trace this...

I understand the usage of editorconfig (or what it is), I'm mainly asking:

  1. What is the intended pathway to troubleshoot "System Notices"?
  2. Can the "System Notices" provide more context in the future?

Screenshots

system_notices

@lunny lunny added the type/enhancement An improvement of existing functionality label Aug 22, 2019
@seanenck
Copy link
Author

FYI: I got lucky and was able to see the error and an action I performed that caused it (browsing to an uninitialized repository)

This certainly needs to be easier to figure out in the future

@mrsdizzie
Copy link
Member

I've added a comment about this specific error to the other bug, but IMO there isn't anything wrong with the notices themselves this is just a bad one/ vague error message :(

Like all errors it is up to whomever is adding them to be clear and have the important information needed. This particular error is just bad and doesn't include the repo/path when it should (as most other ones I've seen).

Once the solution of this particular message is clear, the error message should be updated or just removed if it doesn't really belong in system notices at all.

@charlesmorin
Copy link

charlesmorin commented Sep 13, 2019

Got the exact same thing. Impossible to reproduce as the message is way to vague. System logs isn't providing more details. Looking forward to a fix. Thanks!

Version: 1.9.2

@seanenck
Copy link
Author

I'm fine to close this at this point with the assumption that #7943 will eventually be resolved/make diagnosing this specific case better.

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/enhancement An improvement of existing functionality
Projects
None yet
Development

No branches or pull requests

4 participants