Do not show console error when libnames are failed to parse as a URL

[canova]

This is polluting the console output when we share a profile with URLs removed, because it will try to parse urls like http://<URL>:564:26.

Also ideally, we should start using pages array and ditch using the resource table.

Example profile:
Before / after

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.82%. Comparing base (61e5d10) to head (261969e).
⚠️ Report is 4 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5993   +/-   ##
=======================================
  Coverage   83.81%   83.82%           
=======================================
  Files         328      328           
  Lines       34255    34254    -1     
  Branches     9572     9574    +2     
=======================================
  Hits        28712    28712           
+ Misses       5115     5114    -1     
  Partials      428      428           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[fatadel]

I was thinking maybe we could just lower the level instead of complete removing these messages? For example, make it console.debug. Wdyt?

[canova]

I was thinking maybe we could just lower the level instead of complete removing these messages? For example, make it console.debug. Wdyt?

I think the question comes down to why we want to show this console message. Previously this code had the assumption that all urls have to be valid urls. So if a url was failed to parse, then we would want to know that it's failed because it ideally shouldn't happen in real life. But that assumption has changed since we added the sanitization step that anonymizes the urls. Now it's possible to have urls that won't be parsed. I think console.debug won't add anything more than the noise. If we want to really debug this code path, it's still easy to do it with the debugger or by adding logs locally.

[fatadel]

I was thinking maybe we could just lower the level instead of complete removing these messages? For example, make it console.debug. Wdyt?

I think the question comes down to why we want to show this console message. Previously this code had the assumption that all urls have to be valid urls. So if a url was failed to parse, then we would want to know that it's failed because it ideally shouldn't happen in real life. But that assumption has changed since we added the sanitization step that anonymizes the urls. Now it's possible to have urls that won't be parsed. I think console.debug won't add anything more than the noise. If we want to really debug this code path, it's still easy to do it with the debugger or by adding logs locally.

I believe debug logs are suppressed in browser by default, so no real noise :) But any way works for me 👍🏻

[canova]

I believe debug logs are suppressed in browser by default, so no real noise :) But any way works for me 👍🏻

Ah I see. At least when I open a fresh Firefox DevTools, I see all of the console logs active:

But that can be toggled off and maybe other browsers do it differently.