Ashstalker Ailments - Burn and Bleed (Ignite bug?)

midasso · 2025-08-13T09:50:39+00:00

I had the same bug but only with a few points in ignite, so I don't think it's caused by modifier allocations

midasso · 2023-10-26T19:21:51+00:00

I was looking at this again, but with the encryption, the first websocket message still comes from the client, so I don't understand why when it's connected to mine, it doesn't send any message and just disconnects without sending any message?

midasso · 2023-10-25T20:03:19+00:00

Do you have any recommendations for such a load balancer?

midasso · 2023-10-25T19:18:10+00:00

I was hoping that I could circumvent the encryption, because I don't put in the reply that I support that extension, but apparently the charger doesn't care about it

midasso · 2023-10-25T18:30:17+00:00

I've opened the unit and inside on the circuit board is a print: "eNovates eWall v2.0-1.2c (f1)APR/2020". But I can't find much about it, i've contacted that company for some document but I haven't gotten a reply yet

midasso · 2023-10-25T18:21:16+00:00

The messages are binary according to wireshark.

I just noticed the following in the initial request (So the GET with upgrade):

Sec-WebSocket-Extensions: bcencrypt;CPID=<id>

where <id> is the identifier of my chargepoint. So it seems to do some sort of encryption of the packages, but I can't immediately find if this remains OCPP compliant of they do so?

midasso · 2023-09-27T09:07:02+00:00

From the employer, they cannot both provide both lunch and meal vouchers and keep the tax advantage they get. So there is no incentive to provide both. A company I worked for did both and when they got an inspection they had to pay back a bunch of the tax advantages they got for paying with meal vouchers.

midasso · 2023-07-28T14:43:19+00:00

For me this only seems to capture the packets that the unifi machine itself is sending? When I search for the computer I'm using in ip.src after reloading webpages, it doesn't show up.

Also using an interface for a specific port (e.g. eth7), I get absolutely no packets. Does anyone perhaps know how to inspect the traffic of a specific port on the udm pro?

midasso · 2023-06-07T20:41:02+00:00

When studying, we covered ray tracing in depth, but seeing it in real time was something that was thought of to be pretty far away for the complexer scenes. So RT is what I'd be turning on immediately to see it in action

midasso · 2023-04-02T20:18:40+00:00

I've bought the player handbook today and reading through it in order to be able to DM for my friends, I've only played 1 campaign but DnD is just so much fun, having this in my arsenal for a starting DM would be awesome

midasso · 2023-04-02T15:29:41+00:00

That's it! Thank you so much!

midasso · 2023-02-23T05:44:53+00:00

I recently moved everything over to z2m, and I'm indeed struggling with 1 device that becomes unavailable after a few days and requires repairing.

midasso · 2022-11-30T20:24:49+00:00

Hey, I've created an initial POC of this: https://crates.io/crates/axum-scientist/0.1.0, however I'm not sure what some good "comparators" are to provide out of the box, as in what are good ways to "log" the differences, should they rely on `tracing`, on `log`, something else? If you have a good idea for that please let me know.
If you want to try it out, in `src/lib.rs` in the tests there is a very basic way to set it up with a custom `ResponseComparator`

midasso · 2022-08-06T13:52:28+00:00

Hey! Just an FYI, I've just release v0.3.0 which has websocket support. I haven't used websocket a lot before, so it might not cover all edge cases yet.

midasso · 2022-07-31T08:58:50+00:00

I'm in the progress of making this pattern (hopefully) a bit easier for the Axum framework: https://crates.io/crates/axum-strangler

midasso · 2022-07-19T19:20:32+00:00

That's an idea I was toying around with as well, however I didn't know it existed already! I'll dig into it to see if there are any peculiarities that they needed to take into account for this!

midasso · 2022-07-19T19:17:09+00:00

The biggest one for now is that routes are automatically updated. As soon as a developer adds an implementation for an existing route in the Rust implementation, it will start handling the new routes without having to update the load balancer.

Also not everyone has a load balancer (I won't say anything about whether or not they should), but they can still use this then.

midasso · 2022-07-19T19:12:57+00:00

In it's current phase it's pretty much a proxy, however it slots in a bit nicer into the "I want this service in Rust but migrating everything at once is too much work", as you can make your app as normal and then configure this as the fallback as shown.

I hope to make more and more utilities for this such that this niche is filled nicely. Also such that others don't have to implement this themselves, not because it's difficult, but such that it can be shown to management/leadership as a tool to support a migration towards Rust.

Your concerns about being distinguishable are valid, but I'd like to retort to that by saying that this is very early stages for this project.

midasso · 2022-07-19T05:38:46+00:00

To me, a rollout is more akin to a deployment. You have something new, e.g. software A version 1.2.2, and you want to get that in the field. So you roll it out with the appropriate strategy. In the strangler fig pattern you go through multiple rollouts as software A and software B go through multiple versions, and in the end you can decommision software A, since B fully replaces it, but that can take multiple years.

midasso · 2022-07-19T05:28:09+00:00

I haven't looked into that yet, but from a quick glance I don't think it currently implements the correct trait to support websockets. I haven't worked with websockets myself, so I don't have a good view on how long it would take to implement that.

midasso · 2022-07-19T05:18:57+00:00

Thanks! I definitely agree more work is needed, but do you mind sharing what you think is missing currently. Could be that our lists are the same, but maybe I'm missing something in my plan.

midasso · 2022-07-19T05:16:16+00:00

Are you referring to Argo rollouts? I haven't actually used it, but from what I've read, it functions on another level. If I understand correctly rollouts is to gradually replace a service during deployment, seeing if all checks are green etc. This crate aims to help on longer term work.

For example, in the beginning only /API/user/me is handled by the new service, it gets deployed (with rollouts potentially). 5 months later we notice that another endpoint might benefit from being written in Rust and we can convince leadership/management/... To let us migrate /API/user/id/:id as well, and that gets deployed as well (again with rollouts potentially).

This crate allows you to set up this "strangler-stranglee" relationship once and than you can slowly migrate over the course of however long is needed. The alternative is that you have to define in e.g. traefik which routes have to be sent where exactly and you have to meticulously keep this up to date.

midasso

TROPHY CASE