dybyte commented on PR #10503:
URL: https://github.com/apache/seatunnel/pull/10503#issuecomment-3957291841

   > > > <img alt="image" width="2000" height="312" 
src="https://private-user-images.githubusercontent.com/200727089/554473251-a44ea463-80ea-4927-9478-f7af731a112f.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NzE5OTI2ODAsIm5iZiI6MTc3MTk5MjM4MCwicGF0aCI6Ii8yMDA3MjcwODkvNTU0NDczMjUxLWE0NGVhNDYzLTgwZWEtNDkyNy05NDc4LWY3YWY3MzFhMTEyZi5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMjI1JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDIyNVQwNDA2MjBaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT05YWYxODQ3MTk5NWZmYTA5MDMxNzIwNzYyMjkwYmQ3NTVhMWVjNjhmZTIxMjM0OGEzNTA5MzAyYWQ4MTViNDY4JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.KEpYtx5hkDGarsRZjTRso_OnQcLtOUTTEGhikcactzk";>
   > > > Is this current fix intended to resolve this issue in CI?
   > > 
   > > 
   > > Yes, this fix is intended to resolve that issue.
   > 
   > Okay, I’ve updated the image version to 1.15 on the demo branch, and the 
CI is passing.I’m also a bit curious—how did you figure out it was caused by 
the version issue?
   
   I noticed that the failures started recently and became consistently 
reproducible rather than intermittent.
   
   Since the CI was using the `qdrant:latest` image, I suspected that a recent 
image update might have introduced a breaking change. I checked the release 
notes and found compatibility-related changes in the newer versions of Qdrant.
   After downgrading the image version, the CI started passing consistently.
   
   For reference: https://github.com/qdrant/qdrant/releases/tag/v1.17.0


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