Conversation
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
1 participant
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
This PR addresses issue #44 where users may encounter an
HTTPError: 504 Gateway Time-outwhen fetching the MNIST dataset viafetch_openml('mnist_784', as_frame=False)due to temporary OpenML server downtime or latency.Changes
03_classification.ipynb: Added a commented-out# extra codefallback snippet in cell 4 using pureurllib,numpy, andsklearn.utils.Bunch. Users running into OpenML timeouts can simply uncomment these lines to load the dataset without leaving the notebook.README.md: Added a corresponding entry under the FAQ section explaining the504 Gateway Time-outissue and documenting the fallback solution.Closes #44