Closed alexgleith closed 1 year ago
Note that with datacube==1.8.9
indexing works as expected.
Don't think they are related, @pindge ...
I started hitting this today too! I was converting a test in odc-tools (See https://github.com/opendatacube/odc-tools/pull/555) to access local data instead of over the network. It happens almost every time I try to run the test.
It looks a lot like a threading/connection issue in the new DB code. Either an incompatibility with how ODC connections have been used previously, or, just a bug.
Bothered by this too, it happened to me very randomly though, even locally. But I don't think it's related to datacube version, at least not only datacube version. Got one env built with datacube=1.8.11
, it's just fine. Haven't figured out what exactly the cause is.
Appears to be a transaction handling issue. Damien has done a great job tracking it down to a few lines of code in a single commit, and we can reproduce reasonably reliably now. I'm hoping to look at it this afternoon.
Expected behaviour
Actual behaviour
Steps to reproduce the behaviour
stac-to-dc --catalog-href=https://planetarycomputer.microsoft.com/api/stac/v1/ --collections=io-lulc-9-class --limit 50
Failures are intermittent. The first run it indexed 5 datasets and failed 45. The second it indexed 2, skipped 5 and failed 43!
Environment information
Full environment is this: https://gist.github.com/alexgleith/83813d30bc0798581e9c0b530f9f13bc