...if you aren't a data center selling VPSes for your clients, or if your workload isn't tailored for VMs.

Everyone uses Docker nowadays, but Proxmox doesn't natively support Docker. But you do have three different solutions on how to run Docker in it.

• Installing a Linux OS in a VM and running Docker in it. This is the recommended solution by Proxmox.
• Running Docker in a LXC container. This is not recommended, but it does work. However, if you are using ZFS, you need to install fuse-overlayfs in the container, and some people have reported that this solution can cause the Proxmox host to lock up due to deadlocks.
• Running Docker on the Proxmox host itself. This is super not recommended since you should keep the hypervisor layer "clean".

I always thought that this was a super wtf move, "why wouldn't they support Docker? Everyone uses it nowadays!"

And recently, after using Proxmox since 2017... I understood why.

---

When your Java app crashes due to OutOfMemoryError, you probably want to automatically restart your application. After all, what's the point of keeping the application running if a OutOfMemoryError was thrown, since in that case you probably have a memory leak, so trying to catch the error and continue executing the app is unviable.

To do this, you can add -XX:+ExitOnOutOfMemoryError to your startup flags, this will cause the JVM to automatically exit when a OutOfMemoryError is thrown, sweet!

However, you may also want to create a heap dump when a OutOfMemoryError is thrown, to analyze the heap dump later to figure out what triggered the error. In that case, use -XX:+ExitOnOutOfMemoryError -XX:+HeapDumpOnOutOfMemoryError, this will create a heap dump on OutOfMemoryError and then exit.

You can change the heap dump folder with -XX:HeapDumpPath, so, if you want to store your heap dumps in the /tmp/dump folder, use -XX:HeapDumpPath=/tmp/dump!

Here's how you would use it when starting your application.

java -Xmx1G -Xms1G -XX:+ExitOnOutOfMemoryError -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp/dump -jar ...

---

Se você está com sede, tomar água do mar só lhe deixará com mais sede.

Você pode tentar tomar mais água do mar, tentar buscar a água do mar em outras fontes, tentar requintar a água do mar...

E ela pode até aliviar a sede por alguns instantes, mas jamais saciará a sua sede.

Você almeja saciar a sua sede, desejando que esse sentimento alguma hora passará, e que, ao continuar a tomar água do mar, magicamente o seu problema de sede acabará...

Mas todas as suas tentativas são jogadas em vão, pois água do mar jamais te saciará...

A água do mar não é substituto para o que você realmente almeja, para o que realmente deseja. Mas preso em sua zona de conforto, você acaba não enxergando o motivo que te faz tomar água do mar, ao invés da água que realmente te saciará.

Você deseja quebrar esse loop infinito, explodir e alcançar os seus sonhos e tornar o imaginário em realidade.

Ir contra aos que dizem que é normal tomar água do mar, pessoas cegas pois não querem sair da zona de conforto, mas que, no fundo, possuem os mesmos problemas que você.

Mas para isso, você precisa ter a coragem de dar o primeiro passo...

---

Java's ScheduledExecutorService has a nifty scheduleAtFixedRate API, which allows you to schedule a Runnable to be executed in a recurring manner.

Mimicking scheduleAtFixedRate seems easy, after all, isn't it just a while (true) loop that invokes your task every once in a while?

GlobalScope.launch {
    while (true) {
        println("Hello World!! Loritta is so cute :3")
        delay(5_000)
    }
}

And it seems to work fine, it does print Hello World!! Loritta is so cute :3 every 5s! And you may be wondering: What's wrong with it?

---

---

Recently, I've noticed that my Minecraft server's MOTD was suspiciously switching to my subservers' MOTD if I connected to my subserver and then quit. This was more noticeable if there was a network issue that caused the client to disconnect, due to Minecraft not automatically refreshing the server list.

But how? This is impossible! The Status Response Packet can only be sent if the user is in Status state, not in Play state!

Or perhaps, it ain't impossible since Server Data Packet's introduction in Minecraft 1.19.

Why it exists? While I'm not sure, I think it is related to Minecraft's new reporting system, because it is used to show the infamous "Chat messages can't be verified" toast.

Since BungeeCord dd3f820, the packet is now parsed and blocked on BungeeCord's side, so this is already fixed in newer BungeeCord/Waterfall versions, yay!

---

Desde pequeno eu sempre sonhei em ser um YouTuber famoso, mas nunca tive uma verdadeira oportunidade de cair de cabeça nisso, pois nunca tive um quarto que possuisse paz e harmonia para eu poder criar vídeos sem eu ser interrompido.

Eu queria ser um streamer programador de sucesso igual ao... hm... Eu não conheço ninguém que programa, que faz streaming e que faz sucesso... Tanto faz! Eu vou ser o primeiro a conquistar essa marca, pois eu sou especial!

Um tal de Ben Awad já falou de todos os problemas sobre fazer live streaming de programação, mas eu vou conseguir superar os problemas, pois novamente, eu sou especial! Aluguei até um escritório para que eu possa ter a paz e harmonia que eu tanto almejava, para que a stream fosse perfeita e eu conseguisse ser popular no mesmo nível de famosos como o SypherPK, Ludwig, Ninja, Pokimane... Ah, mal posso esperar por isso!

...

Até que eu experimentei fazer streams de programação, e a realidade é mais enfadonha que a ilusão que eu tinha.

---

