Divyansh200102 commented on code in PR #39879:
URL: https://github.com/apache/arrow/pull/39879#discussion_r1489024551


##########
docs/requirements.txt:
##########
@@ -5,7 +5,7 @@
 breathe
 ipython
 numpydoc
-pydata-sphinx-theme~=0.14
+pydata-sphinx-theme~=0.15.2

Review Comment:
   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
   ```powershell
     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?
   ```powershell
   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) 
   
   ``` 



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to