704da08fdc
* 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 |
||
---|---|---|
.. | ||
migrations.go | ||
v13.go | ||
v14.go | ||
v15.go | ||
v16.go | ||
v17.go | ||
v18.go | ||
v19.go | ||
v20.go | ||
v21.go | ||
v22.go | ||
v23.go | ||
v24.go | ||
v25.go | ||
v26.go | ||
v27.go | ||
v28.go | ||
v29.go | ||
v30.go | ||
v31.go | ||
v32.go | ||
v33.go | ||
v34.go | ||
v35.go | ||
v36.go | ||
v37.go | ||
v38.go | ||
v39.go | ||
v40.go | ||
v41.go | ||
v45.go | ||
v46.go | ||
v47.go | ||
v48.go | ||
v49.go | ||
v50.go | ||
v51.go | ||
v52.go | ||
v53.go | ||
v54.go | ||
v55.go | ||
v56.go | ||
v57.go | ||
v58.go | ||
v59.go | ||
v60.go | ||
v61.go | ||
v62.go | ||
v63.go | ||
v64.go | ||
v65.go | ||
v66.go | ||
v67.go | ||
v68.go | ||
v69.go | ||
v70.go | ||
v71.go | ||
v72.go | ||
v73.go | ||
v74.go | ||
v75.go | ||
v76.go | ||
v77.go | ||
v78.go | ||
v79.go | ||
v80.go | ||
v81.go | ||
v82.go |