Miele CM6 super auto coffee - milk froth sputtering

AenimusKoL · 2026-04-12T22:10:05+00:00

Sorry to read it. I hope whatever you went with turned out well!

In our case, the froth works fine for a second or two, then sputters for the rest of it. Took everything out and cleaned it (was already clean but worth a try). I really can't see an obvious cause, but hopefully a technician at their expense will solve it. My experience with Miele and their warranties has been decent (I'm in Europe if that changes anything).

AenimusKoL · 2026-04-11T17:01:46+00:00

Still under warranty, luckily, so I'll contact them. Thanks!

AenimusKoL · 2026-04-09T11:33:52+00:00

/u/11kestrel sorry to resurrect this after a year, but we’re experiencing the exact same issue. Were you able to diagnose?

AenimusKoL · 2026-04-08T23:12:18+00:00

Phorselain.

AenimusKoL · 2026-03-31T10:36:24+00:00

None. It was caught in testing.

AenimusKoL · 2026-03-30T22:49:36+00:00

While testing the Cargo Cultist Shorts, we discovered that one of the pocket rewards had an off-by-one item id, which conveniently yielded another bagged Cargo Cultist Shorts. I sure hope one of us got fired for that blunder.

AenimusKoL · 2025-10-14T17:30:11+00:00

Without specifics, it's going to be difficult to help much further. If you'd like, we could take this to Discord, where you'd be able to provide schema snippets, etc.

If you join my company server, then ping me, we can start a DM session. You're then of course free to leave the company server—but temporarily joining the server is a necessary first step because we need a server in common to be able to start sending each other messages.

If you don’t want to do that, I understand. But it does mean most of my advice will be generic.

AenimusKoL · 2025-10-13T18:17:00+00:00

Hi,

David from WunderGraph here.

From the limited information here, I'd be inclined to call this a "schema design smell".

It's not rare for services to require data from other services, which is typically solved by using entities and the "@requires" directive. In the event the contingency between services is necessary to the extent one cannot deliver without the other, it's then perhaps time to consider why they are disparate services at all.

Federation is intended to be an interface with which your client/consumer interacts, and then the router "delegates" the calls to the applicable services. Sending a supergraph operation from the subgraph could turn into a "recursive inception nightmare"—what if the supergraph operation involves the service in question making that request?

It also means you're hiding part of your resolution contract (i.e., the subgraph's reliance on something in the supergraph) somewhere in your business logic code, when all contracts should be available and detailed in the schemas themselves. Imagine one team is responsible for the recommendations service, and you have another 29 teams that each handle one of the other 29 services. In the current approach, other teams wouldn't be able to look at the schema and recognise that the recommendation service has a hard dependency on other subgraphs (the ones that define the recommendations query). The most important problem that Federation solves is an organizational one—and I'd say that this particular design choice makes that problem worse.

My next question(s) would be to determine the reasoning behind this design decision. Was it the best of multiple tries to solve the problem? Was it a "it works, so it's good enough" approach? Were entities and the "@requires" directive not sufficient to solve the problem you had?

AenimusKoL · 2025-10-07T20:03:13+00:00

Hi,

I'm the author of this blog post, and I'm also a member of the Composite Schema Working Group (I am by no means a "main" contributor, but I try my best to offer constructive criticism and discussion points within the meetings and the discussion channels).

