Skip to content

Conversation

@cyberflying
Copy link
Contributor

Purpose

  • update custom data format, to adapt to the script in 04 custom data python: timestamp_format = "%Y-%m-%d %H_%M_%S"
  • Processing sample data correctly handles the escaped character %3A, which represents _. However, this handling is missing when processing custom data. Different use cases rely on inconsistent data formats, leading to confusion. It is recommended to standardize all data formats and apply the same decoding logic across all scenarios.

Does this introduce a breaking change?

  • Yes
  • No

Golden Path Validation

  • I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

  • I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid

  • ...

Other Information

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant