luminus 2020-03-06 | Slack Archive

ScArcher04:03:47

I don't have the context of the question, but it's probably to avoid storing passwords in source control. Also if you're working on a team, every dev may have some different configuration relative to their system. (let me know if I'm way off with this answer)

sudakatux11:03:16

sudakatux11:03:50

So when you get an exception. how does one see the exception. im looking for the logs etc but i cant find how to get the details of the exception

bibiki12:03:26

do you have an example you'd like to go through together?

sudakatux12:03:45

so im following the book

sudakatux12:03:07

you get the swagger part

sudakatux12:03:25

if i miss something swagger says 500 Exception

sudakatux12:03:43

now say i want to see the trace for that exception so i can look into what happened

sudakatux12:03:03

how can i get that printed to the log?

sudakatux12:03:20

I already figured out what the problem was. However i would like to know how i can get exceptions printed either in the repl or even better to the log file

bibiki12:03:34

ok, I see what you mean. but I cannot imagine why you would not see exception in repl.

bibiki12:03:13

I mean, when using "lein repl" the config is there for you, and it should just work... not like you have to do something for that

bibiki12:03:04

there is the log directory at the root of the project, do you not have that

sudakatux12:03:19

yeah. but the exception didnt get printed

bibiki12:03:24

and your log config file is env/dev/resources/logback.xml

sudakatux12:03:44

ahh cool