Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

chronotope / chrono Public

Notifications You must be signed in to change notification settings
Fork 543
Star 3.4k

Code
Issues 139
Pull requests 31
Actions
Projects
Wiki
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Wiki
Security
Insights

Remove partial support for handling `-0000` offset#1411

Merged

pitdicker merged 3 commits intochronotope:mainchronotope/chrono:mainfrom pitdicker:remove_unknown_offsetpitdicker/chrono:remove_unknown_offsetCopy head branch name to clipboard

Feb 7, 2024

+34-31

Conversation Commits3 (3)Checks Files changed

Commits

Commits on Feb 7, 2024

Replace 86_400 with MAX_RFC3339_OFFSET
pitdicker
committed
Make range check more accurate, and add comment why it is not useless
pitdicker
committed
Remove incomplete parsing support for -0000 offset
pitdicker
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.