elikoga
elikoga
I believe this is an issue with the current documentation and the sudden (undocumented change) from 1.4 to 1.5 regarding io behaviour.
@c0bra is your rendering plugin still usable? I'm using the vue renderer in my svelte application currently
Found the issue: https://github.com/sveltejs/kit/blob/062f38e9c1716089d3998da9110627c48190ed11/packages/kit/src/core/sync/create_manifest_data/index.js#L386-L388 This comparison function does the sorting of values. ``` a.segments: [[{"...stuff",dynamic},{".json",not-dynamic]] a.id: [...stuff].json b.segments: [[{"...stuff",dynamic}][{"specific.json",not-dynamic]] b.id [...stuff]/specific.json ``` Since The first argument has more parts in...
This is impacted by #5748 and could possibly be closed by that?
This is very related to #4007 but not quite the same complaint I think. I looked in the code and I think the solution is to _not_ use the cache...
We also need to look at https://github.com/nixos/nix/blob/master/src/libfetchers/git.cc#L500-L502
I'm thinking that different download calls should have different (or 0) tarball ttl. The github api calls for example go through the cache too, but I don't see how tarballTtl...
> the problem that the cache is currently per-user not a problem imo
My main complaint is that `tarball-ttl` is used to cache requests that are definetly not tarballs (like git hoster api requests)
- [ ] buildout versionen in supervisor component exposen - [ ] supervisor version hochziehen