- Notifications
You must be signed in to change notification settings - Fork1k
PermalinkChoose a base ref {{ refName }}default Choose a head ref {{ refName }}default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also orlearn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also.Learn more about diff comparisons here.
base repository:coder/coder
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
Uh oh!
There was an error while loading.Please reload this page.
base:main@{1day}
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}defaultLoading
...
head repository:coder/coder
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
Uh oh!
There was an error while loading.Please reload this page.
compare:main
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}defaultLoading
- 7commits
- 23files changed
- 6contributors
Commits on Oct 7, 2025
feat(scaletest): add runner for notifications delivery (#20091)
Relates tocoder/internal#910This PR adds a scaletest runner that simulates users receiving notifications through WebSocket connections.An instance of this notification runner does the following:1. Creates a user (optionally with specific roles like owner).2. Connects to /api/v2/notifications/inbox/watch via WebSocket to receive notifications in real-time.3. Waits for all other concurrently executing runners (per the DialBarrier WaitGroup) to also connect their websockets.4. For receiving users: Watches the WebSocket for expected notifications and records delivery latency for each notification type.5. For regular users: Maintains WebSocket connections to simulate concurrent load while receiving users wait for notifications.6. Waits on the ReceivingWatchBarrier to coordinate between receiving and regular users.7. Cleans up the created user after the test completes.Exposes three prometheus metrics:1. notification_delivery_latency_seconds - HistogramVec. Labels = {username, notification_type}2. notification_delivery_errors_total - CounterVec. Labels = {username, action}3. notification_delivery_missed_total - CounterVec. Labels = {username}The runner measures end-to-end notification latency from when a notification-triggering event occurs (e.g., user creation/deletion) to when the notification is received by a WebSocket client.
chore(docs): update notifications documentation to include task events (
feat: add cli command scaletest dynamic-parameters (#20034)
part ofcoder/internal#912Adds CLI command `coder exp scaletest dynamic-parameters`I've left out the configuration of tracing and timeouts for now. I think I want to do some refactoring of the scaletest CLI to make handling those flags take up less boiler plate.I will add tracing and timeout flags in a follow up PR.
Loading
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 main@{1day}...main
Uh oh!
There was an error while loading.Please reload this page.