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
visit the new page. and the warning message from instruments.js will go on and on until the page dead.
The reason I found is that, when rendering gets a warning, will call console.warn to console the error stack. But the stack includes a Proxy variable. When sentry do safeJoin with String(value), will visit the proxy variable, and visit the get handler, got undefined, so vue will call console.warn again. So the warning loop happends.
`checkStored` is my undeclared var
I tried to fix but I can not deal with how to test a var is Proxied. The way I test will trigger the get handler, so I just disable the console option of Breadcrumbs to solve the problem temporary.
Even though I should clean my code without undeclared var, I think it is still a bug.
Expected Result
do not loop warning
Actual Result
do loop waning.
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
How do you use Sentry?
Self-hosted/on-premise
Which package are you using?
@sentry/vue
SDK Version
7.12.1
Framework Version
Vue 3.2.23
Link to Sentry event
No response
Steps to Reproduce
The reason I found is that, when rendering gets a warning, will call
console.warn
to console the error stack. But the stack includes a Proxy variable. When sentry dosafeJoin
withString(value)
, will visit the proxy variable, and visit theget
handler, got undefined, so vue will callconsole.warn
again. So the warning loop happends.`checkStored` is my undeclared var
I tried to fix but I can not deal with how to test a var is Proxied. The way I test will trigger the
get
handler, so I just disable the console option of Breadcrumbs to solve the problem temporary.Even though I should clean my code without undeclared var, I think it is still a bug.
Expected Result
do not loop warning
Actual Result
do loop waning.
The text was updated successfully, but these errors were encountered: