Worker caching weirdness
We are using a web KV store. For a specific key we have written three blobs of JSON - each write with a different number of array elements in this order (5, 8, and 16). We have a simple windmill typescript script that fetches the data and logs the number of array elements. When we run that script on the windmill deploy (self-hosted EE) the workers get a variety of responses from the fetch (sometimes 5, someimtes 8, sometimes 16). Its like windmill has cached the internal fetch results and is returning that instead of doing the actual fetch. Which seems weird to me - since its just running our script on a worker. However, if I run the exact same fetch on a cloud-hosted windmill, the script always gets 16 elements (which is all that instance has ever seen). Is WM doing something like this or have we just hit some weird distributed caching problem with the KV store we're using?
The fetch is simple:
let result = await fetch(url)
let data = await result.json()
console.log(data.length)
The fetch is simple:
let result = await fetch(url)
let data = await result.json()
console.log(data.length)
