Skip to content

Comments

VIDSOL-442: Remove warn logs from publisher#335

Open
OscarFava wants to merge 3 commits intodevelopfrom
vidsol-442/Remove-logs-from-publisher
Open

VIDSOL-442: Remove warn logs from publisher#335
OscarFava wants to merge 3 commits intodevelopfrom
vidsol-442/Remove-logs-from-publisher

Conversation

@OscarFava
Copy link
Contributor

What is this PR doing?

Removing warn logs from publisher that were only used for dogfooding.

How should this be manually tested?

X

What are the relevant tickets?

A maintainer will add this ticket number.

Resolves VIDSOL-442

Checklist

[X] Branch is based on develop (not main).
[ ] Resolves a Known Issue.
[ ] If yes, did you remove the item from the docs/KNOWN_ISSUES.md?
[ ] Resolves an item reported in Issues.
If yes, which issue? Issue Number?

@OscarFava OscarFava self-assigned this Jan 19, 2026
Copilot AI review requested due to automatic review settings January 19, 2026 14:30
@OscarFava OscarFava added the do-not-merge Do Not Merge label Jan 19, 2026
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR removes debug/dogfooding warning logs from publisher-related code and replaces some warning logs with error logs where appropriate. The changes improve log hygiene by eliminating verbose diagnostic logging that was only needed during development.

Changes:

  • Removed multiple console.warn statements from publisher lifecycle events and subscription handling
  • Changed console.warn to console.error for actual error conditions
  • Updated corresponding test expectations to reflect the logging changes

Reviewed changes

Copilot reviewed 11 out of 11 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
libs/core/src/stores/devices/DevicesContext.ts Changed unsupported enumerateDevices warning to error
frontend/src/utils/VonageVideoClient/vonageVideoClient.ts Removed subscriber and publisher diagnostic warn logs
frontend/src/hooks/useNetworkTest.tsx Changed network test error warning to error
frontend/src/hooks/useDevices.tsx Changed unsupported enumerateDevices warning to error
frontend/src/hooks/tests/useDevices.spec.tsx Updated test to expect error instead of warn
frontend/src/components/MeetingRoom/ReportIssue/FeedbackForm/FilePicker/FilePicker.tsx Changed screenshot error warning to error
frontend/src/Context/SessionProvider/session.tsx Removed subscription error diagnostic warn log
frontend/src/Context/PublisherProvider/usePublisher/usePublisher.tsx Removed extensive publisher lifecycle warn logs; changed error warnings to errors; removed unused dependencies from useCallback
frontend/src/Context/PublisherProvider/usePublisher/usePublisher.spec.tsx Updated test expectations for error instead of warn
frontend/src/Context/PreviewPublisherProvider/usePreviewPublisher/usePreviewPublisher.tsx Changed publisher destruction warning to error
frontend/src/Context/BackgroundPublisherProvider/useBackgroundPublisher/useBackgroundPublisher.tsx Changed publisher destruction warning to error

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@sonarqubecloud
Copy link

Quality Gate Failed Quality Gate failed

Failed conditions
40.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud

Copy link
Contributor

@Hossein-Movahed Hossein-Movahed left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔥

@Vonage Vonage deleted a comment from Copilot AI Feb 10, 2026
Copy link
Contributor

@johnny-quesada-developer johnny-quesada-developer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants