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
What version are you running
6.3.0. Auto-updated from some older version, possibly 6.2.1.
Describe the bug
According the wiki, there should be a check box to enable/disable debugging. I would like to disable debug logging, because it's making it harder to debug a different EDMC problem. However, this checkbox is not present.
To Reproduce
Open the Settings dialog.
EDMC 5.1.2
Canonn plugin 6.3.0
Expected behavior
Check box present and reduces log spam when not checked
Additional Context
I cloned the repo and grepped the whole repo (both master and develop branches) for the string and was unable to find Turn on Debugging. Is the wiki description premature?
But after I double-checked that and restarted EDMC, I'm still getting Canonn DEBUG logs. Here's the log: EDMarketConnector.log
So it looks like there's (1) a documentation bug about the Canonn setting being present, and (2) another bug where debug logging is going when it's not supposed to. This bug might be in EDMC.
What is your commander name
Floor Jansen
What version are you running
6.3.0. Auto-updated from some older version, possibly 6.2.1.
Describe the bug
According the wiki, there should be a check box to enable/disable debugging. I would like to disable debug logging, because it's making it harder to debug a different EDMC problem. However, this checkbox is not present.
To Reproduce
Open the Settings dialog.
EDMC 5.1.2
Canonn plugin 6.3.0
Expected behavior
Check box present and reduces log spam when not checked
Screenshots
https://cdn.discordapp.com/attachments/331059145388064768/872671652624875590/unknown.png
Additional Context
I cloned the repo and grepped the whole repo (both master and develop branches) for the string and was unable to find
Turn on Debugging
. Is the wiki description premature?The text was updated successfully, but these errors were encountered: