-
Notifications
You must be signed in to change notification settings - Fork 101
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
Re-enable numerical asserts since CI now uses Quarto 1.6 #539
Conversation
Actually the upstream issue is not fully fixed; there is a new version of QuartoNotebookRunner.jl with the fix (0.11.5) but Quarto itself needs to be updated https://github.com/quarto-dev/quarto-cli/blob/cf81582a26c4e43501f21ae5dec4d8be90acd4e3/src/resources/julia/Project.toml Blocked by upstream I guess. |
PRs submitted to Quarto. quarto-dev/quarto-cli#11100 and quarto-dev/quarto-cli#11101 Once that is merged and a new version released we just need to make sure that CI loads a new enough version of Quarto. |
Upstream has been merged, just waiting for a release |
1a60d9b
to
9ce75a1
Compare
9ce75a1
to
3b78169
Compare
Preview the changes: https://turinglang.org/docs/pr-previews/539 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good stuff
* Uncomment asserts * Bump Quarto version in CI * Mention Quarto min version in README
The docs contain some assertions to make sure that e.g. posterior predictions are numerically accurate. Due to #533 these assertions were sometimes randomly failing, and I had to comment them out to avoid spurious CI failures.
Since the upstream issue has been fixed, and a new version of Quarto that contains this bugfix released, this PR re-enables the assertions.
Closes #533.