dub-registry
dub-registry copied to clipboard
At least one package is not being updated (dscanner)
D-Scanner is somehow stuck, in the Dub registry, at version 0.5.2
even though it's been 3 days since 0.5.3
has been tagged on Github.
I don't know if other packages are affected however, because looking at the front page, it seems like at least some packages do get updated.
EDIT : I misunderstood how Github displays stuff (https://github.com/dlang-community/D-Scanner/issues/627#issuecomment-387481736), the tagging was done today. So I don't know if there is a real problem here, it has been 6 hours, which while being a lot less than 3 days, is still apparently more than the most recently updated packages. How long do the update take in most cases ?
Seems to be a general bug: https://github.com/atilaneves/unit-threaded/issues/117#event-1618051661
I assume the registry always crashes in the update process and never reaches dscanner. @s-ludwig is anything suspicious showing up the logs?
ddbc v0.3.8 is also effected by this. Other packages have managed to get updated within the last few hours though. Am I right in thinking that github repos are scanned every 30 mins?
Doesn't seem to be a crash AFAICS. BTW, can anyone confirm whether it updates when the update is triggered manually?
@SingingBush There is a 30 minutes pause between the update polls. I'm not sure how long each poll takes these days, but it used to be close to half an hour itself, so the total interval is supposedly around one hour.
Please confirm with manual update, see #291. It could have issues updating specific packages, maybe check the error list in the manage package section. If we don't find anything we'd need to check the server logs.
It looks like this is happening again, with dub this time: its registry page is stuck at v1.13.0-rc.1, even though v1.13.0 has been released a few days ago.
Also affected: bindbc-imgui (https://github.com/Inochi2D/bindbc-imgui/issues/19)