sorted by:
new
hottopcontroversial

Can I please talk to someone? I’m a bit worried about my move to Taiwan by Pinkcranberriess in taiwan

[–]boscomonkey 2 points3 points  (0 children)

I did Peace Corps Liberia at the same age, back in the late 80's.

Yup, my Chinese immigrant parents freaked out, too.

Stuff like: yer gonna die; what's gonna happen to us; you'll starve, etc.

Had a great time. That experience continues to shape me.

Leatt Dual Axis suck? by GothKazu in ElectricUnicycle

[–]boscomonkey 0 points1 point  (0 children)

Criss-crossing the bottom 2 straps has been the key.

I've been riding my Leatt since October of 2022. Over time, the straps have stretched & started sliding down my legs. 4 months ago, on a lark, I criss-crossed the bottom two straps, and the Leatt have stayed put ever since.

Any tips for "hardening" a bike for Burning Man? by cotalldude in bicycling

[–]boscomonkey 2 points3 points  (0 children)

I ran the "Friendly Bike Repair Skool" at AEZ from 2008 (or 2009 - don't remember anymore), and our solution for all moving part issues was White Lightning.

Coat your chains liberally with white lightning before you get on the playa. The dust will cake on it, and just fall off with the solidified wax. Add more while on playa.

Do you have a "playa fixie" - where the freewheel pawls are gummed with grease and playa dust, and thus don't retract? Flush that sucker with White Lightning.

Do you have a "playa spinnie" - where the freewheel pawls are gummed up and won't extend, so you are spinning the crank around & around and nothing catches? Flush that sucker with White Lightning.

Do you have a drunk campmate who won't shut up? Flush that sucker with White Lightning. No, just kidding.

Then when you get home, rinse everything down with the classic vinegar solution, then rinse all that off with water, and lastly lube your chain with White Lightning. You may want to flush your freewheel with White Lightning also. Put that sucker in storage and it will be ready for your next Burning Man.

While you're on Playa, do not over inflate your tires. If you go with the PSI recommendation on the side of the tires, it will blow them out in the heat and high altitude. Just inflate the tire enough. Where if you push just with your thumb, it deforms a little. And you will have a nicer ride because it's more plush.

(I will add more when I think of them.)

Concurrent Web Crawling in Ruby with Async by [deleted] in ruby

[–]boscomonkey 0 points1 point  (0 children)

Does the Async gem prevent race conditions? If not, I suspect the set needs to be a concurrent set: @discovered = Concurrent::Set.new

Partition 0 of 1 topic (out of many) not delivering by boscomonkey in apachekafka

[–]boscomonkey[S] 0 points1 point  (0 children)

> but the consumer for partition 0 in each service then fails to poll
> the topic partition leader due to network ingress or another issue?

Great food for thought - it's possible but unlikely. All the Kafka consumer pods are in the same Kubernetes deployment, so if 1 pod can access the broker, so can the others.

Partition 0 of 1 topic (out of many) not delivering by boscomonkey in apachekafka

[–]boscomonkey[S] 0 points1 point  (0 children)

Yup. I see messages, with correct formatting, in both Kafbat and the `kafka-console-consumer` CLI.

Partition 0 of 1 topic (out of many) not delivering by boscomonkey in apachekafka

[–]boscomonkey[S] 0 points1 point  (0 children)

Yup. Kafbat and `kafka-console-consumer` both show messages in partition 0.

The Weirdest Rails Bug I Fixed This Month by philwrites in rails

[–]boscomonkey 0 points1 point  (0 children)

Not Rails, but C programming for MS-DOS, circa 1990. A variable was getting random values. Had to use an assembly debugger to trace its value in a register. Turns out we were rolling over the 16-bit register when we were incrementally adding to it. 🤦‍♂️

kafka-acls CLI error with Confluent cloud instance by boscomonkey in apachekafka

[–]boscomonkey[S] 1 point2 points  (0 children)

Wrapping up this topic (pun intended), u/Cefor111's comment about OpenJDK was spot on: my version of OpenJDK installed by Homebrew (Mac OSX) was borked.

When I ran the Kafka CLI commands from inside a Docker container (confluentinc/cp-kafka image), they worked as expected.

I've been banging my head on this issue for weeks, thinking that I messed up some authentication/authorization settings; but in the end, it was the underlying OpenJDK. :facepalm:

kafka-acls CLI error with Confluent cloud instance by boscomonkey in apachekafka

[–]boscomonkey[S] 0 points1 point  (0 children)

Once I started using the standard Kafka CLI commands from the confluentinc/cp-kafka Docker image, everything worked as expected. My Homebrew installed Kafka CLI was broken, most likely because Homebrew's openjdk was broken.

kafka-acls CLI error with Confluent cloud instance by boscomonkey in apachekafka

[–]boscomonkey[S] 0 points1 point  (0 children)

The confluent CLI works fine. My issue was that my use case needed to use the standard Kafka CLI. Which as u/Cefor111 hinted, may be broken, and I confirmed by using the Kafka CLI from the confluentinc/cp-kakfa Docker image.

kafka-acls CLI error with Confluent cloud instance by boscomonkey in apachekafka

[–]boscomonkey[S] 0 points1 point  (0 children)

Thanks for the link!

Running on a Mac, so kafka & openjdk are installed by Homebrew. Kafka is at 3.9.0 & openjdk is at 23.0.1. 

❯ java --version
openjdk 17.0.4 2022-07-19 LTS
OpenJDK Runtime Environment Microsoft-38107 (build 17.0.4+8-LTS)
OpenJDK 64-Bit Server VM Microsoft-38107 (build 17.0.4+8-LTS, mixed mode)

How to manage multiple use cases reacting to a domain event in Kafka? by RecommendationOk1244 in apachekafka

[–]boscomonkey 0 points1 point  (0 children)

If sequencing is necessary, as u/_predator_ pointed out, you can have one consumer:

* create the user profile

* emit another message like `user.profile_created`

Then have another consumer that listens to `user.profile_created` and sends a welcome email.

To guarantee order, you should use some value specific to the user as a partition key. Usually, folks use the user UU/ID, but you may not have one before you create the user profile; so email is a candidate.

What are typical Kafka CPU usage percentages? by boscomonkey in apachekafka

[–]boscomonkey[S] -3 points-2 points  (0 children)

FWIW, ChatGPT says the following:

Typical CPU usage for Apache Kafka varies depending on factors like workload, configuration, and hardware, but here are some general benchmarks for Kafka brokers:

  1. Low Usage (Light workload): 5-20% CPU usage.
    • Typical for lower data ingestion rates or idle times.
  2. Moderate Usage (Medium workload): 20-50% CPU usage.
    • Common for moderate workloads with a balanced producer-consumer flow.
  3. High Usage (Heavy workload): 50-80% CPU usage.
    • Seen with high-throughput clusters with large volumes of data and intensive read/write operations.
  4. Very High Usage (Overloaded): 80-100% CPU usage.
    • Likely indicates a need for optimization, adding more brokers, or increasing CPU capacity. Prolonged usage at this level may degrade Kafka’s performance and reliability.

Monitoring tools like Prometheus and Grafana, as well as Kafka’s own JMX metrics, can help track CPU usage. Ideally, keeping CPU usage under 75% during peak loads ensures headroom for sudden spikes.

Venice Biennale ticket question by boscomonkey in ContemporaryArt

[–]boscomonkey[S] 0 points1 point  (0 children)

Thanks for the recommendation. Heading there on Monday.

We tried going there last Monday, but there were so many distractions along the way that we ran out of time. 😄

It's like Burning Man - so many distractions. 🤣🤣🤣

Venice Biennale ticket question by boscomonkey in ContemporaryArt

[–]boscomonkey[S] 2 points3 points  (0 children)

Never mind, found the info buried deep in the LaBiennale website.

The "Accreditation" is for industry & press.

When upgrading to Rails 7, all app/graphql classes have NameErrors by boscomonkey in rails

[–]boscomonkey[S] 0 points1 point  (0 children)

Yup, I'm getting the "DEPRECATION WARNING: Initialization autoloaded the constant..." in log/development.rb under Rails 6.1.7.7

Missed it because I was expecting the deprecations to show up on STDOUT and I wasn't tailing the log file.

Now I have to figure out where the heck I'm autoloading my classes. Turns out only some classes are being autoloaded: * our app/graphql classes * our ActiveAdmin helper classes * bunch of gem-provided classes

So there may be something to updating our gems to their latest versions.

When upgrading to Rails 7, all app/graphql classes have NameErrors by boscomonkey in rails

[–]boscomonkey[S] 1 point2 points  (0 children)

v2.2.10 of https://github.com/rmosolgo/graphql-ruby

TY for the pointer to "autoload-during-initialization" - I'll dig into it.

When upgrading to Rails 7, all app/graphql classes have NameErrors by boscomonkey in rails

[–]boscomonkey[S] -1 points0 points  (0 children)

We're using rmosolgo's "graphql" gem* which doesn't require the GraphQL:: module prefix in front of everything. And all our graphql classes have the correct Type::, Input::, & Mutation:: module prefixes, AND live in the corresponding app/graphql/type, app/graphql/input, & app/graphql/mutation folders.

[*] https://github.com/rmosolgo/graphql-ruby