Closed royassas closed 1 month ago
I think this might have been a GitHub outage. Rebuilding the image works fine for me.
Just tried running it again. Still get
149.5 × Preparing metadata (pyproject.toml) did not run successfully.
149.5 │ exit code: 1
149.5 ╰─> [20 lines of output]
149.5 Updating crates.io index
149.5 error: Unable to update registry `crates-io`
149.5
149.5 Caused by:
149.5 failed to fetch `https://github.com/rust-lang/crates.io-index`
149.5
149.5 Caused by:
149.5 process didn't exit successfully: `git fetch --force --update-head-ok 'https://github.com/rust-lang/crates.io-index' '+HEAD:refs/remotes/origin/HEAD'` (exit status: 128)
149.5 --- stderr
149.5 error: RPC failed; curl 92 HTTP/2 stream 5 was not closed cleanly: CANCEL (err 8)
149.5 error: 2832 bytes of body are still expected
149.5 fetch-pack: unexpected disconnect while reading sideband packet
149.5 fatal: early EOF
149.5 fatal: fetch-pack: invalid index-pack output
149.5 💥 maturin failed
149.5 Caused by: Cargo metadata failed. Does your crate compile with `cargo build`?
149.5 Caused by: `cargo metadata` exited with an error:
149.5 Error running maturin: Command '['maturin', 'pep517', 'write-dist-info', '--metadata-directory', '/tmp/pip-modern-metadata-9f10_vfr', '--interpreter', '/usr/local/bin/python']' returned non-zero exit status 1.
149.5 Checking for Rust toolchain....
149.5 Running `maturin pep517 write-dist-info --metadata-directory /tmp/pip-modern-metadata-9f10_vfr --interpreter /usr/local/bin/python`
149.5 [end of output]
149.5
149.5 note: This error originates from a subprocess, and is likely not a problem with pip.
149.5 error: metadata-generation-failed
Think this could be related to #33742cd58d4d5705b841e0898c61bef3d597f9fd?
No, it seems to be caused by your network connection not being able to pull that Rust repository. If docker compose build --no-cache
doesn't work, try a different internet connection.
I couldn't build either, but it was a different error -- pyunifiprotect doesn't seem to exist anymore. I swapped everything over to uiprotect instead and it worked great (only 3 replacements in the project - no API breakage since uiprotect is a fork of the original project)
I pushed a change to replace the pyunifiprotect dependency.
I pushed a change to replace the pyunifiprotect dependency.
Traceback (most recent call last): File "/usr/local/bin/unifi-cam-proxy", line 5, in <module> from unifi.main import main File "/usr/local/lib/python3.11/site-packages/unifi/main.py", line 8, in <module> from pyunifiprotect import ProtectApiClient ModuleNotFoundError: No module named 'pyunifiprotect'
That should be fixed now.
That should be fixed now.
Thanks just build the thing again and it runs again
Camera
Tapo C100
Firmware version of the camera
No response
Description
Hey @zacharee
Thanks for your fork. I'm trying to use it for my tapo cam. I've adapted my docker compose file to build from your repo. Unfortunately the build can't complete with the following error
This runs on a Raspberry pi.
How to reproduce
use docker compose.yaml as listed in the docs
Expected behaviour
i expect the project to build
Screenshots
No response
Additional information
No response