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
which appear to occur when clients provide a from parameter specified as a date rather than a date+time, like the following: /catalog/oai?verb=ListRecords&metadataPrefix=oai_dc&from=2023-11-04
The error only seems to occur if the result would return enough results to trigger resumption token behaviors. I'm not sure where it's happening in the stack, but it would seem that when the from (or until) field doesn't specify time of day, it gets deserialized as a Date, while when it is specified as a full UTC timestamp (with Z as the timezone) it gets deserialized as a DateTime. Only the latter has a utc method.
The text was updated successfully, but these errors were encountered:
In our hyrax 4 application, which is using blacklight-oai-provider 7.0.2, we are getting periodic errors like the following:
which appear to occur when clients provide a
from
parameter specified as a date rather than a date+time, like the following:/catalog/oai?verb=ListRecords&metadataPrefix=oai_dc&from=2023-11-04
The error only seems to occur if the result would return enough results to trigger resumption token behaviors. I'm not sure where it's happening in the stack, but it would seem that when the
from
(oruntil
) field doesn't specify time of day, it gets deserialized as a Date, while when it is specified as a full UTC timestamp (with Z as the timezone) it gets deserialized as a DateTime. Only the latter has autc
method.The text was updated successfully, but these errors were encountered: