profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/fhriley/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

fhriley/bumpemu 1

A bump controller emulator on a Raspberry Pi Zero W for CellPro PowerLab 6 and 8 chargers. This allows you to use the CCS mobile app to control your charger over bluetooth (BLE).

fhriley/AdGuardHome 0

Network-wide ads & trackers blocking DNS server

fhriley/ads 0

CoreDNS plugin to block ads. Inspried by PiHole.

fhriley/annie 0

👾 Fast, simple and clean video downloader

fhriley/ansible-nomad 0

:watch: Ansible role for Nomad

fhriley/anti-paywall 0

A browser extension that maximizes the chances of bypassing paywalls

fhriley/BattIR-meter 0

This project design allows measuring the internal resistance of each cell in a LiPo, Life, or A123 battery pack.

fhriley/blocky 0

DNS proxy as ad-blocker for local network

fhriley/bypass-paywalls-chrome 0

Bypass Paywalls for Chrome

IssuesEvent

issue commentfhriley/kodi-headless-novnc

kodi log keeps giving error CActiveAESink::OpenSink - no sink was returned

@jackydec I actually found a fix for this. Please pull the image and recreate your container. Let me know if it fixes it for you.

jackydec

comment created time in 3 days

push eventfhriley/kodi-headless-novnc

Frank Riley

commit sha 1b49584dc0320e2e1e6c63dca0c4f048bed2d215

Fix AESink errors

view details

push time in 3 days

issue closedfhriley/kodi-headless-novnc

kodi log keeps giving error CActiveAESink::OpenSink - no sink was returned

Hi, been trying your kodi headless container. working out great so far.

I do notice that my kodi.log gets filled up with errormessages :

INFO <general>: CActiveAESink::OpenSink - initialize sink ERROR <general>: CActiveAESink::OpenSink - no sink was returned ERROR <general>: ActiveAE::InitSink - returned error

Can something be done to avoid these error messages?

Docker is running on a ubuntu server 20.4.3 LTS, which is running on Proxmox 7.0-11.

grtz,

Jacky

closed time in 3 days

jackydec

issue commentfhriley/kodi-headless-novnc

kodi log keeps giving error CActiveAESink::OpenSink - no sink was returned

Unfortunately, kodi does not have any settings to turn off trying to access sound hardware. The messages are harmless, and the only way to get rid of them would be to mount an alsa device into the container.

jackydec

comment created time in 3 days

create barnchfhriley/zfs-key-api

branch : master

created branch time in 11 days

created repositoryfhriley/zfs-key-api

created time in 11 days

issue closedfhriley/kodi-headless-novnc

any arm architecture support in future?

HI I used to use lsioarmhf but since they abandoned this after 19, I am looking for options and I see you ported it over which is great! any chance you can port this to raspberry pi 4 / arm architecture? TIA

closed time in 18 days

Rathna-K

issue commentfhriley/kodi-headless-novnc

any arm architecture support in future?

This isn't a port. It's using the standard kodi PPA for Ubuntu. Unfortunately, they don't provide an arm build in the PPA.

Rathna-K

comment created time in 18 days

issue commentSonarr/Sonarr

Xem season mapping incorrect

It stands to reason that this would apply to the allNames endpoint as well, which means the returned season numbers are the tvdb season numbers.

That is incorrect for at least Fairy Tail S2: #1140 942be36

How do we know the XEM mapping isn't at fault on this one?

I have a proxy set up so I can inject what I want into the xem responses. For example, 90 Day Pillow Talk is not currently on xem so I use the proxy to correctly return the mapping. I can provide this if you want to use it.

This isn't something we're going to support and XEM itself is possibly going to have issues with such a complex mapping.

I'm not asking you to support it. XEM has no problems with this show when you treat the returned season number properly. I can prove it using this proxy.

fhriley

comment created time in a month

issue openedSonarr/Sonarr

Xem season mapping incorrect

Is there an existing issue for this?

  • [X] I have searched the existing issues

Current Behavior

Currently, sonarr queries the xem allNames endpoint with origin=tvdb and uses the returned season numbers as the scene season number. I believe this to be incorrect. It should be setting the returned season numbers as the tvdb season number. There are a couple reasons why:

First, the documentation on the single endpoint says this:

the origin is the name of the site/entity the episode, season (and/or absolute) numbers are based on

It stands to reason that this would apply to the allNames endpoint as well, which means the returned season numbers are the tvdb season numbers.

Second, treating them as scene season numbers causes breakages. For example, 90 Day Fiance Pillow Talk. You can see that each season is based on a season of another 90 Day show. The scene treats each season individually. So, for example, seasons 8, 9, and 10 would map to the scene like this:

S08E01 -> 90 Day The Single Life Pillow Talk S01E01
S09E01 -> 90 Day Fiance Happily Ever After Pillow Talk S06E01
S10E01 -> Darcey and Stacey Pillow Talk S02E01

With the way Sonarr is doing it, the xem allNames mapping would have to be this:

{ "90 Day The Single Life Pillow Talk": 1 }
{ "90 Day Fiance Happily Ever After Pillow Talk": 6 }
{ "Darcey and Stacey Pillow Talk": 2 }

But let's say season 11 of Pillow Talk is 90 Day The Single Life Pillow Talk Season 2. The mapping would then be this:

S08E01 -> 90 Day The Single Life Pillow Talk S01E01
S09E01 -> 90 Day Fiance Happily Ever After Pillow Talk S06E01
S10E01 -> Darcey and Stacey Pillow Talk S02E01
S11E01 -> 90 Day The Single Life Pillow Talk S02E01

And the xem allNames mapping would have to this:

{ "90 Day The Single Life Pillow Talk": 1 }
{ "90 Day Fiance Happily Ever After Pillow Talk": 6 }
{ "Darcey and Stacey Pillow Talk": 2 }
{ "90 Day The Single Life Pillow Talk": 2 }

This is obviously incorrect because Sonarr has an ambiguous mapping for seasons 10 and 11. If Sonarr were treating xem mapping seasons as tvdb seasons, the xem mapping would be this:

{ "90 Day The Single Life Pillow Talk": 8 }
{ "90 Day Fiance Happily Ever After Pillow Talk": 9 }
{ "Darcey and Stacey Pillow Talk": 10 }
{ "90 Day The Single Life Pillow Talk": 11 }

And everything would map properly. I think Sonarr is currently getting lucky that the current way of doing it is working due to the seasons almost always matching between tvdb and the scene.

Expected Behavior

New seasons of Pillow Talk correctly map to the scene seasons.

Steps To Reproduce

No response

Environment

- OS: 
- Sonarr: 3.0.6.1265
- Docker Install: Yes
- Using Reverse Proxy:
- Browser:

What branch are you running?

Main

Anything else?

I have a proxy set up so I can inject what I want into the xem responses. For example, 90 Day Pillow Talk is not currently on xem so I use the proxy to correctly return the mapping. I can provide this if you want to use it.

created time in a month

push eventfhriley/kodi-headless-novnc

Frank Riley

commit sha 7510bf3f010e009add22e72f19456c6a52310442

Use forked version of easy-novnc

view details

push time in a month

fork fhriley/easy-novnc

Single-binary noVNC instance, web UI, and multi-host proxy.

fork in a month

push eventfhriley/kodi-headless-novnc

Frank Riley

commit sha 41a47cbf39c5662e220b7061b7fa188e1a0894e5

easy-novnc updates

view details

push time in a month

push eventfhriley/kodi-headless-novnc

Frank Riley

commit sha f4e3b852251ff4a20924eb3bd2ad5b58ef33ea33

Update README.md

view details

push time in a month

push eventfhriley/kodi-headless-novnc

Frank Riley

commit sha adbb7ee1d256fb1a0713ba845d1392986ae0ed2c

Update README.md

view details

push time in a month

delete branch fhriley/kodi-headless-novnc

delete branch : main

delete time in a month

push eventfhriley/kodi-headless-novnc

Frank Riley

commit sha f369285b00ce462f08ca7e1fc13e4a48bf57b4d3

Update README.md

view details

push time in a month

push eventfhriley/kodi-headless-novnc

Frank Riley

commit sha f0d1c156278b0ec2ba038aa3d0dcc074a6198391

initial commit

view details

Frank Riley

commit sha 0accd1c48f89fcdd42ecbb7b4d8f877b6b2a8b5f

changes

view details

Frank Riley

commit sha b03460c16f342734fbb73e88d3df849bbe7e861f

updates

view details

Frank Riley

commit sha fade199964ec0ec49c238a632edb07f2092743c2

Update README.md

view details

Frank Riley

commit sha a020b3c51b33faceca6944c3f2763d8da3f86dff

Update README.md

view details

Frank Riley

commit sha ea925656d6a96c02b215c28ec5e2daf384c48d1d

Update README.md

view details

Frank Riley

commit sha ba9a08950e47477276e92eee8cde8652d2bbaa16

Update README.md

view details

Frank Riley

commit sha 588e754b02733131fe4f49c048633f1dbe190f11

Update README.md

view details

Frank Riley

commit sha b034a90b83b1971efe2281b7cfe0f23e442ab719

update image name

view details

Frank Riley

commit sha cce6a265cd0f0725ab79c17748995bd0329da82b

update advanced settings

view details

Frank Riley

commit sha 436a37e776307420386b99a1dc33395476cd11ed

Update README.md

view details

Frank Riley

commit sha dcd15a9ab6169e2d1dd0b965f0c3dad55981936b

Remove sources.xml

view details

push time in a month

push eventfhriley/kodi-headless-novnc

Frank Riley

commit sha dcd15a9ab6169e2d1dd0b965f0c3dad55981936b

Remove sources.xml

view details

push time in a month

fork fhriley/LoopTrader

An extensible options trading bot built on top of Python.

fork in a month

push eventfhriley/kodi-headless-novnc

Frank Riley

commit sha 436a37e776307420386b99a1dc33395476cd11ed

Update README.md

view details

push time in 2 months

push eventfhriley/kodi-headless-novnc

Frank Riley

commit sha cce6a265cd0f0725ab79c17748995bd0329da82b

update advanced settings

view details

push time in 2 months

issue commentopenzfs/zfs

Cannot online device when autoexpand=on is set on the pool

@behlendorf I discovered today that this issue still exists:

root@nas:~# zpool online zfs /dev/disk/by-bay/bay8-part1
cannot online /dev/disk/by-bay/bay8-part1: cannot relabel '/dev/disk/by-bay/bay8-part1': unable to read disk capacity
root@nas:~# zpool set autoexpand=off zfs
root@nas:~# zpool online zfs /dev/disk/by-bay/bay8-part1
root@nas:~# zpool set autoexpand=on zfs
root@nas:~# zfs --version
zfs-2.0.4-0york2~20.04
zfs-kmod-2.0.4-0york2~20.04

It's been a few years since I created this pool, but I'm fairly certain the partitions on these disks were created by OpenZFS. This is what they look like:

root@nas:~# fdisk -l /dev/disk/by-bay/bay8
Disk /dev/disk/by-bay/bay8: 7.28 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: WDC WD80EMAZ-00W
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 36D3290F-8510-E048-98D0-D6C851CB1EDE

Device                        Start         End     Sectors  Size Type
/dev/disk/by-bay/bay8p1        2048 15628036095 15628034048  7.3T Solaris /usr & Apple ZFS
/dev/disk/by-bay/bay8p9 15628036096 15628052479       16384    8M Solaris reserved 1
fhriley

comment created time in 2 months

push eventfhriley/kodi-headless-novnc

Frank Riley

commit sha b034a90b83b1971efe2281b7cfe0f23e442ab719

update image name

view details

push time in 3 months

push eventfhriley/kodi-headless-vnc

Frank Riley

commit sha 588e754b02733131fe4f49c048633f1dbe190f11

Update README.md

view details

push time in 3 months

push eventfhriley/kodi-headless-vnc

Frank Riley

commit sha ba9a08950e47477276e92eee8cde8652d2bbaa16

Update README.md

view details

push time in 3 months

push eventfhriley/kodi-headless-vnc

Frank Riley

commit sha ea925656d6a96c02b215c28ec5e2daf384c48d1d

Update README.md

view details

push time in 3 months

push eventfhriley/kodi-headless-vnc

Frank Riley

commit sha a020b3c51b33faceca6944c3f2763d8da3f86dff

Update README.md

view details

push time in 3 months

push eventfhriley/kodi-headless-vnc

Frank Riley

commit sha fade199964ec0ec49c238a632edb07f2092743c2

Update README.md

view details

push time in 3 months