-
Notifications
You must be signed in to change notification settings - Fork 37
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
docs: forward-ports from 3.x #256
Conversation
Need to rebase PR in order to re-run the CI. |
b0633d8
to
ac949f9
Compare
rebased and repushed. |
@dgarcia360 @annastuchlik Please review this PR. @tchaikov I'm not really sure I understand the reasoning for this PR. The cover letter doesn't really explain the intention. |
@avelanarius hi Piotr, the document on 4.x branch does not build without this changeset. that's why i ported the change to address the FTBFS. |
@annastuchlik @tchaikov @avelanarius It looks good to me. The issue is that, without these changes, the 4.x will not build locally. |
Ping reviewers |
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.
I successfully ran make preview
after checking out this branch, however I've seen that script had to downgrade a lot of dependencies. Maybe a rebase is needed.
Github workflows seem incorrect or unnecessary: do we do docs deploy from 4.x branch? Deploy.sh seems not to be there anyway.
Is this purely a port? CustomCommonMarkParser seems to be new, do we not need it in 3.x?
Branchest/Tags need an update: latest tag is 4.18.0.1
on: | ||
push: | ||
branches: | ||
- scylla-3.x |
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.
This feels wrong. Wouldn't that never fire?
.github/workflows/docs-pr.yaml
Outdated
on: | ||
pull_request: | ||
branches: | ||
- scylla-3.x |
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.
Similar as above. We should not have a workflow for PRs to 3.x on 4.x branch.
How do we maintain those two docs branches going forward? Is it possible to make it so we keep up to date setup on |
Before this change, the docs failed to build with the following error: ImportError: cannot import name 'environmentfilter' from 'jinja2' A fix to this problem is to explicitly pin Jinja2 version. (cherry picked from commit cdaf75a)
docs: update dynamic slug Add back index.md Move custom slug to a separate PR Fix typo (cherry picked from commit 8feeb20)
Add Java Driver 4.x branches to the list of generated documentation and bump the LATEST_VERSION variable. (cherry picked from commit 76f7715)
(cherry picked from commit d2e261b)
Fix javadoc redirect Fix (cherry picked from commit a9fcffb)
(cherry picked from commit 7399a0a)
The links in our documentation have a hardcoded version number in them: https://java-driver.docs.scylladb.com/scylla-3.11.2.x/api/ https://docs.datastax.com/en/drivers/java/3.11/com/datastax/driver/core/Cluster.html Therefore, a replacement rule is needed to replace the version to a correct version for a specific driver version we render the docs for. Before this change, only datastax links were replaced. After this change, java-driver.docs.scylladb.com links are also replaced. (cherry picked from commit 8cd4d8e)
(cherry picked from commit 511573f)
Add 4.14.1.x and 4.15.0.x releases to the list of versions to generate the docs for. (cherry picked from commit d296895)
docs: update conf.py docs: update conf.py docs: Update conf.py docs: update conf.py docs: Update conf.py docs: update conf.py (cherry picked from commit 0d1f1c4)
docs: test docs: add skip warnings option (cherry picked from commit 2601b78)
(cherry picked from commit 51ff0d5)
(cherry picked from commit 7ab2a8f)
sure. rebased.
i didn't manually edit the backport commits unless i had to to resolve the conflicts or to fix the document build. the purpose of this changeset is to enable us to build document on 3.x branch. i am not sure if we deploy docs from 4.x branch. guess this is a question to the maintainer of this project. considering this PR has been around for half a year, can we get this changeset reviewed and then work on the CI of document deployment if this is desirable?
yes, it is a backport. but again, this PR has been around for ages. and i haven't cherry-picked new changes from 4.x since i sent it for review. if something is odd. the reason is very likely that it's caused by merge conflict or missing commits from 4.x.
on the contrary, it is old. the change removing
could you be more specific? which files shall i update? |
ac949f9
to
9c7ef60
Compare
v2:
|
again, i think it's up to the maintainer of this project.
i don't think to "copy" the whole
|
9c7ef60
to
d96581f
Compare
Signed-off-by: Kefu Chai <[email protected]> (cherry picked from commit 6a5d3a7)
(cherry picked from commit 8dea9e2)
(cherry picked from commit 9eedcac)
this change is not cherry-picked from 4.x, as it is specific to scylla-3.x branch. Signed-off-by: Kefu Chai <[email protected]>
(cherry picked from commit efe5101)
de2c484
to
8d881b2
Compare
@Bouncheck hi Wojciech, could you please take another look? |
Visiting the
I was guessing that we'd need to just add '4.18.0.1' to
So after all let's not do that for now. |
to silence the warning from sphinx, as we have two "Dropwizard Metrics" sections in manual/core/metrics/index.md: ``` /home/kefu/dev/scylla-java-driver/docs/_source/manual/core/metrics/index.md:291: WARNING: duplicate label manual/core/metrics/index:dropwizard metrics, other instance in /home/kefu/dev/scyll a-java-driver/docs/_source/manual/core/metrics/index.md ``` and the warning breaks the "make test". so let's suppress the warning at this moment. Signed-off-by: Kefu Chai <[email protected]>
it should start with three backticks not four of them. otherwise sphinx warns like: ``` /home/kefu/dev/scylla-java-driver/docs/_source/manual/mapper/daos/getentity/index.md:111: WARNING: Lexing literal_block '@GetEntity\nProduct asProduct(Row row);\n\n@GetEntity\nProduct firstR owAsProduct(ResultSet resultSet);\n```\n\n' as "java" resulted in an error at token: '`'. Retrying in relaxed mode. ``` in this change, let's use three backticks. and the warning disappears. Signed-off-by: Kefu Chai <[email protected]>
8d881b2
to
a250fee
Compare
i commented out "multiversionpreview" to workaround a dependency issue on python 3.12, but forgot to revert it. the latest version dropped this workaround. so the multiversion should be back now.
we have the same error on 3.x branch.
i think this is due to the removed multiversion in previous reversion. and should be fixed.
yeah, all 4.x tags are broken at this moment. i think the first step is to fix the 4.x branch.
|
a250fee
to
3311fc8
Compare
v3:
|
@Bouncheck i see you are still asking for changes. may i learn what exactly the changes i need to make? |
I'm not getting redirected to javadoc when clicking on API Documentation on generated page ( |
@Bouncheck to my best knowledge, this is indeed intended. see java-driver/docs/source/conf.py Lines 174 to 179 in 9eedcac
we redirect the api doc to
i'd appreciate if you could help approve and merge this change. based on this change, we would be able to improve the 4.x document further. |
the document on 4.x branch does not build without this changeset. in order to build docs from 4.x branch, we have to have cdaf75a. but since we are here, let's forward-port all 3.x doc change to 4.x.
tested using