-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
BUG: Docs won't build (S3 bucket does not exist) #56592
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
Comments
A PR to change the example to a |
May I take? |
+1 to @srinivaspavan9 , I also could not reproduce from a fresh build in a docker container. System info attached. Documents built without any error, nor any warning about an S3 bucket. I got the same depreciation warnings as above, but I assume that is a different issue(?) System info attached. Python version is 3.10.8. Happy to continue work if there's a next step. |
@JackCollins91 In your system info, it shows python 3.9. Was the system info generated outside the container? |
And to confirm, you all are using a container built using this Dockerfile? https://github.com/pandas-dev/pandas/blob/main/Dockerfile |
Here's my stacktrace by the way...
|
Hi @johnstacy and @srinivaspavan9 Yes confirmed docker container is the same as you've used. Thanks for the stack trace, the issue is coming from However, I was able to build the docs without an issue and the code blocks seem to be running and working. Is it possible this is actually caused by some other kind of web connection error? or some issue with your particular machine to access s3? Perhaps try from a different machine if possible? @mroeschke If we cannot replicate the issue, is there still a desire to make a PR for either of the following?
OR
|
Yes there's still a desire to convert this to a |
I am seeing the error both from my machine at home as well as trying to build it in a CI pipeline...so I'm basically ruling out a connection issue. Also, on my machine, I pulled the aws cli container and was able to anonymously access the bucket with I'm curious if anybody has tried building a brand new image from the Dockerfile and using that or if you're using old images. |
Thanks for the thorough information @johnstacy . Thanks also for checking Multiple machines. I'm also puzzled about why we cannot recreate it. Although the suggested changes above should fix no matter what. I'll take the step of creating a completely fresh instance on a new machine and running exactly your provided docker container and see if this changes the result. Would also be interested to hear of anything from your investigation on no-sign-requests. |
For each S3 bucket code block, ideally we show what the output would be, but without making an actual call. Unfortunately, for several of the S3 buckets, there are issues with the code, which we must fix in another commit or PR. For now, the two S3 examples that do work, we edit to make the code block show what the output would have been if it had run successfully. Find details on issues in conversation on PR pandas-dev#56592
* Update io.rst Make consistent with other s3 bucket URL examples and avoid doc build error when problem with s3 url. * Update io.rst Make example consistent with other code block examples * Update v2.3.0.rst * immitating interactive mode For each S3 bucket code block, ideally we show what the output would be, but without making an actual call. Unfortunately, for several of the S3 buckets, there are issues with the code, which we must fix in another commit or PR. For now, the two S3 examples that do work, we edit to make the code block show what the output would have been if it had run successfully. Find details on issues in conversation on PR #56592 * Update io.rst Code still doesn't run, but at least unmatched } is no longer the issue. * Update v2.3.0.rst avoids unnecessary file change in PR * Update io.rst Rollback changes to one of the examples (out of scope) * Update io.rst * Update io.rst --------- Co-authored-by: JackCollins1991 <[email protected]>
…56762) * Update io.rst Make consistent with other s3 bucket URL examples and avoid doc build error when problem with s3 url. * Update io.rst Make example consistent with other code block examples * Update v2.3.0.rst * immitating interactive mode For each S3 bucket code block, ideally we show what the output would be, but without making an actual call. Unfortunately, for several of the S3 buckets, there are issues with the code, which we must fix in another commit or PR. For now, the two S3 examples that do work, we edit to make the code block show what the output would have been if it had run successfully. Find details on issues in conversation on PR pandas-dev#56592 * Update io.rst Code still doesn't run, but at least unmatched } is no longer the issue. * Update v2.3.0.rst avoids unnecessary file change in PR * Update io.rst Rollback changes to one of the examples (out of scope) * Update io.rst * Update io.rst --------- Co-authored-by: JackCollins1991 <[email protected]>
Pandas version checks
I have checked that this issue has not already been reported.
I have confirmed this bug exists on the latest version of pandas.
I have confirmed this bug exists on the main branch of pandas.
Reproducible Example
Issue Description
Built a Docker image using the provided Dockerfile. Inside the container, ran the attached commands to build the docs. It complains about not finding an S3 bucket (
s3://pmc-oa-opendata/oa_comm/xml/all/PMC1236943.xml
). I'm running with--num-jobs 1
because when I was running the build with parallel processing, it would fail but not tell me what the issue actually was.Expected Behavior
HTML docs build successfully.
Installed Versions
INSTALLED VERSIONS
commit : a671b5a
python : 3.10.8.final.0
python-bits : 64
OS : Linux
OS-release : 6.5.0-14-generic
Version : #14-Ubuntu SMP PREEMPT_DYNAMIC Tue Nov 14 15:13:47 UTC 2023
machine : x86_64
processor :
byteorder : little
LC_ALL : None
LANG : C.UTF-8
LOCALE : en_US.UTF-8
pandas : 2.1.4
numpy : 1.26.2
pytz : 2023.3.post1
dateutil : 2.8.2
setuptools : 63.2.0
pip : 23.3.2
Cython : 0.29.33
pytest : 7.4.3
hypothesis : 6.92.1
sphinx : 6.2.1
blosc : 1.11.1
feather : None
xlsxwriter : 3.1.9
lxml.etree : 4.9.4
html5lib : 1.1
pymysql : 1.4.6
psycopg2 : 2.9.9
jinja2 : 3.1.2
IPython : 8.18.1
pandas_datareader : None
bs4 : 4.12.2
bottleneck : 1.3.7
dataframe-api-compat: None
fastparquet : 2023.10.1
fsspec : 2023.12.2
gcsfs : 2023.12.2post1
matplotlib : 3.7.4
numba : 0.58.1
numexpr : 2.8.8
odfpy : None
openpyxl : 3.1.2
pandas_gbq : None
pyarrow : 14.0.2
pyreadstat : 1.2.6
pyxlsb : 1.0.10
s3fs : 2023.12.2
scipy : 1.11.4
sqlalchemy : 2.0.23
tables : 3.9.2
tabulate : 0.9.0
xarray : 2023.12.0
xlrd : 2.0.1
zstandard : 0.22.0
tzdata : 2023.3
qtpy : None
pyqt5 : None
The text was updated successfully, but these errors were encountered: