-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
GH-39759: [Docs] Update pydata-sphinx-theme to 0.15.x #39879
GH-39759: [Docs] Update pydata-sphinx-theme to 0.15.x #39879
Conversation
Thanks for opening a pull request! If this is not a minor PR. Could you open an issue for this pull request on GitHub? https://github.com/apache/arrow/issues/new/choose Opening GitHub issues ahead of time contributes to the Openness of the Apache Arrow project. Then could you also rename the pull request title in the following format?
or
In the case of PARQUET issues on JIRA the title also supports:
See also: |
@github-actions crossbow submit preview-docs |
|
This is not a MINOR change: https://github.com/apache/arrow/blob/main/CONTRIBUTING.md#Minor-Fixes Could you use |
I think that we need to do like #39658 . |
|
Could you also fill items in our PR template? |
Got it |
Revision: 9a5314f Submitted crossbow builds: ursacomputing/crossbow @ actions-c32f679e0f
|
|
2 similar comments
|
|
@github-actions crossbow submit preview-docs |
docs/requirements.txt
Outdated
@@ -5,7 +5,7 @@ | |||
breathe | |||
ipython | |||
numpydoc | |||
pydata-sphinx-theme~=0.14 | |||
pydata-sphinx-theme~=0.15.2 |
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.
@jorisvandenbossche @AlenkaF Do we need .2
with ~=
?
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.
AFAIK if ~=
is added then pip will install the latest 0.15.x
version that is higher or equal to 0.15.2.
So I think this is fine.
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.
Then why are the checks failing?
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 do not think they are connected.
We can still try and change to ==0.15.*
to see if it makes a difference.
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.
Or remove the .2
as Kou suggested 😊
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.
It seems that you have too much indent for line 1201-1208.
Anyway, we should do it ( #39879 (comment) ) in a separated PR as @AlenkaF suggested ( #39879 (comment) ).
Could you open an issue for it to work on it as a separated task?
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.
If you want @kou I can work on the indentation in this pr ?
BTW I think these are the errors coming in the docker-compose.yml
file so if I am supposed to open a separate issue should I work on only this part where I made the code changes
1204:13 error wrong indentation: expected 8 but found 12 (indentation)
1206:13 error wrong indentation: expected 8 but found 12 (indentation)
or on all the errors?
Divyansh@LAPTOP-8JH824JM MINGW64 ~/Documents/GitHub/arrow (Update-pydata-sphinx-theme-to-0.15.x)
$ yamllint docker-compose.yml
docker-compose.yml
1:61 error wrong new line character: expected \n (new-lines)
56:1 warning missing document start "---" (document-start)
116:5 error wrong indentation: expected 6 but found 4 (indentation)
117:7 error wrong indentation: expected 8 but found 6 (indentation)
120:9 error wrong indentation: expected 10 but found 8 (indentation)
121:11 error wrong indentation: expected 12 but found 10 (indentation)
132:5 error wrong indentation: expected 6 but found 4 (indentation)
133:7 error wrong indentation: expected 8 but found 6 (indentation)
136:5 error wrong indentation: expected 6 but found 4 (indentation)
140:5 error wrong indentation: expected 6 but found 4 (indentation)
144:5 error wrong indentation: expected 6 but found 4 (indentation)
146:7 error wrong indentation: expected 8 but found 6 (indentation)
149:7 error wrong indentation: expected 8 but found 6 (indentation)
156:5 error wrong indentation: expected 6 but found 4 (indentation)
171:5 error wrong indentation: expected 6 but found 4 (indentation)
328:81 error line too long (87 > 80 characters) (line-length)
697:81 error line too long (81 > 80 characters) (line-length)
1102:81 error line too long (110 > 80 characters) (line-length)
1113:81 error line too long (111 > 80 characters) (line-length)
1122:81 error line too long (100 > 80 characters) (line-length)
1139:81 error line too long (82 > 80 characters) (line-length)
1153:81 error line too long (89 > 80 characters) (line-length)
1204:13 error wrong indentation: expected 8 but found 12 (indentation)
1206:13 error wrong indentation: expected 8 but found 12 (indentation)
1354:8 error too many spaces inside brackets (brackets)
1356:81 error line too long (93 > 80 characters) (line-length)
1358:77 error too many spaces inside brackets (brackets)
1439:81 error line too long (81 > 80 characters) (line-length)
1460:81 error line too long (96 > 80 characters) (line-length)
1515:81 error line too long (96 > 80 characters) (line-length)
1541:81 error line too long (108 > 80 characters) (line-length)
1542:81 error line too long (119 > 80 characters) (line-length)
1912:81 error line too long (90 > 80 characters) (line-length)
1914:81 error line too long (93 > 80 characters) (line-length)
1934:81 error line too long (88 > 80 characters) (line-length)
1939:81 error line too long (85 > 80 characters) (line-length)
1962:81 error line too long (88 > 80 characters) (line-length)
1967:81 error line too long (82 > 80 characters) (line-length)
1991:81 error line too long (88 > 80 characters) (line-length)
(myenv)
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.
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.
Please don't do it in this PR. If you want to work on it, please open a new PR for it. It's not related to this PR.
BTW, here is an yamllint
output on my environment:
$ yamllint docker-compose.yml
docker-compose.yml
1:1 warning missing document start "---" (document-start)
It seems that you broke docker-compose.yml
on your environment.
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.
So is this PR good to merge?Also is there a way to fix my docker-compose.yml
I tried recloning the whole project but still the same errors are coming
Revision: 6587af4 Submitted crossbow builds: ursacomputing/crossbow @ actions-85368391e7
|
@github-actions crossbow submit preview-docs |
Revision: 9f0c727 Submitted crossbow builds: ursacomputing/crossbow @ actions-ea146315be
|
@github-actions crossbow submit preview-docs |
Revision: 1020946 Submitted crossbow builds: ursacomputing/crossbow @ actions-37f7ce3b94
|
Some quick notes from looking at the preview:
|
@kou Are there any more changes needed in this pr? |
Could you check #39879 (comment) ? |
Could you please tell how do I proceed to solve the issues mentioned in #39879 (comment) @kou |
Sure:
|
@Divyansh200102 would you have time to rebase this PR? In the meantime pydata-sphinx-theme 0.15.3 was released, so it would be good to test it with the latest version |
I am a bit busy for a couple days but I 'll do it as soon as I find the
time to do so.
…On Thu, 6 Jun 2024 at 21:51, Joris Van den Bossche ***@***.***> wrote:
@Divyansh200102 <https://github.com/Divyansh200102> would you have time
to rebase this PR? In the meantime pydata-sphinx-theme 0.15.3 was released,
so it would be good to test it with the latest version
—
Reply to this email directly, view it on GitHub
<#39879 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/BDA2PCIHG3ZS4PJOCT5MJJTZGCEABAVCNFSM6AAAAABCU2D5RGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJSHEZDINZWHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
This reverts commit ba40ce0.
Rationale for this change
What changes are included in this PR?
Updated pydata-sphinx-theme to 0.15.x
Are these changes tested?
Yes
Are there any user-facing changes?
No