maplebeats

use `dpkg --force-bad-version -i` can fix it. the deb packaging is irregular

``` panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0xaba573] goroutine 14292 [running]: github.com/linkedin/Burrow/core/internal/consumer.(*KafkaClient).partitionConsumer(0xc000204510, 0xe58ee0, 0xc004925680) /home/titustian/go/src/github.com/linkedin/Burrow/core/internal/consumer/kafka_client.go:174 +0x1d3 created by github.com/linkedin/Burrow/core/internal/consumer.(*KafkaClient).startKafkaConsumer /home/titustian/go/src/github.com/linkedin/Burrow/core/internal/consumer/kafka_client.go:226...

maybe LDS with RDS also has this issue, I haven't tested it.

> @maplebeats Did you configure envoy to use ADS? yes, use ADS mode ```yaml dynamic_resources: cds_config: ads: {} resource_api_version: V3 initial_fetch_timeout: 0s ads_config: api_type: GRPC grpc_services: - envoy_grpc: cluster_name: envolve_xds_cluster...

#461 this PR points out the problem, it's STOW design flaws

> hi @maplebeats thanks again for opening this issue. I was able to confirm this with the conformance suite, we'll look into this. I might take over that SOTW drafts...

I'm try to replace tag to ordered_ads branch and start server with ordered option ```go srv := server.NewServer(ctx, snapCache, cb, sotw.WithOrderedADS()) ``` but it doesn't work , plane send xds...

@alecholmez I use ``` err := snapCache.SetSnapshot(context.Background(), node, snap) ``` to update snapshot. I found cache use a map store id-xds , and range it to respond ``` for id,...

I test 10 nodes few times, all works fine