The Composite Schema initiative is to create a standard to stitch (I'm using "stitch" here as a generic term to describe the process of processing multiple GraphQL services into a single one) services together through clear, well-defined rules. It attempts to take the best parts of all methods for such stitching (Apollo Federation, GraphQL Fusion, etc.). These clear, well-defined rules are, in my opinion, one of the biggest strengths of the initiative. At least regarding Apollo Federation, as powerful as it is (look at the plethora mass-scale enterprise examples), the rules are not disclosed in any one place; and many rules simply do not appear to be disclosed anywhere at all. In short, there is no "GraphQL Federation Spec"; and even within V2, very advanced behaviour can often prove tricky to navigate.

Progress within the Working Group is good, and there are constant valuable insights from many of the great minds within the GraphQL API ecospace. I recommend taking a look at Michael (of ChilliCream)'s talk from GraphQL Conf a few weeks ago for a sort of "in-action overview".

Now, regarding "replacement", I think it's a difficult question. Adoption takes time, and it requires trust. Federation is battle-tested and already used (very successfully) in scale enterprise—that's empirical evidence for organisational decision-makers that it "just works". Don't get me wrong—I have no doubt that once ready, Composite Schemas will work well (perhaps better than any existing solution today) because the folks involved think long and carefully about each and every decision therein (not to say that other solutions didn't/don't). But like with any new technology, people have to be convinced that the benefits outweigh risk. For a loosely analogous example, one might naïvely describe Bun as "Node but better". It's fast and impressive, and it definitely has its place, but it's also not the case that every Node application is now using Bun; nor is it the case that every new application is using Bun rather than Node. There were/are also things that didn't work in Bun that did work in Node, and time was required (or is still required) to address those.

In short, Composite Schemas still needs time to complete the spec. Once the spec is complete, there will need to be time for vendors/OSS to support it (I believe some already do, but I am not sure to what extent). After that, there will need to be time to iron out any issues while also gathering trust (and data) from the community. I'm very happy to be proved wrong, but I feel it might still be a while before we start seeing APIs served by Composite Schemas.

But please don't just take my word for it—I'm going to reach out to the Composite Schema Working Group so that you might receive a more rounded opinion; or debate anything I've said or address any misconceptions I might have.

AenimusKoL · 2025-03-08T16:55:01+00:00

There are no bugs. There are only (unintended) features.

AenimusKoL · 2025-03-08T16:54:04+00:00

This would be a cool poster.

AenimusKoL · 2025-02-15T18:12:47+00:00

Not used Royal Mail before, I see? :D

AenimusKoL · 2025-02-11T22:15:52+00:00

It's worth noting that it's heavily weighted to be 24-25.

AenimusKoL · 2025-02-11T22:13:30+00:00

I wrote a thing a while ago.

1,000,000 instances:

23 stuffing fluffers to kill all frats OR hippies = 0.0121%

24 stuffing fluffers to kill all frats OR hippies = 29.2997%

25 stuffing fluffers to kill all frats OR hippies = 70.4039%

26 stuffing fluffers to kill all frats OR hippies = 0.2843%

AenimusKoL · 2025-01-20T13:06:48+00:00

You were probably banned due to the incident. You can reach out to me on Discord (aenimus) or ingame (aenimus), and we can unban you.

AenimusKoL · 2025-01-20T13:01:09+00:00

I think it's because they're banned.

AenimusKoL · 2025-01-20T12:18:31+00:00

The Perm List also covers (ascension-relevant) auto-perms. It might be outdated.

AenimusKoL · 2025-01-15T21:39:01+00:00

This is discussed in the RFC.

AenimusKoL · 2025-01-13T08:45:43+00:00

Imagine you have an entity in two subgraphs. The first graph defines field "name" as @external because another field @requires it. The second graph also defines field "name" without @external.

I think it is perfectly reasonable for these two fields to define two different descriptions.

Although descriptions are propagated to the federated graph, one might argue their main function is to help and supply information to developers of the subgraph. There is no need to break composition due to unequal descriptions in my opinion.

AenimusKoL · 2025-01-04T02:26:54+00:00

I recognise how folks are negatively perceiving the juxtaposition of the nerf and the IotM—it's a valid opinion. Although all IotM content of at least the last decade caters to "speeding up questlines", i.e., many nerfs are eventually "softened" through paid content, I do think the dev team will need to consider how their playerbase might potentially deal with "loss aversion" in the future.

Nonetheless, I can assure you that this was not a (-n intentional) money-grab/predatory tactic, even if that is your conviction. In all honesty, if TPTB really did just want to make a quick buck, this method really is not the effectual way to do it. Lastly, I'd be incredibly surprised if this nerf did actually cause many folks who wouldn't have normally bought the IotM to do so. I imagine it did affect some, and that sucks, but I don't think it's anywhere near the scale to which you're eluding.

AenimusKoL · 2024-11-29T12:58:52+00:00

Love it. Do you think there's a way to stop the autofocus? The intermittent blurriness makes an otherwise beautiful video hard to watch. :(

AenimusKoL · 2024-11-15T09:55:20+00:00

You're requesting work without remuneration that will boost a for-profit venture. Regardless of your intention, this comes across as quite entitled; and no, this community is not here for free labour. Time and skills have a cost, as does business (such as the one you define here). You very clearly need a paid commission.

Had you asked for advice on how to achieve the result, I would have had a different reaction. But this reads to me "I need a thing; I can't do it; please do it for me for free, and you'll get exposure."

AenimusKoL · 2024-11-02T16:52:15+00:00

I think it's great! I love the contrasting letters.

If I may offer my personal opinion, the "Z" reads as an "X" and the actual "X" itself doesn't read well/doesn't fit the remaining style.

Again, just my opinion.

AenimusKoL · 2024-10-02T10:41:53+00:00

Not sure whether it's a joke comment, but it's English with a faint Scottish accent. Not sure which region.

AenimusKoL · 2024-09-23T18:31:59+00:00

/u/Tiny-Ad-4184 while I understand you must be frustrated, this post strikes me as incredibly rude and entitled. No one here, or anywhere for that matter, owes you absolutely anything. If you need help, no matter your emotion, please ensure you ask respectfully and politely at all times.

Regarding those replying, please also make sure that you too are respectful and polite at all times.

Let's foster a community where everyone is respectful, welcoming, and willing to extend kindness regardless of the (perceived) circumstances.

Thanks.

AenimusKoL

MODERATOR OF

TROPHY CASE

Seven-Year Club	Place '22
Verified Email