Docker multi-platform images
Invalid Exec Format They gave me a MacBook Pro at work. I built a docker image locally. I pushed it to Amazon cloud to run. I got “invalid exec format” […]
Logarithmic Fibonacci
Code: https://github.com/ikriv-samples/logarthmic-fibonacci. Fibonacci sequence is defined as a sequence starting with 0, 1 where each subsequent member is calculated as fib(n) = fib(n-1)+fib(n-2). This yields an infinite sequence 0, 1, […]
Running Pytorch with Apache mod_wsgi
TL;DR make sure to add magic words WSGIApplicationGroup %{GLOBAL} to the Apache config, otherwise import torch will hang. I tried to integrate my PyTorch AI model with my Apache web […]
Ubuntu: uid/gid option required to gain write access to remote share
I have Synology NAS, and I share the “home” directory as a CIFS share. From Windows, I simply do net use N: \\home\nas /user:myuser *, and it works. Corresponding command […]
WordPress themes and software decay
I have discovered a few broken things with my WordPress site. This post, as much of this blog, is mostly description of events, so I won’t forget what exactly happened. […]
C++ how future::wait_until(time) handles multiple clocks?
std::future::wait_until(time) converts time to a standard clock, and thus implicitly assumes that all clocks run at the same pace.
Design and evolution of C++ future continuations
Standard C++ is still lacking standardized future continuation. Boost has “experimental” implementation that is 11 years old. In the meantime, at least three major proposals were brought before the standard committee, but none made it into the standard. Current proposal is 190 printed pages long. The earliest it can become standard is C++26, and even that is not guaranteed. Such glacial speed of change results in a lot of confusion and feature lag behind other languages. C# had continuations since 2010, and JavaScript since 2015 (EC6). While C++ 11 was relatively on par with the industry when introducing futures, current C++ is quite behind the crowd. “Experimental” code should not stick around for over a decade in any library, and especially in a semi-standard library like Boost. There must be a way to solve problems faster.
C++ syntax rant (template guides)
C++ syntax is notoriously complex and full of gotchas both for compilers and for humans. I don’t know what was the reasoning in selecting the syntax for template deduction guides […]
Stopping bash script on error, and what can possibly go wrong
TL;DR Don’t mix set -e and && operators in bash, it’s not going to work well. What is ‘set -e’ Bash command set -e stops the script when any of […]
Fun with fold expressions
Fold expressions, starting with C++ 17, provide succinct, if somewhat unorthodox, syntax for processing of parameter packs. Printing a pack to standard output Suppose, I want to write a function […]