Bump karma from 3.1.4 to 6.4.4 in /scripts/node_modules.sh/debug in the npm_and_yarn group across 1 directory #1
Conversation
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
Bumps the npm_and_yarn group with 1 update in the /scripts/node_modules.sh/debug directory: [karma](https://github.com/karma-runner/karma). Updates `karma` from 3.1.4 to 6.4.4 - [Release notes](https://github.com/karma-runner/karma/releases) - [Changelog](https://github.com/karma-runner/karma/blob/master/CHANGELOG.md) - [Commits](karma-runner/karma@v3.1.4...v6.4.4) --- updated-dependencies: - dependency-name: karma dependency-type: direct:development dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
the
dependencies
Owner
|
Updates karma from 3.1.4 to 6.4.4 |
….sh/debug/npm_and_yarn-1dc217bc5b
Owner
|
Bump karma from 3.1.4 to 6.4.4 in /scripts/node_modules.sh/debug in the npm_and_yarn group across 1 directory #1 |
CodeMonkeyCybersecurity
added a commit
that referenced
this pull request
Oct 13, 2025
…ake LiteLLM default CRITICAL FIXES - DO NOT DEPLOY WITHOUT THESE: Issue #1: Open WebUI Not Connected to LiteLLM (CRITICAL) - Added OPENAI_API_BASE_URL=http://litellm-proxy:4000 to docker-compose.yml - Added OPENAI_API_KEY=${LITELLM_MASTER_KEY} to docker-compose.yml - Added connection variables to .env template - Without this, Open WebUI has NO backend and is completely non-functional Issue #2: LiteLLM Now DEFAULT (as requested) - Changed from --use-litellm flag to --direct-mode flag - LiteLLM production mode is now enabled by default - Direct mode is opt-in for development only - Updated all help text and examples Issue #3: Enhanced User Experience - Clear indication of production vs development mode - Warning message when using direct mode - Production features list shown by default TECHNICAL DETAILS: Docker Compose Changes: - openwebui service now has environment block - OPENAI_API_BASE_URL uses Docker service name (litellm-proxy:4000) - OPENAI_API_KEY references LITELLM_MASTER_KEY from .env - Proper service-to-service communication on Docker network Environment File Changes: - Added OPENAI_API_BASE_URL=http://litellm-proxy:4000 - Added OPENAI_API_KEY=${LITELLM_MASTER_KEY} - These tell Open WebUI where to find LiteLLM CLI Changes: - Removed: --use-litellm flag - Added: --direct-mode flag (disables LiteLLM) - Default behavior: LiteLLM enabled - Updated examples to show default is production-ready Type Changes: - Added DirectMode bool field - UseLiteLLM set to true by default when DirectMode is false - Clear separation between production and development modes Success Message Changes: - Shows LiteLLM URLs by default - Lists production features enabled - Warning when direct mode is used VERIFICATION: ✅ AZURE_MODEL format correct: azure/gpt-4 ✅ Docker service names correct: litellm-proxy ✅ LiteLLM config structure correct ✅ Volume mounts correct ✅ Open WebUI connection configured ✅ LiteLLM is default mode ✅ All packages compile successfully This fixes the critical issue where Open WebUI would deploy but have no backend to connect to, resulting in a completely non-functional system. Reference: OPENWEBUI_LITELLM_REVIEW.md for detailed technical review
CodeMonkeyCybersecurity
added a commit
that referenced
this pull request
Oct 13, 2025
…ment VERIFICATION COMPLETE - ALL ISSUES FIXED ✅ Confirmed in current codebase: ✅ Issue #1: Open WebUI connection to LiteLLM - FIXED (lines 727-732) ✅ Issue #2: LiteLLM default mode - FIXED (lines 95-97, cmd flags) ✅ Issue #3: Environment variables - FIXED (lines 612-614) All critical configuration points verified: ✅ AZURE_MODEL format: azure/%s (line 598) ✅ Service name: http://litellm-proxy:4000 (not localhost) ✅ LiteLLM config: os.environ/AZURE_MODEL (line 673) ✅ Volume mount: ./litellm_config.yaml:/app/config.yaml (line 737) ✅ DirectMode defaults to false (LiteLLM enabled by default) Status: READY FOR TESTING Includes complete testing checklist and deployment steps.
CodeMonkeyCybersecurity
pushed a commit
that referenced
this pull request
Nov 22, 2025
Architecture enforcement: Extracted ALL business logic from cmd/debug/iris.go to pkg/iris/debug/ following Assess → Intervene → Evaluate pattern. Changes: - Reduce cmd/debug/iris.go from 1507 lines → 65 lines (96% reduction) - Create pkg/iris/debug/ package with 7 files: * types.go (45 lines) - IrisConfig, CheckResult, DiagnosticConfig * diagnostics.go (101 lines) - Main RunDiagnostics() orchestration * checks_infrastructure.go (447 lines) - Project, Temporal, ports, binaries * checks_config.go (172 lines) - Config, Azure OpenAI, SMTP * checks_services.go (355 lines) - Worker, webhook, systemd, workflows * checks_system.go (71 lines) - Go dependencies * utils.go (391 lines) - Display, binary location, test alerts Architecture Compliance: - cmd/debug/iris.go now pure orchestration (flag parsing + delegation) - All business logic in pkg/ with proper error handling - Follows Assess → Intervene → Evaluate pattern - All exported functions have godoc comments - Structured logging with otelzap.Ctx(rc.Ctx) - No file operations, loops, or complex conditionals in cmd/ Verification: - go build ./pkg/iris/debug/... passes ✓ - go vet ./pkg/iris/debug/... passes ✓ - Zero functionality lost - 25 functions successfully migrated Impact: - cmd/debug/iris.go: 1507 → 65 lines (1442 lines extracted) - Improved testability (pkg/ functions are unit-testable) - Better code organization (checks grouped by category) - Maintains all diagnostic functionality Part of systematic cmd/ to pkg/ migration (#1 of 15 files). Next: cmd/debug/bootstrap.go (853 lines)
dependabot
bot
deleted the
dependabot/npm_and_yarn/scripts/node_modules.sh/debug/npm_and_yarn-1dc217bc5b
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Bumps the npm_and_yarn group with 1 update in the /scripts/node_modules.sh/debug directory: karma.
Updates
karmafrom 3.1.4 to 6.4.4Release notes
Sourced from karma's releases.
... (truncated)
Changelog
Sourced from karma's changelog.
... (truncated)
Commits
84f85e7chore(release): 6.4.4 [skip ci]a4d1284build(deps-dev): bump ws from 6.2.1 to 6.2.3d8cf806chore(release): 6.4.3 [skip ci]d7f2d69fix: add build commits for patch release85a2eebbuild(deps-dev): bump decode-uri-component from 0.2.0 to 0.2.20bffce2build(deps): updated socket.io version to fix security issues with socket.io-...86667abbuild(deps): bump follow-redirects from 1.11.0 to 1.15.4450fdfddocs: Add deprecation notice to Karma README9de3c00chore(release): 6.4.2 [skip ci]c6a4271fix: few typosDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditionsYou can disable automated security fix PRs for this repo from the Security Alerts page.