You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idea : Have more contextual engine log.
Keep network traces only for a specific channel :
- Add debug bool or log_level field in channel model
Debug a specific translation.
- Add readrecorddebug bool in translate model
- Add mappingdebug bool in translate model
And make the engine write his log according to it.
Original issue reported on code.google.com by [email protected] on 18 Apr 2014 at 10:39
The text was updated successfully, but these errors were encountered:
think that would be possible.
for channels there is the problem that at the moment there are no more 'spare
field' in the database.
(try to avoid changes in database because migration is less easy)
(for myself: I use these extended log settings only in development. And
nowadays I mostly use the 'checklevel' setting. )
Yes I agree for mapping, but for networks, dev and prod could have different
rules for each part, and it could help in some cases if errortext is not enough
: server certificate change, proxy, imap, ftp, server down, ...
I don't know if errortext is enough to investigate all case.
Original issue reported on code.google.com by
[email protected]
on 18 Apr 2014 at 10:39The text was updated successfully, but these errors were encountered: