Development resources at your finger tips
Build with the coolest Web3 projects
Recurring funding for Open Source
Ethical ads to power Open Source
Learn about Web3 & earn rewards
Show appreciation for each other
Meet fellow developers, designers, futurists and more. Collaborate and BUIDL awesome projects together.
Discover great web3 organizations, work on meaningful projects and build relationships with like minded people. Browse Tribes
Meet the top hunters and contributors from our community.
KERNEL is an 8-week, invite-only program for top tech talent looking to build relationships, products, and companies in blockchain and Web 3. 100 tal…
Heyo Gitcoiners! With an entire city of hackers, coders and blockchain innovators relocated on our platform, the atmosphere is just buzzing with crea…
Type in [[ 2- term.length]] more characters to get results
[[ result.title ]]
[[ result.description | truncate(70) ]]
No matches found
Gitcoin is GDPR complaint. Learn more in
Gitcoin's Terms & Conditions.
Check out the Issue Explorer
Looking to fund some work? You can submit a new Funded Issue here.
In case the segmenter terminates unexpectedly, we should attempt to re-create the segmenter If the source stream is still going.
We should preserve segment sequence numbers here. Note that the end of the source stream can be signaled by `rs.EOF` within `core.SegmentRTMPToHLS`.
Unit tests should be implemented to ensure this behavior is reliable, however the `core` package does not have any unit tests yet.
One approach that should be avoided is doing the retry within `segmenter.RTMPToHLS` since, despite the name, it is transport agnostic, and we don't want to box the API into one type of stream or another.
If you need help join our Discord chat and post your question in the #dev channel: https://discord.gg/7wRSUGX