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

[Bug] localtime_to_timestamp tool throw 'no attribute localize' error when it executes without specifying a timezone parameter #15950

New Issue
Closed
opened 2026-02-21 19:24:05 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 19:24:05 -05:00
Owner
Copy Link
Copy Source

Originally created by @goofy-z on GitHub (Aug 6, 2025).

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.7.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

  1. create localtime_to_timestamp tool node
  2. click the timezone field and not input any content
    image
  3. run node in single step

✔️ Expected Behavior

It should run successfully without entering the timezone parameter

❌ Actual Behavior

node will throw an error like this
image

Originally created by @goofy-z on GitHub (Aug 6, 2025). ### 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.7.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce 1. create localtime_to_timestamp tool node 2. click the timezone field and not input any content <img width="409" height="307" alt="image" src="https://github.com/user-attachments/assets/c9805132-19df-4014-813d-7a3b27678e15" /> 3. run node in single step ### ✔️ Expected Behavior It should run successfully without entering the timezone parameter ### ❌ Actual Behavior node will throw an error like this <img width="414" height="468" alt="image" src="https://github.com/user-attachments/assets/9083fbc4-88ea-459f-bbb2-3869f5e39cd7" />
yindo added the 🐞 bug label 2026-02-21 19:24:05 -05:00
yindo closed this issue 2026-02-21 19:24:05 -05:00
yindo commented 2026-02-21 19:24:06 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 6, 2025):

Hi @goofy-z! I'm Dosu and I’m helping the dify team.

The error happens because when the timezone parameter is left empty, the backend sets it to None and then defaults to the system's local timezone using datetime.now().astimezone().tzinfo. This object is a standard Python datetime.timezone, which does not have a .localize() method (that method is specific to pytz timezones). The code then tries to call .localize() on this object, causing the error you see.

There is an open pull request that directly fixes this issue by ensuring the tool handles empty or missing timezone parameters correctly, so the error won't occur in future versions. You can track the status and details of the fix here: PR #23517.

As a temporary workaround, you can manually edit your local api/core/tools/builtin_tool/providers/time/tools/localtime_to_timestamp.py to ensure that when the timezone is not specified, you default to a valid pytz timezone (like 'Asia/Shanghai' or 'UTC') instead of using the system tzinfo object. This will prevent the .localize() error until the official fix is merged and released.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Aug 6, 2025): <!-- Greeting --> Hi @goofy-z! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> The error happens because when the timezone parameter is left empty, the backend sets it to None and then defaults to the system's local timezone using `datetime.now().astimezone().tzinfo`. This object is a standard Python `datetime.timezone`, which does not have a `.localize()` method (that method is specific to pytz timezones). The code then tries to call `.localize()` on this object, causing the error you see. There is an open pull request that directly fixes this issue by ensuring the tool handles empty or missing timezone parameters correctly, so the error won't occur in future versions. You can track the status and details of the fix here: [PR #23517](https://github.com/langgenius/dify/pull/23517). As a temporary workaround, you can manually edit your local `api/core/tools/builtin_tool/providers/time/tools/localtime_to_timestamp.py` to ensure that when the timezone is not specified, you default to a valid pytz timezone (like `'Asia/Shanghai'` or `'UTC'`) instead of using the system tzinfo object. This will prevent the `.localize()` error until the official fix is merged and released. <!-- 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/c9316f0f-b750-4a9a-86c5-fd3c019dd063?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/c9316f0f-b750-4a9a-86c5-fd3c019dd063?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/c9316f0f-b750-4a9a-86c5-fd3c019dd063?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/c9316f0f-b750-4a9a-86c5-fd3c019dd063?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/c9316f0f-b750-4a9a-86c5-fd3c019dd063?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/c9316f0f-b750-4a9a-86c5-fd3c019dd063?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/c9316f0f-b750-4a9a-86c5-fd3c019dd063?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&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/23531)
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#15950
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?