Replies: 2 comments 2 replies
|
There no additional verbosity available. That's a low level error from a library. It's not a CDL error. We can't modify the message. But this is the kind of errors that should never happen, which means the error it not actually accurate and the actual error is further up the logic chain. Whatever message gets printed here will be irrelevant. The only import detail is the trace-back to see to chain of methods that eventually raises the error. You have to run the source code in an IDE to figure out what is actually happening. TLDR: If you get a critical error, fill a bug report |
|
It's now possible to get developer logs in v6.6.1 Set the environment variable |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I already run with
log_level: 10but I feel like that's not enough.here's one example. I'm scraping a particular forum thread, and CDL crashes with
it would be nice to see the exact URL it does not like, or at least the exact forum post link where it occurs, right?
so, ether debug log level should include that info, or we need an even more verbose log option.
I'm a bit hesitant to file this as feature request because, chances are, I'm holding it wrong.
thoughts?
All reactions