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
We recently encountered a panic in go-runtime/compile/schema.go (fix) triggered by the PFI code, but we were not able to easily identify exactly what line in PFI caused the panic. Alec suggested "we should have a recover() in the code that tracks the current node being parsed so we can report where the panic occurs. Something like defer catch(node)"
The text was updated successfully, but these errors were encountered:
We recently encountered a
panic
in go-runtime/compile/schema.go (fix) triggered by the PFI code, but we were not able to easily identify exactly what line in PFI caused the panic. Alec suggested "we should have arecover()
in the code that tracks the current node being parsed so we can report where the panic occurs. Something like defer catch(node)"The text was updated successfully, but these errors were encountered: