The netkan bot won't pick up multple releases if they are released too close to each other about netkan

[AlexanderDzhoganov]

This should be in CKAN-netkan, could you move it?

[hakan42]

This issue was moved to KSP-CKAN/CKAN-netkan#23

[pjf]

and unmoved. :)

[Dazpoet]

I think this is acctually for NetKAN-bot rather than this directory, notifying @techman83 who is either interested enough to open a duplicate over there or close this :)

[techman83]

I'm hoping KSP-CKAN/NetKAN-bot#2 will help this. Currently NetKAN grabs the latest release and pushes it into CKAN-meta and that only happens every 3 hours currently (due to cpu utilisation).

How common is this situation? What are we missing by missing a release if a new one was released soon after (presumably it would most commonly done to fix a futzed release?).

[Dazpoet]

Not sure how big of a problem this really is acctually, I can't say I've ever ran into a problem because of this.

For the completionist in all of us it would be nice to have an as complete repository as possible though which should include all versions, no matter how insignificant.

[plague006]

@techman83 if this can't be (reasonably) fixed, can we close the issue?

[techman83]

@plague006 generally if releases are really close together it probably means a bug and we'll likely miss the buggy one. So it's probably pretty edge case.

There is room in the code for more frequent indexing and we'll get there eventually. So I think yes 👍