-
Notifications
You must be signed in to change notification settings - Fork 196
Comparing changes
Open a pull request
base repository: livepeer/go-livepeer
base: v0.7.8
head repository: livepeer/go-livepeer
compare: v0.7.9
- 8 commits
- 30 files changed
- 6 contributors
Commits on Sep 2, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 2e55134 - Browse repository at this point
Copy the full SHA 2e55134View commit details
Commits on Sep 5, 2024
-
build.yaml: Skip upload step raising an error for PR from forks (#3162)
We don't want our gcp buckets to get overfilled with builds from external devs.
Configuration menu - View commit details
-
Copy full SHA for 384b703 - Browse repository at this point
Copy the full SHA 384b703View commit details -
Configuration menu - View commit details
-
Copy full SHA for 48a92a1 - Browse repository at this point
Copy the full SHA 48a92a1View commit details
Commits on Sep 9, 2024
-
broadcaster: Fix media compatibility check (#3164)
Not all fields will be identical segment-to-segment, particularly DurationSecs. This caused unnecessary transcoder re-initialization.
Configuration menu - View commit details
-
Copy full SHA for a99a631 - Browse repository at this point
Copy the full SHA a99a631View commit details -
Add node version and orch addr to transcoded metadata (#3165)
* Update LPMS to latest. * protoc: Regenerate
Configuration menu - View commit details
-
Copy full SHA for eec6ed3 - Browse repository at this point
Copy the full SHA eec6ed3View commit details
Commits on Sep 10, 2024
-
Clean up inactive sessions (#3166)
* Clean up inactive sessions Not cleaning up the sessions causes quite a big memory leak which in effect causes OOMKilled * Clean up inactive sessions Not cleaning up the sessions causes quite a big memory leak which in effect causes OOMKilled
Configuration menu - View commit details
-
Copy full SHA for 45652c4 - Browse repository at this point
Copy the full SHA 45652c4View commit details -
selection: Clear known sessions if none of them has good enough laten…
…cy score (#3086) Problem: We never cleaned the known sessions, even if all of them had too low latency score to use; example of what sometimes happens: 1) Broadcaster accumulated 8 known sessions, but all had too low latency score 2) Session refresh was not triggered because we had a lot of knows session in the pool 3) At the same time, we didn't have sessions in unknown session pool 4) Selection checked that it cannot use the known session and tried to select from unknown sessions (but the pool was empty or there were no sessions fulfilling the condition of max price or perf score) Co-authored-by: Thom Shutt <thomshutt@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 834a9c6 - Browse repository at this point
Copy the full SHA 834a9c6View commit details -
Configuration menu - View commit details
-
Copy full SHA for 56a8a88 - Browse repository at this point
Copy the full SHA 56a8a88View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v0.7.8...v0.7.9