NASA-AMMOS / NASA-AMMOS/plandev
Misformatted timestamp in scheduling error response
Open
Nobody has claimed this yet.
bug
- Dominant language
- Java
- Stars
- 128
- Forks
- 33
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 12
Description
I noticed a small formatting bug with the timestamp in scheduling error responses. I'm getting two decimal points and the numbers after the second decimal point seem to be a partial repetition of the microseconds.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is identified in the issue. Start by reproducing a scheduling error response and tracing where its timestamp is formatted; done means the response has one decimal separator and the microseconds are not repeated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100