thepaperpilot/forgejo
1
0
Fork 0
Code Issues Pull requests Releases Activity Actions

[TESTS] increase test-sqlite log level to Trace

Browse source 
It does not pollute the output because they go to sqlite-log/gitea.log
and it may provide clues for debugging. When trying to figure out a
problem in production, Debug is likely to be used but in a development
environment a very fine grain log is the most useful. If that's really
too much noise, the lines can be trimmed by removing all those with [T].

(cherry picked from commit 666b02eb9d)
(cherry picked from commit b69e4d3058)
This commit is contained in:
Earl Warren 2023-07-21 07:35:52 +02:00
parent 46acb6a9a7
commit 0c1aecd7ec
No known key found for this signature in database
GPG key ID: 0579CB2928A78A00
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
tests/sqlite.ini.tmpl
View file

@ -91,7 +91,7 @@ LEVEL = Info
COLORIZE = true COLORIZE = true
[log.file] [log.file]
LEVEL = Debug LEVEL = Trace
[security] [security]
PASSWORD_HASH_ALGO = argon2 PASSWORD_HASH_ALGO = argon2