guss77

deb http://archive.ubuntu.com/ubuntu lunar main restricted
deb-src http://il.archive.ubuntu.com/ubuntu/ lunar main restricted

deb http://archive.ubuntu.com/ubuntu lunar-updates main restricted
deb-src http://il.archive.ubuntu.com/ubuntu/ lunar-updates main restricted

deb http://archive.ubuntu.com/ubuntu lunar universe
deb-src http://il.archive.ubuntu.com/ubuntu/ lunar universe

deb http://archive.ubuntu.com/ubuntu lunar-updates universe

guss77

#!/bin/bash
#
# Installation:
# 1. put this script somewhere in your path - `/usr/local/bin/powerdraw` is probably
#    a good idea.
# 2. Give the script execution permissions, e.g. `sudo chmod a+x /usr/local/bin/powerdraw`
# 3. Optional - add a sudoers file to allow users to execute this file without typing their
#    password over and over. For example, create `/etc/sudoers.d/allow-powerdraw` with the
#    following content:
#        %admin ALL = NOPASSWD: /usr/local/bin/powerdraw, /usr/local/bin/powerdraw -f

guss77

#!/bin/bash

##
# Helper to find the user configured name of an activity, by its ID
function getActivityName() {
  qdbus org.kde.ActivityManager /ActivityManager/Activities \
    org.kde.ActivityManager.Activities.ActivityName "$1"
}

##

guss77

package coil.geek;

import java.util.concurrent.atomic.AtomicLong;

/**
 * A token-based rate limiter, inspired by https://stackoverflow.com/a/55349487/53538
 * 
 * The original implementation boasts an O(1) time complexity as well as O(1) space complexity, but controls
 * concurrency using synchronization. This implementation uses atomic operations to offer lock-less concurrency
 * and reentrancy.

guss77

package testing;

import io.vertx.core.Future;
import io.vertx.core.Promise;
import io.vertx.core.Vertx;

public class VertxFutureTest {
	
	static Object waiter = new Object();
	static boolean done = false;

guss77

Introduction

I ran into a some problems trying to deploy a Vert.x based HTTP service, using Hazelcast as the cluster manager, on AWS ECS Fargate (a container orchestration service where you deploy docker containers without worrying about the underlying virtual machines - kind of like Kubernetes, but simpler perhaps?).

Some Problems

Hazelcast has good documentation on their website on using Hazelcast on AWS ECS, but all of it assumes that you are configuring the cluster with their YAML configuration language - which unfortunately doesn't

guss77

#include <memory>
#include <ranges>
#include <iostream>

class Digit {
	unsigned char val;
	std::unique_ptr<Digit> moreSignificant;
	static unsigned int sevens;
public:
	Digit(unsigned char startVal) : val(startVal) {}

guss77

#include <memory>
#include <ranges>
#include <iostream>

class Digit {
	unsigned char val, sevenCount;
	std::unique_ptr<Digit> moreSignificant;
public:
	Digit(unsigned char startVal) : val(startVal), sevenCount(startVal % 7) {}
	void inc() {

guss77

#!/bin/bash

# Based on https://docs.microsoft.com/en-us/azure/storage/common/storage-rest-api-auth

function GetCanonicalizedResource() {
	local address="$1" storageAccountName="$2"
	echo -n "/${storageAccountName}$(cut -d? -f1 <<<"$address")"
	cut -d? -f2- <<<"$address" | tr '&' '\n' | (while IFS="=" read key val; do printf '\n%s:%s' "$key" "$val"; done)
}

guss77

#!/bin/bash -e
verbosity=info
tokfile="/tmp/tok-$$"
domlist_pfx="/tmp/doms-$$-"

doctl_tokens=(
	# Place all your DO personal access tokens here in this array as simple text, preferably one per line
)

function log() {