Skip to content
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

Chrome Extension Fills Developer Console with Errors #562

Open
1 task
lorenwest opened this issue Dec 27, 2024 · 5 comments
Open
1 task

Chrome Extension Fills Developer Console with Errors #562

lorenwest opened this issue Dec 27, 2024 · 5 comments
Assignees
Labels
app:web extension blocked blocked by something bug Something isn't working status:triaged The ticket has been reviewed, prioritized, categorized, and assigned to the appropriate team member.

Comments

@lorenwest
Copy link

lorenwest commented Dec 27, 2024

Software

Web Extension

Operating System / Platform

macOS

Your Pieces OS Version

11.0.3

Early Access Program

  • Yes, this is related to an Early Access Program feature.

Kindly describe the bug and include as much detail as possible on what you were doing so we can reproduce the bug.

It appears the browser extension is sniffing a bunch of local ports - starting with 1000. This is a bit concerning, and a little invasive, but I do have the Pieces OS running, and it does finally get a response at a high port.

This fills my devtools console tab, degrading my development experience by clouding errors I'm looking for in my own app.

For a product designed to enhance my development experience I'm marking this as a bug.

Image
@mark-at-pieces mark-at-pieces added bug Something isn't working status:triaged The ticket has been reviewed, prioritized, categorized, and assigned to the appropriate team member. app:web extension labels Dec 30, 2024
@rutvik110
Copy link

hey @lorenwest, this is expected. With our recent updates to Pieces OS, we don't have a designated port at which we can expect Pieces OS to be running as it can be changed by the user. For this purpose, we're checking against the expected ports and find which one's active. The failed calls in the above screenshot are basically attempts where we're checking if Pieces OS api is running or not. This checks are made only against Pieces OS endpoint and doesn't scan for anything else on your machine. So, your privacy is still well respected.

But I can still take look into if I can hide or better handle the errors from the inactive Pieces OS port checks to not flood the dev tool. Lmk if there's anything else but thanx for reporting this.

@lorenwest
Copy link
Author

Thanks for your reply. Other than it appearing invasive, I figured it was easily explained and not something to be concerned about.

The reason for this post was about it filling up a development console that we use daily for debugging our software, and that we've spent a good deal of time cleaning up so we're not mixing phantom errors with real errors.

I really want to like Pieces, and can overlook this during our trials. Addressing it would be welcome (possibly necessary) for us to really ❤️ this tool.

@rutvik-at-pieces
Copy link

rutvik-at-pieces commented Jan 3, 2025

Totally there with you on the issue @lorenwest! Expect a fix for this in the upcoming patch update for extension that should happen sometime next week.

@rutvik-at-pieces
Copy link

So, I looked into this issue and it seems like this may be a Chrome bug where it surfaces the network request failures from extension even when those failures were handled by the extension to fail silently. There's not a definite answer on whether this issue is going to be fixed in the near future and no clear solution is given for the developers/users to handle this issue.
https://issues.chromium.org/issues/40788570
https://issues.chromium.org/issues/41293123

@rutvik-at-pieces rutvik-at-pieces added the blocked blocked by something label Jan 6, 2025
@rutvik-at-pieces
Copy link

Users can however check this "Hide Network Messages" box in the dev console settings to prevent network logs from being shown in the console. Not sure how feasible this is for the end users though @lorenwest

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
app:web extension blocked blocked by something bug Something isn't working status:triaged The ticket has been reviewed, prioritized, categorized, and assigned to the appropriate team member.
Projects
None yet
Development

No branches or pull requests

4 participants