rootwyrm / talecaster Goto Github PK

TaleCaster currently will attempt to run below minimum memory (16GB) and even below ZFS floor (4GB) due to a lack of checking at IPL stages. This is a major deficiency. Scripts will need to be developed to integrate early on in the RC process to make the call and refuse to start accordingly.

Master issue for OpenVPN enhancement. This feature is intended for users in countries where ISPs engage in harmful blocking, arbitrary censorship, and any forms of interference which violate human rights including deep packet inspection and traffic sniffing.

Title explains it all. The poudriere(8) components are required to maintain compliance with copyrights and licenses which prohibit the project from redistributing compiled code with or without source.

Need to automatically set the appbase directory in the Docker mode to reduce some headaches.

Native CLR Servarr apps will sometimes exhibit long stalls on initial page load where signalR is not loading in a timely fashion. This appears to be related to CLR GC behavior. Will continue to monitor on test and production environments. If this persists, may need to revisit the CLR allocation and GC behavior with the .NET teams since this was already fixed prior to 5.0.

tc_transmission logging is just... impossibly bad. It's all going to stdout and extremely noisy. This needs to be fixed. Not tagging for R1V1 because there's probably some upstream involved.

This one has been on the backburner for a while since I have clamav scanning on the NAS side. Not everyone will be using a NAS with scanning capabilities, nor is that an intended requirement. This does require a corresponding pre-processing script.

The overall design of TaleCaster is intended to provide a centralized store for multiple users. A single system that offers each user a unique database and their own secure isolated database of interests.

This is ostensibly possible thanks to PostgreSQL 10 and it's PUB/SUB replication. This will also allow parental control of media.

Much, much more complex than you would think though. Need intermediating interfaces for things like Amazon Prime, Netflix, etc.

Sub-module components should be tracked from the tc_docker container (which is the true master) and should not have their own versions.

http://www.lian-li.com/pc-q34/?preview=true

http://www.lian-li.com/en/dt-portfolio/pc-10n/

http://www.chenbro.com/en-US/products/RackmountChassis/3U_Chassis/RM31616

http://www.chenbro.com/en-US/products/RackmountChassis/4U_Chassis/RM417

https://pcpartpicker.com/product/2FjG3C/silverstone-case-sstgd08b

??? Custom Component ???

k5start fails to fully initialize the krb5 user from AD during startup, causing later startups (nzbget, transmission, sickrage, etc) to not have the required media user to operate as. Need to implement a prefacing rc.d that will check/verify/fire dedicated keytabs. Also need to improve keytab management for the non-jailed variant to resolve multi-user access.

At this point, arm64 builds may be able to be turned on for linux/arm64. RPi4 8GB should be able to handle TaleCaster duties assuming NAS, but will need the config stored on something besides eMMC or SD. If stored on these, the configuration stores will brick the module in a matter of weeks at the longest.
Linux/arm64 restrictions will be documented in the Wiki for now.

The Transmission proxy does not work in Chromium browsers and instead returns a 409 on session-id. This appears to be a browser issue, but may be a proxy caching issue.

Primarily to link to mono/mono#7167

Symptom is very very long hangs in FUTEX_WAIT attempting to build. This fails in Docker Cloud due to timeout. Builds run 8+ hours even on my workstation using alpine 3.8.

./configure --prefix=$MONO_PREFIX --sysconfdir=$SYSCONF --mandir=$MANDIR --infodir=$INFODIR --localstatedir=/var --enable-ninja --enable-system-aot --disable-boehm --without-x --with-mcs-docs=no --enable-small-config

This is a tracking ticket for Synology issues.

• /sys is not available on Synology, but is required by openrc, creating cgroups problems that can hurt CLR badly
• mono dependent applications (aka still just freaking Sonarr) will cause problems with the Synology itself due to GC behavior (trigger at 90%)
• Needs documentation in general, since the setup is slightly less straightforward

Present since December 27, 2017. Clearly a Docker Hub problem. Does not reproduce for local compose or local build. ENV is being ignored by Hub for unknown reasons. Build errors in RUN but Docker Hub is no longer respecting ERROR conditions and pushing broken images anyways.

�[91mERROR: unsatisfiable constraints: �[0m pkg_common (missing): required by: world[pkg_common] �[91mln: /etc/service/: No such file or directory

The GH action is too inflexible and just isn't working right at all. It's choking on comments.

Switch to https://github.com/hadolint/hadolint instead

Too many of the scripts have been written in an ad-hoc fashion. Normalize variable writing, standardizing naming. A style(9)-alike document stating conventions should also be created (since these are required for plugins on both FreeBSD and Linux.)

Sonarr contains RestSharp vulnerable to CVE-2021-27293. Severity is indeterminate; vulnerability can be triggered by malformed requests or malformed responses.

Sonarr/Sonarr#4793

With the release of 3.7, edge use is no longer required for any containers (including tc_mono) and should be discontinued.

tc_docker -> FROM: alpine:3.7
tc_* -> FROM: tc_docker
All actions which do or may modify /etc/apk/repositories need to be removed. There should not be any exceptions left at this point.

Public tracking bug only - NDA materials involved
Internal: TC18Q1AP04

Public Summary: USB tuner #2 attached to USB3 in XHCI will sometimes be dropped due to power management or missed poll. When the device reattaches, (redacted) driver will intermittently fail to detect loss of bootstrap.

Copyright notices are currently inconsistent, and there are many dangling files. Need to go through and clean all of these up. Will need to create a new 'cleanup' branch for that.

All use of /etc/rc.conf except for hostname, network, and selected base system functions is to be replaced by use of /etc/rc.conf.d/ in order to reduce code complexity.

Internal Issue: TC18Q1FB103

All links in this repository need to be updated to point to the master branch on the child projects. They currently map to the commit at the time the link was made.

This is critical path for R1V1U0 as otherwise, chain-upgrades do not trigger.

This is to add deluge/deluge-web as a possible provider for torrents.

Initial work is already done, but running into obnoxiousness with python.

Build hooks are not currently working and I forgot how I got them working. Need to fix them.

I would like to get tc_mono down to a more reasonable (read: less than 183MB!) size before R1V1U0.

Lidarr does not currently provide any mechanism by which to import an SSL certificate, making SSL essentially non-functional. This violates the SSL-only policy for sub-services.

This is due to a Docker bug. Symptom:

[root@airwolf talecaster]# docker exec -it torrent /bin/bash
OCI runtime exec failed: exec failed: container_linux.go:370: starting container process caused: read init-p: connection reset by peer: unknown

Upstream is: moby/moby#40399

The TaleCaster user will be changed from media to talecaster in order to more clearly reflect the product and resolve potential conflicts with a number of distributions that may want to use this for other things.

The tc_docker container is no longer in a building state and is using a version of Mono which is vulnerable to multiple exploits.

Update Mono to 5.8.0.108 and perform major revisions to fix build.

There is no effective reporting of the time spent in various phases of build and run. Enhance the Dockerfile and build scripts to print the time spent in various phases outside of DEBUG; especially ones that are deliberately silenced.