bug: panic's not logged to log file when --file-logging is specified
#223
Comments
techfg
added a commit
to techfg/skuid-cli
that referenced
this issue
Oct 5, 2024
…r codebase This commit started with the goal of improving logging (skuid#220) to help aid with identifying when outcomes were not as expected due to the many issues currently present in the CLI and on the server-side. During the course of improving the logging which required going through essentially every line of code in the codebase, many new issues were identified and fixes for nearly all of them implemented. Additionally,validations of all steps in the CLI were improved to and logs emitted with the results. Lastly, the code was significnatly refactored in many areas to improve code maintainability (skuid#230). Due to the size of this commit, there is too much to explain in detail in a commit message. See forthcoming comment in skuid#205 for full details of this commit. Resolves skuid#59 Resolves skuid#165 Resolves skuid#199 Resolves skuid#218 Resolves skuid#220 Resolves skuid#221 Resolves skuid#222 Resolves skuid#223 Resolves skuid#224 Resolves skuid#228 Resolves skuid#230 Resolves skuid#231
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When CLI is executed with
--file-logging, any panic that occurs is not logged to the log file.The text was updated successfully, but these errors were encountered: