Project

Profile

Help

Bug #5479

closed

SaxonCS: new AtomicValue() given a DateTime or DateTimeOffset crashes

Added by Michael Kay almost 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
.NET API
Sprint/Milestone:
-
Start date:
2022-05-07
Due date:
% Done:

100%

Estimated time:
Legacy ID:
Applies to branch:
10, 11, trunk
Fix Committed on Branch:
11, trunk
Fixed in Maintenance Release:
Platforms:
.NET

Actions #1

Updated by Michael Kay almost 2 years ago

A unit test has been created to reproduce the problem.

Actions #2

Updated by Martin Honnen almost 2 years ago

The problem also exists in Saxon .NET 10.

Actions #3

Updated by Michael Kay almost 2 years ago

It took a while but I lost the new unit tests in a repo reorganisation, and I've just managed to recover them from Time Machine. For future reference, the test module is named TestXdmDateTimeDuration.cs

Actions #4

Updated by Michael Kay almost 2 years ago

  • Status changed from In Progress to Resolved
  • Applies to branch 10 added
  • Fix Committed on Branch 11, trunk added
  • Platforms .NET added

Fixed on the 11.x and 12.x branches.

I also found that the timezone offsets weren't being picked up correctly.

Actions #5

Updated by Debbie Lockett over 1 year ago

  • Status changed from Resolved to Closed
  • % Done changed from 0 to 100
  • Fixed in Maintenance Release 11.4 added

Bug fix applied in the Saxon 11.4 maintenance release.

Please register to edit this issue

Also available in: Atom PDF