-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does changing log level affect the execution log in front end #146
Comments
What console do you refer to?
What happens when you try this on the command-line (or a JS app)? |
Both, I checked browser console, "server" console and the execution log. Other errors such as Network Errors or 404 get displayed in the execution log correctly. From what I've tried it's only
I haven't tried this yet. |
And where does this error come from exactly? Are you using some kind of auth mechanism? |
It originates from a SolidPod which I try to querry but for which I am not authorized.
I am using all basic settings except for lenient mode. |
Could be a bug then in the solid auth logic, where it doesn't propagate errors. |
Oh okay, I will look into this. Thanks for your help! |
Currently in the source code the logger is set to
info
level.I tried to adjust this by changing it to e.g.
trace
, logging the context before querying confirms that thelogger
is indeed changed totrace
, but the outcome remains the same (in the execution log) and I do not get logs in console while in devnpm run dev
or by building a static version and hosting it withhttp-server.
I am trying to achieve this because when encountering an
UnauthorizedHttpError
no results get shown not even those for which I was authorized. When using lenient mode to prevent this, the fact that I am unautherized doesn't get logged anymore.The text was updated successfully, but these errors were encountered: