crates

A deny.toml without an [advisories] section will still check the RustSec when running cargo deny check advisories. This is great and the correct behaviour imo, but it would be good to document the default value for all configuration option and afaict it is not.

Thanks! :)

Is your feature request related to a problem? Please describe.

The webapp example could definitely be improved.

Describe the solution you'd like

• Add token refreshing
• Use the new API properly (at some point we do spotify.token = ..., we can surely avoid that).
• Proper error handling? It has too many unwrap in my opinion.
• Add string interpolation where possible

Currently, cv-pinhole has the essential matrix and various methods designed to help people extract pose from it, among other things. The same thing needs to be done for the homography matrix.

This is a tracking issue for additional Store implementations.

Here is a non-exhaustive list of potential candidates for an Store implementation:

• S3Storage:
  This would store crate tarballs and rendered README pages into Amazon's S3.
• RemoteStorage:
  Requires to implement a companion server.
  The idea is to have a reserved folder on another machine which runs a comp

I am looking at using ktra as an internal registry at work, and while I don't think I will loose my password, there is the possibility for others to do so. It would be nice to have a way to delete user accounts or forcibly set an account's password to allow for recovery.

This should work:

cat test.txt | unic-inspector