Kafka is not a straightforward protocol and has a few odd niches. Not to mention that message formats have changed over the years. Even the base product has recently dropped support for some of the oldest API versions. And there are still plenty of clients out there using old versions of librdkafka (he says from experience).
So I'd be interested how (backward-)compatible they are.
I agree that it isn't straight forward! Tansu uses the JSON protocol descriptors from Apache Kafka, generating ~60k LoC of Rust to represent the structures. It then uses a custom Serde encoder/decoder to implement the protocol: original, flexible and tag buffers formats for every API version (e.g., the 18 just in FETCH). It is based off spending the past ~10 years using Kafka, and writing/maintaining an Erlang client (there are no "good" Kafka clients for Erlang!). It also uses a bunch of collected protocol examples, to encode/decode during the tests. Tansu is also a Kafka proxy, which is also used to feed some of those tests.
However, there are definitely cases I am sure where Tansu isn't compatible. For example, Kafka UI (kafbat) reports a strange error when doing a fetch (despite actually showing the fetched data), which I've yet to get to the bottom of.
If you find any compatibility issues, then please raise an issue, and I can take a look.
The history books say the Azores were discovered by Portuguese explorers in 1427. But mouse DNA and lake sediment suggest that the mid-Atlantic archipelago was actually discovered as much as 700 years earlier, by Vikings.
No, but you can get the form to request the form. Then it must be stamped by an official in the [strikethrough]Ministry of Information[/strikethrough] Ofcom. Please allow 4-5 months for processing thanks to our partners delivering efficient intersection of Government and Industry, Capita.
Popularity is a poor measure of performance in UK politics. The British public are regularly shown to be fickle and easily led in their judgements.
Results are a bit meh so far with Labour but at least they're not Trussesque dangerous. And positive achievements rarely get a mention in our press. Can't think why.
One thing that I don't understand though. The theory is they washed up a local river, got embedded in sediment and are only now being released. Given that, I would have thought their condition would be much worse. More likely that they were well-packaged on the wreck and have only just been released ?
Not only for a surprisingly long time, but also in surprisingly good condition. For example at Vindolanda on Hadrian's Wall archeologists have found not one or two, or even ten but over 5000 amazingly preserved Roman shoes that were apparently thrown away into the fortress's moat and survived buried in the mud <https://www.vindolanda.com/Blog/the-curators-favourite-shoes>.
Hilariously they're never found a pair of shoes, only singles. So that's why they think they were thrown away as rubbish, because one shoe broke so they threw it in the ditch. In the museum on site there's a fantastic "wall of shoes" on display where you can see the amazing leatherwork from 2000 years ago <https://www.thehistoryblog.com/archives/37305>.
> Hilariously they're never found a pair of shoes, only singles.
From that first link: “These two little treasures were part of the hoard of over 400 shoes excavated in 2016. One would probably think that we have lots of pairs of shoes however, we only have a few. But this pair was easier to identify as they were small and have a less usual construction style as they do not have a seam that stitches them up over the toe and they were also found close together.”
Also, looking at those shoes, many of them don’t look beyond repair to me. Quite a few look like they’d need only minor repairs.
My prior understanding was that before the industrial revolution dramatically reduced the labor costs, clothing was expensive. Most people only owned two or three outfits, and replacing one would cost a month's wages sort of expensive.
How could one afford to throw away a perfectly good non-matching shoe?
> kafka compatible
Kafka is not a straightforward protocol and has a few odd niches. Not to mention that message formats have changed over the years. Even the base product has recently dropped support for some of the oldest API versions. And there are still plenty of clients out there using old versions of librdkafka (he says from experience).
So I'd be interested how (backward-)compatible they are.
reply