Desde 2011 eu usava o nickname "SonicteamPower" para as coisas aleatórias que eu fazia na internet, dentre elas, o meu blog e o meu canal no YouTube, onde eu tentava realizar o meu sonho de ser um YouTuber famoso que passa o dia jogando games.

• Sonic Team = equipe da SEGA que faz jogos do Sonic
• Power = parte roubada do nome do antigo fansite Power Sonic

Mas em 2013 eu decidi mudar o meu nick para algo melhor... algo mais cativante, pois o meu sonho de tentar ser um YouTuber de sucesso tinha acabado após ter sido rejeitado da TGN, uma network de YouTubers que eu queria entrar nela pois o cazum8 estava nela e eu era muito fã dele. Então, ao invés de resolver o verdadeiro problema de não me aceitarem (meus vídeos não eram bons), eu decidi mudar de nickname para dar um ar novo a minha carreira de YouTuber.

Eu queria colocar "PowerGamer", mas na época o YouTube não deixava dois canais terem o mesmo nome, então o YouTube me sugeriu colocar "MrPowerGamer", e aí eu taquei um "BR" no final só para saberem que eu sou brasileiro. Enquanto para nós o "BR" deixa claro que eu sou brasileiro, já conheci muito gringo que não sabia que o "BR" do meu nick significava "Brasil".

No começo de 2014 eu usava o nickname "LeonardoGamer", mas esse nome era tão genérico e sem graça que depois eu voltei a usar "MrPowerGamerBR".

Enquanto hoje em dia o meu nickname tem um ar tosco e antiquado, com pessoas dizendo "troca isso, parece nick de youtuber de 2013", eu gosto dele e não pretendo mudar, pois eu já fiz muitas coisas com esse nick e as pessoas acabam me reconhecendo por causa dele, me deixando feliz pois é como você tivesse deixado uma "marca" na vida da pessoa.

E o melhor de tudo, ele é único!

---

No /r/brdev, /u/sock_templar compartilhou um endpoint dos Correios que permite você rastrear pacotes dos Correios.

curl https://proxyapp.correios.com.br/v1/sro-rastro/CodigoDeRastreioAqui

Ela mostra os eventos sobre o pacote, parecido com os eventos que você recebe ao rastrear um pacote pelo website dos Correios, e inclusive esse endpoint é usado em várias libraries que existem pela internet.

Mas sabia que existe outro endpoint de rastreio dos Correios, que mostra mais informações sobre o pacote sendo rastreado, como também permite você rastrear vários pacotes em um único request?

---

---

If your PostgreSQL instance is randomly going into recovery mode... Have you checked if your disk is full?

2022-04-26 13:22:24.962 UTC [382] LOG: database system was not properly shut down; automatic recovery in progress

In the past, if my PostgreSQL LXC container disk was full, PostgreSQL would throw I/O errors when trying to write new data to it, so when my instance was randomly going into recovery, I was stumped, what is causing this?

Until by accident I noticed that my disk was dangerously close to full, so I've decided to check if the disk being full could be culprit of why it was going into recovery, and, fortunately, it was!

My theory is that this was a change made in newer PostgreSQL versions. If the disk is full, fsync fails, which causes PostgreSQL to consider that the data is now unreliable and starts restoring the database state from WAL files. Previous PostgreSQL versions were using fsync incorrectly, then changing how it works so, if fsync fails, PostgreSQL will automatically shut down and initiate recovery mode.

Or maybe it is because I migrated my LXC container from a EXT4 partition to ZFS, who knows!

But if your free disk space is suspiciously low after a recover, and you want to be sure that this is what triggered recovery: Create a large file that fits in your free disk space, wait until PostgreSQL tries doing any I/O, and check if PostgreSQL crashes and starts automatic recovery. If yes, then your disk being full is what could have triggered recovery mode!

However, you may be wondering...

If the issue was that there wasn't any free space, how PostgreSQL was able to successfully recover and start up again?

When PostgreSQL finishes its recovery process, a bunch of free space was cleared up, this may be because PostgreSQL was reading data from WAL files, applying them to the tables' data, and then deleting the WAL files, which ends up freeing disk space, and that allows PostgreSQL to continue working until the disk fills up again.

Anyhow, if your PostgreSQL is randomly going into recovery for no apparent reason, don't forget to check your available free disk space!

---

Trying to figure out how to list files from a Java Resources folder is hard, there are tons of solutions on StackOverflow, however most of them are weird hacks and they only work when executing your app via your IDE, or when executing your app via the command line, not both.

Joop Eggen's answer is awesome, however it can only do one of two things:

• Read the resources content when running from a IDE
• Read the resources content when running the JAR via the command line

So here's an example (Kotlin, but it should be easy to migrate it to Java) that allows you to have both: Reading the resources content when running from a IDE or via the command line!

    val uri = MainApp::class.java.getResource("/locales/").toURI()
    val dirPath = try {
        Paths.get(uri)
    } catch (e: FileSystemNotFoundException) {
        // If this is thrown, then it means that we are running the JAR directly (example: not from an IDE)
        val env = mutableMapOf<String, String>()
        FileSystems.newFileSystem(uri, env).getPath("/locales/")
    }

    Files.list(dirPath).forEach {
        println(it.fileName)
        if (it.fileName.toString().endsWith("txt")) {
            println("Result:")
            println(Files.readString(it))
        }
    }

StackOverflow Post: https://stackoverflow.com/a/67839914/7271796

---