langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Encountering Errors During flask db upgrade After Latest Pull #4076

New Issue
Closed
opened 2026-02-21 18:04:38 -05:00 by yindo · 5 comments
yindo commented 2026-02-21 18:04:38 -05:00
Owner
Copy Link
Copy Source

Originally created by @XiaoLey on GitHub (Jun 13, 2024).

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.6.10

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

After creating a new conda environment and pulling the latest code from the main branch of Dify in an empty directory, I encountered the following error when executing flask db upgrade:

/home/xiaoley/anaconda3/envs/dify/lib/python3.10/site-packages/pydantic/_internal/_fields.py:160: UserWarning: Field "model_type" has conflict with protected namespace "model_".

You may be able to resolve this warning by setting `model_config['protected_namespaces'] = ()`.
  warnings.warn(
None of PyTorch, TensorFlow >= 2.0, or Flax have been found. Models won't be available and only tokenizers, configuration and file/data utilities can be used.
...
error: 2 validation errors for WebscraperTool
parameters.2.options.0.value
  Input should be a valid string [type=string_type, input_value=True, input_type=bool]
    For further information visit https://errors.pydantic.dev/2.7/v/string_type
parameters.2.options.1.value
  Input should be a valid string [type=string_type, input_value=False, input_type=bool]
    For further information visit https://errors.pydantic.dev/2.7/v/string_type
...
error: 1 validation error for BingSearchTool
parameters.8.options.24.value
  Input should be a valid string [type=string_type, input_value=False, input_type=bool]
    For further information visit https://errors.pydantic.dev/2.7/v/string_type
...

Steps to Reproduce:

  1. Create a new conda environment:

    conda create -n dify python=3.10
conda activate dify

  2. Clone the latest main branch code of Dify in an empty directory:

    git clone https://github.com/langgenius/dify.git
cd dify/api

  3. Install project dependencies:

    pip install -r requirements.txt

  4. Execute the database migration command:

    flask db upgrade

✔️ Expected Behavior

The database migration command should execute successfully without any errors.

❌ Actual Behavior

As described above, Pydantic field validation errors and namespace conflict warnings were encountered.

Additional Information:

This issue did not occur previously and is suspected to be related to a recent commit that updated the Pydantic version (potentially PR #4592). However, this has not been confirmed yet.

I hope this issue can be resolved soon as I was planning to start enhancing the Jina tool integration but am currently unable to proceed due to this issue.

Thank you very much!

Originally created by @XiaoLey on GitHub (Jun 13, 2024). ### Self Checks - [X] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [X] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [X] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.6.10 ### Cloud or Self Hosted Self Hosted (Source) ### Steps to reproduce After creating a new conda environment and pulling the latest code from the main branch of Dify in an empty directory, I encountered the following error when executing `flask db upgrade`: ``` /home/xiaoley/anaconda3/envs/dify/lib/python3.10/site-packages/pydantic/_internal/_fields.py:160: UserWarning: Field "model_type" has conflict with protected namespace "model_". You may be able to resolve this warning by setting `model_config['protected_namespaces'] = ()`. warnings.warn( None of PyTorch, TensorFlow >= 2.0, or Flax have been found. Models won't be available and only tokenizers, configuration and file/data utilities can be used. ... error: 2 validation errors for WebscraperTool parameters.2.options.0.value Input should be a valid string [type=string_type, input_value=True, input_type=bool] For further information visit https://errors.pydantic.dev/2.7/v/string_type parameters.2.options.1.value Input should be a valid string [type=string_type, input_value=False, input_type=bool] For further information visit https://errors.pydantic.dev/2.7/v/string_type ... error: 1 validation error for BingSearchTool parameters.8.options.24.value Input should be a valid string [type=string_type, input_value=False, input_type=bool] For further information visit https://errors.pydantic.dev/2.7/v/string_type ... ``` **Steps to Reproduce:** 1. Create a new conda environment: ```bash conda create -n dify python=3.10 conda activate dify ``` 2. Clone the latest main branch code of Dify in an empty directory: ```bash git clone https://github.com/langgenius/dify.git cd dify/api ``` 3. Install project dependencies: ```bash pip install -r requirements.txt ``` 4. Execute the database migration command: ```bash flask db upgrade ``` ### ✔️ Expected Behavior The database migration command should execute successfully without any errors. ### ❌ Actual Behavior As described above, Pydantic field validation errors and namespace conflict warnings were encountered. ## Additional Information: This issue did not occur previously and is suspected to be related to a recent commit that updated the Pydantic version (potentially PR #4592). However, this has not been confirmed yet. I hope this issue can be resolved soon as I was planning to start enhancing the Jina tool integration but am currently unable to proceed due to this issue. Thank you very much!
yindo added the 🐞 bug label 2026-02-21 18:04:38 -05:00
yindo closed this issue 2026-02-21 18:04:38 -05:00
yindo commented 2026-02-21 18:04:38 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jun 13, 2024):

To resolve the validation errors encountered during the flask db upgrade command after pulling the latest code from the main branch of Dify, you need to ensure that the migration script is correctly applied. The provided migration scripts include the necessary changes to the database schema.

Here are the relevant migration scripts for reference:

Migration Script: e1901f623fd0_add_annotation_reply.py

"""add-annotation-reply

Revision ID: e1901f623fd0
Revises: fca025d3b60f
Create Date: 2023-12-12 06:58:41.054544

"""
import sqlalchemy as sa
from alembic import op
from sqlalchemy.dialects import postgresql

# revision identifiers, used by Alembic.
revision = 'e1901f623fd0'
down_revision = 'fca025d3b60f'
branch_labels = None
depends_on = None

def upgrade():
    # ### commands auto generated by Alembic - please adjust! ###
    op.create_table('app_annotation_hit_histories',
    sa.Column('id', postgresql.UUID(), server_default=sa.text('uuid_generate_v4()'), nullable=False),
    sa.Column('app_id', postgresql.UUID(), nullable=False),
    sa.Column('annotation_id', postgresql.UUID(), nullable=False),
    sa.Column('source', sa.Text(), nullable=False),
    sa.Column('question', sa.Text(), nullable=False),
    sa.Column('account_id', postgresql.UUID(), nullable=False),
    sa.Column('created_at', sa.DateTime(), server_default=sa.text('CURRENT_TIMESTAMP(0)'), nullable=False),
    sa.PrimaryKeyConstraint('id', name='app_annotation_hit_histories_pkey')
    )
    with op.batch_alter_table('app_annotation_hit_histories', schema=None) as batch_op:
        batch_op.create_index('app_annotation_hit_histories_account_idx', ['account_id'], unique=False)
        batch_op.create_index('app_annotation_hit_histories_annotation_idx', ['annotation_id'], unique=False)
        batch_op.create_index('app_annotation_hit_histories_app_idx', ['app_id'], unique=False)

    with op.batch_alter_table('app_model_configs', schema=None) as batch_op:
        batch_op.add_column(sa.Column('annotation_reply', sa.Text(), nullable=True))

    with op.batch_alter_table('dataset_collection_bindings', schema=None) as batch_op:
        batch_op.add_column(sa.Column('type', sa.String(length=40), server_default=sa.text("'dataset'::character varying"), nullable=False))

    with op.batch_alter_table('message_annotations', schema=None) as batch_op:
        batch_op.add_column(sa.Column('question', sa.Text(), nullable=True))
        batch_op.add_column(sa.Column('hit_count', sa.Integer(), server_default=sa.text('0'), nullable=False))
        batch_op.alter_column('conversation_id',
               existing_type=postgresql.UUID(),
               nullable=True)
        batch_op.alter_column('message_id',
               existing_type=postgresql.UUID(),
               nullable=True)

    # ### end Alembic commands ###

def downgrade():
    # ### commands auto generated by Alembic - please adjust! ###
    with op.batch_alter_table('message_annotations', schema=None) as batch_op:
        batch_op.alter_column('message_id',
               existing_type=postgresql.UUID(),
               nullable=False)
        batch_op.alter_column('conversation_id',
               existing_type=postgresql.UUID(),
               nullable=False)
        batch_op.drop_column('hit_count')
        batch_op.drop_column('question')

    with op.batch_alter_table('dataset_collection_bindings', schema=None) as batch_op:
        batch_op.drop_column('type')

    with op.batch_alter_table('app_model_configs', schema=None) as batch_op:
        batch_op.drop_column('annotation_reply')

    with op.batch_alter_table('app_annotation_hit_histories', schema=None) as batch_op:
        batch_op.drop_index('app_annotation_hit_histories_app_idx')
        batch_op.drop_index('app_annotation_hit_histories_annotation_idx')
        batch_op.drop_index('app_annotation_hit_histories_account_idx')

    op.drop_table('app_annotation_hit_histories')
    # ### end Alembic commands ###

Migration Script: 5fda94355fce_custom_disclaimer.py

"""Custom Disclaimer

Revision ID: 5fda94355fce
Revises: 47cc7df8c4f3
Create Date: 2024-05-10 20:04:45.806549

"""
import sqlalchemy as sa
from alembic import op

import models as models

# revision identifiers, used by Alembic.
revision = '5fda94355fce'
down_revision = '47cc7df8c4f3'
branch_labels = None
depends_on = None

def upgrade():
    # ### commands auto generated by Alembic - please adjust! ###
    with op.batch_alter_table('recommended_apps', schema=None) as batch_op:
        batch_op.add_column(sa.Column('custom_disclaimer', sa.String(length=255), nullable=True))

    with op.batch_alter_table('sites', schema=None) as batch_op:
        batch_op.add_column(sa.Column('custom_disclaimer', sa.String(length=255), nullable=True))

    with op.batch_alter_table('tool_api_providers', schema=None) as batch_op:
        batch_op.add_column(sa.Column('custom_disclaimer', sa.String(length=255), nullable=True))

    # ### end Alembic commands ###


def downgrade():
    # ### commands auto generated by Alembic - please adjust! ###
    with op.batch_alter_table('tool_api_providers', schema=None) as batch_op:
        batch_op.drop_column('custom_disclaimer')

    with op.batch_alter_table('sites', schema=None) as batch_op:
        batch_op.drop_column('custom_disclaimer')

    with op.batch_alter_table('recommended_apps', schema=None) as batch_op:
        batch_op.drop_column('custom_disclaimer')

    # ### end Alembic commands ###

Migration Script: 246ba09cbbdb_add_app_anntation_setting.py

"""add_app_anntation_setting

Revision ID: 246ba09cbbdb
Revises: 714aafe25d39
Create Date: 2023-12-14 11:26:12.287264

"""
import sqlalchemy as sa
from alembic import op
from sqlalchemy.dialects import postgresql

# revision identifiers, used by Alembic.
revision = '246ba09cbbdb'
down_revision = '714aafe25d39'
branch_labels = None
depends_on = None


def upgrade():
    # ### commands auto generated by Alembic - please adjust! ###
    op.create_table('app_annotation_settings',
    sa.Column('id', postgresql.UUID(), server_default=sa.text('uuid_generate_v4()'), nullable=False),
    sa.Column('app_id', postgresql.UUID(), nullable=False),
    sa.Column('score_threshold', sa.Float(), server_default=sa.text('0'), nullable=False),
    sa.Column('collection_binding_id', postgresql.UUID(), nullable=False),
    sa.Column('created_user_id', postgresql.UUID(), nullable=False),
    sa.Column('created_at', sa.DateTime(), server_default=sa.text('CURRENT_TIMESTAMP(0)'), nullable=False),
    sa.Column('updated_user_id', postgresql.UUID(), nullable=False),
    sa.Column('updated_at', sa.DateTime(), server_default=sa.text('CURRENT_TIMESTAMP(0)'), nullable=False),
    sa.PrimaryKeyConstraint('id', name='app_annotation_settings_pkey')
    )
    with op.batch_alter_table('app_annotation_settings', schema=None) as batch_op:
        batch_op.create_index('app_annotation_settings_app_idx', ['app_id'], unique=False)

    with op.batch_alter_table('app_model_configs', schema=None) as batch_op:
        batch_op.drop_column('annotation_reply')

    # ### end Alembic commands ###


def downgrade():
    # ### commands auto generated by Alembic - please adjust! ###
    with op.batch_alter_table('app_model_configs', schema=None) as batch_op:
        batch_op.add_column(sa.Column('annotation_reply', sa.TEXT(), autoincrement=False, nullable=True))

    with op.batch_alter_table('app_annotation_settings', schema=None) as batch_op:
        batch_op.drop_index('app_annotation_settings_app_idx')

    op.drop_table('app_annotation_settings')
    # ### end Alembic commands ###

Ensure that you have the latest migration scripts and that your database is in sync with these scripts. You can do this by running the following commands:

  1. Check for new migrations:

    flask db migrate

  2. Apply the migrations:

    flask db upgrade

Additionally, Dify has a GitHub workflow to test database migrations on pull requests to the main branch. This ensures that migrations are validated before being merged. Here is the relevant part of the workflow:

name: DB Migration Test

on:
  pull_request:
    branches:
      - main
    paths:
      - api/migrations/**

concurrency:
  group: db-migration-test-${{ github.ref }}
  cancel-in-progress: true

jobs:
  db-migration-test:
    runs-on: ubuntu-latest
    strategy:
      matrix:
        python-version:
          - "3.10"

    steps:
      - name: Checkout code
        uses: actions/checkout@v4

      - name: Install Poetry
        uses: abatilo/actions-poetry@v3

      - name: Set up Python ${{ matrix.python-version }}
        uses: actions/setup-python@v5
        with:
          python-version: ${{ matrix.python-version }}
          cache: 'poetry'
          cache-dependency-path: |
            api/pyproject.toml
            api/poetry.lock

      - name: Install dependencies
        run: poetry install -C api

      - name: Set up Middleware
        uses: hoverkraft-tech/compose-action@v2.0.0
        with:
          compose-file: |
            docker/docker-compose.middleware.yaml
          services: |
            db

      - name: Prepare configs
        run: |
          cd api
          cp .env.example .env

      - name: Run DB Migration
        run: |
          cd api
          poetry run python -m flask db upgrade

If you still encounter validation errors, it might be due to conflicts or missing dependencies in the migration scripts. Double-check the down_revision and ensure that all previous migrations have been applied correctly [1][2][3][4].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Jun 13, 2024): <!-- Answer --> To resolve the validation errors encountered during the `flask db upgrade` command after pulling the latest code from the main branch of Dify, you need to ensure that the migration script is correctly applied. The provided migration scripts include the necessary changes to the database schema. Here are the relevant migration scripts for reference: ### Migration Script: `e1901f623fd0_add_annotation_reply.py` ```py """add-annotation-reply Revision ID: e1901f623fd0 Revises: fca025d3b60f Create Date: 2023-12-12 06:58:41.054544 """ import sqlalchemy as sa from alembic import op from sqlalchemy.dialects import postgresql # revision identifiers, used by Alembic. revision = 'e1901f623fd0' down_revision = 'fca025d3b60f' branch_labels = None depends_on = None def upgrade(): # ### commands auto generated by Alembic - please adjust! ### op.create_table('app_annotation_hit_histories', sa.Column('id', postgresql.UUID(), server_default=sa.text('uuid_generate_v4()'), nullable=False), sa.Column('app_id', postgresql.UUID(), nullable=False), sa.Column('annotation_id', postgresql.UUID(), nullable=False), sa.Column('source', sa.Text(), nullable=False), sa.Column('question', sa.Text(), nullable=False), sa.Column('account_id', postgresql.UUID(), nullable=False), sa.Column('created_at', sa.DateTime(), server_default=sa.text('CURRENT_TIMESTAMP(0)'), nullable=False), sa.PrimaryKeyConstraint('id', name='app_annotation_hit_histories_pkey') ) with op.batch_alter_table('app_annotation_hit_histories', schema=None) as batch_op: batch_op.create_index('app_annotation_hit_histories_account_idx', ['account_id'], unique=False) batch_op.create_index('app_annotation_hit_histories_annotation_idx', ['annotation_id'], unique=False) batch_op.create_index('app_annotation_hit_histories_app_idx', ['app_id'], unique=False) with op.batch_alter_table('app_model_configs', schema=None) as batch_op: batch_op.add_column(sa.Column('annotation_reply', sa.Text(), nullable=True)) with op.batch_alter_table('dataset_collection_bindings', schema=None) as batch_op: batch_op.add_column(sa.Column('type', sa.String(length=40), server_default=sa.text("'dataset'::character varying"), nullable=False)) with op.batch_alter_table('message_annotations', schema=None) as batch_op: batch_op.add_column(sa.Column('question', sa.Text(), nullable=True)) batch_op.add_column(sa.Column('hit_count', sa.Integer(), server_default=sa.text('0'), nullable=False)) batch_op.alter_column('conversation_id', existing_type=postgresql.UUID(), nullable=True) batch_op.alter_column('message_id', existing_type=postgresql.UUID(), nullable=True) # ### end Alembic commands ### def downgrade(): # ### commands auto generated by Alembic - please adjust! ### with op.batch_alter_table('message_annotations', schema=None) as batch_op: batch_op.alter_column('message_id', existing_type=postgresql.UUID(), nullable=False) batch_op.alter_column('conversation_id', existing_type=postgresql.UUID(), nullable=False) batch_op.drop_column('hit_count') batch_op.drop_column('question') with op.batch_alter_table('dataset_collection_bindings', schema=None) as batch_op: batch_op.drop_column('type') with op.batch_alter_table('app_model_configs', schema=None) as batch_op: batch_op.drop_column('annotation_reply') with op.batch_alter_table('app_annotation_hit_histories', schema=None) as batch_op: batch_op.drop_index('app_annotation_hit_histories_app_idx') batch_op.drop_index('app_annotation_hit_histories_annotation_idx') batch_op.drop_index('app_annotation_hit_histories_account_idx') op.drop_table('app_annotation_hit_histories') # ### end Alembic commands ### ``` ### Migration Script: `5fda94355fce_custom_disclaimer.py` ```py """Custom Disclaimer Revision ID: 5fda94355fce Revises: 47cc7df8c4f3 Create Date: 2024-05-10 20:04:45.806549 """ import sqlalchemy as sa from alembic import op import models as models # revision identifiers, used by Alembic. revision = '5fda94355fce' down_revision = '47cc7df8c4f3' branch_labels = None depends_on = None def upgrade(): # ### commands auto generated by Alembic - please adjust! ### with op.batch_alter_table('recommended_apps', schema=None) as batch_op: batch_op.add_column(sa.Column('custom_disclaimer', sa.String(length=255), nullable=True)) with op.batch_alter_table('sites', schema=None) as batch_op: batch_op.add_column(sa.Column('custom_disclaimer', sa.String(length=255), nullable=True)) with op.batch_alter_table('tool_api_providers', schema=None) as batch_op: batch_op.add_column(sa.Column('custom_disclaimer', sa.String(length=255), nullable=True)) # ### end Alembic commands ### def downgrade(): # ### commands auto generated by Alembic - please adjust! ### with op.batch_alter_table('tool_api_providers', schema=None) as batch_op: batch_op.drop_column('custom_disclaimer') with op.batch_alter_table('sites', schema=None) as batch_op: batch_op.drop_column('custom_disclaimer') with op.batch_alter_table('recommended_apps', schema=None) as batch_op: batch_op.drop_column('custom_disclaimer') # ### end Alembic commands ### ``` ### Migration Script: `246ba09cbbdb_add_app_anntation_setting.py` ```py """add_app_anntation_setting Revision ID: 246ba09cbbdb Revises: 714aafe25d39 Create Date: 2023-12-14 11:26:12.287264 """ import sqlalchemy as sa from alembic import op from sqlalchemy.dialects import postgresql # revision identifiers, used by Alembic. revision = '246ba09cbbdb' down_revision = '714aafe25d39' branch_labels = None depends_on = None def upgrade(): # ### commands auto generated by Alembic - please adjust! ### op.create_table('app_annotation_settings', sa.Column('id', postgresql.UUID(), server_default=sa.text('uuid_generate_v4()'), nullable=False), sa.Column('app_id', postgresql.UUID(), nullable=False), sa.Column('score_threshold', sa.Float(), server_default=sa.text('0'), nullable=False), sa.Column('collection_binding_id', postgresql.UUID(), nullable=False), sa.Column('created_user_id', postgresql.UUID(), nullable=False), sa.Column('created_at', sa.DateTime(), server_default=sa.text('CURRENT_TIMESTAMP(0)'), nullable=False), sa.Column('updated_user_id', postgresql.UUID(), nullable=False), sa.Column('updated_at', sa.DateTime(), server_default=sa.text('CURRENT_TIMESTAMP(0)'), nullable=False), sa.PrimaryKeyConstraint('id', name='app_annotation_settings_pkey') ) with op.batch_alter_table('app_annotation_settings', schema=None) as batch_op: batch_op.create_index('app_annotation_settings_app_idx', ['app_id'], unique=False) with op.batch_alter_table('app_model_configs', schema=None) as batch_op: batch_op.drop_column('annotation_reply') # ### end Alembic commands ### def downgrade(): # ### commands auto generated by Alembic - please adjust! ### with op.batch_alter_table('app_model_configs', schema=None) as batch_op: batch_op.add_column(sa.Column('annotation_reply', sa.TEXT(), autoincrement=False, nullable=True)) with op.batch_alter_table('app_annotation_settings', schema=None) as batch_op: batch_op.drop_index('app_annotation_settings_app_idx') op.drop_table('app_annotation_settings') # ### end Alembic commands ### ``` Ensure that you have the latest migration scripts and that your database is in sync with these scripts. You can do this by running the following commands: 1. **Check for new migrations:** ```sh flask db migrate ``` 2. **Apply the migrations:** ```sh flask db upgrade ``` Additionally, Dify has a GitHub workflow to test database migrations on pull requests to the main branch. This ensures that migrations are validated before being merged. Here is the relevant part of the workflow: ```yml name: DB Migration Test on: pull_request: branches: - main paths: - api/migrations/** concurrency: group: db-migration-test-${{ github.ref }} cancel-in-progress: true jobs: db-migration-test: runs-on: ubuntu-latest strategy: matrix: python-version: - "3.10" steps: - name: Checkout code uses: actions/checkout@v4 - name: Install Poetry uses: abatilo/actions-poetry@v3 - name: Set up Python ${{ matrix.python-version }} uses: actions/setup-python@v5 with: python-version: ${{ matrix.python-version }} cache: 'poetry' cache-dependency-path: | api/pyproject.toml api/poetry.lock - name: Install dependencies run: poetry install -C api - name: Set up Middleware uses: hoverkraft-tech/compose-action@v2.0.0 with: compose-file: | docker/docker-compose.middleware.yaml services: | db - name: Prepare configs run: | cd api cp .env.example .env - name: Run DB Migration run: | cd api poetry run python -m flask db upgrade ``` If you still encounter validation errors, it might be due to conflicts or missing dependencies in the migration scripts. Double-check the `down_revision` and ensure that all previous migrations have been applied correctly <sup>[[1]](https://github.com/langgenius/dify/blob/main/api/migrations/versions/e1901f623fd0_add_annotation_reply.py)</sup><sup>[[2]](https://github.com/langgenius/dify/blob/main/.github/workflows/db-migration-test.yml)</sup><sup>[[3]](https://github.com/langgenius/dify/blob/main/api/migrations/versions/5fda94355fce_custom_disclaimer.py)</sup><sup>[[4]](https://github.com/langgenius/dify/blob/main/api/migrations/versions/246ba09cbbdb_add_app_anntation_setting.py)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:04:38 -05:00
Author
Owner
Copy Link
Copy Source

@bowenliang123 commented on GitHub (Jun 13, 2024):

Hi, the db migration commands works well in CI jobs with the latest fixes for Pydantic 2.x migration in #5171.
CI logs:
https://github.com/langgenius/dify/actions/runs/9507160967/job/26205995254?pr=5176#step:8:1

Would you like to try again on the latest commit of the main branch?

@bowenliang123 commented on GitHub (Jun 13, 2024): Hi, the db migration commands works well in CI jobs with the latest fixes for Pydantic 2.x migration in #5171. CI logs: https://github.com/langgenius/dify/actions/runs/9507160967/job/26205995254?pr=5176#step:8:1 Would you like to try again on the latest commit of the main branch?
yindo commented 2026-02-21 18:04:39 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jun 13, 2024):

Can not reproduce this problem, I just tried this command morning.

None of PyTorch, TensorFlow >= 2.0, or Flax have been found. Models won't be available and only tokenizers, configuration and file/data utilities can be used.
2024-06-14 00:36:14.908 WARNING [MainThread] [extensible.py:71] - Missing cloud_service.py file in /Users/Li.Zheng/Program/dify/api/core/moderation/cloud_service, Skip.
2024-06-14 00:36:14.912 WARNING [MainThread] [extensible.py:71] - Missing weather_search.py file in /Users/Li.Zheng/Program/dify/api/core/external_data_tool/weather_search, Skip.
2024-06-14 00:36:14.916 WARNING [MainThread] [ext_mail.py:50] - MAIL_TYPE is not set
INFO  [alembic.runtime.migration] Context impl PostgresqlImpl.
INFO  [alembic.runtime.migration] Will assume transactional DDL.
@crazywoola commented on GitHub (Jun 13, 2024): Can not reproduce this problem, I just tried this command morning. ``` None of PyTorch, TensorFlow >= 2.0, or Flax have been found. Models won't be available and only tokenizers, configuration and file/data utilities can be used. 2024-06-14 00:36:14.908 WARNING [MainThread] [extensible.py:71] - Missing cloud_service.py file in /Users/Li.Zheng/Program/dify/api/core/moderation/cloud_service, Skip. 2024-06-14 00:36:14.912 WARNING [MainThread] [extensible.py:71] - Missing weather_search.py file in /Users/Li.Zheng/Program/dify/api/core/external_data_tool/weather_search, Skip. 2024-06-14 00:36:14.916 WARNING [MainThread] [ext_mail.py:50] - MAIL_TYPE is not set INFO [alembic.runtime.migration] Context impl PostgresqlImpl. INFO [alembic.runtime.migration] Will assume transactional DDL. ```
yindo commented 2026-02-21 18:04:39 -05:00
Author
Owner
Copy Link
Copy Source

@XiaoLey commented on GitHub (Jun 13, 2024):

Can not reproduce this problem, I just tried this command morning.

None of PyTorch, TensorFlow >= 2.0, or Flax have been found. Models won't be available and only tokenizers, configuration and file/data utilities can be used.
2024-06-14 00:36:14.908 WARNING [MainThread] [extensible.py:71] - Missing cloud_service.py file in /Users/Li.Zheng/Program/dify/api/core/moderation/cloud_service, Skip.
2024-06-14 00:36:14.912 WARNING [MainThread] [extensible.py:71] - Missing weather_search.py file in /Users/Li.Zheng/Program/dify/api/core/external_data_tool/weather_search, Skip.
2024-06-14 00:36:14.916 WARNING [MainThread] [ext_mail.py:50] - MAIL_TYPE is not set
INFO  [alembic.runtime.migration] Context impl PostgresqlImpl.
INFO  [alembic.runtime.migration] Will assume transactional DDL.

It appears that this issue has already been fixed a few hours ago. I have now pulled the latest code from the main branch and it works fine.

Thanks!

@XiaoLey commented on GitHub (Jun 13, 2024): > Can not reproduce this problem, I just tried this command morning. > > ``` > None of PyTorch, TensorFlow >= 2.0, or Flax have been found. Models won't be available and only tokenizers, configuration and file/data utilities can be used. > 2024-06-14 00:36:14.908 WARNING [MainThread] [extensible.py:71] - Missing cloud_service.py file in /Users/Li.Zheng/Program/dify/api/core/moderation/cloud_service, Skip. > 2024-06-14 00:36:14.912 WARNING [MainThread] [extensible.py:71] - Missing weather_search.py file in /Users/Li.Zheng/Program/dify/api/core/external_data_tool/weather_search, Skip. > 2024-06-14 00:36:14.916 WARNING [MainThread] [ext_mail.py:50] - MAIL_TYPE is not set > INFO [alembic.runtime.migration] Context impl PostgresqlImpl. > INFO [alembic.runtime.migration] Will assume transactional DDL. > ``` It appears that this issue has already been fixed a few hours ago. I have now pulled the latest code from the main branch and it works fine. Thanks!
yindo commented 2026-02-21 18:04:39 -05:00
Author
Owner
Copy Link
Copy Source

@bowenliang123 commented on GitHub (Jun 13, 2024):

👍🏻 Credit goes to @takatost .

@bowenliang123 commented on GitHub (Jun 13, 2024): 👍🏻 Credit goes to @takatost .
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🐞 bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#4076
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?