xtdb 2021-01-11 | Slack Archive

nivekuil11:01:49

I'm puzzled by this log line: 2021-01-11 03:40:32 2021-01-11T11:40:32.623Z 395282b8415d WARN [crux.s3:326] - S3 key not found: UnsafeBuffer{addressOffset=16, capacity=21, byteArray=[[email protected], byteBuffer=null} it seems crux.s3 has never been 326 lines long and s3-key is created by str so it shouldn't be an UnsafeBuffer in the log? https://github.com/juxt/crux/blob/master/crux-s3/src/crux/s3.clj#L54

refset18:01:35

Hi @U797MAJ8M it's not clear what might have happened here - we'll dig into it soon though! Just to confirm, is it just this log line that you noticed? No other errors/anomalies during API operations?

nivekuil04:01:00

glancing at the code, I would actually expect an exception to be thrown at (.get fut) here since it should be nil if I'm seeing the "s3 key not found" message? https://github.com/juxt/crux/blob/master/crux-s3/src/crux/s3.clj#L62

refset09:01:16

Thanks for digging in further - I will take a proper look at this today 🙂

refset14:01:56

Circling back round to this - we think the latest dev-SNAPSHOT version should have resolved this, assuming it was caused by the eql/project issue resolved here: https://github.com/juxt/crux/commit/33dcef2f444cf6e2f78f076586b68e544d4e44c1 It would be interesting if you are able to confirm that, but hopefully it doesn't come up again anyway.

nivekuil21:01:55

I think so!

2021-01-11

Channels