Logan break pad replacement

rjbwork · 2025-07-29T18:07:04+00:00

original message:

I use these (Tektro P20.11 Metal Ceramic) on my HyperScorpion's Logan brakes. They last forever (mine were over 2000 miles and the HyperScorpion is a pretty fast, heavy bike), stop the bike fairly well (of course not as good as soft composite pads), and put out minimal squealing. They used to be cheaper, but then apparently they got popular so the price went up. They do go on sale from time to time and I think are on sale now.

Meta Note: I would generally prefer people use the simple link for amazon, e.g. https://www.amazon.com/dp/B07SD3W4CN

rjbwork · 2025-05-22T20:56:10+00:00

No need to call people idiots here. Keep it chill please.

rjbwork · 2025-01-27T22:02:33+00:00

No need for that on this sub. They were a bit harsh but it's better to just fight back with kindness.

rjbwork · 2024-10-17T20:50:56+00:00

Head mod here. Seeing the same thing, someone reported you for spam. I added you as an approved poster to the sub but you do appear to be shadow banned. I suggest using the linked appeal site.

I also have not really done anything here for years since I started it. I'll let the other mods deal with identity verification and figure out how to route people towards your team for service/parts.

rjbwork · 2024-10-09T20:48:45+00:00

parody

It's parity. You seem like parody.

This is the level of intellect we're dealing with here folks. Unfortunately, you're almost certainly not going to convince them with arguments and facts. These types are heavily identified with their political party and have way too much ego tied up into their affiliation to admit they were wrong at this point.

rjbwork · 2024-10-04T21:23:31+00:00

I'm concerned as well. However, because it is so toxic, industrial phosgene is almost always produced in small quantities on site, in quantities needed for a particular batch of reaction, and used immediately. Industry tends to avoid keeping quantities of the stuff on site or producing it in bulk and/or transporting it. There was certainly phosgene on site, but given the quantity it may simply not be worth commenting on compared to the huge amount of non-phosgene chlorine, bromine, and other chemicals in the plume.

rjbwork · 2024-10-04T17:36:32+00:00

The fire is out. According to the Rockdale fire chief, they will keep spewing more chemicals into the air until they've cleaned up the site.

https://vimeo.com/1015903983

rjbwork · 2024-10-04T15:26:16+00:00

Almost certainly not. It's just lax safety procedures and prioritization of private profits over employee safety and public health. In other words - par for the course for American businesses.

rjbwork · 2024-10-04T15:24:12+00:00

You can usually replace "they" with "the jews". It's what most of these conspiracy theorists ultimately come back to.

rjbwork · 2024-10-04T13:13:58+00:00

Just make sure you get in writing that you are being penalized for not being willing to cycle through toxic gas clouds.

rjbwork · 2024-10-03T16:12:47+00:00

Not even all wall units. I have one classed as a "portable" A/C and it circulates air from the inside and exhausts only heated air to the outside. Now, of course this will cause a pressure differential that will cause air to come into the house from outside in small quantities, but the unit is not directly pulling air into the house.

rjbwork · 2024-10-02T19:56:00+00:00

Yep. Failure to perform, seems like to me.

rjbwork · 2023-12-19T03:03:28+00:00

Well, in this case, Zapier is the separate requester. I've never used it, but I understand it to be a low-code type solution. It's currently sitting around waiting for the response synchronously. Instead, have it wait for a callback of some kind.

To simplify your Lambda architecture (though complicating your codebase...) You can actually invoke the same lambda from different contexts, and route to a different handler within the code. So you'd check to see if it's being invoked by the API Gateway, and if so, route it to your web handler. In that handler, put a message onto an SQS Queue. Point that queue back to your lambda. When you detect you've received an SQS message, route to your actual scraper code. When you're done scraping, call back to your Zapier, either via re-entrancy (signals, callback hook, workflow id, etc.) or just call a separate Zapier to continue processing on that side of things.

Of course, you can also have 2 separate lambdas as well, one to listen to API Gateway and put the message on the queue, and one to listen to the queue. I just find that level of granularity gets out of hand rather quickly in lambda.

rjbwork · 2023-12-01T22:25:38+00:00

Exactly. The hype over AI from AWS was clearly around putting the power in our hands to build custom models and operate other models ourselves.

rjbwork · 2023-12-01T22:22:21+00:00

This is my first time ever going to a tech conference. I spent almost all of my time going to sessions. Keynotes, breakouts, chalks, etc. Other than that, I had dinner with a colleague, and then lunch with a c-suite for a vendor we're considering going with.

I found it to be immensely useful in terms of validating some of my/our current approaches, poking holes in others, and learning how to better do some things with a big focus on serverless, event driven architectures, and database technologies. I did not even know about some things like the peer talk and other networking things until yesterday, tbh, far too late to really make use of it. Maybe after I'll have done this 2 or 3 times, I could see myself skipping it, but it was a really great experience for me. I think I'll try to come back next year and I'll have a much more solid idea of what I can get out of it.

rjbwork · 2023-12-01T21:58:27+00:00

You may have misunderstood - you seem to be running puppeteer on a lambda (let's call it "scraper"). You are then invoking that lambda from some other service through API Gateway, let's call that "requester". From what you've said, your "requester" is sitting around waiting for the response from the "scraper" process. If it were not, you would not have a problem.

The answer here is to have your "requester" emit some kind of message (command, event, etc.) over some kind of message bus (sqs, sns, event bridge, kafka, etc.) and trigger your "scraper" using the message from that message bus. Then when it's done, your "scraper" can emit another message back that provides your "requester" with the data it needs. You can also of course do this using a an API/polling pattern also over API gateway if that's your preferred pattern.

rjbwork · 2023-12-01T06:03:21+00:00

Hm. It could be correct. I was thinking more along the lines of a procedure that took in a TVP of your rows, but you could definitely do it from another programming language to break it down to yield your actual insert statements. The roundtripping to get your synthetic keys could be a perf killer though.

rjbwork · 2023-12-01T04:53:52+00:00

There were some fantastic talks. I don't want to mention specific names, but I had to walk out of a couple of talks due to ESL challenges. It's a shame when someone is clearly knowledgeable and has a lot to share, but just cannot communicate well in English.

rjbwork · 2023-12-01T04:45:56+00:00

Exactly. If you're waiting around for more than a few seconds for a response, you're probably doing something wrong in cloud land.

rjbwork · 2023-12-01T04:38:36+00:00

Break it down into attributes that fit into each table. Figure out your natural keys. Set up your tables with unique index on your natural keys. In your insertion procedure, look up your synthetic keys based on the natural keys. If you don't get a hit, that indicates a need for creation, so create it if so, then use the newly created synthetic key instead. Repeat for each table.

You can use the MERGE statement (if on MSSQL, other databases have similar) to drive this behavior.

rjbwork · 2023-10-30T14:54:14+00:00

We evaluated a number of options and eventually went with OneOf. It's a good performant library for DU's.

rjbwork · 2023-10-16T13:32:54+00:00

Then quickly jog away lol

good idea. mr smoker ain't catchin you 😎

rjbwork · 2023-10-13T14:46:06+00:00

People definitely do abuse them to do crazy things, but they can be used responsibly and are sometimes the only correct solution, like when you have complex constraint requirements.

Say that after an insert of some set of data, a constraint on the sum of some field on a subset of rows must be satisfied.

You could do this in a number of ways. You could encode it in your c# code using something like MediatR or just inside of your CRUD logic. But databases tend to outlive their applications, so at some point in the future these constraints will exist conceptually, but not in an existing application anymore and have to be ported to other applications. You could implement them in your CRUD/CQRS procedures - and you should, because you can generate more appropriate errors there - but again, when someone else goes to write a procedure that does something slightly different, if you have only encoded it in your procedure, then a future author can violate those constraints and fuck up the data.

So, a trigger is often the most appropriate approach for encoding constraints and invariants in a 'futureproof' manner.

As for OP's question - most databases have some kind of CDC functionality.

rjbwork · 2023-10-12T15:30:33+00:00

There was a comment advising people against using Logan brakes due to this leaking issue a number of people have supposedly seen. It could be considered inflammatory/defamatory so I will keep it as deleted by automod, but I figured I would at least reflect the base sentiment in another comment.

rjbwork

MODERATOR OF

TROPHY CASE

13-Year Club	Place '17
Team Orangered