Skip to content

Conversation

@boks1971
Copy link
Contributor

NOTE: Need a frostbyte73/core PR to merge and tag a release
PR pending: frostbyte73/core#5

NOTE: Need a frostbyte73/core PR to merge and tag a release
PR pending: frostbyte73/core#5
@changeset-bot
Copy link

changeset-bot bot commented Feb 12, 2025

⚠️ No Changeset found

Latest commit: e867a9a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

💥 An error occurred when fetching the changed packages and changesets in this PR
Some errors occurred when validating the changesets config:
The package or glob expression "github.com/livekit/protocol" specified in the `fixed` option does not match any package in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch.

@boks1971 boks1971 requested review from a team, kuba-- and shishirng February 12, 2025 06:22
"queueDuration", time.Since(enqueuedAt),
)
sentStart := time.Now()
if !n.pool.Submit(n.eventKey(event), func() {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the needed change to core to get a synchronous return value from Submit if it is successful or not. That will allow logging/posting event for dropped events too.

go.mod Outdated
google.golang.org/genproto/googleapis/api v0.0.0-20241202173237-19429a94021a // indirect
)

replace github.com/frostbyte73/core => ../frostbyte73/core/core
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we fork these? (this and iters)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

core - we have @frostbyte73 to ping, so maybe can remain there?
iters - are we making changes, if up streaming is delaying things makes sense to fork

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

they're both maintained by our people it's just awkward that no one else has write access and applying upstream changes can block landing code here

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh, is iters from @dennwc , did not realise that, sorry

yeah, would be good to not have that dependency, forking and upstreaming without blocking makes sense.

@frostbyte73 @dennwc @davidzhao okay to fork those into livekit org?

@boks1971 boks1971 merged commit 9b6e5d7 into main Feb 13, 2025
1 check passed
@boks1971 boks1971 deleted the raja_webhook_analytics branch February 13, 2025 04:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants