Description

• Added timezone support for the datetime_tools, so now it will automatically extract the x-timezone from the headers from context, which will be used to format the current time.

  • If the x-timezone is not present in the headers, default UTC time is used.
  • The documentations should also be clear now.

• Fixed a small issue in NeMo-Agent-Toolkit/src/nat/builder/user_interaction_manager.py. Before the timestamp is in UTC (as seen by the Z suffix in the timestamp), but the timestamp is in the local timezone, which is most likely not in UTC timezone.

• Made a tiny change for the NeMo-Agent-Toolkit-UI repository. So now the front-end also stores the timezone in IANA format in its header to be sent to the backend.

  • The change: Adding timezone info to request header NeMo-Agent-Toolkit-UI#38

FAQs

Q: why did you use UTC time by default?

• A: UTC is industry standard's default timezone.

Q: why did you use IANA format for timezone?

• A: IANA time zone (like "America/New_York" or "Etc/UTC") provides a standardized identifier that encodes daylight-saving rules and ensures consistent behavior across platforms and regions, and also widely accepted in industry.

Demo

Closes #445

By Submitting this PR I confirm:

• I am familiar with the Contributing Guidelines.
• We require that all contributors "sign-off" on their commits. This certifies that the contribution is your original work, or you have rights to submit it under the same license, or a compatible license.
  • Any contribution which contains commits that are not Signed-Off will not be accepted.
• When the PR is ready for review, new or existing tests cover these changes.
• When the PR is ready for review, the documentation is up to date with these changes.