gitea

History

zeripath 704da08fdc Better logging (#6038 ) (#6095 ) * Panic don't fatal on create new logger Fixes #5854 Signed-off-by: Andrew Thornton <art27@cantab.net> * partial broken * Update the logging infrastrcture Signed-off-by: Andrew Thornton <art27@cantab.net> * Reset the skip levels for Fatal and Error Signed-off-by: Andrew Thornton <art27@cantab.net> * broken ncsa * More log.Error fixes Signed-off-by: Andrew Thornton <art27@cantab.net> * Remove nal * set log-levels to lowercase * Make console_test test all levels * switch to lowercased levels * OK now working * Fix vetting issues * Fix lint * Fix tests * change default logging to match current gitea * Improve log testing Signed-off-by: Andrew Thornton <art27@cantab.net> * reset error skip levels to 0 * Update documentation and access logger configuration * Redirect the router log back to gitea if redirect macaron log but also allow setting the log level - i.e. TRACE * Fix broken level caching * Refactor the router log * Add Router logger * Add colorizing options * Adjust router colors * Only create logger if they will be used * update app.ini.sample * rename Attribute ColorAttribute * Change from white to green for function * Set fatal/error levels * Restore initial trace logger * Fix Trace arguments in modules/auth/auth.go * Properly handle XORMLogger * Improve admin/config page * fix fmt * Add auto-compression of old logs * Update error log levels * Remove the unnecessary skip argument from Error, Fatal and Critical * Add stacktrace support * Fix tests * Remove x/sync from vendors? * Add stderr option to console logger * Use filepath.ToSlash to protect against Windows in tests * Remove prefixed underscores from names in colors.go * Remove not implemented database logger This was removed from Gogs on 4 Mar 2016 but left in the configuration since then. * Ensure that log paths are relative to ROOT_PATH * use path.Join * rename jsonConfig to logConfig * Rename "config" to "jsonConfig" to make it clearer * Requested changes * Requested changes: XormLogger * Try to color the windows terminal If successful default to colorizing the console logs * fixup * Colorize initially too * update vendor * Colorize logs on default and remove if this is not a colorizing logger * Fix documentation * fix test * Use go-isatty to detect if on windows we are on msys or cygwin * Fix spelling mistake * Add missing vendors * More changes * Rationalise the ANSI writer protection * Adjust colors on advice from @0x5c * Make Flags a comma separated list * Move to use the windows constant for ENABLE_VIRTUAL_TERMINAL_PROCESSING * Ensure matching is done on the non-colored message - to simpify EXPRESSION		6 years ago
..
activity.go	…
attachment.go	…
branch.go	Better logging (#6038 ) (#6095 )	6 years ago
commit.go	Better logging (#6038 ) (#6095 )	6 years ago
download.go	…
editor.go	Better logging (#6038 ) (#6095 )	6 years ago
editor_test.go	…
http.go	Better logging (#6038 ) (#6095 )	6 years ago
issue.go	Better logging (#6038 ) (#6095 )	6 years ago
issue_dependency.go	…
issue_label.go	…
issue_label_test.go	…
issue_lock.go	…
issue_stopwatch.go	…
issue_timetrack.go	…
issue_watch.go	…
main_test.go	…
middlewares.go	…
milestone.go	…
pull.go	Better logging (#6038 ) (#6095 )	6 years ago
pull_review.go	…
release.go	…
release_test.go	…
repo.go	Better logging (#6038 ) (#6095 )	6 years ago
search.go	…
setting.go	Better logging (#6038 ) (#6095 )	6 years ago
setting_protected_branch.go	…
settings_test.go	…
topic.go	Better logging (#6038 ) (#6095 )	6 years ago
view.go	Better logging (#6038 ) (#6095 )	6 years ago
webhook.go	…
wiki.go	…
wiki_test.go	…