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
cherry pick #2583 - allowing flexibility as we didn't inform the team on
branch cut deadlines
Fixes https://linear.app/sourcegraph/issue/QA-149
## Chnages
Adds detailed Cody logging, e.g. network errors.
Required dev mode (e.g. `:customRunIde`) or debug logging enabled in
settings for trace/debug/info messages,
errors and warning are logged always. Cody Console is popping out only
in dev mode regardless of the message severity.
## Test plan
1. Run `:customRunIde` - there is good chance you will notice some
network errors at the start, but there should not be much of them
2. Go to the Cody settings and enable debug logging.
3. Restart IDE
4. Now you should see much more debug messages in Cody Console and in
the logs

## Test plan
<!-- All pull requests REQUIRE a test plan:
https://sourcegraph.com/docs/dev/background-information/testing_principles
Why does it matter?
These test plans are there to demonstrate that are following industry
standards which are important or critical for our customers.
They might be read by customers or an auditor. There are meant be simple
and easy to read. Simply explain what you did to ensure
your changes are correct!
Here are a non exhaustive list of test plan examples to help you:
- Making changes on a given feature or component:
- "Covered by existing tests" or "CI" for the shortest possible plan if
there is zero ambiguity
- "Added new tests"
- "Manually tested" (if non trivial, share some output, logs, or
screenshot)
- Updating docs:
- "previewed locally"
- share a screenshot if you want to be thorough
- Updating deps, that would typically fail immediately in CI if
incorrect
- "CI"
- "locally tested"
-->
Co-authored-by: Piotr Kukiełka <pkukielka@users.noreply.github.com>
0 commit comments