clairemcginty commented on PR #36838: URL: https://github.com/apache/beam/pull/36838#issuecomment-3554394143
> Thanks @kennknowles, @clairemcginty is planning to do some testing today. Ran our [tests](https://github.com/spotify/scio/actions/runs/19513763696/job/55860003717) with the locally built snapshot, still seeing the following error: ``` [info] Cause: java.lang.IllegalArgumentException: Cannot output with timestamp 1970-01-01T00:00:00.001Z. Output timestamps must be no earlier than the timestamp of the current input or timer (1970-01-01T00:00:00.010Z) minus the allowed skew (0 milliseconds) and no later than 294247-01-10T04:00:54.775Z. See the DoFn#getAllowedTimestampSkew() Javadoc for details on changing the allowed skew. [info] at org.apache.beam.runners.core.SimpleDoFnRunner.checkTimestamp(SimpleDoFnRunner.java:263) [info] at org.apache.beam.runners.core.SimpleDoFnRunner.access$1300(SimpleDoFnRunner.java:89) [info] at org.apache.beam.runners.core.SimpleDoFnRunner$DoFnProcessContext.lambda$outputWindowedValue$0(SimpleDoFnRunner.java:464) [info] at org.apache.beam.sdk.values.WindowedValues$Builder.output(WindowedValues.java:222) [info] at org.apache.beam.runners.core.SimpleDoFnRunner$DoFnProcessContext.outputWindowedValue(SimpleDoFnRunner.java:467) [info] at org.apache.beam.sdk.transforms.DoFnOutputReceivers$WindowedContextOutputReceiver.output(DoFnOutputReceivers.java:123) [info] at org.apache.beam.sdk.values.WindowedValues$Builder.output(WindowedValues.java:222) [info] at org.apache.beam.sdk.transforms.DoFn$OutputReceiver.outputWindowedValue(DoFn.java:416) [info] at com.spotify.scio.transforms.FileDownloadDoFn.lambda$processElement$0(FileDownloadDoFn.java:105) [info] at com.spotify.scio.transforms.FileDownloadDoFn.flush(FileDownloadDoFn.java:141) [info] ... ``` is it possible the precision of the timestamp checks changed, or something like that? `1970-01-01T00:00:00.001Z` and `1970-01-01T00:00:00.010Z` are only off by a millisecond -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
