-
Notifications
You must be signed in to change notification settings - Fork 37
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
analyze.py error: "max() arg is an empty sequence" #15
Comments
Should have really waited for your feedback before making that release haha. Will look into that soon, probably not today anymore (the bug is already obvious to me and the fix is quick -- it's just difficult to test these edge cases in advance, so your report is hugely valuable again))! |
Would appreciate that if that's OK for you! I'll still have to see if I'm courageous enough to actually run that in your repo, but for the testing work of course it saves you and me both some time! |
Fix for scenario where all views/clones fragments are empty (#15)
Landed #16 which should address the problem shown. |
Btw @olets if you like to, you can remove empty CSV files from your data repository by just pushing a corresponding commit manually. In your case this is What I like here is the concept of being able to manually fix/change/tweak the state of data via a simple git workflow, leaving transparent history of changes. It think that's a conceptual strength of this solution (compared to e.g. having to 'fix' the state of an object in S3 or in a database). Sorry for the annoyances -- young software, limited testing and all. |
It works! 🙌
I'll set it up if there's a problem again 👍 That data repo's project is deprecated. Now that we don't need it for debuggin, I'm going to freeze the repo anyway!
Not annoying at all! |
Thank you for the feedback @olets as always!! |
The recent updates resolved the errors I was getting in two repos!
It unearthed a new error in one repo. Until yesterday I was getting this error:
Now instead I get
I don't use Python much so I haven't looked for the bug :)
I can make you a repo collaborator if that's helpful — I think that would let you run the action on the repo?
The text was updated successfully, but these errors were encountered: