Repository navigation
Check the Dify plugin in a native application - #946
Merged
Merged
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>
The native tool workflows need the application and relational store, while the optional dataset subsystem stays disabled. Verify the resolved configuration and initialize only the fresh plugin storage bind under the pinned image user. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
…ication Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
The editor defaults endpoint omits start and end nodes. Construct their required fields directly and retain native tool execution checks. Fixed phase labels identify subsequent schema failures without recording response payloads. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
The current Community Edition initializes both application and plugin storage before the daemon starts. Verify its fresh bind, completion dependency and ownership rather than running a second root helper. Record the two readiness observations separately. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
The direct memory row query returns JSON text. Keep the exact identity tuple and row count, compare the encoded value, and retain observed rows before a mismatch fails the check. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
The packaged setup guide must describe the native check and its candidate SDK scope while retaining the untested Cloud and version-matrix limitations. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
10 of 14 tasks
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
Dify tools have a hosted Community Edition application check for registration, workflow execution and stored user identity.
Why
Archive and isolated tool tests do not exercise application setup, plugin discovery or workflow parameter binding. A disposable Community Edition application checks those boundaries against the candidate plugin, server and SDK wheel.
Scope and risk
The application uses current Community Edition pinned to its immutable source commit, ordinary setup/login/workspace debugging routes, signature verification and the configured plugin-daemon image user. The tools use Loom memory and document search; the host's optional dataset subsystem stays disabled through its supported empty vector-store selector. The check requires that selection in the resolved API, worker and Beat configuration and the exact 14-service closure.
The platform's official initialization service owns the fresh plugin-storage bind. Both readiness checkpoints require the original directory identity, owner and initialization marker. No custom root helper or replacement backend runs. Workflow start and end nodes use their declared schemas.
Remember, same-user recall, empty recall for a second user, namespace-shared document search and exactly one seven-field stored identity/value row must pass. The stored fact is compared as the exact JSON text written by memory.set. Image IDs, resource caps and owned process/container/volume/network cleanup remain enforced. Incomplete census, monitor failure or unverified cleanup invalidates success; credentials are redacted from retained evidence.
The final package's README describes the exercised scope. Cloud, browser, protected-session families and host dataset retrieval are untested. The scenario uses fake providers and a candidate-built isolated SDK wheel; it does not qualify the published registry wheel or a complete host/version/architecture matrix. Private runtime files are retained, and intentional interruption was not exercised by the successful application run.
Compatibility, rollout and rollback
No product operation, wire field, setting, schema, migration or runtime behavior changes. The reach manifest records fixture calls. No operator steps are needed; the stack exists only on the disposable hosted runner. Revert the check to roll it back.
Tests
AI assistance in the code (leave one; writing this description with AI is fine):
AI-generated: Codex prepared the workflow and checks, with independent source and actual-execution reviews.
I can explain every line of this diff and how it interacts with the rest of Loom.
Checklist