user can specify arbitrary valid int64_t value as the timestamp
Open
class/enhancement
- Dominant language
- C++
- Stars
- 1.9k
- Forks
- 432
- PR merge metrics
- No merged PRs in 30d
Description
This issue has no description.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue body names no files, tests, or entry points. Start by locating timestamp handling and its tests in the Tera codebase, then clarify the accepted int64_t range, the user-facing entry point, and the test that should demonstrate support for arbitrary valid values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100