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
Browsers you attempted to reproduce this bug on (the more the merrier): chrome(maybe)
Does the problem persist after removing "assets/node_modules" and trying again? Yes/no: I don't know.
Actual behavior
We encountered the following backtrace twice in our production server. Unfortunately, I cannot reproduce the issue locally or in staging environments, so this report is based solely on the production logs.
The event that triggered this issue was intended to be sent to a live component but was instead handled by the parent live view.
Under normal circumstances, this event is sent correctly to the live component, and the functionality works as expected.
This anomaly happened only twice in production, with no identifiable pattern.
No additional context or logs were captured at the time, and I regret that further debugging information is unavailable.
Expected behavior
The event should consistently be sent to the intended live component, as it does under normal operation.
This is a simple bug report due to the lack of reproducibility and detailed debugging information. If you have suggestions for additional diagnostics or logging that could help identify the root cause, please let me know so I can implement them in production to capture more data if this happens again.
The text was updated successfully, but these errors were encountered:
Environment
Actual behavior
We encountered the following backtrace twice in our production server. Unfortunately, I cannot reproduce the issue locally or in staging environments, so this report is based solely on the production logs.
Backtrace:
lib/**/*_live.ex **Live.handle_event("...")
lib/phoenix_live_view/channel.ex:508 anonymous fn/3 in Phoenix.LiveView.Channel.view_handle_event/3
/app/deps/telemetry/src/telemetry.erl:324 :telemetry.span/3
lib/phoenix_live_view/channel.ex:260 Phoenix.LiveView.Channel.handle_info/2
gen_server.erl:2345 :gen_server.try_handle_info/3
gen_server.erl:2433 :gen_server.handle_msg/6
proc_lib.erl:329 :proc_lib.init_p_do_apply/3
Observations:
The event that triggered this issue was intended to be sent to a live component but was instead handled by the parent live view.
Under normal circumstances, this event is sent correctly to the live component, and the functionality works as expected.
This anomaly happened only twice in production, with no identifiable pattern.
No additional context or logs were captured at the time, and I regret that further debugging information is unavailable.
Expected behavior
The event should consistently be sent to the intended live component, as it does under normal operation.
This is a simple bug report due to the lack of reproducibility and detailed debugging information. If you have suggestions for additional diagnostics or logging that could help identify the root cause, please let me know so I can implement them in production to capture more data if this happens again.
The text was updated successfully, but these errors were encountered: