Repository navigation
Conversation
Exercise ordinary setup, discovery and scoped workflows with the candidate wheel and explicit owned cleanup on a disposable hosted runner. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Keep anonymous-volume refusal after mapping image storage to explicit project-owned volumes. Retain credentials only in memory and private files, and regenerate fixture operation reach. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Handle transport resets during readiness polling, keep permission refusals terminal, and record the failing startup stage without exposing response bodies. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
This branch has not been deployed
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
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.
Changelog category (leave one):
Changelog entry (one or two sentences a user of Loom can read without the diff; the release pull request collects these into the release notes):
The Dify plugin has a hosted application check for native tool registration and workflow execution.
Why
Archive and isolated tool tests do not exercise application setup, plugin discovery or workflow parameter binding. A disposable Community Edition deployment checks those boundaries against the candidate plugin and SDK wheel.
Scope and risk
The workflow starts the pinned official platform on a standard hosted Linux runner. It retains the security sidecars and signature verification, checks actual resource capacity before startup, and monitors bounded resource use. Insufficient capacity fails the job without changing its limits or deployment profile.
The scenario uses ordinary setup, login, workspace debugging and workflow routes. It checks remember, same-user recall, empty recall for a second user, shared knowledge search and the stored identity tuple. A fresh auth-on Loom fixture uses fake providers. Image-declared storage uses explicit owned volumes. Process generations, exact container ownership and scoped cleanup are checked; incomplete cleanup fails the job. Credentials are never written to stdout; retained logs and evidence use explicit redaction. No Cloud, marketplace acceptance or protected-session qualification is claimed.
Compatibility, rollout and rollback
Tests
AI assistance in the code (leave one; writing this description with AI is fine):
AI-generated: Codex prepared the workflow and checks. Independent source review runs alongside hosted CI.
I can explain every line of this diff and how it interacts with the rest of Loom.
Checklist