Jussi Kukkonen
Jussi Kukkonen
calibration seems to succeed but keeping the device level and turning it around the z-axis still produces a point cloud that's not centered at origin... Possibly the axes aren't closely...
Apparently this may have been why dependabot silently failed if setup.py was missing: https://github.com/dependabot/dependabot-core/pull/5392 We can try removing setup.py again (but check the dependabot logs to see that it really...
There have been a few suggestions to document ngclient internals (or to publish that documentation): * RequestsFetcher * TrustedMetadataSet https://github.com/theupdateframework/python-tuf/issues/1543, https://github.com/theupdateframework/python-tuf/pull/1517#discussion_r694700337 I think we could talk a bit about RequestsFetcher...
We pin hatchling in pyproject.toml: `build-system.requires = ["hatchling==0.22.0"]`. I think this is the correct choice: otherwise the build is not really reproducible. It looks like Dependabot does not notice this...
_EDIT: The overall issue is described in detail in https://docs.google.com/document/d/1rWHAM2qCUtnjWD4lOrGWE2EIDLoA7eSy4-jB66Wgh0o . The suggestion here is roughly the **Metadata role (file) as search index** solution in the document._ Assume a setup...
This is what I believe makes sense: * "test" dependencies are mostly pinned to make sure we know which versions are being used and that the current version doesnt't surprisingly...
#1915 adds metadata generation (with stored expected results). We should expand the collection in two directions: * The current metadata is basically all with default values: Add More variation on...
The example client has two conflicting goals: * provide "production-like" error messages: don't dump a 300 line stack trace if the network is down * be a useful debugging tool...
Spec defines ecdsa public keys as PEM strings: python-tuf implements them as PEM strings (with the "BEGIN PUBLIC KEY" preamble). go-tuf implements ecdsa public keys as hex encoded bytes. Here...
(Documenting test improvement ideas from #1346) A lot (most?) of our tests require a test server (or several). This typically means moving metadata from sources to a temp directory, serving...