-
Notifications
You must be signed in to change notification settings - Fork 10
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
Ensure that errors due to env instantiation are printed #215
base: main
Are you sure you want to change the base?
Conversation
256e7e5
to
fa242b2
Compare
The errors now show up when run via
@felixcremer, @penelopeysm give this branch a try if you're able to and see whether it's showing up the errors correctly for you as well? |
1c35e3e
to
81b19d6
Compare
Works for me 😄 |
81b19d6
to
74643fc
Compare
Maybe we should put this behind an env variable flag because I've read once on Slack how people were annoyed not being able to run certain code when a dep wouldn't precompile that they didn't actually need. So there should maybe be an escape hatch to avoid that in case the user cannot fix the precompile failure. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #215 +/- ##
=======================================
Coverage 51.63% 51.63%
=======================================
Files 30 30
Lines 1286 1286
=======================================
Hits 664 664
Misses 622 622 ☔ View full report in Codecov by Sentry. |
Preferable we'd not need to add extra escape hatches for this. Perhaps there's a more straightforward approach to this check, maybe just checking if the manifest has the right |
I can also see the error message, but I don't like that it is drowned out by the whole stack trace and if I wouldn't know what to look for I might have missed the important part of the error. There is Base.collect_manifest_warnings() which gives the text of the warning that is shown when the manifest file was resolved with a different julia version and there is also |
Right, agreed that there's a lot there. Pretty sure this part is not able to be changed:
I'm sure the
The following needs to stay as far as I'm concerned, if the
|
Yes dropping the Malt part and maybe removing the stacktrace of the precompile error would make it much more digestible. |
Addresses #210 by making sure that the underlying error is printed out in
quarto
logs when it happens.