Closed kitsonk closed 1 year ago
For me they all look the same; what exactly is the issue?
Details were in https://github.com/denoland/dotland/issues/2472
Going to https://deno.land/std@0.155.0/http/mod.ts :
Compare that with https://deno.land/std@0.153.0/http/mod.ts / https://deno.land/std@0.154.0/http/mod.ts :
The specific issue with
std
is fixed. The "problem" is that some modules are too CPU intensive to be able to complete the documentation "lazily" on Deno Deploy. We are going through a fair amount of change internally on how we handle this, and we haven't integrated the updating as part of release process yet.Since this started out with the
std
issue and the title reflects that, I am going to close this now the 1.155.0 has been manually loaded and open a new issue around the allo_arguments as it seems to be unreleated (a forced reload didn't resolve the issue, like it did forstd
).
Looks like this is no longer reproducible on the link I shared. Feel free to close. Perhaps another example will come up.
Ah, actually is was broken for me, then I did a reload manually, but it didn't fix it because I forgot the api isolate caches the response, so it fixed it.
We need to have a cleanup job that runs every hour that mops up failed loads because of CPU time limits.
The cause of this is that it's caching the blank page that's rendered due to CPU time limits?
Is the caching behavior part of Deno Deploy, Fresh, or the code in dotland/docland?
This seems to be fixed.
From @chrisirhc:
This weird state where the left-hand panel seems to be affecting other modules/versions randomly: