Hans Kristian Flaatten

Yes, this is unfortunate but this setup requires an environment file with your personal/secret configurations. I'll see if I can post which environment variables are required to get Sentry up...

That server was taken offline not long ago.

I'm trying to replicate the reported issue using the [OSM demo](http://turistforeningen.github.io/leaflet-routing/examples/osm.html) without luck. Does any of you have a set of steps to reproduce this behaviour?

Sorry for the lack of effort by my part. It looks like a solid effort has been made into this, @nrenner! I would very much like you to take over...

Looks like channel is not respected either... at least it looks like it in our deployments 😕

@jksolbakken (AppSec) and I (Platforms) from the Norwegian Labor and Welfare Administration (@navikt) would like to participate on this whitepaper!

@Charley-Mann That time works very well for me!

I believe you need to register on the CNCF platform and then you can see the meeting info here: https://zoom-lfx.platform.linuxfoundation.org/meeting/92496539385?password=c2394fad-98a0-486d-9746-deff3b7de463

Regarding this I ran into similar errors even with "use client" on the most recent version of Next.js. Did some upgrades and replaced dompurify with isomorphic-dompurify. If you guys want...

I had the same experience (docker/macos/arm64/colima). To reliably switch the feature toggles both flagd and the service that uses the flag had to be restarted. ``` vim src/flagd/demo.flagd.json docker-compose restart...