-
Notifications
You must be signed in to change notification settings - Fork 496
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Breaks build of cargo-c #1040
Comments
This fixes cargo-c...
|
groovybits
pushed a commit
to groovybits/rscap
that referenced
this issue
Apr 20, 2024
broken upstream cc crate requires a specific custom version I rigged up for now :/ rust-lang/cc-rs#1040
Yeah this is the same issue as #1039 , closed since it is duplicate |
groovybits
added a commit
to groovybits/rscap
that referenced
this issue
Apr 21, 2024
RsProbe Release 0.6.0 seems solid without backing up eating memory and running direct kafka output of the probe process. complete refactor and renaming (Crate name was taken for rscap). more efficient and simpler overall hopefully. design was re-engineered with the hind-sight of the experience of building up to this point. * remove mention of monitor * clean up documents, scripts and other aspects removed. * adjust scripts and remove warnings * remove unnecessary cfg arg * get more data through to kafka thread * merge kafka into probe * direct kafka from probe, simple less overhead. * adjustment of buffer sizes * make sure we have the PMT and stream_type number first. * use to_owned() on clone of stream_data * use rwlock for pidmap avoid mutex * systems stats single get in kafka thread * avoid system stats being called for every packet, only every second. * improve system stats so it contains more information and is always up to date. * get all the system processes running. * network stats should keep updating. * include network errors and processes over a threshold * cleanup readme * fix image link, add another * update docker * fix links and images in readme * remove unused scripts * update cargo.toml and name * rename crate to rsprobe * change names in code * update various aspects of naming * update rpm name to rsprobe * update schema in test_data for kafka, rename kafka_schema * update dockerfile for centos7 build * remove unneeded deps for git build * rename rscap directory to rsprobe * change directories to rsprobe * replace RsCap with RsProbe * remove unused fonts * drop the map * improve how gstreamer buffer reading and image encode is done * fix wget * update cargo-c with working version broken upstream cc crate requires a specific custom version I rigged up a temp solution for now :/ special cargo-c with cc reverted to .94 version till upstream fixed. rust-lang/cc-rs#1040 * install local cargo-c * allow git to work * add git fix to install script * fix git clone * fix system stats and base64 image * don't send image each time, reset it per stream. only include system stats on the base of the schema * update kafka schema * sleep less, increase send to kafka timeout * remove batch timeout * consolidate main loop into one thread * don't setup gstreamer if we are not extracting images * kafka tuning adjustments * configure producer for better performance. non blocking sending. * if not sending to kafka print stream data and clear batch` * overhaul for efficiency * refactored how works overall to use pid-map for stream stats. * avoid overloading kafka, keep stats and data without sending so many small packets. * remove SMPTE2110 from readme. support is farther off than originally planned. * send pid_map to kafka * update kafka json schema * fix pmt pid and program number get/set * move kafka schema * have network prefix the interface iteration * optimize kafka to send multiple threads, avoid kafka bottlenecks ---------
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I tracked this error down, suddenly my cargo-c build fails and it seems to be the cc crate dep for it being updated within the last few hours...
(This worked a few hours ago)
The text was updated successfully, but these errors were encountered: