lp:~icecast/icecast/kh

Branch merges

This import branch has no branches proposed for merge into it.

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

877. By Karl Heyes <email address hidden> on 2020-01-28

Merge pull request #257 from trilliot/add-icy-metadata-cors

add Icy-MetaData to Access-Control-Allow-Headers

876. By Karl Heyes <email address hidden> on 2020-01-28

last cleanups for versioning/typos

875. By Karl Heyes <email address hidden> on 2020-01-28

push a kh13 release out

874. By Karl Heyes <email address hidden> on 2020-01-28

fix possible null deref from previous commit and optimise the no lag case when joining queue

873. By Karl Heyes <email address hidden> on 2020-01-28

allow for seconds to be specified in burst, queue and min queue settings

we still allow for the numbers as before but if you want to use seconds then specify like

<burst-size>5s</burst-size>

the awkward bit has been the calculation of bitrate assessment. As there is a variable element
to it (eg relays getting a burst) then the calculation is re-assessed every few seconds. This
should allow for the default to be specified in secs for any stream, eg 30 secs for queue and
may be 6 seconds for burst and that would apply to 32k or 128k streams.

872. By Karl Heyes <email address hidden> on 2020-01-14

memory leak and corruption fix

intro content from auth and small YP leak fixed. race condition leading to use after free
bug with listener connection getting closed when queue shrinkage occurs

other small internal cleanups

871. By Karl Heyes <email address hidden> on 2019-10-19

missing on-demand setting in master block.

This is just like an alias for the relays-on-demand setting. If the multiple master
facility gets done then it can be used specifically for that master.

870. By Karl Heyes <email address hidden> on 2019-10-18

fix race case, adjust locking area when listeners move or drop off.

In some cases, when moving to another worker or leaving a stream, there is a point where
a source is referred to but not locked as it should be. By changing the locking constraints
a lock/data is being maintained even if the source is to be freed up.

869. By Karl Heyes <email address hidden> on 2019-09-22

add some tolerance when pruning queue

normally it should not matter but there is a race case between source client pruning and
a listener detaching from queue when the lock is re-acquired for updating.

868. By Karl Heyes <email address hidden> on 2019-09-10

prevent incorrectly defined mime types from breaking relays

This is not usually a problem, but if one is define and it is not a recognised type then some
initialisation of relays can be missed out on retrying. Initially when relays a created they
are setup and work fine, but on retry, the structures and settings are not cleared out as type
checking for listeners is maintained but initialisation needs to be done for certain things
like metadata inserts.

This mismatch was tripping a bug here causing metadata alignment problems. Now we verify the
specified type before overriding.