This repository was archived by the owner on Aug 28, 2025. It is now read-only.
Remove shebangs from notebooks #197
Closed
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
ethanwharris
requested review from
Borda,
carmocca,
kaushikb11 and
rohitgr7
as code owners
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #197 +/- ##
===================================
Coverage 75% 75%
===================================
Files 2 2
Lines 370 370
===================================
Hits 276 276
Misses 94 94 |
Borda
approved these changes
Sep 5, 2022
Contributor
|
Some timeout, probably make the training smaller? |
Contributor
|
let's update it with master, but strange that now it fails :/ |
Contributor
|
It was carried with some more fixes in #208 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
Before submitting
What does this PR do?
Attempting to fix hanging issue for publishing workflow
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