lostluck commented on issue #32559:
URL: https://github.com/apache/beam/issues/32559#issuecomment-2375468157

   > > question about whether the bug still exists in 2.59.0? Prism is under 
active development, so it's not impossible it was fixed between versions.
   > 
   > Great news! I upgraded to `2.59.0` and the panics I saw earlier are indeed 
gone! w.r.t. where the panic was occurring, I can pull that stack trace if you 
would like, but considering it no longer is occurring maybe thats unneeded?
   
   Glad to hear it! I don't think the stack trace is necessary now, if the 
panic is gone. I recall that I had to fix timer handling wrt bytes being 
incorrectly interpreted, to pass additional tests so that's probably what did 
it.
   
   Closing this issue for now.
   
   


-- 
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]

Reply via email to