[Claude PR] Fix HTTP connection issue for schedule triggers #5849
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.
Summary
Fixed the issue where schedule triggers couldn't be created when connecting to Windmill over HTTP. The problem was caused by
crypto.randomUUID()
requiring a secure context (HTTPS), which broke functionality for users on internal HTTP networks.Changes Made
crypto.randomUUID()
withgenerateRandomString()
intriggers.svelte.ts
generateRandomString
import from$lib/utils
generateRandomString()
function usesMath.random()
which works in any contextIssue Reference
Fixes #5847
Test Plan
Generated with Claude Code
Important
Replaces
crypto.randomUUID()
withgenerateRandomString()
intriggers.svelte.ts
to fix schedule trigger creation over HTTP.crypto.randomUUID()
withgenerateRandomString()
intriggers.svelte.ts
to fix schedule trigger creation over HTTP.generateRandomString()
usesMath.random()
to work in any context.generateRandomString
import from$lib/utils
intriggers.svelte.ts
.This description was created by
for d0a4456. You can customize this summary. It will automatically update as commits are pushed.