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

Introspection runs into endless exception reporting #79

Open
haraldsteinlechner opened this issue Aug 24, 2022 · 2 comments
Open

Introspection runs into endless exception reporting #79

haraldsteinlechner opened this issue Aug 24, 2022 · 2 comments

Comments

@haraldsteinlechner
Copy link
Member

haraldsteinlechner commented Aug 24, 2022

in, pro3d, not all packages are up to date and i missed quite some development there, introspection runs into an endless exception reporting loop. Is this something somebody stumbled across already? it looks like this:
image

this might go forever... (could not wait for infinity yet to know ;))

@haraldsteinlechner
Copy link
Member Author

haraldsteinlechner commented Aug 24, 2022

nope, not goes forever but for several minutes. it seems to happen within custom pickler registration.
image
pro3d-space/PRo3D#228

PRo3D, autodeploy branch can be used to reproduce the problem.

EDIT: also i just found out that for this specific run i got complete crash within aardvark.init (which should not happen at all)
image

@haraldsteinlechner
Copy link
Member Author

haraldsteinlechner commented Aug 24, 2022

so in the end, adaptify seems to silently require f# 6.0 at runtime, and our introspection code is not robust to problems like this by printing thousands of errors till it finally crashes. I think proper exception handling could be integrated easily. finding out where all those prints come from is bonus.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant