-
Notifications
You must be signed in to change notification settings - Fork 68
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
ottr::export fails when pdf can’t be generated #766
Comments
Upon further investigation, it's possible at least some of this might be tied to generic Berkeley datahub issues. https://ds-modules.slack.com/archives/C3ESHBX2N/p1705901646319269 |
Thanks. With the Datahub issues resolved, looks like the issue persists with force save set to TRUE but the function works without either the force save or PDF flags. |
Sorry, I'm confused now. Can you send a screenshot of running with both pdf and force_save set to true now that the hub issues are resolved? |
What you're seeing in For |
@dbroockman, any update on this? |
|
Looks like the hub has some incompatible package versions; I'm guessing it's an outdated version of From this it looks like notebook v7 (which is what the hub is using) isn't compatible with notebook extensions? I'm not 100% sure. |
Thank you, bug opened here: datahub-project/datahub#9732 |
I think that's the wrong repo. Berkeley datahub (afaik) is run from https://github.com/berkeley-dsep-infra/datahub |
Thanks for the flag. |
yep, this is 100% the case: notebook v7 isn't compatible with notebook v6 extensions. |
I've opened ucbds-infra/ottr#21 to continue exporting the submission zip if a PDF can't be generated, which should be the only change required on otter's end for this issue. It will be included in v1.5.0 of ottr, which will come out once I've fixed #767 as well. |
look into both why the pdf can’t be generated and why the zip export fails
Thanks @… here it is https://github.com/dbroockman/PS3-SP24-Public/blob/main/w2/w2a1/student/Week2_Activity1.ipynb
Slack Message
The text was updated successfully, but these errors were encountered: