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 brski CLI is extremely difficult to debug if anything goes wrong.
For example, I've encountered errors like:
2023-06-20 01:38:04.961 ERROR httplib_wrapper.cpp:251: httplib::Client fail with "Success"
I've also encountered times where the brski CLI seems to crash, but there are no logs, and brski returns 0 (aka SUCCESS) instead of an error exit code.
It seems like most of these issues are caused by the lack of error handling/logging capabilities in the HTTP library that brski uses: cpp-httplib.
cpp-httplib seems like a simple and easy-to-use library, but it doesn't have good error handling capabilities. In my opinion, we need to replace the http library used by brski to a different library, or even spin up our own HTTP handling.
The brski CLI is extremely difficult to debug if anything goes wrong.
For example, I've encountered errors like:
I've also encountered times where the
brski
CLI seems to crash, but there are no logs, andbrski
returns0
(aka SUCCESS) instead of an error exit code.It seems like most of these issues are caused by the lack of error handling/logging capabilities in the HTTP library that
brski
uses: cpp-httplib.cpp-httplib seems like a simple and easy-to-use library, but it doesn't have good error handling capabilities. In my opinion, we need to replace the http library used by
brski
to a different library, or even spin up our own HTTP handling.Potential HTTP library replacements
Server-side
(equivalent to JavaScript Promises/
await
/async
)debian/unstable
.libqt6network6
.features
Client-side
The text was updated successfully, but these errors were encountered: