Conversation
added 6 commits
January 25, 2022 16:30
Member
Author
|
@seisman, the vercel deployment fails on the Since you have more experience with the vercel setup, do you know of any reason to avoid venv and bootstrapping a user pip install for this case? |
Member
|
The raw error message is: Perhaps this solution (sloria/TextBlob#173 (comment)) works? |
added 2 commits
January 27, 2022 14:02
Member
Author
|
Thanks @seisman, the vercel docs are working now with dvc. |
Member
Author
|
I added |
PaulWessel
approved these changes
Jan 27, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of proposed changes
Originally we discussed only using dvc to track the test images, in part because there are fewer docs images and theoretically they change less often. However, there are already several outdated docs images with more likely due to remote dataset updates. This PR configures the docs and tests workflows to use dvc rather than git to manage the baseline images in doc/examples and doc/scripts to allow for these to be updated without bloating the git history.
One current limitation is that the CMake settings do not include the new
doc/examples/imagesanddoc/scripts/imagesdirectories in the release tarballs, meaning that people can not build the html docs from the tarballs. But, this relates to #2681 in that we also includedocs_releasein the release tarballs which contains optimized versions of those images. So do we need both? Or could we set a CMake target to generate the .PS files from the scripts as a compromise that would allow some users to build the html docs from source while shrinking the release tarball size for everyone?Part of #5724