Use oldest file when race condition causes multiple files per item

[jwodder]

Fixes #264.

[codecov]

Codecov Report

Merging #265 into master will decrease coverage by 0.01%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #265      +/-   ##
==========================================
- Coverage   81.04%   81.02%   -0.02%     
==========================================
  Files          52       52              
  Lines        4362     4363       +1     
==========================================
  Hits         3535     3535              
- Misses        827      828       +1     

Flag	Coverage Δ
unittests	81.02% <0.00%> (-0.02%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
dandi/girder.py	82.10% <0.00%> (-0.24%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f424a31...3e93250. Read the comment docs.

[yarikoptic]

Looks good and didn't break any test, so good to go - merge whenever we are ready to "auto-release". I meanwhile will try it on drogon

[jwodder]

@yarikoptic Oops — I merged this, but forgot that #257 wasn't merged yet (It is now). Is there another quick PR we could merge to try out a release?

[yarikoptic]

nothing comes to mind... I guess there should be some provisioning for that with this setup to just trigger a release from current master? if not -- just make some nonimportant PR (some tune up to formatting of CHANGELOG or README or whatnot)

[jwodder]

@yarikoptic PR made and release triggered successfully!

[yarikoptic]

whoohoo -- I see 0.7.1 on https://pypi.org/project/dandi/ !

[yarikoptic]

and a nice CHANGELOG! awesome.
I wonder -- could we make sure that no PR is unlabeled "properly"? or is that already done?

[jwodder]

@yarikoptic PRs without labels default to the "Bug Fix" category, though I believe it can be changed to a different category. Is that what you're asking?

[yarikoptic]

I thought: would be nice if bot reported "failed" state (so people do not merge) for the PR until some needed label(s) were added (something like WIP bot does if there is a label WIP present)

[jwodder]

@yarikoptic It doesn't do that. Searching a bit, the only thing I can find that does do that is dimagi/required-labels, which we would have to host somewhere ourselves.

[yarikoptic]

ok, let's just look after each other to not forget proper labeling