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]Error processing environment variables: envconfig.Process: assigning S3_USE_AWS to S3UseAWS #140

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

Originally created by @tomy-kyu on GitHub (Jun 17, 2025).

Originally assigned to: @41tair on GitHub.

Thank you for your continued support.
I applied the latest version of the main build up to 3d1e2ab using dify-plugin-daemon, but it kept restarting in panic mode, so I am reporting this issue.
I checked the logs of the target container and found the following error messages.

2025/06/18 00:17:22 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({0x26454a8, 0x5}, {0x26a3945?, 0xc0002e8588?}, 0x1, {0xc00059ff28, 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

As far as I can tell from docker-compose.yaml, there were no changes in the settings when using generate_docker_compose.
Both have the following settings.

Parameters implemented in common at the beginning of api/worker/plugin_daemon

  PLUGIN_S3_USE_AWS: ${PLUGIN_S3_USE_AWS:-}

The settings in the container are as follows.

      S3_USE_AWS: ${PLUGIN_S3_USE_AWS:-}

Since the variable is not set in .env, we understand that the default value is defined (not set).

The 0.1.2-local version on dockerhub worked, so it is likely that updates after that triggered the issue.

Thank you for your cooperation.

Originally created by @tomy-kyu on GitHub (Jun 17, 2025). Originally assigned to: @41tair on GitHub. Thank you for your continued support. I applied the latest version of the main build up to 3d1e2ab using dify-plugin-daemon, but it kept restarting in panic mode, so I am reporting this issue. I checked the logs of the target container and found the following error messages. ``` 2025/06/18 00:17:22 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({0x26454a8, 0x5}, {0x26a3945?, 0xc0002e8588?}, 0x1, {0xc00059ff28, 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 ``` As far as I can tell from docker-compose.yaml, there were no changes in the settings when using generate_docker_compose. Both have the following settings. Parameters implemented in common at the beginning of api/worker/plugin_daemon ``` PLUGIN_S3_USE_AWS: ${PLUGIN_S3_USE_AWS:-} ``` The settings in the container are as follows. ``` S3_USE_AWS: ${PLUGIN_S3_USE_AWS:-} ``` Since the variable is not set in .env, we understand that the default value is defined (not set). The 0.1.2-local version on dockerhub worked, so it is likely that updates after that triggered the issue. Thank you for your cooperation.
yindo closed this issue 2026-02-16 00:20:04 -05:00
yindo commented 2026-02-16 00:20:04 -05:00
Author
Owner
Copy Link
Copy Source

@tomy-kyu commented on GitHub (Jun 17, 2025):

The version of dify-api is 1.4.3, which includes updates up to commit 2440ac43b191691548936587a58ae7b12ea1f866.

@tomy-kyu commented on GitHub (Jun 17, 2025): The version of dify-api is 1.4.3, which includes updates up to commit 2440ac43b191691548936587a58ae7b12ea1f866.
yindo commented 2026-02-16 00:20:05 -05:00
Author
Owner
Copy Link
Copy Source

@41tair commented on GitHub (Jun 17, 2025):

I will fix it in dify repo. You can temporarily work around this issue by manually adding the environment variables. https://github.com/langgenius/dify-plugin-daemon/blob/main/README.md?plain=1#L51

@41tair commented on GitHub (Jun 17, 2025): I will fix it in dify repo. You can temporarily work around this issue by manually adding the environment variables. https://github.com/langgenius/dify-plugin-daemon/blob/main/README.md?plain=1#L51
yindo commented 2026-02-16 00:20:05 -05:00
Author
Owner
Copy Link
Copy Source

@tomy-kyu commented on GitHub (Jun 18, 2025):

Thank you for letting us know about the workaround.

We have temporarily switched the branch to 0.1.2, rebuilt the Docker image, and applied it.
In particular, for configurations under a proxy, which are common in Japan, users who have customized images should be cautious.

The dependencies between dify-api 1.4.3 and dify-plugin-daemon 0.1.2 are strong, and using images prior to dify-plugin-daemon-0.1.1 may result in unexpected issues such as the agent failing to respond.

@tomy-kyu commented on GitHub (Jun 18, 2025): Thank you for letting us know about the workaround. We have temporarily switched the branch to 0.1.2, rebuilt the Docker image, and applied it. In particular, for configurations under a proxy, which are common in Japan, users who have customized images should be cautious. The dependencies between dify-api 1.4.3 and dify-plugin-daemon 0.1.2 are strong, and using images prior to dify-plugin-daemon-0.1.1 may result in unexpected issues such as the agent failing to respond.
yindo commented 2026-02-16 00:20:05 -05:00
Author
Owner
Copy Link
Copy Source

@tomy-kyu commented on GitHub (Jun 18, 2025):

Thank you very much for your cooperation.

@tomy-kyu commented on GitHub (Jun 18, 2025): Thank you very much for your cooperation.
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#140
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?