Turbo stops using cache, error "skipping HTTP Request, too many failures have occurred"
dobesv opened this issue ยท 1 comments
dobesv commented
๐ Bug Report
Because this does not support all the operations used by turbo, turbo will just stop using it after a few failed requests.
When run in verbose mode you can see an error:
2023-03-17T15:31:40.766-0700 [DEBUG] turbo.analytics: failed to record cache usage analytics: error="skipping HTTP Request, too many failures have occurred"
2
The server output is like this:
โค YN0007: โ turborepo-remote-cache@npm:1.13.2 must be built because it never has been before or the last one failed
โค YN0000: โ turborepo-remote-cache@npm:1.13.2 STDERR npm WARN exec The following package was not found and will be installed: only-allow@1.1.1
โค YN0000: โ Completed in 2s 423ms
โค YN0000: Done with warnings in 34s 967ms
{"severity":"INFO","level":30,"time":1679091896878,"pid":21521,"hostname":"44cb917766de","message":"Server listening at http://0.0.0.0:4444"}
{"severity":"INFO","level":30,"time":1679091897852,"pid":21521,"hostname":"44cb917766de","reqId":"PRk_gsXKRoyq60Zzc71Yaw-0","req":{"method":"GET","url":"/v8/artifacts/851d9ae536aeee95?teamId=team_formative","hostname":"localhost:4444","remoteAddress":"127.0.0.1","remotePort":41986},"message":"incoming request"}
{"severity":"INFO","level":30,"time":1679091897897,"pid":21521,"hostname":"44cb917766de","reqId":"PRk_gsXKRoyq60Zzc71Yaw-1","req":{"method":"GET","url":"/v8/artifacts/e19892748780222a?teamId=team_formative","hostname":"localhost:4444","remoteAddress":"127.0.0.1","remotePort":41984},"message":"incoming request"}
{"severity":"INFO","level":30,"time":1679091898039,"pid":21521,"hostname":"44cb917766de","reqId":"PRk_gsXKRoyq60Zzc71Yaw-1","res":{"statusCode":200},"responseTime":141.249200001359,"message":"request completed"}
{"severity":"INFO","level":30,"time":1679091898047,"pid":21521,"hostname":"44cb917766de","reqId":"PRk_gsXKRoyq60Zzc71Yaw-0","res":{"statusCode":200},"responseTime":194.30381099879742,"message":"request completed"}
This is running the latest version every time, using yarn dlx
. Reproduced this today using 1.13.2
dobesv commented
I think I need to look into this more myself, sorry for the noise