langgenius/dify-plugin-daemon
1
0
Fork 0
mirror of https://github.com/langgenius/dify-plugin-daemon.git synced 2026-07-21 17:25:23 -04:00
Code Issues 111 Packages Projects Releases 10 Wiki Activity

[PANIC]处理环境变量时出错：envconfig.Process: 将 S3_USE_AWS 分配给 S3UseAWS #157

New Issue
Closed
opened 2026-02-16 00:20:12 -05:00 by yindo · 3 comments
yindo commented 2026-02-16 00:20:12 -05:00
Owner
Copy Link
Copy Source

Originally created by @owen-chang001 on GitHub (Jul 9, 2025).

[https://github.com/langgenius/dify-plugin-daemon/issues/350]

I encountered the above-mentioned issue again in the 1.5.1 update. With the same bug:

2025/07/09 05:10:10 main.go:19: [PANIC]Error processing environment variables: envconfig.Process: assigning S3_USE_AWS to S3UseAWS: converting '' to type bool. details: strconv.ParseBool: parsing "": invalid syntax
panic: [PANIC]Error processing environment variables: envconfig.Process: assigning S3_USE_AWS to S3UseAWS: converting '' to type bool. details: strconv.ParseBool: parsing "": invalid syntax

goroutine 1 [running]:
github.com/langgenius/dify-plugin-daemon/internal/utils/log.writeLog({0x265e168, 0x5}, {0x26bc6b7?, 0xc000633188?}, 0x1, {0xc00078ff28, 0x1, 0x1})
/app/internal/utils/log/log.go:40 +0x305
github.com/langgenius/dify-plugin-daemon/internal/utils/log.Panic(...)
/app/internal/utils/log/log.go:66
main.main()
/app/cmd/server/main.go:19 +0x9f

Checking the docker-compose.yaml, it was found that the following values have no default assignment. ```
PLUGIN_S3_USE_AWS: ${PLUGIN_S3_USE_AWS:-}

But I configured the .env file, and the default value of PLUGIN_S3_USE_AWS inside it is false. 
I temporarily solved this issue by setting a default value of `false` for `PLUGIN_S3_USE_AWS: ${PLUGIN_S3_USE_AWS:-}` in the `docker-compose.yaml`. Is this bug caused by the configuration information in `.env` not being accurately assigned to `docker-compose.yaml` or something?
Originally created by @owen-chang001 on GitHub (Jul 9, 2025). [https://github.com/langgenius/dify-plugin-daemon/issues/350] I encountered the above-mentioned issue again in the 1.5.1 update. With the same bug: ``` 2025/07/09 05:10:10 main.go:19: [PANIC]Error processing environment variables: envconfig.Process: assigning S3_USE_AWS to S3UseAWS: converting '' to type bool. details: strconv.ParseBool: parsing "": invalid syntax panic: [PANIC]Error processing environment variables: envconfig.Process: assigning S3_USE_AWS to S3UseAWS: converting '' to type bool. details: strconv.ParseBool: parsing "": invalid syntax goroutine 1 [running]: github.com/langgenius/dify-plugin-daemon/internal/utils/log.writeLog({0x265e168, 0x5}, {0x26bc6b7?, 0xc000633188?}, 0x1, {0xc00078ff28, 0x1, 0x1}) /app/internal/utils/log/log.go:40 +0x305 github.com/langgenius/dify-plugin-daemon/internal/utils/log.Panic(...) /app/internal/utils/log/log.go:66 main.main() /app/cmd/server/main.go:19 +0x9f ``` Checking the docker-compose.yaml, it was found that the following values have no default assignment. ``` PLUGIN_S3_USE_AWS: ${PLUGIN_S3_USE_AWS:-} ``` But I configured the .env file, and the default value of PLUGIN_S3_USE_AWS inside it is false. I temporarily solved this issue by setting a default value of `false` for `PLUGIN_S3_USE_AWS: ${PLUGIN_S3_USE_AWS:-}` in the `docker-compose.yaml`. Is this bug caused by the configuration information in `.env` not being accurately assigned to `docker-compose.yaml` or something?
yindo closed this issue 2026-02-16 00:20:12 -05:00
yindo commented 2026-02-16 00:20:13 -05:00
Author
Owner
Copy Link
Copy Source

@fsh2102 commented on GitHub (Jul 13, 2025):

问题解决了吗

@fsh2102 commented on GitHub (Jul 13, 2025): 问题解决了吗
yindo commented 2026-02-16 00:20:13 -05:00
Author
Owner
Copy Link
Copy Source

@owen-chang001 commented on GitHub (Jul 14, 2025):

重新安装了一次, 问题已经解决

@owen-chang001 commented on GitHub (Jul 14, 2025): 重新安装了一次, 问题已经解决
yindo commented 2026-02-16 00:20:13 -05:00
Author
Owner
Copy Link
Copy Source

@fsh2102 commented on GitHub (Jul 22, 2025):

重新安装了一次, 问题已经解决

好的感谢

@fsh2102 commented on GitHub (Jul 22, 2025): > 重新安装了一次, 问题已经解决 好的感谢
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Windows
bug
cmd
documentation
enhancement
go
good first issue
plugin-daemon
pull-request
Mirrored from GitHub Pull Request
 question
No Label
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-plugin-daemon#157
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?