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
This used to be very helpful because back in the day when specs would run, you had a full HTTP server that booted, and you could tail this file to watch the logs and see what was going on. However, that's not the case anymore because booting an HTTP server on spec run is expensive and slow.
This leads to an issue where you run your specs, and you get a 500 error in an action, and tailing this log just looks like this
We need to figure out how we can rework this so your queries and errors and everything can go to this file and not STDOUT to the terminal. You should be able to tail this file while running specs and get good information as to what queries your spec is running and what exceptions or errors you're hitting.
The text was updated successfully, but these errors were encountered:
When you generate a new app, you get this section in your
config/log.cr
filelucky_cli/src/web_app_skeleton/config/log.cr.ecr
Lines 3 to 11 in 8344b27
This used to be very helpful because back in the day when specs would run, you had a full HTTP server that booted, and you could tail this file to watch the logs and see what was going on. However, that's not the case anymore because booting an HTTP server on spec run is expensive and slow.
This leads to an issue where you run your specs, and you get a 500 error in an action, and tailing this log just looks like this
We need to figure out how we can rework this so your queries and errors and everything can go to this file and not STDOUT to the terminal. You should be able to tail this file while running specs and get good information as to what queries your spec is running and what exceptions or errors you're hitting.
The text was updated successfully, but these errors were encountered: