langgenius/dify

AI Summary: Users of Dify version 1.8.1 (Cloud) have reported a bug where an incorrect icon is displayed in the navigation dropdown. This occurs when logging into the console, opening any app in the studio, and then clicking the top-left dropdown menu that shows the current app's name.

AI Summary: A Dify user is requesting native integration with ServiceNow as a critical tool, citing it as a blocker for their company's adoption. They suggest an integration similar to what n8n offers, which would be the deciding factor for them to choose Dify.

AI Summary: The 'Invite Team Member' modal in Dify version 1.7.1 (both Cloud and Self-Hosted) has a bug where the email input area does not scroll when a large number of emails (15+) are added. This prevents users from viewing or managing all entered emails, as the content exceeds the fixed height without providing a scrollbar.

AI Summary: The issue reports a bug where the `web/api/saved-messages` endpoint returns incorrect results when a user has no saved messages. This occurs on a new web app when making API calls with the pinned filter. The reporter notes it's a duplicate of issue #23668.

AI Summary: This GitHub issue reports a UI bug in Dify (v1.7.2, self-hosted) where the first "Deep Thinking..." indicator for an Agent with a "Thinking Model" never stops spinning after the final answer is fully displayed, particularly when Knowledge Base retrieval is triggered. The indicator only disappears upon page refresh, contrary to the expected behavior of stopping automatically.

AI Summary: This GitHub issue proposes a refactoring task to replace plain `str` type hints with `typing.Literal` in Python code. The goal is to enhance type safety and clarity by explicitly defining a fixed set of allowed string values where applicable. An example file, `api/controllers/service_api/app/annotation.py`, is provided to illustrate the intended change.

AI Summary: The user requests an enhancement for the chat input field's vertical height. They find it too narrow when many items are present and desire it to expand more vertically, similar to other chat services, to improve usability.

AI Summary: The user requests a new feature to allow the removal of an uploaded avatar image. Currently, once an avatar is set, there is no option within the account management modal to delete or revert it.

AI Summary: The user reports a bug in Dify version 1.7.2 (self-hosted) where the pop-up box displayed after attempting to check the Dify version cannot be closed. This prevents users from dismissing the version information window.

AI Summary: Implement default value functionality for all input types within the Dify platform, enhancing user experience, particularly for the 'Chat Opener' feature which utilizes variables. This involves modifying the existing input handling to accommodate default values and ensuring seamless integration with the variable system.

AI Summary: Debug a Dify Cloud application import issue. The issue occurs when importing a folder of DSL files; the API returns an error "yaml_content is required when import_mode is yaml-content", despite the import seemingly using a file-based approach rather than YAML content directly. The task involves investigating the API request and response, identifying why 'yaml_content' is unexpectedly required, and fixing the underlying bug in the Dify Cloud application import functionality.

AI Summary: Debug and fix a bug in the Dify platform's HTTP node where URL parameters are incorrectly modified by adding an equals sign ('=') when making requests. The issue occurs in a self-hosted Docker instance of Dify version 1.7.1. The solution requires identifying the source of the unexpected '=' addition within the HTTP node's code and correcting it to ensure proper URL parameter handling.

AI Summary: The task is to fix a bug in the Dify workflow editor where renaming input parameters is not correctly reflected in IF/ELSE nodes, causing workflow breakage. The fix requires updating the IF/ELSE node to track parameter renames.

AI Summary: Enhance the Dify platform by adding a quick action in the 'Last Run' tab that allows users to directly focus on a specific node in the 'Variable Inspect' section. This will improve workflow debugging by providing easier access to inspect, edit, or delete node outputs from the previous run.

AI Summary: Debug a Dify self-hosted instance (version 1.7.1) where locally installed large language models (DeepSeek and Qwen) are not appearing as options within the agent node of the workflow editor. The task involves investigating why these models are not being detected or loaded correctly by the Dify application.

AI Summary: The task is to fix a bug in the Dify platform's `ApiTool` where the `_invoke` method always returns a `TEXT` message type instead of `JSON` when the API response is valid JSON. The fix should correctly parse JSON responses and populate the `json` field accordingly, improving the handling of JSON data from custom API tools.

AI Summary: The task is to fix a bug in the Dify platform where the use of Windows path separators causes file access failures when interacting with Huawei OSS. The solution involves modifying the `generate_key_pair()` and `get_decrypt_decoding()` functions to consistently use POSIX-style paths (forward slashes) regardless of the operating system.

AI Summary: The task is to fix a bug in the Dify platform's date input field. The date input currently displays and outputs dates in an unexpected format, regardless of locale settings, and doesn't support a specific date format. The fix should ensure correct display and output of dates according to locale and allow for a specified date format ('yyyy-dd-mm').

AI Summary: Debug a frontend error in the Dify self-hosted application (v1.7.1) that occurs when loading specific plugin tools within a workflow. The error manifests as a white screen and a 'client-side exception' message, with the root cause seemingly within an obfuscated JavaScript file. The task involves analyzing provided screenshots and console logs (not included in this context) to identify the source of the null pointer exception during a split operation.

AI Summary: The task is to debug a Dify workflow API call that fails due to an incorrect filename extraction from a remote URL. The issue stems from the `_get_remote_file_info` function in `api/factories/file_factory.py`, which uses an incorrect method to split the URL and extract the filename, leading to an invalid filename and a 400 error. The solution involves correcting the filename extraction logic to accurately parse the filename from the URL, handling query parameters correctly.

AI Summary: The task is to debug a Dify (an open-source LLM app development platform) issue where the `MAX_PARALLEL_LIMIT` environment variable does not correctly affect the `MAX_ITERATION_PARALLEL_NUM` setting within the application. The issue occurs in the cloud version of Dify (version 1.7.1). The solution involves investigating the codebase to understand why the expected value from `MAX_PARALLEL_LIMIT` is not being read and used to set `MAX_ITERATION_PARALLEL_NUM`, and then correcting the code to ensure proper functionality.

AI Summary: Debug a JavaScript error ('Cannot read properties of null') occurring in the Dify 1.7.0 self-hosted application when clicking a Question Classifier node during workflow execution. The error prevents the node panel from opening and causes UI unresponsiveness. The task involves analyzing provided screenshots, reproducing the error, and identifying the root cause within the Dify codebase to provide a fix.

AI Summary: Implement a dark mode variant for the overlay notification in the Agent Application within the Dify platform. This involves creating a visually consistent dark mode version of the existing notification to improve user experience in dark mode settings.

AI Summary: The task is to debug a bug in the Dify platform where the `file_upload.allowed_file_types` parameter does not correctly reset when switching between multimodal and non-multimodal LLMs. The bug causes the parameter to retain values inappropriate for non-multimodal models. The solution requires identifying the code section responsible for updating this parameter based on the selected LLM and correcting the logic to ensure it resets correctly when a non-multimodal model is chosen.

AI Summary: The task is to fix a UI issue in the Dify workflow tool where the 'Configure' button appears clickable to non-manager users, even though it's non-functional for them. The solution involves modifying the button's styling (likely adding a 'cursor-not-allowed' style and reduced opacity) and potentially adding a tooltip explaining the restriction. Alternatively, the functionality could be made available to non-managers.

AI Summary: The task is to fix a bug in the Dify platform's tool manager. The bug involves the `provider_config_cache` not being correctly deleted after credentials are refreshed, leading to the retrieval of outdated credentials. The solution requires modifying the `get_tool_runtime` function in `api/core/tools/tool_manager.py` to include the deletion of the old cache after a successful refresh.

AI Summary: Debug a metadata filtering issue in the Dify Cloud platform where only 10 out of potentially more selected records are being passed to the backend. The issue needs investigation to determine why the filter is limiting the number of records transferred and needs to be corrected to allow all selected items to be processed.

AI Summary: The task involves addressing UI issues in the Dify platform. Specifically, it requires removing an extra divider and correcting a potentially incorrect section title within the user interface. The issue report includes screenshots highlighting the problems.

AI Summary: Debug a reported bug in the Dify open-source LLM app development platform where importing a specific YAML file and viewing an MCP node causes a page crash with an 'Uncaught TypeError: e.match is not a function' error. The task involves analyzing the provided YAML file, reproducing the error, identifying the root cause within the Dify codebase (likely related to plugins), and proposing a fix.

AI Summary: The task is to debug a bug in Dify's cloud-based HTTP Request component. The component fails to correctly generate multipart/form-data requests for file uploads, resulting in server-side errors. The solution requires identifying and fixing the issue within the component's code that's responsible for constructing the request body and headers, ensuring proper boundary inclusion and formatting.

AI Summary: The task is to debug a bug in the Dify email plugin (version 0.0.7) where the encryption method dropdown is not functioning correctly, preventing users from configuring the plugin. The issue occurs in a self-hosted (Docker) instance of Dify v1.7.0. The solution requires investigating the plugin's code and configuration to identify why the dropdown isn't populating or allowing selection.

AI Summary: Debug a REST API endpoint for deleting conversations in a self-hosted Dify instance (version 1.6.0). The API is returning a 404 error ('Conversation Not Exists') even though the conversation exists. The issue needs investigation to determine why the API cannot find the conversation created through a Typebot integration.

AI Summary: Increase the 24-character limitation on tool names generated by Dify workflows and MCP servers. This involves identifying the code responsible for the limitation, assessing its impact on the system, and implementing a change to increase the character limit while ensuring system stability and backward compatibility.

AI Summary: The task involves refactoring the Dify codebase to replace all instances of `datetime.now(UTC).replace(tzinfo=None)` with the existing helper function `naive_utc_now()`. This is a code cleanup and consistency improvement to enhance maintainability and reduce potential errors.

AI Summary: Implement a configurable naming scheme for Elasticsearch indices created by Dify's Knowledge feature, allowing users to specify a format including workspace and knowledge name to enhance security and multi-tenancy support within an Elasticsearch cluster. This involves modifying Dify's code to accept a new environment variable or configuration option for the index naming pattern and updating the index creation logic accordingly.

AI Summary: The task involves improving the user interface (UI) of agent tools within the Dify platform. Specifically, it requires fixing the incorrect placement of tool popovers, which are currently hidden behind the main panel, and resolving a discrepancy in the number of iterations displayed between the agent tool and the Agent app. This likely involves adjustments to the UI code and potentially backend logic to ensure consistent iteration counts.

AI Summary: Debug and fix a bug in the Dify open-source LLM app development platform where the node titles in copied iterative nodes do not increment correctly when parallel branches exist. The issue occurs in the self-hosted Docker version (1.6.0) and involves inspecting the node title incrementing logic within the application's workflow editor.

AI Summary: Debug a bug in the Dify workflow editor where selecting a sub-item from a file list in the variable aggregator prevents selecting another sub-item of the same type. The issue occurs in a self-hosted Docker instance of Dify version 1.6.0. The expected behavior is the ability to select multiple sub-items (e.g., `first_record.name` and `last_record.name`) from the same file list. The actual behavior restricts selection after the first sub-item is chosen.

AI Summary: The task is to debug a Dify (version 1.5.1) self-hosted instance where the `/chat-messages` API is incorrectly returning file data within a "message" event instead of the expected "message_file" event. The solution involves investigating the API response, identifying the source of the error within the Dify codebase (likely related to how file uploads are handled by the chatflow agent and Answer node), and correcting the event type to ensure proper file handling.

AI Summary: The task involves resolving database upgrade issues encountered when updating the Dify platform (version 1.6.0) to a self-hosted instance. The primary problem is a missing pgcrypto extension and duplicated/incomplete indexes. The solution requires manually installing the extension, modifying Alembic migration scripts to include `if_not_exists=True` for index creation, and potentially manually deleting existing, partially created indexes before re-running the upgrade.

AI Summary: Debug and fix a bug in Dify version 1.6.0 where the `basePath` is duplicated in URLs generated when creating a new knowledge base. The issue stems from a change in commit db20f9b where the `basePath` was manually added to href in the <Link> component, which already automatically prepends the `basePath`. The fix involves removing the manually added `basePath` from the href attribute.

AI Summary: The task is to debug a bug in the Dify (version 1.6.0) self-hosted application where editing the output of an iteration node fails, resulting in a JSON editor error. The solution requires investigating the application's codebase to identify why the JSON editor prevents modification of the iteration node's output object.

AI Summary: The task is to modify the Dify platform's MCP (likely Model Configuration Panel or similar) tool to automatically populate its description field with the workflow description if one exists. This ensures consistency and reduces manual input.

AI Summary: A bug report has been filed regarding a visual issue in the Dify self-hosted application (version 1.6.0). The background color is missing from question parts within the chat interface of agents/workflows. The task involves investigating and resolving this UI rendering problem, potentially requiring debugging of the frontend code.

AI Summary: The task is to debug a problem in the Dify platform where the problem classifier LLM model intermittently throws an AttributeError ('NoneType' object has no attribute 'content') when processing user queries. The issue seems related to the format of the LLM's response not matching the expected format for the problem classifier node. The solution likely involves investigating the LLM prompt engineering, response parsing within the Dify node, or potentially the LLM model's capabilities.

AI Summary: Debug a Dify workflow. The issue is an MCP (likely Model Control Plane) error occurring when a workflow lacks input parameters. The task involves reproducing the error, investigating the root cause (possibly within the Dify codebase or its interaction with the model), and providing a fix or workaround. This might involve examining logs, network traffic, or the Dify application's internal state.