-
Notifications
You must be signed in to change notification settings - Fork 111
Add deployment to CreateDispatchOptions
#675
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
lukasIO
wants to merge
2
commits into
main
Choose a base branch
from
lukas/agent-deployment
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+124
−6
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| --- | ||
| "livekit-server-sdk": patch | ||
| --- | ||
|
|
||
| Add `deployment` to `CreateDispatchOptions` |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
82 changes: 82 additions & 0 deletions
82
packages/livekit-server-sdk/src/AgentDispatchClient.test.ts
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,82 @@ | ||
| // SPDX-FileCopyrightText: 2024 LiveKit, Inc. | ||
| // | ||
| // SPDX-License-Identifier: Apache-2.0 | ||
| import { describe, expect, it } from 'vitest'; | ||
| import { validateAgentDeploymentString } from './AgentDispatchClient.js'; | ||
|
|
||
| describe('validateAgentDeploymentString', () => { | ||
| it('accepts a valid deployment string with allowed separators', () => { | ||
| expect(() => validateAgentDeploymentString('my-agent_v1.0')).not.toThrow(); | ||
| }); | ||
|
|
||
| it('accepts a single alphanumeric character', () => { | ||
| expect(() => validateAgentDeploymentString('a')).not.toThrow(); | ||
| }); | ||
|
|
||
| it('throws when the string exceeds 63 characters', () => { | ||
| expect(() => validateAgentDeploymentString('a'.repeat(64))).toThrow( | ||
| 'Deployment string must not exceed 63 characters', | ||
| ); | ||
| }); | ||
|
|
||
| it('throws when it does not start with an alphanumeric character', () => { | ||
| expect(() => validateAgentDeploymentString('-agent')).toThrow( | ||
| 'Deployment must start and end with an alphanumeric character', | ||
| ); | ||
| }); | ||
|
|
||
| it('throws when it does not end with an alphanumeric character', () => { | ||
| expect(() => validateAgentDeploymentString('agent.')).toThrow( | ||
| 'Deployment must start and end with an alphanumeric character', | ||
| ); | ||
| }); | ||
|
|
||
| it.each(['my agent', 'a/b', 'a@b', 'a:b', 'a+b', 'a,b'])( | ||
| 'throws on unallowed character in the middle: %j', | ||
| (deployment) => { | ||
| expect(() => validateAgentDeploymentString(deployment)).toThrow( | ||
| 'Deployment must start and end with an alphanumeric character', | ||
| ); | ||
| }, | ||
| ); | ||
|
|
||
| it('accepts an empty string (targets the production deployment)', () => { | ||
| // An empty deployment is explicitly allowed: per the docstring, leaving it | ||
| // empty targets the production deployment. The validator early-returns | ||
| // before the alphanumeric regex would otherwise reject it. | ||
| expect(() => validateAgentDeploymentString('')).not.toThrow(); | ||
| }); | ||
|
|
||
| it.each([ | ||
| ['null byte', 'agent\0'], | ||
| ['tab', 'a\tb'], | ||
| ['newline in the middle', 'a\nb'], | ||
| ['carriage return', 'a\rb'], | ||
| ['vertical tab', 'a\x0bb'], | ||
| ])('throws on control character (%s)', (_label, deployment) => { | ||
| expect(() => validateAgentDeploymentString(deployment)).toThrow( | ||
| 'Deployment must start and end with an alphanumeric character', | ||
| ); | ||
| }); | ||
|
|
||
| it('rejects a trailing newline (JS $ must not match before it)', () => { | ||
| // Without the `m` flag, JS anchors `$` at the true end of string, so a | ||
| // smuggled trailing newline ("agent\n") is correctly rejected rather than | ||
| // treated as a valid "agent". | ||
| expect(() => validateAgentDeploymentString('agent\n')).toThrow( | ||
| 'Deployment must start and end with an alphanumeric character', | ||
| ); | ||
| }); | ||
|
|
||
| it.each([ | ||
| ['path traversal', '../etc'], | ||
| ['leading slash', '/agent'], | ||
| ['leading whitespace', ' agent'], | ||
| ['trailing whitespace', 'agent '], | ||
| ['unicode homoglyph', 'agént'], | ||
| ])('rejects security-relevant input (%s)', (_label, deployment) => { | ||
| expect(() => validateAgentDeploymentString(deployment)).toThrow( | ||
| 'Deployment must start and end with an alphanumeric character', | ||
| ); | ||
| }); | ||
| }); |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tbd if we even need client side validation. If we don't I'll simply remove this helper and the related tests
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you do decide this is important (you may have more context than me on this), definitely make sure it ends up in livekit/client-sdk-js#1971 too.
I also agree though that I think it probably makes sense to start without this, and if validation is really needed IMO it might be better to do it in upstream systems (ie, something agents hosting related?) and have it surface the validation error over webrtc.