Is this a known issue? It's not possible to go in...
# confetti
b
Is this a known issue? It's not possible to go into the details of the talk AI and Kotlin: Perfect mix
j
yeah, I see same issue here with app.....will take a look shortly in IDE and check
👍 1
we had issue like this before I think when there'd been updates to schedule but I just re-synced now and still seeing same issue
I'm not seeing anything in client logs....will up level for those and check again. It seems to get data from cache ok but then fails when it tries to get updated data from backend. I also looked in backend logs and don't see any errors there
getting 200 from backend but doesn't seem to be expected data in response. @mbonnin just in case anything jumps out from this?
Copy code
2024-04-29 17:49:07.538 19473-19593 okhttp.OkHttpClient     dev.johnoreilly.confetti             I  [0 ms] callStart: Request{method=GET, url=<https://confetti-app.dev/graphql?operationName=GetSession&variables=%7B%22id%22%3A%22671939%22%7D&extensions=%7B%22persistedQuery%22%3A%7B%22version%22%3A1%2C%22sha256Hash%22%3A%221b83f8a549dfe609515ef4427f6f76c1a27e1df2c0f76a8603c33e8c3125f802%22%7D%7D>, headers=[Apollo-Require-Preflight:true, Accept:multipart/mixed;deferSpec=20220824, application/json, conference:kotlinconf2024]}
2024-04-29 17:49:07.539 19473-19593 okhttp.OkHttpClient     dev.johnoreilly.confetti             I  [1 ms] connectionAcquired: Connection{confetti-app.dev:443, proxy=DIRECT hostAddress=confetti-app.dev/34.120.192.247:443 cipherSuite=TLS_AES_128_GCM_SHA256 protocol=h2}
2024-04-29 17:49:07.546 19473-19593 okhttp.OkHttpClient     dev.johnoreilly.confetti             I  [7 ms] requestHeadersStart
2024-04-29 17:49:07.548 19473-19593 okhttp.OkHttpClient     dev.johnoreilly.confetti             I  [9 ms] requestHeadersEnd
2024-04-29 17:49:07.564 19473-19593 okhttp.OkHttpClient     dev.johnoreilly.confetti             I  [26 ms] responseHeadersStart
2024-04-29 17:49:07.565 19473-19593 okhttp.OkHttpClient     dev.johnoreilly.confetti             I  [27 ms] responseHeadersEnd: Response{protocol=h2, code=200, message=, url=<https://confetti-app.dev/graphql?operationName=GetSession&variables=%7B%22id%22%3A%22671939%22%7D&extensions=%7B%22persistedQuery%22%3A%7B%22version%22%3A1%2C%22sha256Hash%22%3A%221b83f8a549dfe609515ef4427f6f76c1a27e1df2c0f76a8603c33e8c3125f802%22%7D%7D>}
2024-04-29 17:49:07.569 19473-19593 okhttp.OkHttpClient     dev.johnoreilly.confetti             I  [30 ms] responseBodyStart
2024-04-29 17:49:07.569 19473-19593 okhttp.OkHttpClient     dev.johnoreilly.confetti             I  [31 ms] responseBodyEnd: byteCount=162
2024-04-29 17:49:07.571 19473-19593 okhttp.OkHttpClient     dev.johnoreilly.confetti             I  [32 ms] connectionReleased
2024-04-29 17:49:07.571 19473-19593 okhttp.OkHttpClient     dev.johnoreilly.confetti             I  [33 ms] callEnd
It does seem to point to case where this is cached session that no longer exists. It's still shown at https://kotlinconf.com/schedule/ fwiw
m
Yup, it's on me. Fix is here
👍 1
🎉 1
Too much content!
j
It looks happy now!
ah, sorry, thought it was but got same error again...thought that had been deployed
m
Mmm should be happy now, let me check
I've rerun the deploy. It failed on some
.tflock
file
Looks like a previous deployed was canceled in flight and did not release the terraform lock 👀
It should be happy again
PS: we should probably display the stale data if any, in case of error instead of failing the whole screen
🦜 1
j
Yeah, looks good now
🎉 1