diff options
Diffstat (limited to 'po/fr/LC_MESSAGES')
86 files changed, 12976 insertions, 0 deletions
diff --git a/po/fr/LC_MESSAGES/_articles/2018-07-17-running-guix-on-nixos.po b/po/fr/LC_MESSAGES/_articles/2018-07-17-running-guix-on-nixos.po new file mode 100644 index 0000000..c76ab51 --- /dev/null +++ b/po/fr/LC_MESSAGES/_articles/2018-07-17-running-guix-on-nixos.po @@ -0,0 +1,235 @@ +# +msgid "" +msgstr "" + +msgid "" +"title: Running Guix on NixOS\n" +"date: 2018-07-17\n" +"layout: post\n" +"lang: en\n" +"ref: running-guix-on-nixos" +msgstr "" + +msgid "" +"I wanted to run Guix on a NixOS machine. Even though the Guix manual " +"explains how to do it [step by " +"step](https://www.gnu.org/software/guix/manual/en/html_node/Binary-" +"Installation.html#Binary-Installation), I needed a few extra ones to make it" +" work properly." +msgstr "" + +msgid "Creating `guixbuilder` users" +msgstr "" + +msgid "" +"Guix requires you to create non-root users that will be used to perform the " +"builds in the isolated environments." +msgstr "" + +msgid "" +"The [manual](https://www.gnu.org/software/guix/manual/en/html_node/Build-" +"Environment-Setup.html#Build-Environment-Setup) already provides you with a " +"ready to run (as root) command for creating the build users:" +msgstr "" + +msgid "" +"However, In my personal NixOS I have disabled " +"[`users.mutableUsers`](https://nixos.org/nixos/manual/index.html#sec-user-" +"management), which means that even if I run the above command it means that " +"they'll be removed once I rebuild my OS:" +msgstr "" + +msgid "" +"Instead of enabling `users.mutableUsers` I could add the Guix users by " +"adding them to my system configuration:" +msgstr "" + +msgid "" +"Here I used `fold` and the `//` operator to merge all of the configuration " +"sets into a single `extraUsers` value." +msgstr "" + +msgid "Creating the `systemd` service" +msgstr "" + +msgid "One other thing missing was the `systemd` service." +msgstr "" + +msgid "" +"First I couldn't just copy the `.service` file to `/etc` since in NixOS that" +" folder isn't writable. But also I wanted the service to be better " +"integrated with the OS." +msgstr "" + +msgid "" +"That was a little easier than creating the users, all I had to do was " +"translate the provided [`guix-" +"daemon.service.in`](https://git.savannah.gnu.org/cgit/guix.git/tree/etc/guix-" +"daemon.service.in?id=00c86a888488b16ce30634d3a3a9d871ed6734a2) configuration" +" to an equivalent Nix expression" +msgstr "" + +msgid "This sample `systemd` configuration file became:" +msgstr "" + +msgid "" +"There you go! After running `sudo nixos-rebuild switch` I could get Guix up " +"and running:" +msgstr "" + +msgid "Some improvements to this approach are:" +msgstr "" + +msgid "" +"looking into [NixOS modules](https://nixos.org/nixos/manual/index.html#sec-" +"writing-modules) and trying to bundle everything together into a single " +"logical unit;" +msgstr "" + +msgid "" +"[build Guix from " +"source](https://www.gnu.org/software/guix/manual/en/html_node/Requirements.html#Requirements)" +" and share the Nix store and daemon with Guix." +msgstr "" + +msgid "Happy Guix/Nix hacking!" +msgstr "" + +msgid "" +"groupadd --system guixbuild\n" +"for i in `seq -w 1 10`;\n" +"do\n" +" useradd -g guixbuild -G guixbuild \\\n" +" -d /var/empty -s `which nologin` \\\n" +" -c \"Guix build user $i\" --system \\\n" +" guixbuilder$i;\n" +"done\n" +msgstr "" + +msgid "" +"$ sudo nixos-rebuild switch\n" +"(...)\n" +"removing user ‘guixbuilder7’\n" +"removing user ‘guixbuilder3’\n" +"removing user ‘guixbuilder10’\n" +"removing user ‘guixbuilder1’\n" +"removing user ‘guixbuilder6’\n" +"removing user ‘guixbuilder9’\n" +"removing user ‘guixbuilder4’\n" +"removing user ‘guixbuilder2’\n" +"removing user ‘guixbuilder8’\n" +"removing user ‘guixbuilder5’\n" +"(...)\n" +msgstr "" + +msgid "" +"{ config, pkgs, ...}:\n" +"\n" +"{\n" +"\n" +" # ... NixOS usual config ellided ...\n" +"\n" +" users = {\n" +" mutableUsers = false;\n" +"\n" +" extraUsers =\n" +" let\n" +" andrehUser = {\n" +" andreh = {\n" +" # my custom user config\n" +" };\n" +" };\n" +" buildUser = (i:\n" +" {\n" +" \"guixbuilder${i}\" = { # guixbuilder$i\n" +" group = \"guixbuild\"; # -g guixbuild\n" +" extraGroups = [\"guixbuild\"]; # -G guixbuild\n" +" home = \"/var/empty\"; # -d /var/empty\n" +" shell = pkgs.nologin; # -s `which nologin`\n" +" description = \"Guix build user ${i}\"; # -c \"Guix buid user $i\"\n" +" isSystemUser = true; # --system\n" +" };\n" +" }\n" +" );\n" +" in\n" +" # merge all users\n" +" pkgs.lib.fold (str: acc: acc // buildUser str)\n" +" andrehUser\n" +" # for i in `seq -w 1 10`\n" +" (map (pkgs.lib.fixedWidthNumber 2) (builtins.genList (n: n+1) 10));\n" +"\n" +" extraGroups.guixbuild = {\n" +" name = \"guixbuild\";\n" +" };\n" +" };\n" +"}\n" +msgstr "" + +msgid "" +"# This is a \"service unit file\" for the systemd init system to launch\n" +"# 'guix-daemon'. Drop it in /etc/systemd/system or similar to have\n" +"# 'guix-daemon' automatically started.\n" +"\n" +"[Unit]\n" +"Description=Build daemon for GNU Guix\n" +"\n" +"[Service]\n" +"ExecStart=/var/guix/profiles/per-user/root/guix-profile/bin/guix-daemon --build-users-group=guixbuild\n" +"Environment=GUIX_LOCPATH=/root/.guix-profile/lib/locale\n" +"RemainAfterExit=yes\n" +"StandardOutput=syslog\n" +"StandardError=syslog\n" +"\n" +"# See <https://lists.gnu.org/archive/html/guix-devel/2016-04/msg00608.html>.\n" +"# Some package builds (for example, go@1.8.1) may require even more than\n" +"# 1024 tasks.\n" +"TasksMax=8192\n" +"\n" +"[Install]\n" +"WantedBy=multi-user.target\n" +msgstr "" + +msgid "" +"guix-daemon = {\n" +" enable = true;\n" +" description = \"Build daemon for GNU Guix\";\n" +" serviceConfig = {\n" +" ExecStart = \"/var/guix/profiles/per-user/root/guix-profile/bin/guix-daemon --build-users-group=guixbuild\";\n" +" Environment=\"GUIX_LOCPATH=/root/.guix-profile/lib/locale\";\n" +" RemainAfterExit=\"yes\";\n" +" StandardOutput=\"syslog\";\n" +" StandardError=\"syslog\";\n" +" TaskMax= \"8192\";\n" +" };\n" +" wantedBy = [ \"multi-user.target\" ];\n" +"};\n" +msgstr "" + +msgid "" +"$ guix package -i hello\n" +"The following package will be installed:\n" +" hello 2.10 /gnu/store/bihfrh609gkxb9dp7n96wlpigiv3krfy-hello-2.10\n" +"\n" +"substitute: updating substitutes from 'https://mirror.hydra.gnu.org'... 100.0%\n" +"The following derivations will be built:\n" +" /gnu/store/nznmdn6inpwxnlkrasydmda4s2vsp9hg-profile.drv\n" +" /gnu/store/vibqrvw4c8lacxjrkqyzqsdrmckv77kq-fonts-dir.drv\n" +" /gnu/store/hi8alg7wi0wgfdi3rn8cpp37zhx8ykf3-info-dir.drv\n" +" /gnu/store/cvkbp378cvfjikz7mjymhrimv7j12p0i-ca-certificate-bundle.drv\n" +" /gnu/store/d62fvxymnp95rzahhmhf456bsf0xg1c6-manual-database.drv\n" +"Creating manual page database...\n" +"1 entries processed in 0.0 s\n" +"2 packages in profile\n" +"$ hello\n" +"Hello, world!\n" +msgstr "" + +msgid "" +"I couldn't just install GuixSD because my wireless network card doesn't have" +" any free drivers (yet)." +msgstr "" + +#~ msgid "" +#~ "I couldn't just install GuixSD because my wireless network card doesn't have" +#~ " any free/libre drivers (yet)." +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_articles/2018-08-01-verifying-npm-ci-reproducibility.po b/po/fr/LC_MESSAGES/_articles/2018-08-01-verifying-npm-ci-reproducibility.po new file mode 100644 index 0000000..a4af1a6 --- /dev/null +++ b/po/fr/LC_MESSAGES/_articles/2018-08-01-verifying-npm-ci-reproducibility.po @@ -0,0 +1,216 @@ +# +msgid "" +msgstr "" + +msgid "" +"title: Verifying \"npm ci\" reproducibility\n" +"date: 2018-08-01\n" +"layout: post\n" +"lang: en\n" +"ref: verifying-npm-ci-reproducibility\n" +"updated_at: 2019-05-22" +msgstr "" + +msgid "" +"When [npm@5](https://blog.npmjs.org/post/161081169345/v500) came bringing " +"[package-locks](https://docs.npmjs.com/files/package-locks) with it, I was " +"confused about the benefits it provided, since running `npm install` more " +"than once could resolve all the dependencies again and yield yet another " +"fresh `package-lock.json` file. The message saying \"you should add this " +"file to version control\" left me hesitant on what to do[^package-lock-" +"message](The)." +msgstr "" + +msgid "" +"However the [addition of `npm " +"ci`](https://blog.npmjs.org/post/171556855892/introducing-npm-ci-for-faster-" +"more-reliable) filled this gap: it's a stricter variation of `npm install` " +"which guarantees that \"[subsequent installs are able to generate identical " +"trees](https://docs.npmjs.com/files/package-lock.json)\". But are they " +"really identical? I could see that I didn't have the same problems of " +"different installation outputs, but I didn't know for **sure** if it was " +"really identical." +msgstr "" + +msgid "Computing the hash of a directory's content" +msgstr "" + +msgid "" +"I quickly searched for a way to check for the hash signature of an entire " +"directory tree, but I couldn't find one. I've made a poor man's [Merkle " +"tree](https://en.wikipedia.org/wiki/Merkle_tree) implementation using " +"`sha256sum` and a few piped commands at the terminal:" +msgstr "" + +msgid "Going through it line by line:" +msgstr "" + +msgid "#1 we define a Bash function called `merkle-tree`;" +msgstr "" + +msgid "" +"#2 it accepts a single argument: the directory to compute the merkle tree " +"from. If nothing is given, it runs on the current directory (`.`);" +msgstr "" + +msgid "" +"#3 we go to the directory, so we don't get different prefixes in `find`'s " +"output (like `../a/b`);" +msgstr "" + +msgid "" +"#4 we get all files from the directory tree. Since we're using `sha256sum` " +"to compute the hash of the file contents, we need to filter out folders from" +" it;" +msgstr "" + +msgid "" +"#5 we need to sort the output, since different file systems and `find` " +"implementations may return files in different orders;" +msgstr "" + +msgid "" +"#6 we use `xargs` to compute the hash of each file individually through " +"`sha256sum`. Since a file may contain spaces we need to escape it with " +"quotes;" +msgstr "" + +msgid "" +"#7 we compute the hash of the combined hashes. Since `sha256sum` output is " +"formatted like `<hash> <filename>`, it produces a different final hash if a " +"file ever changes name without changing it's content;" +msgstr "" + +msgid "" +"#8 we get the final hash output, excluding the `<filename>` (which is `-` in" +" this case, aka `stdin`)." +msgstr "" + +msgid "Positive points:" +msgstr "" + +msgid "" +"ignore timestamp: running more than once on different installation yields " +"the same hash;" +msgstr "" + +msgid "the name of the file is included in the final hash computation." +msgstr "" + +msgid "Limitations:" +msgstr "" + +msgid "it ignores empty folders from the hash computation;" +msgstr "" + +msgid "" +"the implementation's only goal is to represent using a digest whether the " +"content of a given directory is the same or not. Leaf presence checking is " +"obviously missing from it." +msgstr "" + +msgid "Testing locally with sample data" +msgstr "" + +msgid "It seems to work for this simple test case." +msgstr "" + +msgid "You can try copying and pasting it to verify the hash signatures." +msgstr "" + +msgid "Using `merkle-tree` to check the output of `npm ci`" +msgstr "" + +msgid "*I've done all of the following using Node.js v8.11.3 and npm@6.1.0.*" +msgstr "" + +msgid "" +"In this test case I'll take the main repo of " +"[Lerna](https://lernajs.io/)[^lerna-package-lock]:" +msgstr "" + +msgid "Good job `npm ci` :)" +msgstr "" + +msgid "" +"#6 and #9 take some time to run (21 seconds in my machine), but this " +"specific use case isn't performance sensitive. The slowest step is computing" +" the hash of each individual file." +msgstr "" + +msgid "Conclusion" +msgstr "" + +msgid "`npm ci` really \"generates identical trees\"." +msgstr "" + +msgid "" +"I'm not aware of any other existing solution for verifying the hash " +"signature of a directory. If you know any I'd [like to know](mailto:{{ " +"site.author.email }})." +msgstr "" + +msgid "*Edit*" +msgstr "" + +msgid "" +"[documentation](https://docs.npmjs.com/cli/install#description) claims `npm " +"install` is driven by the existing `package-lock.json`, but that's actually " +"[a little bit " +"tricky](https://github.com/npm/npm/issues/17979#issuecomment-332701215)." +msgstr "" + +msgid "" +"[^lerna-package-lock]: Finding a big known repo that actually committed the " +"`package-lock.json` file was harder than I expected." +msgstr "" + +msgid "" +"merkle-tree () {\n" +" dirname=\"${1-.}\"\n" +" pushd \"$dirname\"\n" +" find . -type f | \\\n" +" sort | \\\n" +" xargs -I{} sha256sum \"{}\" | \\\n" +" sha256sum | \\\n" +" awk '{print $1}'\n" +" popd\n" +"}\n" +msgstr "" + +msgid "" +"mkdir /tmp/merkle-tree-test/\n" +"cd /tmp/merkle-tree-test/\n" +"mkdir -p a/b/ a/c/ d/\n" +"echo \"one\" > a/b/one.txt\n" +"echo \"two\" > a/c/two.txt\n" +"echo \"three\" > d/three.txt\n" +"merkle-tree . # output is be343bb01fe00aeb8fef14a3e16b1c3d1dccbf86d7e41b4753e6ccb7dc3a57c3\n" +"merkle-tree . # output still is be343bb01fe00aeb8fef14a3e16b1c3d1dccbf86d7e41b4753e6ccb7dc3a57c3\n" +"echo \"four\" > d/four.txt\n" +"merkle-tree . # output is now b5464b958969ed81815641ace96b33f7fd52c20db71a7fccc45a36b3a2ae4d4c\n" +"rm d/four.txt\n" +"merkle-tree . # output back to be343bb01fe00aeb8fef14a3e16b1c3d1dccbf86d7e41b4753e6ccb7dc3a57c3\n" +"echo \"hidden-five\" > a/b/one.txt\n" +"merkle-tree . # output changed 471fae0d074947e4955e9ac53e95b56e4bc08d263d89d82003fb58a0ffba66f5\n" +msgstr "" + +msgid "" +"cd /tmp/\n" +"git clone https://github.com/lerna/lerna.git\n" +"cd lerna/\n" +"git checkout 57ff865c0839df75dbe1974971d7310f235e1109\n" +"npm ci\n" +"merkle-tree node_modules/ # outputs 11e218c4ac32fac8a9607a8da644fe870a25c99821167d21b607af45699afafa\n" +"rm -rf node_modules/\n" +"npm ci\n" +"merkle-tree node_modules/ # outputs 11e218c4ac32fac8a9607a8da644fe870a25c99821167d21b607af45699afafa\n" +"npm ci # test if it also works with an existing node_modules/ folder\n" +"merkle-tree node_modules/ # outputs 11e218c4ac32fac8a9607a8da644fe870a25c99821167d21b607af45699afafa\n" +msgstr "" + +msgid "2019-05-22: Fix spelling." +msgstr "" + +#~ msgid "2019/05/22: Fix spelling." +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_articles/2018-12-21-using-youtube-dl-to-manage-youtube-subscriptions.po b/po/fr/LC_MESSAGES/_articles/2018-12-21-using-youtube-dl-to-manage-youtube-subscriptions.po new file mode 100644 index 0000000..c66831d --- /dev/null +++ b/po/fr/LC_MESSAGES/_articles/2018-12-21-using-youtube-dl-to-manage-youtube-subscriptions.po @@ -0,0 +1,383 @@ +# +msgid "" +msgstr "" + +msgid "" +"title: Using \"youtube-dl\" to manage YouTube subscriptions\n" +"date: 2018-12-21\n" +"layout: post\n" +"lang: en\n" +"ref: using-youtube-dl-to-manage-youtube-subscriptions" +msgstr "" + +msgid "" +"I've recently read the " +"[announcement](https://www.reddit.com/r/DataHoarder/comments/9sg8q5/i_built_a_selfhosted_youtube_subscription_manager/)" +" of a very nice [self-hosted YouTube subscription " +"manager](https://github.com/chibicitiberiu/ytsm). I haven't used YouTube's " +"built-in subscriptions for a while now, and haven't missed it at all. When I" +" saw the announcement, I considered writing about the solution I've built on" +" top of [youtube-dl](https://youtube-dl.org/)." +msgstr "" + +msgid "Background: the problem with YouTube" +msgstr "" + +msgid "" +"In many ways, I agree with [André Staltz's view on data ownership and " +"privacy](https://staltz.com/what-happens-when-you-block-internet-" +"giants.html):" +msgstr "" + +msgid "" +"I started with the basic premise that \"I want to be in control of my " +"data\". Sometimes that meant choosing when to interact with an internet " +"giant and how much I feel like revealing to them. Most of times it meant not" +" interacting with them at all. I don't want to let them be in full control " +"of how much they can know about me. I don't want to be in autopilot mode. " +"(...) Which leads us to YouTube. While I was able to find alternatives to " +"Gmail (Fastmail), Calendar (Fastmail), Translate (Yandex Translate), *etc.* " +"YouTube remains as the most indispensable Google-owned web service. It is " +"really really hard to avoid consuming YouTube content. It was probably the " +"smartest startup acquisition ever. My privacy-oriented alternative is to " +"watch YouTube videos through Tor, which is technically feasible but not " +"polite to use the Tor bandwidth for these purposes. I'm still scratching my " +"head with this issue." +msgstr "" + +msgid "" +"Even though I don't use most alternative services he mentions, I do watch " +"videos from YouTube. But I also feel uncomfortable logging in to YouTube " +"with a Google account, watching videos, creating playlists and similar " +"things." +msgstr "" + +msgid "" +"Using the mobile app is worse: you can't even block ads in there. You're in " +"less control on what you share with YouTube and Google." +msgstr "" + +msgid "youtube-dl" +msgstr "" + +msgid "" +"youtube-dl is a command-line tool for downloading videos, from YouTube and " +"[many other sites](https://rg3.github.io/youtube-dl/supportedsites.html):" +msgstr "" + +msgid "" +"It can be used to download individual videos as showed above, but it also " +"has some interesting flags that we can use:" +msgstr "" + +msgid "" +"`--output`: use a custom template to create the name of the downloaded file;" +msgstr "" + +msgid "" +"`--download-archive`: use a text file for recording and remembering which " +"videos were already downloaded;" +msgstr "" + +msgid "" +"`--prefer-free-formats`: prefer free video formats, like `webm`, `ogv` and " +"Matroska `mkv`;" +msgstr "" + +msgid "" +"`--playlist-end`: how many videos to download from a \"playlist\" (a " +"channel, a user or an actual playlist);" +msgstr "" + +msgid "" +"`--write-description`: write the video description to a `.description` file," +" useful for accessing links and extra content." +msgstr "" + +msgid "Putting it all together:" +msgstr "" + +msgid "" +"This will download the latest 20 videos from the selected channel, and write" +" down the video IDs in the `youtube-dl-seen.conf` file. Running it " +"immediately after one more time won't have any effect." +msgstr "" + +msgid "" +"If the channel posts one more video, running the same command again will " +"download only the last video, since the other 19 were already downloaded." +msgstr "" + +msgid "" +"With this basic setup you have a minimal subscription system at work, and " +"you can create some functions to help you manage that:" +msgstr "" + +msgid "" +"With these functions, you now can have a subscription fetching script to " +"download the latest videos from your favorite channels:" +msgstr "" + +msgid "" +"Now, whenever you want to watch the latest videos, just run the above script" +" and you'll get all of them in your local machine." +msgstr "" + +msgid "Tradeoffs" +msgstr "" + +msgid "I've made it for myself, with my use case in mind" +msgstr "" + +msgid "Offline" +msgstr "" + +msgid "" +"My internet speed it somewhat reasonable[^internet-speed], but it is really " +"unstable. Either at work or at home, it's not uncommon to loose internet " +"access for 2 minutes 3~5 times every day, and stay completely offline for a " +"couple of hours once every week." +msgstr "" + +msgid "" +"Working through the hassle of keeping a playlist on disk has payed off many," +" many times. Sometimes I even not notice when the connection drops for some " +"minutes, because I'm watching a video and working on some document, all on " +"my local computer." +msgstr "" + +msgid "" +"There's also no quality adjustment for YouTube's web player, I always pick " +"the higher quality and it doesn't change during the video. For some types of" +" content, like a podcast with some tiny visual resources, this doesn't " +"change much. For other types of content, like a keynote presentation with " +"text written on the slides, watching on 144p isn't really an option." +msgstr "" + +msgid "" +"If the internet connection drops during the video download, youtube-dl will " +"resume from where it stopped." +msgstr "" + +msgid "" +"This is an offline first benefit that I really like, and works well for me." +msgstr "" + +msgid "Sync the \"seen\" file" +msgstr "" + +msgid "" +"I already have a running instance of Nextcloud, so just dumping the " +"`youtube-dl-seen.conf` file inside Nextcloud was a no-brainer." +msgstr "" + +msgid "" +"You could try putting it in a dedicated git repository, and wrap the script " +"with an autocommit after every run. If you ever had a merge conflict, you'd " +"simply accept all changes and then run:" +msgstr "" + +msgid "to tidy up the file." +msgstr "" + +msgid "Doesn't work on mobile" +msgstr "" + +msgid "" +"My primary device that I use everyday is my laptop, not my phone. It works " +"well for me this way." +msgstr "" + +msgid "" +"Also, it's harder to add ad-blockers to mobile phones, and most mobile " +"software still depends on Google's and Apple's blessing." +msgstr "" + +msgid "" +"If you wish, you can sync the videos to the SD card periodically, but that's" +" a bit of extra manual work." +msgstr "" + +msgid "The Good" +msgstr "" + +msgid "Better privacy" +msgstr "" + +msgid "" +"We don't even have to configure the ad-blocker to keep ads and trackers " +"away!" +msgstr "" + +msgid "" +"YouTube still has your IP address, so using a VPN is always a good idea. " +"However, a timing analysis would be able to identify you (considering the " +"current implementation)." +msgstr "" + +msgid "No need to self-host" +msgstr "" + +msgid "There's no host that needs maintenance. Everything runs locally." +msgstr "" + +msgid "" +"As long as you keep youtube-dl itself up to date and sync your \"seen\" " +"file, there's little extra work to do." +msgstr "" + +msgid "Track your subscriptions with git" +msgstr "" + +msgid "" +"After creating a `subscriptions.sh` executable that downloads all the " +"videos, you can add it to git and use it to track metadata about your " +"subscriptions." +msgstr "" + +msgid "The Bad" +msgstr "" + +msgid "Maximum playlist size is your disk size" +msgstr "" + +msgid "" +"This is a good thing for getting a realistic view on your actual \"watch " +"later\" list. However I've run out of disk space many times, and now I need " +"to be more aware of how much is left." +msgstr "" + +msgid "The Ugly" +msgstr "" + +msgid "" +"We can only avoid all the bad parts of YouTube with youtube-dl as long as " +"YouTube keeps the videos public and programmatically accessible. If YouTube " +"ever blocks that we'd loose the ability to consume content this way, but " +"also loose confidence on considering YouTube a healthy repository of videos " +"on the internet." +msgstr "" + +msgid "Going beyond" +msgstr "" + +msgid "" +"Since you're running everything locally, here are some possibilities to be " +"explored:" +msgstr "" + +msgid "A playlist that is too long for being downloaded all at once" +msgstr "" + +msgid "" +"You can wrap the `download_playlist` function (let's call the wrapper " +"`inc_download`) and instead of passing it a fixed number to the `--playlist-" +"end` parameter, you can store the `$n` in a folder (something like " +"`$HOME/.yt-db/$PLAYLIST_ID`) and increment it by `$step` every time you run " +"`inc_download`." +msgstr "" + +msgid "" +"This way you can incrementally download videos from a huge playlist without " +"filling your disk with gigabytes of content all at once." +msgstr "" + +msgid "Multiple computer scenario" +msgstr "" + +msgid "" +"The `download_playlist` function could be aware of the specific machine that" +" it is running on and apply specific policies depending on the machine: " +"always download everything; only download videos that aren't present " +"anywhere else; *etc.*" +msgstr "" + +msgid "Conclusion" +msgstr "" + +msgid "" +"youtube-dl is a great tool to keep at hand. It covers a really large range " +"of video websites and works robustly." +msgstr "" + +msgid "" +"Feel free to copy and modify this code, and [send me](mailto:{{ " +"site.author.email }}) suggestions of improvements or related content." +msgstr "" + +msgid "*Edit*" +msgstr "" + +msgid "" +"[^internet-speed]: Considering how expensive it is and the many ways it " +"could be better, but also how much it has improved over the last years, I " +"say it's reasonable." +msgstr "" + +msgid "" +"$ youtube-dl https://www.youtube.com/watch?v=rnMYZnY3uLA\n" +"[youtube] rnMYZnY3uLA: Downloading webpage\n" +"[youtube] rnMYZnY3uLA: Downloading video info webpage\n" +"[download] Destination: A Origem da Vida _ Nerdologia-rnMYZnY3uLA.mp4\n" +"[download] 100% of 32.11MiB in 00:12\n" +msgstr "" + +msgid "" +"$ youtube-dl \"https://www.youtube.com/channel/UClu474HMt895mVxZdlIHXEA\" \\\n" +" --download-archive ~/Nextcloud/cache/youtube-dl-seen.conf \\\n" +" --prefer-free-formats \\\n" +" --playlist-end 20 \\\n" +" --write-description \\\n" +" --output \"~/Downloads/yt-dl/%(uploader)s/%(upload_date)s - %(title)s.%(ext)s\"\n" +msgstr "" + +msgid "" +"#!/bin/sh\n" +"\n" +"export DEFAULT_PLAYLIST_END=15\n" +"\n" +"download() {\n" +" youtube-dl \"$1\" \\\n" +" --download-archive ~/Nextcloud/cache/youtube-dl-seen.conf \\\n" +" --prefer-free-formats \\\n" +" --playlist-end $2 \\\n" +" --write-description \\\n" +" --output \"~/Downloads/yt-dl/%(uploader)s/%(upload_date)s - %(title)s.%(ext)s\"\n" +"}\n" +"export -f download\n" +"\n" +"\n" +"download_user() {\n" +" download \"https://www.youtube.com/user/$1\" ${2-$DEFAULT_PLAYLIST_END}\n" +"}\n" +"export -f download_user\n" +"\n" +"\n" +"download_channel() {\n" +" download \"https://www.youtube.com/channel/$1\" ${2-$DEFAULT_PLAYLIST_END}\n" +"}\n" +"export -f download_channel\n" +"\n" +"\n" +"download_playlist() {\n" +" download \"https://www.youtube.com/playlist?list=$1\" ${2-$DEFAULT_PLAYLIST_END}\n" +"}\n" +"export -f download_playlist\n" +msgstr "" + +msgid "" +"#!/bin/sh\n" +"\n" +"download_user ClojureTV 15\n" +"download_channel \"UCmEClzCBDx-vrt0GuSKBd9g\" 100\n" +"download_playlist \"PLqG7fA3EaMRPzL5jzd83tWcjCUH9ZUsbX\" 15\n" +msgstr "" + +msgid "$ uniq youtube-dl-seen.conf > youtube-dl-seen.conf\n" +msgstr "" + +msgid "2019-05-22: Fix spelling." +msgstr "" + +#~ msgid "2019/05/22: Fix spelling." +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_articles/2019-06-02-using-nixos-as-an-stateless-workstation.po b/po/fr/LC_MESSAGES/_articles/2019-06-02-using-nixos-as-an-stateless-workstation.po new file mode 100644 index 0000000..c469b02 --- /dev/null +++ b/po/fr/LC_MESSAGES/_articles/2019-06-02-using-nixos-as-an-stateless-workstation.po @@ -0,0 +1,229 @@ +# +msgid "" +msgstr "" + +msgid "" +"Last week[^last-week] I changed back to an old[^old-computer] Samsung " +"laptop, and installed [NixOS](https://nixos.org/) on it." +msgstr "" + +msgid "" +"After using NixOS on another laptop for around two years, I wanted verify " +"how reproducible was my desktop environment, and how far does NixOS actually" +" can go on recreating my whole OS from my configuration files and personal " +"data. I gravitated towards NixOS after trying (and failing) to create an " +"`install.sh` script that would imperatively install and configure my whole " +"OS using apt-get. When I found a GNU/Linux distribution that was built on " +"top of the idea of declaratively specifying the whole OS I was automatically" +" convinced[^convinced-by-declarative-aspect]." +msgstr "" + +msgid "" +"I was impressed. Even though I've been experiencing the benefits of Nix " +"isolation daily, I always felt skeptical that something would be missing, " +"because the devil is always on the details. But the result was much better " +"than expected!" +msgstr "" + +msgid "There were only 2 missing configurations:" +msgstr "" + +msgid "tap-to-click on the touchpad wasn't enabled by default;" +msgstr "" + +msgid "" +"the default theme from the gnome-terminal is \"Black on white\" instead of " +"\"White on black\"." +msgstr "" + +msgid "That's all." +msgstr "" + +msgid "" +"I haven't checked if I can configure those in NixOS GNOME module, but I " +"guess both are scriptable and could be set in a fictional `setup.sh` run." +msgstr "" + +msgid "This makes me really happy, actually. More happy than I anticipated." +msgstr "" + +msgid "" +"Having such a powerful declarative OS makes me feel like my data is the " +"really important stuff (as it should be), and I can interact with it on any " +"workstation. All I need is an internet connection and a few hours to " +"download everything. It feels like my physical workstation and the installed" +" OS are serving me and my data, instead of me feeling as hostage to the " +"specific OS configuration at the moment. Having a few backup copies of " +"everything important extends such peacefulness." +msgstr "" + +msgid "" +"After this positive experience with recreating my OS from simple Nix " +"expressions, I started to wonder how far I could go with this, and started " +"considering other areas of improvements:" +msgstr "" + +msgid "First run on a fresh NixOS installation" +msgstr "" + +msgid "" +"Right now the initial setup relies on non-declarative manual tasks, like " +"decrypting some credentials, or manually downloading **this** git repository" +" with specific configurations before **that** one." +msgstr "" + +msgid "" +"I wonder what some areas of improvements are on this topic, and if investing" +" on it is worth it (both time-wise and happiness-wise)." +msgstr "" + +msgid "Emacs" +msgstr "" + +msgid "" +"Right now I'm using the [Spacemacs](http://spacemacs.org/), which is a " +"community package curation and configuration on top of " +"[Emacs](https://www.gnu.org/software/emacs/)." +msgstr "" + +msgid "" +"Spacemacs does support the notion of " +"[layers](http://spacemacs.org/doc/LAYERS.html), which you can declaratively " +"specify and let Spacemacs do the rest." +msgstr "" + +msgid "" +"However this solution isn't nearly as robust as Nix: being purely " +"functional, Nix does describe everything required to build a derivation, and" +" knows how to do so. Spacemacs it closer to more traditional package " +"managers: even though the layers list is declarative, the installation is " +"still very much imperative. I've had trouble with Spacemacs not behaving the" +" same on different computers, both with identical configurations, only " +"brought to convergence back again after a `git clean -fdx` inside " +"`~/.emacs.d/`." +msgstr "" + +msgid "" +"The ideal solution would be managing Emacs packages with Nix itself. After a" +" quick search I did found that [there is support for Emacs packages in " +"Nix](https://nixos.org/nixos/manual/index.html#module-services-emacs-adding-" +"packages). So far I was only aware of [Guix support for Emacs " +"packages](https://www.gnu.org/software/guix/manual/en/html_node/Application-" +"Setup.html#Emacs-Packages)." +msgstr "" + +msgid "" +"This isn't a trivial change because Spacemacs does include extra curation " +"and configuration on top of Emacs packages. I'm not sure the best way to " +"improve this right now." +msgstr "" + +msgid "myrepos" +msgstr "" + +msgid "" +"I'm using [myrepos](https://myrepos.branchable.com/) to manage all my git " +"repositories, and the general rule I apply is to add any repository specific" +" configuration in myrepos' `checkout` phase:" +msgstr "" + +msgid "" +"This way when I clone this repo again the email sending is already pre-" +"configured." +msgstr "" + +msgid "" +"This works well enough, but the solution is too imperative, and my " +"`checkout` phases tend to become brittle over time if not enough care is " +"taken." +msgstr "" + +msgid "GNU Stow" +msgstr "" + +msgid "Conclusion" +msgstr "" + +msgid "" +"I'm really satisfied with NixOS, and I intend to keep using it. If what I've" +" said interests you, maybe try tinkering with the [Nix package " +"manager](https://nixos.org/nix/) (not the whole NixOS) on your current " +"distribution (it can live alongside any other package manager)." +msgstr "" + +msgid "" +"If you have experience with declarative Emacs package managements, GNU Stow " +"or any similar tool, *etc.*, [I'd like some tips](mailto:{{ " +"site.author.email }}). If you don't have any experience at all, I'd still " +"love to hear from you." +msgstr "" + +msgid "" +"[^last-week]: \"Last week\" as of the start of this writing, so around the " +"end of May 2019." +msgstr "" + +msgid "" +"[^old-computer]: I was using a 32GB RAM, i7 and 250GB SSD Samsung laptop. " +"The switch was back to a 8GB RAM, i5 and 500GB HDD Dell laptop. The biggest " +"difference I noticed was on faster memory, both RAM availability and the " +"disk speed, but I had 250GB less local storage space." +msgstr "" + +msgid "" +"[^convinced-by-declarative-aspect]: The declarative configuration aspect is " +"something that I now completely take for granted, and wouldn't consider " +"using something which isn't declarative. A good metric to show this is me " +"realising that I can't pinpoint the moment when I decided to switch to " +"NixOS. It's like I had a distant past when this wasn't true." +msgstr "" + +msgid "" +"# sample ~/.mrconfig file snippet\n" +"[dev/guix/guix]\n" +"checkout =\n" +" git clone https://git.savannah.gnu.org/git/guix.git guix\n" +" cd guix/\n" +" git config sendemail.to guix-patches@gnu.org\n" +msgstr "" + +msgid "title: Using NixOS as an stateless workstation" +msgstr "" + +msgid "date: 2019-06-02" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: using-nixos-as-an-stateless-workstation" +msgstr "" + +msgid "" +"For my home profile and personal configuration I already have a few dozens " +"of symlinks that I manage manually. This has worked so far, but the solution" +" is sometimes fragile and [not declarative at " +"all](https://euandreh.xyz/dotfiles.git/tree/bash/symlinks.sh?id=316939aa215181b1d22b69e94241eef757add98d)." +" I wonder if something like [GNU Stow](https://www.gnu.org/software/stow/) " +"can help me simplify this." +msgstr "" + +#~ msgid "" +#~ "title: Using NixOS as an stateless workstation\n" +#~ "date: 2019-06-02\n" +#~ "layout: post\n" +#~ "lang: en\n" +#~ "ref: using-nixos-as-an-stateless-workstation" +#~ msgstr "" + +#~ msgid "" +#~ "For my home profile and personal configuration I already have a few dozens " +#~ "of symlinks that I manage manually. This has worked so far, but the solution" +#~ " is sometimes fragile and [not declarative at " +#~ "all](https://git.sr.ht/~euandreh/dotfiles/tree/316939aa215181b1d22b69e94241eef757add98d/bash/symlinks.sh#L14-75)." +#~ " I wonder if something like [GNU Stow](https://www.gnu.org/software/stow/) " +#~ "can help me simplify this." +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_articles/2020-08-10-guix-inside-sourcehut-builds-sr-ht-ci.po b/po/fr/LC_MESSAGES/_articles/2020-08-10-guix-inside-sourcehut-builds-sr-ht-ci.po new file mode 100644 index 0000000..2396848 --- /dev/null +++ b/po/fr/LC_MESSAGES/_articles/2020-08-10-guix-inside-sourcehut-builds-sr-ht-ci.po @@ -0,0 +1,154 @@ +# +msgid "" +msgstr "" + +msgid "" +"title: Guix inside sourcehut builds.sr.ht CI\n" +"date: 2020-08-10\n" +"updated_at: 2020-08-19\n" +"layout: post\n" +"lang: en\n" +"ref: guix-inside-sourcehut-builds-sr-ht-ci" +msgstr "" + +msgid "" +"After the release of the [NixOS images in " +"builds.sr.ht](https://man.sr.ht/builds.sr.ht/compatibility.md#nixos) and " +"much usage of it, I also started looking at [Guix](https://guix.gnu.org/) " +"and wondered if I could get it on the awesome builds.sr.ht service." +msgstr "" + +msgid "" +"The Guix manual section on the [binary " +"installation](https://guix.gnu.org/manual/en/guix.html#Binary-Installation) " +"is very thorough, and even a [shell installer " +"script](https://git.savannah.gnu.org/cgit/guix.git/plain/etc/guix-" +"install.sh) is provided, but it is built towards someone installing Guix on " +"their personal computer, and relies heavily on interactive input." +msgstr "" + +msgid "" +"I developed the following set of scripts that I have been using for some " +"time to run Guix tasks inside builds.sr.ht jobs. First, `install-guix.sh`:" +msgstr "" + +msgid "" +"Almost all of it is taken directly from the [binary " +"installation](https://guix.gnu.org/manual/en/guix.html#Binary-Installation) " +"section from the manual, with the interactive bits stripped out: after " +"downloading and extracting the Guix tarball, we create some symlinks, add " +"guixbuild users and authorize the `ci.guix.gnu.org.pub` signing key." +msgstr "" + +msgid "" +"After installing Guix, we perform a `guix pull` to update Guix inside " +"`start-guix.sh`:" +msgstr "" + +msgid "" +"Then we can put it all together in a sample `.build.yml` configuration file " +"I'm using myself:" +msgstr "" + +msgid "" +"We have to add the `guix-daemon` to `~/.buildenv` so it can be started on " +"every following task run. Also, since we used `wget` inside `install-" +"guix.sh`, we had to add it to the images package list." +msgstr "" + +msgid "" +"After the `install-guix` task, you can use Guix to build and test your " +"project, or run any `guix environment --ad-hoc my-package -- my script` :)" +msgstr "" + +msgid "Improvements" +msgstr "" + +msgid "" +"When I originally created this code I had a reason why to have both a `sudo`" +" call for `sudo ./scripts/install-guix.sh` and `sudo` usages inside " +"`install-guix.sh` itself. I couldn't figure out why (it feels like my past " +"self was a bit smarter 😬), but it feels ugly now. If it is truly required I " +"could add an explanation for it, or remove this entirely in favor of a more " +"elegant solution." +msgstr "" + +msgid "" +"I could also contribute the Guix image upstream to builds.sr.ht, but there " +"wasn't any build or smoke tests in the original " +"[repository](https://git.sr.ht/~sircmpwn/builds.sr.ht), so I wasn't inclined" +" to make something that just \"works on my machine\" or add a maintainence " +"burden to the author. I didn't look at it again recently, though." +msgstr "" + +msgid "" +"#!/usr/bin/env bash\n" +"set -x\n" +"set -Eeuo pipefail\n" +"\n" +"VERSION='1.0.1'\n" +"SYSTEM='x86_64-linux'\n" +"BINARY=\"guix-binary-${VERSION}.${SYSTEM}.tar.xz\"\n" +"\n" +"cd /tmp\n" +"wget \"https://ftp.gnu.org/gnu/guix/${BINARY}\"\n" +"tar -xf \"${BINARY}\"\n" +"\n" +"sudo mv var/guix /var/\n" +"sudo mv gnu /\n" +"sudo mkdir -p ~root/.config/guix\n" +"sudo ln -fs /var/guix/profiles/per-user/root/current-guix ~root/.config/guix/current\n" +"\n" +"GUIX_PROFILE=\"$(echo ~root)/.config/guix/current\"\n" +"source \"${GUIX_PROFILE}/etc/profile\"\n" +"\n" +"groupadd --system guixbuild\n" +"for i in $(seq -w 1 10);\n" +"do\n" +" useradd -g guixbuild \\\n" +" -G guixbuild \\\n" +" -d /var/empty \\\n" +" -s \"$(command -v nologin)\" \\\n" +" -c \"Guix build user ${i}\" --system \\\n" +" \"guixbuilder${i}\";\n" +"done\n" +"\n" +"mkdir -p /usr/local/bin\n" +"cd /usr/local/bin\n" +"ln -s /var/guix/profiles/per-user/root/current-guix/bin/guix .\n" +"ln -s /var/guix/profiles/per-user/root/current-guix/bin/guix-daemon .\n" +"\n" +"guix archive --authorize < ~root/.config/guix/current/share/guix/ci.guix.gnu.org.pub\n" +msgstr "" + +msgid "" +"#!/usr/bin/env bash\n" +"set -x\n" +"set -Eeuo pipefail\n" +"\n" +"sudo guix-daemon --build-users-group=guixbuild &\n" +"guix pull\n" +"guix package -u\n" +"guix --version\n" +msgstr "" + +msgid "" +"image: debian/stable\n" +"packages:\n" +" - wget\n" +"sources:\n" +" - https://git.sr.ht/~euandreh/songbooks\n" +"tasks:\n" +" - install-guix: |\n" +" cd ./songbooks/\n" +" ./scripts/install-guix.sh\n" +" ./scripts/start-guix.sh\n" +" echo 'sudo guix-daemon --build-users-group=guixbuild &' >> ~/.buildenv\n" +" echo 'export PATH=\"${HOME}/.config/guix/current/bin${PATH:+:}$PATH\"' >> ~/.buildenv\n" +" - tests: |\n" +" cd ./songbooks/\n" +" guix environment -m build-aux/guix.scm -- make check\n" +" - docs: |\n" +" cd ./songbooks/\n" +" guix environment -m build-aux/guix.scm -- make publish-dist\n" +msgstr "" diff --git a/po/fr/LC_MESSAGES/_articles/2020-08-31-the-database-i-wish-i-had.po b/po/fr/LC_MESSAGES/_articles/2020-08-31-the-database-i-wish-i-had.po new file mode 100644 index 0000000..753c699 --- /dev/null +++ b/po/fr/LC_MESSAGES/_articles/2020-08-31-the-database-i-wish-i-had.po @@ -0,0 +1,409 @@ +# +msgid "" +msgstr "" + +msgid "" +"I watched the talk \"[Platform as a Reflection of Values: Joyent, Node.js " +"and beyond](https://vimeo.com/230142234)\" by Bryan Cantrill, and I think he" +" was able to put into words something I already felt for some time: if " +"there's no piece of software out there that reflects your values, it's time " +"for you to build that software[^talk-time]." +msgstr "" + +msgid "" +"[^talk-time]: At the very end, at time 29:49. When talking about the draft " +"of this article with a friend, he noted that Bryan O'Sullivan (a different " +"Bryan) says a similar thing on his talk \"[Running a startup on " +"Haskell](https://www.youtube.com/watch?v=ZR3Jirqk6W8)\", at time 4:15." +msgstr "" + +msgid "" +"I kind of agree with what he said, because this is already happening to me. " +"I long for a database with a certain set of values, and for a few years I " +"was just waiting for someone to finally write it. After watching his talk, " +"Bryan is saying to me: \"time to stop waiting, and start writing it " +"yourself\"." +msgstr "" + +msgid "" +"So let me try to give an overview of such database, and go over its values." +msgstr "" + +msgid "Overview" +msgstr "" + +msgid "" +"I want a database that allows me to create decentralized client-side " +"applications that can sync data." +msgstr "" + +msgid "The best one-line description I can give right now is:" +msgstr "" + +msgid "It's sort of like PouchDB, Git, Datomic, SQLite and Mentat." +msgstr "" + +msgid "A more descriptive version could be:" +msgstr "" + +msgid "An embedded, immutable, syncable relational database." +msgstr "" + +msgid "Let's go over what I mean by each of those aspects one by one." +msgstr "" + +msgid "Embedded" +msgstr "" + +msgid "" +"I think the server-side database landscape is diverse and mature enough for " +"my needs (even though I end up choosing SQLite most of the time), and what " +"I'm after is a database to be embedded on client-side applications itself, " +"be it desktop, browser, mobile, *etc.*" +msgstr "" + +msgid "" +"The purpose of such database is not to keep some local cache of data in case" +" of lost connectivity: we have good solutions for that already. It should " +"serve as the source of truth, and allow the application to work on top of " +"it." +msgstr "" + +msgid "" +"[**SQLite**](https://sqlite.org/index.html) is a great example of that: it " +"is a very powerful relational database that runs [almost " +"anywhere](https://sqlite.org/whentouse.html). What I miss from it that " +"SQLite doesn't provide is the ability to run it on the browser: even though " +"you could compile it to WebAssembly, ~~it assumes a POSIX filesystem that " +"would have to be emulated~~[^posix-sqlite]." +msgstr "" + +msgid "" +"[^posix-sqlite]: It was [pointed out to " +"me](https://news.ycombinator.com/item?id=24338881) that SQLite doesn't " +"assume the existence of a POSIX filesystem, as I wrongly stated. Thanks for " +"the correction." +msgstr "" + +msgid "" +"[**PouchDB**](https://pouchdb.com/) is another great example: it's a full " +"reimplementation of [CouchDB](https://couchdb.apache.org/) that targets " +"JavaScript environments, mainly the browser and Node.js. However I want a " +"tool that can be deployed anywhere, and not limit its applications to places" +" that already have a JavaScript runtime environment, or force the developer " +"to bundle a JavaScript runtime environment with their application. This is " +"true for GTK+ applications, command line programs, Android apps, *etc.*" +msgstr "" + +msgid "" +"[**Mentat**](https://github.com/mozilla/mentat) was an interesting project, " +"but its reliance on SQLite makes it inherit most of the downsides (and " +"benefits too) of SQLite itself." +msgstr "" + +msgid "" +"Having such a requirement imposes a different approach to storage: we have " +"to decouple the knowledge about the intricacies of storage from the usage of" +" storage itself, so that a module (say query processing) can access storage " +"through an API without needing to know about its implementation. This allows" +" the database to target a POSIX filesystems storage API and an IndexedDB " +"storage API, and make the rest of the code agnostic about storage. PouchDB " +"has such mechanism (called [adapters](https://pouchdb.com/adapters.html)) " +"and Datomic has them too (called [storage " +"services](https://docs.datomic.com/on-prem/storage.html))." +msgstr "" + +msgid "" +"This would allow the database to adapt to where it is embedded: when " +"targeting the browser the IndexedDB storage API would provide the " +"persistence layer that the database requires, and similarly the POSIX " +"filesystem storage API would provide the persistence layer when targeting " +"POSIX systems (like desktops, mobile, *etc.*)." +msgstr "" + +msgid "" +"But there's also an extra restriction that comes from by being embedded: it " +"needs to provide and embeddable artifact, most likely a binary library " +"object that exposes a C compatible FFI, similar to [how SQLite " +"does](https://www.sqlite.org/amalgamation.html). Bundling a full runtime " +"environment is possible, but doesn't make it a compelling solution for " +"embedding. This rules out most languages, and leaves us with C, Rust, Zig, " +"and similar options that can target POSIX systems and WebAssembly." +msgstr "" + +msgid "Immutable" +msgstr "" + +msgid "" +"Being immutable means that only new information is added, no in-place update" +" ever happens, and nothing is ever deleted." +msgstr "" + +msgid "" +"Having an immutable database presents us with similar trade-offs found in " +"persistent data structures, like lack of coordination when doing reads, " +"caches being always coherent, and more usage of space." +msgstr "" + +msgid "" +"[**Datomic**](https://www.datomic.com/) is the go to database example of " +"this: it will only add information (datoms) and allows you to query them in " +"a multitude of ways. Stuart Halloway calls it \"accumulate-only\" over " +"\"append-only\"[^accumulate-only](Video \"[Day of Datomic Part " +"2](https://vimeo.com/116315075)\"):" +msgstr "" + +msgid "" +"It's accumulate-only, it is not append-only. So append-only, most people " +"when they say that they're implying something physical about what happens." +msgstr "" + +msgid "on Datomic's information model, at time 12:28." +msgstr "" + +msgid "" +"Also a database can be append-only and overwrite existing information with " +"new information, by doing clean-ups of \"stale\" data. I prefer to adopt the" +" \"accumulate-only\" naming and approach." +msgstr "" + +msgid "" +"[**Git**](https://git-scm.com/) is another example of this: new commits are " +"always added on top of the previous data, and it grows by adding commits " +"instead of replacing existing ones." +msgstr "" + +msgid "" +"Git repositories can only grow in size, and that is not only an acceptable " +"condition, but also one of the reasons to use it." +msgstr "" + +msgid "" +"All this means that no in-place updates happens on data, and the database " +"will be much more concerned about how compact and efficiently it stores data" +" than how fast it does writes to disk. Being embedded, the storage " +"limitation is either a) how much storage the device has or b) how much " +"storage was designed for the application to consume. So even though the " +"database could theoretically operate with hundreds of TBs, a browser page or" +" mobile application wouldn't have access to this amount of storage. SQLite " +"even [says](https://sqlite.org/limits.html) that it does support " +"approximately 280 TBs of data, but those limits are untested." +msgstr "" + +msgid "" +"The upside of keeping everything is that you can have historical views of " +"your data, which is very powerful. This also means that applications should " +"turn this off when not relevant[^no-history]." +msgstr "" + +msgid "" +"[^no-history]: Similar to [Datomic's " +"`:db/noHistory`](https://docs.datomic.com/cloud/best.html#nohistory-for-" +"high-churn)." +msgstr "" + +msgid "Syncable" +msgstr "" + +msgid "" +"This is a frequent topic when talking about offline-first solutions. When " +"building applications that:" +msgstr "" + +msgid "can fully work offline," +msgstr "" + +msgid "stores data," +msgstr "" + +msgid "propagates that data to other application instances," +msgstr "" + +msgid "" +"then you'll need a conflict resolution strategy to handle all the situations" +" where different application instances disagree. Those application instances" +" could be a desktop and a browser version of the same application, or the " +"same mobile app in different devices." +msgstr "" + +msgid "" +"A three-way merge seems to be the best approach, on top of which you could " +"add application specific conflict resolution functions, like:" +msgstr "" + +msgid "pick the change with higher timestamp;" +msgstr "" + +msgid "if one change is a delete, pick it;" +msgstr "" + +msgid "present the diff on the screen and allow the user to merge them." +msgstr "" + +msgid "" +"Some databases try to make this \"easy\", by choosing a strategy for you, " +"but I've found that different applications require different conflict " +"resolution strategies. Instead, the database should leave this up to the " +"user to decide, and provide tools for them to do it." +msgstr "" + +msgid "" +"[**Three-way merges in version " +"control**](https://en.wikipedia.org/wiki/Merge_(version_control)) are the " +"best example, performing automatic merges when possible and asking the user " +"to resolve conflicts when they appear." +msgstr "" + +msgid "" +"The unit of conflict for a version control system is a line of text. The " +"database equivalent would probably be a single attribute, not a full entity " +"or a full row." +msgstr "" + +msgid "" +"Making all the conflict resolution logic be local should allow the database " +"to have encrypted remotes similar to how [git-remote-" +"gcrypt](https://spwhitton.name/tech/code/git-remote-gcrypt/) adds this " +"functionality to Git. This would enable users to sync the application data " +"across devices using an untrusted intermediary." +msgstr "" + +msgid "Relational" +msgstr "" + +msgid "I want the power of relational queries on the client applications." +msgstr "" + +msgid "" +"Most of the arguments against traditional table-oriented relational " +"databases are related to write performance, but those don't apply here. The " +"bottlenecks for client applications usually aren't write throughput. Nobody " +"is interested in differentiating between 1 MB/s or 10 MB/s when you're " +"limited to 500 MB total." +msgstr "" + +msgid "" +"The relational model of the database could either be based on SQL and tables" +" like in SQLite, or maybe [datalog](https://docs.datomic.com/on-" +"prem/query.html) and [datoms](https://docs.datomic.com/cloud/whatis/data-" +"model.html#datoms) like in Datomic." +msgstr "" + +msgid "From aspects to values" +msgstr "" + +msgid "" +"Now let's try to translate the aspects above into values, as suggested by " +"Bryan Cantrill." +msgstr "" + +msgid "Portability" +msgstr "" + +msgid "" +"Being able to target so many different platforms is a bold goal, and the " +"embedded nature of the database demands portability to be a core value." +msgstr "" + +msgid "Integrity" +msgstr "" + +msgid "" +"When the local database becomes the source of truth of the application, it " +"must provide consistency guarantees that enables applications to rely on it." +msgstr "" + +msgid "Expressiveness" +msgstr "" + +msgid "" +"The database should empower applications to slice and dice the data in any " +"way it wants to." +msgstr "" + +msgid "Next steps" +msgstr "" + +msgid "" +"Since I can't find any database that fits these requirements, I've finally " +"come to terms with doing it myself." +msgstr "" + +msgid "" +"It's probably going to take me a few years to do it, and making it portable " +"between POSIX and IndexedDB will probably be the biggest challenge. I got " +"myself a few books on databases to start." +msgstr "" + +msgid "I wonder if I'll ever be able to get this done." +msgstr "" + +msgid "External links" +msgstr "" + +msgid "" +"See discussions on " +"[Reddit](https://www.reddit.com/r/programming/comments/ijwz5b/the_database_i_wish_i_had/)," +" [lobsters](https://lobste.rs/s/m9vkg4/database_i_wish_i_had), " +"[HN](https://news.ycombinator.com/item?id=24337244) and [a lengthy email " +"exchange](https://lists.sr.ht/~euandreh/public-" +"inbox/%3C010101744a592b75-1dce9281-f0b8-4226-9d50-fd2c7901fa72-000000%40us-" +"west-2.amazonses.com%3E)." +msgstr "" + +msgid "" +"This makes me consider it as a storage backend all by itself. I\n" +"initially considered having an SQLite storage backend as one implementation\n" +"of the POSIX filesystem storage API that I mentioned. My goal was to rely on\n" +"it so I could validate the correctness of the actual implementation, given\n" +"SQLite's robustness.\n" +"\n" +"However it may even better to just use SQLite, and get an ACID backend\n" +"without recreating a big part of SQLite from scratch. In fact, both Datomic\n" +"and PouchDB didn't create an storage backend for themselves, they just\n" +"plugged on what already existed and already worked. I'm beginning to think\n" +"that it would be wiser to just do the same, and drop entirely the from\n" +"scratch implementation that I mentioned.\n" +"\n" +"That's not to say that adding an IndexedDB compatibility layer to SQLite\n" +"would be enough to make it fit the other requirements I mention on this\n" +"page. SQLite still is an implementation of a update-in-place, SQL,\n" +"table-oriented database. It is probably true that cherry-picking the\n" +"relevant parts of SQLite (like storage access, consistency, crash recovery,\n" +"parser generator, *etc.*) and leaving out the unwanted parts (SQL, tables,\n" +"threading, *etc.*) would be better than including the full SQLite stack, but\n" +"that's simply an optimization. Both could even coexist, if desired.\n" +"\n" +"SQLite would have to be treated similarly to how Datomic treats SQL\n" +"databases: instead of having a table for each entities, spread attributes\n" +"over the tables, *etc.*, it treats SQL databases as a key-value storage so it\n" +"doesn't have to re-implement interacting with the disk that other databases\n" +"do well.\n" +"\n" +"The tables would contain blocks of binary data, so there isn't a difference\n" +"on how the SQLite storage backend behaves and how the IndexedDB storage\n" +"backend behaves, much like how Datomic works the same regardless of the\n" +"storage backend, same for PouchDB.\n" +"\n" +"I welcome corrections on what I said above, too.\n" +msgstr "" + +msgid "" +"title: The database I wish I had\n" +"date: 2020-08-31\n" +"updated_at: 2020-09-03\n" +"layout: post\n" +"lang: en\n" +"ref: the-database-i-wish-i-had\n" +"eu_categories: mediator" +msgstr "" + +#~ msgid "" +#~ "title: The database I wish I had\n" +#~ "date: 2020-08-31\n" +#~ "updated_at: 2020-09-03\n" +#~ "layout: post\n" +#~ "lang: en\n" +#~ "ref: the-database-i-wish-i-had\n" +#~ "category: mediator" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_articles/2020-10-05-cargo2nix-dramatically-simpler-rust-in-nix.po b/po/fr/LC_MESSAGES/_articles/2020-10-05-cargo2nix-dramatically-simpler-rust-in-nix.po new file mode 100644 index 0000000..7231ea3 --- /dev/null +++ b/po/fr/LC_MESSAGES/_articles/2020-10-05-cargo2nix-dramatically-simpler-rust-in-nix.po @@ -0,0 +1,115 @@ +# +msgid "" +msgstr "" + +msgid "" +"In the same vein of my earlier post on [swift2nix]({% link " +"_articles/2020-10-05-swift2nix-run-swift-inside-nix-builds.md %}), I was " +"able to quickly prototype a Rust and Cargo variation of it: " +"[cargo2nix](https://euandreh.xyz/cargo2nix.git/)." +msgstr "" + +msgid "" +"The initial prototype is even smaller than swift2nix: it has only [37 lines " +"of " +"code](https://euandreh.xyz/cargo2nix.git/tree/default.nix?id=472dde8898296c8b6cffcbd10b3b2c3ba195846d)." +msgstr "" + +msgid "Here's how to use it (snippet taken from the repo's README):" +msgstr "" + +msgid "" +"That `cargo test` part on line 20 is what I have been fighting with every " +"\"\\*2nix\" available for Rust out there. I don't want to bash any of them. " +"All I want is to have full control of what Cargo commands to run, and the " +"\"*2nix\" tool should only setup the environment for me. Let me drive Cargo " +"myself, no need to parameterize how the tool runs it for me, or even " +"replicate its internal behaviour by calling the Rust compiler directly." +msgstr "" + +msgid "" +"Sure it doesn't support private registries or Git dependencies, but how much" +" bigger does it has to be to support them? Also, it doesn't support those " +"**yet**, there's no reason it can't be extended. I just haven't needed it " +"yet, so I haven't added. Patches welcome." +msgstr "" + +msgid "" +"The layout of the `vendor/` directory is more explicit and public then what " +"swift2nix does: it is whatever the command `cargo vendor` returns. However I" +" haven't checked if the shape of the `.cargo-checksum.json` is specified, or" +" internal to Cargo." +msgstr "" + +msgid "Try out the demo (also taken from the repo's README):" +msgstr "" + +msgid "Report back if you wish. Again, patches welcome." +msgstr "" + +msgid "" +"let\n" +" niv-sources = import ./nix/sources.nix;\n" +" mozilla-overlay = import niv-sources.nixpkgs-mozilla;\n" +" pkgs = import niv-sources.nixpkgs { overlays = [ mozilla-overlay ]; };\n" +" src = pkgs.nix-gitignore.gitignoreSource [ ] ./.;\n" +" cargo2nix = pkgs.callPackage niv-sources.cargo2nix {\n" +" lockfile = ./Cargo.lock;\n" +" };\n" +"in pkgs.stdenv.mkDerivation {\n" +" inherit src;\n" +" name = \"cargo-test\";\n" +" buildInputs = [ pkgs.latest.rustChannels.nightly.rust ];\n" +" phases = [ \"unpackPhase\" \"buildPhase\" ];\n" +" buildPhase = ''\n" +" # Setup dependencies path to satisfy Cargo\n" +" mkdir .cargo/\n" +" ln -s ${cargo2nix.env.cargo-config} .cargo/config\n" +" ln -s ${cargo2nix.env.vendor} vendor\n" +"\n" +" # Run the tests\n" +" cargo test\n" +" touch $out\n" +" '';\n" +"}\n" +msgstr "" + +msgid "" +"pushd \"$(mktemp -d)\"\n" +"git clone https://euandreh.xyz/cargo2nix-demo.git\n" +"cd cargo2nix-demo/\n" +"nix-build\n" +msgstr "" + +msgid "title: \"cargo2nix: Dramatically simpler Rust in Nix\"" +msgstr "" + +msgid "date: 2020-10-05 2" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: cargo2nix-dramatically-simpler-rust-in-nix" +msgstr "" + +#~ msgid "" +#~ "title: \"cargo2nix: Dramatically simpler Rust in Nix\"\n" +#~ "date: 2020-10-05 2\n" +#~ "layout: post\n" +#~ "lang: en\n" +#~ "ref: cargo2nix-dramatically-simpler-rust-in-nix\n" +#~ "eu_categories: mediator" +#~ msgstr "" + +#~ msgid "" +#~ "title: \"cargo2nix: Dramatically simpler Rust in Nix\"\n" +#~ "date: 2020-10-05 2\n" +#~ "layout: post\n" +#~ "lang: en\n" +#~ "ref: cargo2nix-dramatically-simpler-rust-in-nix\n" +#~ "category: mediator" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_articles/2020-10-05-swift2nix-run-swift-inside-nix-builds.po b/po/fr/LC_MESSAGES/_articles/2020-10-05-swift2nix-run-swift-inside-nix-builds.po new file mode 100644 index 0000000..1500ff0 --- /dev/null +++ b/po/fr/LC_MESSAGES/_articles/2020-10-05-swift2nix-run-swift-inside-nix-builds.po @@ -0,0 +1,308 @@ +# +msgid "" +msgstr "" + +msgid "" +"While working on a Swift project, I didn't find any tool that would allow " +"Swift to run inside [Nix](https://nixos.org/) builds. Even thought you *can*" +" run Swift, the real problem arises when using the package manager. It has " +"many of the same problems that other package managers have when trying to " +"integrate with Nix, more on this below." +msgstr "" + +msgid "" +"I wrote a simple little tool called " +"[swift2nix](https://euandreh.xyz/swift2nix.git/) that allows you trick " +"Swift's package manager into assuming everything is set up. Here's the " +"example from swift2nix's README file:" +msgstr "" + +msgid "" +"The key parts are lines 15~17: we just fake enough files inside `.build/` " +"that Swift believes it has already downloaded and checked-out all " +"dependencies, and just moves on to building them." +msgstr "" + +msgid "" +"I've worked on it just enough to make it usable for myself, so beware of " +"unimplemented cases. Patches welcome." +msgstr "" + +msgid "Design" +msgstr "" + +msgid "" +"What swift2nix does is just provide you with the bare minimum that Swift " +"requires, and readily get out of the way:" +msgstr "" + +msgid "" +"I explicitly did not want to generated a `Package.nix` file, since " +"`Package.resolved` already exists and contains the required information;" +msgstr "" + +msgid "" +"I didn't want to have an \"easy\" interface right out of the gate, after " +"fighting with \"*2nix\" tools that focus too much on that." +msgstr "" + +msgid "" +"The final [actual " +"code](https://euandreh.xyz/swift2nix.git/tree/default.nix?id=2af83ffe43fac631a8297ffaa8be3ff93b2b9e7c)" +" was so small (46 lines) that it made me think about package managers, " +"\"*2nix\" tools and some problems with many of them." +msgstr "" + +msgid "Problems with package managers" +msgstr "" + +msgid "" +"I'm going to talk about solely language package managers. Think npm and " +"cargo, not apt-get." +msgstr "" + +msgid "" +"Package managers want to do too much, or assume too much, or just want to " +"take control of the entire build of the dependencies." +msgstr "" + +msgid "" +"This is a recurrent problem in package managers, but I don't see it as an " +"intrinsic one. There's nothing about a \"package manager\" that prevents it " +"from *declaring* what it expects to encounter and in which format. The " +"*declaring* part is important: it should be data, not code, otherwise you're" +" back in the same problem, just like lockfiles are just data. Those work in " +"any language, and tools can cooperate happily." +msgstr "" + +msgid "" +"There's no need for this declarative expectation to be standardized, or be " +"made compatible across languages. That would lead to a poor format that no " +"package manager really likes. Instead, If every package manager could say " +"out loud what it wants to see exactly, than more tools like swift2nix could " +"exist, and they would be more reliable." +msgstr "" + +msgid "" +"This could even work fully offline, and be simply a mapping from the " +"lockfile (the `Package.resolved` in Swift's case) to the filesystem " +"representation. For Swift, the `.build/dependencies-state.json` comes very " +"close, but it is internal to the package manager." +msgstr "" + +msgid "" +"Even though this pain only exists when trying to use Swift inside Nix, it " +"sheds light into this common implicit coupling that package managers have. " +"They usually have fuzzy boundaries and tight coupling between:" +msgstr "" + +msgid "" +"resolving the dependency tree and using some heuristic to pick a package " +"version;" +msgstr "" + +msgid "generating a lockfile with the exact pinned versions;" +msgstr "" + +msgid "" +"downloading the dependencies present on the lockfile into some local cache;" +msgstr "" + +msgid "" +"arranging the dependencies from the cache in a meaningful way for itself " +"inside the project;" +msgstr "" + +msgid "work using the dependencies while *assuming* that step 4 was done." +msgstr "" + +msgid "" +"When you run `npm install` in a repository with no lockfile, it does 1~~4. " +"If you do the same with `cargo build`, it does 1~~5. That's too much: many " +"of those assumptions are implicit and internal to the package manager, and " +"if you ever need to rearrange them, you're on your own. Even though you can " +"perform some of those steps, you can't compose or rearrange them." +msgstr "" + +msgid "Instead a much saner approach could be:" +msgstr "" + +msgid "this stays the same;" +msgstr "" + +msgid "this also stays the same;" +msgstr "" + +msgid "" +"be able to generate some JSON/TOML/edn which represents the local expected " +"filesystem layout with dependencies (i.e. exposing what the package manager " +"expects to find), let's call it `local-registry.json`;" +msgstr "" + +msgid "" +"if a `local-registry.json` was provided, do a build using that. Otherwise " +"generate its own, by downloading the dependencies, arranging them, *etc.*" +msgstr "" + +msgid "" +"The point is just making what the package manager requires visible to the " +"outside world via some declarative data. If this data wasn't provided, it " +"can move on to doing its own automatic things." +msgstr "" + +msgid "" +"By making the expectation explicit and public, one can plug tools *à la " +"carte* if desired, but doesn't prevent the default code path of doing things" +" the exact same way they are now." +msgstr "" + +msgid "Problems with \"*2nix\" tools" +msgstr "" + +msgid "I have to admit: I'm unhappy with most of they." +msgstr "" + +msgid "" +"They conflate \"using Nix\" with \"replicating every command of the package " +"manager inside Nix\"." +msgstr "" + +msgid "" +"The avoidance of an \"easy\" interface that I mentioned above comes from me " +"fighting with some of the \"\\*2nix\" tools much like I have to fight with " +"package managers: I don't want to offload all build responsibilities to the " +"\"*2nix\" tool, I just want to let it download some of the dependencies and " +"get out of the way. I want to stick with `npm test` or `cargo build`, and " +"Nix should only provide the environment." +msgstr "" + +msgid "" +"This is something that [node2nix](https://github.com/svanderburg/node2nix) " +"does right. It allows you to build the Node.js environment to satisfy NPM, " +"and you can keep using NPM for everything else:" +msgstr "" + +msgid "" +"Its natural to want to put as much things into Nix as possible to benefit " +"from Nix's advantages. Isn't that how NixOS itself was born?" +msgstr "" + +msgid "" +"But a \"*2nix\" tool should leverage Nix, not be coupled with it. The above " +"example lets you run any arbitrary NPM command while profiting from " +"isolation and reproducibility that Nix provides. It is even less brittle: " +"any changes to how NPM runs some things will be future-compatible, since " +"node2nix isn't trying to replicate what NPM does, or fiddling with NPM's " +"internal." +msgstr "" + +msgid "" +"\\**A \"*2nix\" tool should build the environment, preferably from the " +"lockfile directly and offload everything else to the package manager**. The " +"rest is just nice-to-have." +msgstr "" + +msgid "" +"swift2nix itself could provide an \"easy\" interface, something that allows " +"you to write:" +msgstr "" + +msgid "" +"The implementation of those would be obvious: create a new " +"`pkgs.stdenv.mkDerivation` and call `swift build -c release` and `swift " +"test` while using `swift2nix.env` under the hood." +msgstr "" + +msgid "Conclusion" +msgstr "" + +msgid "" +"Package managers should provide exact dependencies via a data " +"representation, i.e. lockfiles, and expose via another data representation " +"how they expect those dependencies to appear on the filesystem, i.e. `local-" +"registry.json`. This allows package managers to provide an API so that " +"external tools can create mirrors, offline builds, other registries, " +"isolated builds, *etc.*" +msgstr "" + +msgid "" +"\"\\*2nix\" tools should build simple functions that leverage that `local-" +"registry.json`[^local-registry] data and offload all the rest back to the " +"package manager itself. This allows the \"*2nix\" to not keep chasing the " +"package manager evolution, always trying to duplicate its behaviour." +msgstr "" + +msgid "" +"[^local-registry]: This `local-registry.json` file doesn't have to be " +"checked-in the repository at all. It could be always generated on the fly, " +"much like how Swift's `dependencies-state.json` is." +msgstr "" + +msgid "" +"let\n" +" niv-sources = import ./nix/sources.nix;\n" +" pkgs = import niv-sources.nixpkgs { };\n" +" src = pkgs.nix-gitignore.gitignoreSource [ ] ./.;\n" +" swift2nix = pkgs.callPackage niv-sources.swift2nix {\n" +" package-resolved = ./Package.resolved;\n" +" };\n" +"in pkgs.stdenv.mkDerivation {\n" +" inherit src;\n" +" name = \"swift-test\";\n" +" buildInputs = with pkgs; [ swift ];\n" +" phases = [ \"unpackPhase\" \"buildPhase\" ];\n" +" buildPhase = ''\n" +" # Setup dependencies path to satisfy SwiftPM\n" +" mkdir .build\n" +" ln -s ${swift2nix.env.dependencies-state-json} .build/dependencies-state.json\n" +" ln -s ${swift2nix.env.checkouts} .build/checkouts\n" +"\n" +" # Run the tests\n" +" swift test\n" +" touch $out\n" +" '';\n" +"}\n" +msgstr "" + +msgid "" +"ln -s ${node2nix-package.shell.nodeDependencies}/lib/node_modules ./node_modules\n" +"npm test\n" +msgstr "" + +msgid "" +"nix-build -A swift2nix.release\n" +"nix-build -A swift2nix.test\n" +msgstr "" + +msgid "title: \"swift2nix: Run Swift inside Nix builds\"" +msgstr "" + +msgid "date: 2020-10-05 1" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: swift2nix-run-swift-inside-nix-builds" +msgstr "" + +#~ msgid "" +#~ "title: \"swift2nix: Run Swift inside Nix builds\"\n" +#~ "date: 2020-10-05 1\n" +#~ "layout: post\n" +#~ "lang: en\n" +#~ "ref: swift2nix-run-swift-inside-nix-builds\n" +#~ "eu_categories: mediator" +#~ msgstr "" + +#~ msgid "" +#~ "title: \"swift2nix: Run Swift inside Nix builds\"\n" +#~ "date: 2020-10-05 1\n" +#~ "layout: post\n" +#~ "lang: en\n" +#~ "ref: swift2nix-run-swift-inside-nix-builds\n" +#~ "category: mediator" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_articles/2020-10-19-feature-flags-differences-between-backend-frontend-and-mobile.po b/po/fr/LC_MESSAGES/_articles/2020-10-19-feature-flags-differences-between-backend-frontend-and-mobile.po new file mode 100644 index 0000000..89911ca --- /dev/null +++ b/po/fr/LC_MESSAGES/_articles/2020-10-19-feature-flags-differences-between-backend-frontend-and-mobile.po @@ -0,0 +1,444 @@ +# +msgid "" +msgstr "" + +msgid "" +"*This article is derived from a [presentation][presentation] on the same " +"subject.*" +msgstr "" + +msgid "" +"When discussing about feature flags, I find that their costs and benefits " +"are often well exposed and addressed. Online articles like \"[Feature Toggle" +" (aka Feature Flags)][feature-flags-article]\" do a great job of explaining " +"them in detail, giving great general guidance of how to apply techniques to " +"adopt it." +msgstr "" + +msgid "" +"However the weight of those costs and benefits apply differently on backend," +" frontend or mobile, and those differences aren't covered. In fact, many of " +"them stop making sense, or the decision of adopting a feature flag or not " +"may change depending on the environment." +msgstr "" + +msgid "" +"In this article I try to make the distinction between environments and how " +"feature flags apply to them, with some final best practices I've acquired " +"when using them in production." +msgstr "" + +msgid "" +"[presentation]: {% link _slides/2020-10-19-rollout-feature-flag-experiment-" +"operational-toggle.slides %} [feature-flags-article]: " +"https://martinfowler.com/articles/feature-toggles.html" +msgstr "" + +msgid "Why feature flags" +msgstr "" + +msgid "" +"Feature flags in general tend to be cited on the context of [continuous " +"deployment](https://www.atlassian.com/continuous-" +"delivery/principles/continuous-integration-vs-delivery-vs-deployment):" +msgstr "" + +msgid "A: With continuous deployment, you deploy to production automatically" +msgstr "" + +msgid "B: But how do I handle deployment failures, partial features, *etc.*?" +msgstr "" + +msgid "" +"A: With techniques like canary, monitoring and alarms, feature flags, *etc.*" +msgstr "" + +msgid "" +"Though adopting continuous deployment doesn't force you to use feature " +"flags, it creates a demand for it. The inverse is also true: using feature " +"flags on the code points you more obviously to continuous deployment. Take " +"the following code sample for example, that we will reference later on the " +"article:" +msgstr "" + +msgid "" +"While being developed, being tested for suitability or something similar, " +"`notifyListeners()` may not be included in the code at once. So instead of " +"keeping it on a separate, long-lived branch, a feature flag can decide when " +"the new, partially implemented function will be called:" +msgstr "" + +msgid "" +"This allows your code to include `notifyListeners()`, and decide when to " +"call it at runtime. For the price of extra things around the code, you get " +"more dynamicity." +msgstr "" + +msgid "" +"So the fundamental question to ask yourself when considering adding a " +"feature flag should be:" +msgstr "" + +msgid "Am I willing to pay with code complexity to get dynamicity?" +msgstr "" + +msgid "" +"It is true that you can make the management of feature flags as " +"straightforward as possible, but having no feature flags is simpler than " +"having any. What you get in return is the ability to parameterize the " +"behaviour of the application at runtime, without doing any code changes." +msgstr "" + +msgid "" +"Sometimes this added complexity may tilt the balance towards not using a " +"feature flag, and sometimes the flexibility of changing behaviour at runtime" +" is absolutely worth the added complexity. This can vary a lot by code base," +" feature, but fundamentally by environment: its much cheaper to deploy a new" +" version of a service than to release a new version of an app." +msgstr "" + +msgid "" +"So the question of which environment is being targeted is key when reasoning" +" about costs and benefits of feature flags." +msgstr "" + +msgid "Control over the environment" +msgstr "" + +msgid "" +"The key differentiator that makes the trade-offs apply differently is how " +"much control you have over the environment." +msgstr "" + +msgid "" +"When running a **backend** service, you usually are paying for the servers " +"themselves, and can tweak them as you wish. This means you have full control" +" do to code changes as you wish. Not only that, you decide when to do it, " +"and for how long the transition will last." +msgstr "" + +msgid "" +"On the **frontend** you have less control: even though you can choose to " +"make a new version available any time you wish, you can't force[^force] " +"clients to immediately switch to the new version. That means that a) clients" +" could skip upgrades at any time and b) you always have to keep backward and" +" forward compatibility in mind." +msgstr "" + +msgid "" +"Even though I'm mentioning frontend directly, it applies to other " +"environment with similar characteristics: desktop applications, command-line" +" programs, *etc*." +msgstr "" + +msgid "" +"On **mobile** you have even less control: app stores need to allow your app " +"to be updated, which could bite you when least desired. Theoretically you " +"could make you APK available on third party stores like " +"[F-Droid](https://f-droid.org/), or even make the APK itself available for " +"direct download, which would give you the same characteristics of a frontend" +" application, but that happens less often." +msgstr "" + +msgid "" +"On iOS you can't even do that. You have to get Apple's blessing on every " +"single update. Even though we already know that is a [bad " +"idea](http://www.paulgraham.com/apple.html) for over a decade now, there " +"isn't a way around it. This is where you have the least control." +msgstr "" + +msgid "" +"In practice, the amount of control you have will change how much you value " +"dynamicity: the less control you have, the more valuable it is. In other " +"words, having a dynamic flag on the backend may or may not be worth it since" +" you could always update the code immediately after, but on iOS it is " +"basically always worth it." +msgstr "" + +msgid "" +"[^force]: Technically you could force a reload with JavaScript using " +"`window.location.reload()`, but that not only is invasive and impolite, but " +"also gives you the illusion that you have control over the client when you " +"actually don't: clients with disabled JavaScript would be immune to such " +"tactics." +msgstr "" + +msgid "Rollout" +msgstr "" + +msgid "A rollout is used to *roll out* a new version of software." +msgstr "" + +msgid "" +"They are usually short-lived, being relevant as long as the new code is " +"being deployed. The most common rule is percentages." +msgstr "" + +msgid "" +"On the **backend**, it is common to find it on the deployment infrastructure" +" itself, like canary servers, blue/green deployments, [a kubernetes " +"deployment " +"rollout](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#creating-" +"a-deployment), *etc*. You could do those manually, by having a dynamic " +"control on the code itself, but rollbacks are cheap enough that people " +"usually do a normal deployment and just give some extra attention to the " +"metrics dashboard." +msgstr "" + +msgid "" +"Any time you see a blue/green deployment, there is a rollout happening: most" +" likely a load balancer is starting to direct traffic to the new server, " +"until reaching 100% of the traffic. Effectively, that is a rollout." +msgstr "" + +msgid "" +"On the **frontend**, you can selectively pick which user's will be able to " +"download the new version of a page. You could use geographical region, IP, " +"cookie or something similar to make this decision." +msgstr "" + +msgid "" +"CDN propagation delays and people not refreshing their web pages are also " +"rollouts by themselves, since old and new versions of the software will " +"coexist." +msgstr "" + +msgid "" +"On **mobile**, the Play Store allows you to perform fine-grained [staged " +"rollouts](https://support.google.com/googleplay/android-" +"developer/answer/6346149?hl=en), and the App Store allows you to perform " +"limited [phased releases](https://help.apple.com/app-store-" +"connect/#/dev3d65fcee1)." +msgstr "" + +msgid "" +"Both for Android and iOS, the user plays the role of making the download." +msgstr "" + +msgid "" +"In summary: since you control the servers on the backend, you can do " +"rollouts at will, and those are often found automated away in base " +"infrastructure. On the frontend and on mobile, there are ways to make new " +"versions available, but users may not download them immediately, and many " +"different versions of the software end up coexisting." +msgstr "" + +msgid "Feature flag" +msgstr "" + +msgid "" +"A feature flag is a *flag* that tells the application on runtime to turn on " +"or off a given *feature*. That means that the actual production code will " +"have more than one possible code paths to go through, and that a new version" +" of a feature coexists with the old version. The feature flag tells which " +"part of the code to go through." +msgstr "" + +msgid "" +"They are usually medium-lived, being relevant as long as the new code is " +"being developed. The most common rules are percentages, allow/deny lists, " +"A/B groups and client version." +msgstr "" + +msgid "" +"On the **backend**, those are useful for things that have a long development" +" cycle, or that needs to done by steps. Consider loading the feature flag " +"rules in memory when the application starts, so that you avoid querying a " +"database or an external service for applying a feature flag rule and avoid " +"flakiness on the result due to intermittent network failures." +msgstr "" + +msgid "" +"Since on the **frontend** you don't control when to update the client " +"software, you're left with applying the feature flag rule on the server, and" +" exposing the value through an API for maximum dynamicity. This could be in " +"the frontend code itself, and fallback to a \"just refresh the page\"/\"just" +" update to the latest version\" strategy for less dynamic scenarios." +msgstr "" + +msgid "" +"On **mobile** you can't even rely on a \"just update to the latest version\"" +" strategy, since the code for the app could be updated to a new feature and " +"be blocked on the store. Those cases aren't recurrent, but you should always" +" assume the store will deny updates on critical moments so you don't find " +"yourself with no cards to play. That means the only control you actually " +"have is via the backend, by parameterizing the runtime of the application " +"using the API. In practice, you should always have a feature flag to control" +" any relevant piece of code. There is no such thing as \"too small code " +"change for a feature flag\". What you should ask yourself is:" +msgstr "" + +msgid "" +"If the code I'm writing breaks and stays broken for around a month, do I " +"care?" +msgstr "" + +msgid "" +"If you're doing an experimental screen, or something that will have a very " +"small impact you might answer \"no\" to the above question. For everything " +"else, the answer will be \"yes\": bug fixes, layout changes, refactoring, " +"new screen, filesystem/database changes, *etc*." +msgstr "" + +msgid "Experiment" +msgstr "" + +msgid "" +"An experiment is a feature flag where you care about analytical value of the" +" flag, and how it might impact user's behaviour. A feature flag with " +"analytics." +msgstr "" + +msgid "" +"They are also usually medium-lived, being relevant as long as the new code " +"is being developed. The most common rule is A/B test." +msgstr "" + +msgid "" +"On the **backend**, an experiment rely on an analytical environment that " +"will pick the A/B test groups and distributions, which means those can't be " +"held in memory easily. That also means that you'll need a fallback value in " +"case fetching the group for a given customer fails." +msgstr "" + +msgid "" +"On the **frontend** and on **mobile** they are no different from feature " +"flags." +msgstr "" + +msgid "Operational toggle" +msgstr "" + +msgid "" +"An operational toggle is like a system-level manual circuit breaker, where " +"you turn on/off a feature, fail over the load to a different server, *etc*. " +"They are useful switches to have during an incident." +msgstr "" + +msgid "" +"They are usually long-lived, being relevant as long as the code is in " +"production. The most common rule is percentages." +msgstr "" + +msgid "" +"They can be feature flags that are promoted to operational toggles on the " +"**backend**, or may be purposefully put in place preventively or after a " +"postmortem analysis." +msgstr "" + +msgid "" +"On the **frontend** and on **mobile** they are similar to feature flags, " +"where the \"feature\" is being turned on and off, and the client interprets " +"this value to show if the \"feature\" is available or unavailable." +msgstr "" + +msgid "Best practices" +msgstr "" + +msgid "Prefer dynamic content" +msgstr "" + +msgid "" +"Even though feature flags give you more dynamicity, they're still somewhat " +"manual: you have to create one for a specific feature and change it by hand." +msgstr "" + +msgid "" +"If you find yourself manually updating a feature flags every other day, or " +"tweaking the percentages frequently, consider making it fully dynamic. Try " +"using a dataset that is generated automatically, or computing the content on" +" the fly." +msgstr "" + +msgid "" +"Say you have a configuration screen with a list of options and sub-options, " +"and you're trying to find how to better structure this list. Instead of " +"using a feature flag for switching between 3 and 5 options, make it fully " +"dynamic. This way you'll be able to perform other tests that you didn't " +"plan, and get more flexibility out of it." +msgstr "" + +msgid "Use the client version to negotiate feature flags" +msgstr "" + +msgid "" +"After effectively finishing a feature, the old code that coexisted with the " +"new one will be deleted, and all traces of the transition will vanish from " +"the code base. However if you just remove the feature flags from the API, " +"all of the old versions of clients that relied on that value to show the new" +" feature will go downgrade to the old feature." +msgstr "" + +msgid "" +"This means that you should avoid deleting client-facing feature flags, and " +"retire them instead: use the client version to decide when the feature is " +"stable, and return `true` for every client with a version greater or equal " +"to that. This way you can stop thinking about the feature flag, and you " +"don't break or downgrade clients that didn't upgrade past the transition." +msgstr "" + +msgid "Beware of many nested feature flags" +msgstr "" + +msgid "Nested flags combine exponentially." +msgstr "" + +msgid "" +"Pick strategic entry points or transitions eligible for feature flags, and " +"beware of their nesting." +msgstr "" + +msgid "Include feature flags in the development workflow" +msgstr "" + +msgid "" +"Add feature flags to the list of things to think about during whiteboarding," +" and deleting/retiring a feature flags at the end of the development." +msgstr "" + +msgid "Always rely on a feature flag on the app" +msgstr "" + +msgid "" +"Again, there is no such thing \"too small for a feature flag\". Too many " +"feature flags is a good problem to have, not the opposite. Automate the " +"process of creating a feature flag to lower its cost." +msgstr "" + +msgid "" +"function processTransaction() {\n" +" validate();\n" +" persist();\n" +" // TODO: add call to notifyListeners()\n" +"}\n" +msgstr "" + +msgid "" +"function processTransaction() {\n" +" validate();\n" +" persist();\n" +" if (featureIsEnabled(\"activate-notify-listeners\")) {\n" +" notifyListeners();\n" +" }\n" +"}\n" +msgstr "" + +msgid "" +"title: \"Feature flags: differences between backend, frontend and mobile\"\n" +"date: 2020-10-19\n" +"updated_at: 2020-11-03\n" +"layout: post\n" +"lang: en\n" +"ref: feature-flags-differences-between-backend-frontend-and-mobile\n" +"eu_categories: presentation" +msgstr "" + +#~ msgid "" +#~ "title: \"Feature flags: differences between backend, frontend and mobile\"\n" +#~ "date: 2020-10-19\n" +#~ "updated_at: 2020-11-03\n" +#~ "layout: post\n" +#~ "lang: en\n" +#~ "ref: feature-flags-differences-between-backend-frontend-and-mobile\n" +#~ "category: presentation" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_articles/2020-10-20-how-not-to-interview-engineers.po b/po/fr/LC_MESSAGES/_articles/2020-10-20-how-not-to-interview-engineers.po new file mode 100644 index 0000000..2dd6645 --- /dev/null +++ b/po/fr/LC_MESSAGES/_articles/2020-10-20-how-not-to-interview-engineers.po @@ -0,0 +1,476 @@ +# +msgid "" +msgstr "" + +msgid "" +"title: How not to interview engineers\n" +"date: 2020-10-20\n" +"updated_at: 2020-10-24\n" +"layout: post\n" +"lang: en\n" +"ref: how-not-to-interview-engineers" +msgstr "" + +msgid "" +"This is a response to Slava's \"[How to interview " +"engineers](https://defmacro.substack.com/p/how-to-interview-engineers)\" " +"article. I initially thought it was a satire, [as have " +"others](https://defmacro.substack.com/p/how-to-interview-" +"engineers/comments#comment-599996), but he has [doubled down on " +"it](https://twitter.com/spakhm/status/1315754730740617216):" +msgstr "" + +msgid "" +"(...) Some parts are slightly exaggerated for sure, but the essay isn't " +"meant as a joke." +msgstr "" + +msgid "" +"That being true, he completely misses the point on how to improve hiring, " +"and proposes a worse alternative on many aspects. It doesn't qualify as " +"provocative, it is just wrong." +msgstr "" + +msgid "" +"I was comfortable taking it as a satire, and I would just ignore the whole " +"thing if it wasn't (except for the technical memo part), but friends of mine" +" considered it to be somewhat reasonable. This is a adapted version of parts" +" of the discussions we had, risking becoming a gigantic showcase of [Poe's " +"law](https://en.wikipedia.org/wiki/Poe%27s_law)." +msgstr "" + +msgid "" +"In this piece, I will argument against his view, and propose an alternative " +"approach to improve hiring." +msgstr "" + +msgid "" +"It is common to find people saying how broken technical hiring is, as well " +"put in words by a phrase on [this " +"comment](https://news.ycombinator.com/item?id=24757511):" +msgstr "" + +msgid "" +"Everyone loves to read and write about how developer interviewing is flawed," +" but no one wants to go out on a limb and make suggestions about how to " +"improve it." +msgstr "" + +msgid "" +"I guess Slava was trying to not fall on this trap, and make a suggestion on " +"how to improve instead, which all went terribly wrong." +msgstr "" + +msgid "What not to do" +msgstr "" + +msgid "Time candidates" +msgstr "" + +msgid "" +"Timing the candidate shows up on the \"talent\" and \"judgment\" sections, " +"and they are both bad ideas for the same reason: programming is not a " +"performance." +msgstr "" + +msgid "" +"What do e-sports, musicians, actors and athletes have in common: performance" +" psychologists." +msgstr "" + +msgid "" +"For a pianist, their state of mind during concerts is crucial: they not only" +" must be able to deal with stage anxiety, but to become really successful " +"they will have to learn how to exploit it. The time window of the concert is" +" what people practice thousands of hours for, and it is what defines one's " +"career, since how well all the practice went is irrelevant to the nature of " +"the profession. Being able to leverage stage anxiety is an actual goal of " +"them." +msgstr "" + +msgid "" +"That is also applicable to athletes, where the execution during a " +"competition makes them sink or swim, regardless of how all the training was." +msgstr "" + +msgid "" +"The same cannot be said about composers, though. They are more like book " +"writers, where the value is not on very few moments with high adrenaline, " +"but on the aggregate over hours, days, weeks, months and years. A composer " +"may have a deadline to finish a song in five weeks, but it doesn't really " +"matter if it is done on a single night, every morning between 6 and 9, at " +"the very last week, or any other way. No rigid time structure applies, only " +"whatever fits best to the composer." +msgstr "" + +msgid "" +"Programming is more like composing than doing a concert, which is another " +"way of saying that programming is not a performance. People don't practice " +"algorithms for months to keep them at their fingertips, so that finally in a" +" single afternoon they can sit down and write everything at once in a rigid " +"4 hours window, and launch it immediately after." +msgstr "" + +msgid "" +"Instead software is built iteratively, by making small additions, than " +"refactoring the implementation, fixing bugs, writing a lot at once, *etc*. " +"all while they get a firmer grasp of the problem, stop to think about it, " +"come up with new ideas, *etc*." +msgstr "" + +msgid "" +"Some specifically plan for including spaced pauses, and call it \"[Hammock " +"Driven Development](https://www.youtube.com/watch?v=f84n5oFoZBc)\", which is" +" just artist's \"creative idleness\" for hackers." +msgstr "" + +msgid "" +"Unless you're hiring for a live coding group, a competitive programming " +"team, or a professional live demoer, timing the candidate that way is more " +"harmful than useful. This type of timing doesn't find good programmers, it " +"finds performant programmers, which isn't the same thing, and you'll end up " +"with people who can do great work on small problems but who might be unable " +"to deal with big problems, and loose those who can very well handle huge " +"problems, slowly. If you are lucky you'll get performant people who can also" +" handle big problems on the long term, but maybe not." +msgstr "" + +msgid "" +"An incident is the closest to a \"performance\" that it gets, and yet it is " +"still dramatically different. Surely it is a high stress scenario, but while" +" people are trying to find a root cause and solve the problem, only the " +"downtime itself is visible to the exterior. It is like being part of the " +"support staff backstage during a play: even though execution matters, you're" +" still not on the spot. During an incident you're doing debugging in anger " +"rather than live coding." +msgstr "" + +msgid "" +"Although giving a candidate the task to write a \"technical memo\" has " +"potential to get a measure of the written communication skills of someone, " +"doing so in a hard time window also misses the point for the same reasons." +msgstr "" + +msgid "Pay attention to typing speed" +msgstr "" + +msgid "" +"Typing is speed in never the bottleneck of a programmer, no matter how great" +" they are." +msgstr "" + +msgid "" +"As [Dijkstra " +"said](https://www.cs.utexas.edu/users/EWD/transcriptions/EWD05xx/EWD512.html):" +msgstr "" + +msgid "" +"But programming, when stripped of all its circumstantial irrelevancies, " +"boils down to no more and no less than very effective thinking so as to " +"avoid unmastered complexity, to very vigorous separation of your many " +"different concerns." +msgstr "" + +msgid "In other words, programming is not about typing, it is about thinking." +msgstr "" + +msgid "" +"Otherwise, the way to get those star programmers that can't type fast enough" +" a huge productivity boost is to give them a touch typing course. If they " +"are so productive with typing speed being a limitation, imagine what they " +"could accomplish if they had razor sharp touch typing skills?" +msgstr "" + +msgid "" +"Also, why stop there? A good touch typist can do 90 WPM (words per minute), " +"and a great one can do 120 WPM, but with a stenography keyboard they get to " +"200 WPM+. That is double the productivity! Why not try [speech-to-" +"text](https://www.youtube.com/watch?v=Mz3JeYfBTcY)? Make them all use " +"[J](https://www.jsoftware.com/#/) so they all need to type less! How come " +"nobody thought of that?" +msgstr "" + +msgid "" +"And if someone couldn't solve the programming puzzle in the given time " +"window, but could come back in the following day with an implementation that" +" is not only faster, but uses less memory, was simpler to understand and " +"easier to read than anybody else? You'd be losing that person too." +msgstr "" + +msgid "IQ" +msgstr "" + +msgid "" +"For \"building an extraordinary team at a hard technology startup\", " +"intelligence is not the most important, [determination " +"is](http://www.paulgraham.com/determination.html)." +msgstr "" + +msgid "" +"And talent isn't \"IQ specialized for engineers\". IQ itself isn't a measure" +" of how intelligent someone is. Ever since Alfred Binet with Théodore Simon " +"started to formalize what would become IQ tests years later, they already " +"acknowledged limitations of the technique for measuring intelligence, which " +"is [still true today](https://sci-" +"hub.do/https://psycnet.apa.org/doiLanding?doi=10.1037%2F1076-8971.6.1.33)." +msgstr "" + +msgid "" +"So having a high IQ tells only how smart people are for a particular aspect " +"of intelligence, which is not representative of programming. There are " +"numerous aspects of programming that are covered by IQ measurement: how to " +"name variables and functions, how to create models which are compatible with" +" schema evolution, how to make the system dynamic for runtime " +"parameterization without making it fragile, how to measure and observe " +"performance and availability, how to pick between acquiring and paying " +"technical debt, *etc*." +msgstr "" + +msgid "" +"Not to say about everything else that a programmer does that is not purely " +"programming. Saying high IQ correlates with great programming is a stretch, " +"at best." +msgstr "" + +msgid "Ditch HR" +msgstr "" + +msgid "Slava tangentially picks on HR, and I will digress on that a bit:" +msgstr "" + +msgid "" +"A good rule of thumb is that if a question could be asked by an intern in " +"HR, it's a non-differential signaling question." +msgstr "" + +msgid "" +"Stretching it, this is a rather snobbish view of HR. Why is it that an " +"intern in HR can't make signaling questions? Could the same be said of an " +"intern in engineering?" +msgstr "" + +msgid "" +"In other words: is the question not signaling because the one asking is from" +" HR, or because the one asking is an intern? If the latter, than he's just " +"arguing that interns have no place in interviewing, but if the former than " +"he was picking on HR." +msgstr "" + +msgid "" +"Extrapolating that, it is common to find people who don't value HR's work, " +"and only see them as inferiors doing unpleasant work, and who aren't capable" +" enough (or *smart* enough) to learn programming." +msgstr "" + +msgid "" +"This is equivalent to people who work primarily on backend, and see others " +"working on frontend struggling and say: \"isn't it just building views and " +"showing them on the browser? How could it possibly be that hard? I bet I " +"could do it better, with 20% of code\". As you already know, the answer to " +"it is \"well, why don't you go do it, then?\"." +msgstr "" + +msgid "" +"This sense of superiority ignores the fact that HR have actual professionals" +" doing actual hard work, not unlike programmers. If HR is inferior and so " +"easy, why not automate everything away and get rid of a whole department?" +msgstr "" + +msgid "" +"I don't attribute this world view to Slava, this is only an extrapolation of" +" a snippet of the article." +msgstr "" + +msgid "Draconian mistreating of candidates" +msgstr "" + +msgid "" +"If I found out that people employed theatrics in my interview so that I " +"could feel I've \"earned the privilege to work at your company\", I would " +"quit." +msgstr "" + +msgid "" +"If your moral compass is so broken that you are comfortable mistreating me " +"while I'm a candidate, I immediately assume you will also mistreat me as an " +"employee, and that the company is not a good place to work, as [evil begets " +"stupidity](http://www.paulgraham.com/apple.html):" +msgstr "" + +msgid "" +"But the other reason programmers are fussy, I think, is that evil begets " +"stupidity. An organization that wins by exercising power starts to lose the " +"ability to win by doing better work. And it's not fun for a smart person to " +"work in a place where the best ideas aren't the ones that win. I think the " +"reason Google embraced \"Don't be evil\" so eagerly was not so much to " +"impress the outside world as to inoculate themselves against arrogance." +msgstr "" + +msgid "" +"Paul Graham goes beyond \"don't be evil\" with a better motto: \"[be " +"good](http://www.paulgraham.com/good.html)\"." +msgstr "" + +msgid "" +"Abusing the asymmetric nature of an interview to increase the chance that " +"the candidate will accept the offer is, well, abusive. I doubt a solid team " +"can actually be built on such poor foundations, surrounded by such evil " +"measures." +msgstr "" + +msgid "" +"And if you really want to give engineers \"the measure of whoever they're " +"going to be working with\", there are plenty of reasonable ways of doing it " +"that don't include performing fake interviews." +msgstr "" + +msgid "Personality tests" +msgstr "" + +msgid "" +"Personality tests around the world need to be a) translated, b) adapted and " +"c) validated. Even though a given test may be applicable and useful in a " +"country, this doesn't imply it will work for other countries." +msgstr "" + +msgid "" +"Not only tests usually come with translation guidelines, but also its " +"applicability needs to be validated again after the translation and " +"adaptation is done to see if the test still measures what it is supposed to." +msgstr "" + +msgid "" +"That is also true within the same language. If a test is shown to work in " +"England, it may not work in New Zealand, in spite of both speaking english. " +"The cultural context difference is influent to the point of invalidating a " +"test and making it be no longer valid." +msgstr "" + +msgid "" +"Irregardless of the validity of the proposed \"big five\" personality test, " +"saying \"just use attributes x, y and z this test and you'll be fine\" is a " +"rough simplification, much like saying \"just use Raft for distributed " +"systems, after all it has been proven to work\" shows he throws all of that " +"background away." +msgstr "" + +msgid "" +"So much as applying personality tests themselves is not a trivial task, and " +"psychologists do need special training to become able to effectively apply " +"one." +msgstr "" + +msgid "More cargo culting" +msgstr "" + +msgid "" +"He calls the ill-defined \"industry standard\" to be cargo-culting, but his " +"proposal isn't sound enough to not become one." +msgstr "" + +msgid "" +"Even if the ideas were good, they aren't solid enough, or based on solid " +"enough things to make them stand out by themselves. Why is it that talent, " +"judgment and personality are required to determine the fitness of a good " +"candidate? Why not 2, 5, or 20 things? Why those specific 3? Why is talent " +"defined like that? Is it just because he found talent to be like that?" +msgstr "" + +msgid "" +"Isn't that definitionally also [cargo-" +"culting](http://calteches.library.caltech.edu/51/2/CargoCult.htm)[^cargo-" +"culting-archive]? Isn't he just repeating whatever he found to work form " +"him, without understanding why?" +msgstr "" + +msgid "What Feynman proposes is actually the opposite:" +msgstr "" + +msgid "" +"In summary, the idea is to try to give **all** of the information to help " +"others to judge the value of your contribution; not just the information " +"that leads to judgment in one particular direction or another." +msgstr "" + +msgid "" +"What Slava did was just another form of cargo culting, but this was one that" +" he believed to work." +msgstr "" + +msgid "" +"[^cargo-culting-archive]: [Archived " +"version](https://web.archive.org/web/20201003090303/http://calteches.library.caltech.edu/51/2/CargoCult.htm)." +msgstr "" + +msgid "What to do" +msgstr "" + +msgid "" +"I will not give you a list of things that \"worked for me, thus they are " +"correct\". I won't either critique the current \"industry standard\", nor " +"what I've learned from interviewing engineers." +msgstr "" + +msgid "" +"Instead, I'd like to invite you to learn from history, and from what other " +"professionals have to teach us." +msgstr "" + +msgid "" +"Programming isn't an odd profession, where everything about it is different " +"from anything else. It is just another episode in the \"technology\" series," +" which has seasons since before recorded history. It may be an episode where" +" things move a bit faster, but it is fundamentally the same." +msgstr "" + +msgid "" +"So here is the key idea: what people did *before* software engineering?" +msgstr "" + +msgid "" +"What hiring is like for engineers in other areas? Don't civil, electrical " +"and other types of engineering exist for much, much longer than software " +"engineering does? What have those centuries of accumulated experience " +"thought the world about technical hiring?" +msgstr "" + +msgid "" +"What studies were performed on the different success rate of interviewing " +"strategies? What have they done right and what have they done wrong?" +msgstr "" + +msgid "" +"What is the purpose of HR? Why do they even exist? Do we need them, and if " +"so, what for? What is the value they bring, since everybody insist on " +"building an HR department in their companies? Is the existence of HR another" +" form of cargo culting?" +msgstr "" + +msgid "" +"What is industrial and organizational psychology? What is that field of " +"study? What do they specialize in? What have they learned since the " +"discipline appeared? What have they done right and wrong over history? Is is" +" the current academic consensus on that area? What is a hot debate topic in " +"academia on that area? What is the current bleeding edge of research? What " +"can they teach us about hiring? What can they teach us about technical " +"hiring?" +msgstr "" + +msgid "Conclusion" +msgstr "" + +msgid "" +"If all I've said makes me a \"no hire\" in the proposed framework, I'm " +"really glad." +msgstr "" + +msgid "" +"This says less about my programming skills, and more about the employer's " +"world view, and I hope not to be fooled into applying for a company that " +"adopts this one." +msgstr "" + +msgid "" +"Claiming to be selecting \"extraordinary engineers\" isn't an excuse to " +"reinvent the wheel, poorly." +msgstr "" diff --git a/po/fr/LC_MESSAGES/_articles/2020-11-07-diy-an-offline-bug-tracker-with-text-files-git-and-email.po b/po/fr/LC_MESSAGES/_articles/2020-11-07-diy-an-offline-bug-tracker-with-text-files-git-and-email.po new file mode 100644 index 0000000..272aba0 --- /dev/null +++ b/po/fr/LC_MESSAGES/_articles/2020-11-07-diy-an-offline-bug-tracker-with-text-files-git-and-email.po @@ -0,0 +1,173 @@ +# +msgid "" +msgstr "" + +msgid "title: DIY an offline bug tracker with text files, Git and email" +msgstr "" + +msgid "date: 2020-11-07" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: diy-an-offline-bug-tracker-with-text-files-git-and-email" +msgstr "" + +msgid "" +"When [push comes to " +"shove](https://github.com/github/dmca/blob/master/2020/10/2020-10-23-RIAA.md)," +" the operational aspects of governance of a software project matter a lot. " +"And everybody likes to chime in with their alternative of how to avoid " +"single points of failure in project governance, just like I'm doing right " +"now." +msgstr "" + +msgid "The most valuable assets of a project are:" +msgstr "" + +msgid "source code" +msgstr "" + +msgid "discussions" +msgstr "" + +msgid "documentation" +msgstr "" + +msgid "builds" +msgstr "" + +msgid "tasks and bugs" +msgstr "" + +msgid "" +"For **source code**, Git and other DVCS solve that already: everybody gets a" +" full copy of the entire source code." +msgstr "" + +msgid "" +"If your code forge is compromised, moving it to a new one takes a couple of " +"minutes, if there isn't a secondary remote serving as mirror already. In " +"this case, no action is required." +msgstr "" + +msgid "" +"If you're having your **discussions** by email, \"[taking this archive " +"somewhere else and carrying on is " +"effortless](https://sourcehut.org/blog/2020-10-29-how-mailing-lists-prevent-" +"censorship/)\"." +msgstr "" + +msgid "" +"Besides, make sure to backup archives of past discussions so that the " +"history is also preserved when this migration happens." +msgstr "" + +msgid "" +"The **documentation** should [live inside the repository " +"itself](https://podcast.writethedocs.org/2017/01/25/episode-3-trends/)[^writethedocs-" +"in-repo], so that not only it gets first class treatment, but also gets " +"distributed to everybody too. Migrating the code to a new forge already " +"migrates the documentation with it." +msgstr "" + +msgid "" +"[^writethedocs-in-repo]: Described as \"the ultimate marriage of the two\". " +"Starts at time 31:50." +msgstr "" + +msgid "" +"As long as you keep the **builds** vendor neutral, the migration should only" +" involve adapting how you call your `tests.sh` from the format of " +"`provider-1.yml` uses to the format that `provider-2.yml` accepts. It isn't " +"valuable to carry the build history with the project, as this data quickly " +"decays in value as weeks and months go by." +msgstr "" + +msgid "" +"But for **tasks and bugs** many rely on a vendor-specific service, where you" +" register and manage those issues via a web browser. Some provide an " +"[interface for interacting via email](https://man.sr.ht/todo.sr.ht/#email-" +"access) or an API for [bridging local bugs with vendor-specific " +"services](https://github.com/MichaelMure/git-bug#bridges). But they're all " +"layers around the service, that disguises it as being a central point of " +"failure, which when compromised would lead to data loss. When push comes to " +"shove, you'd loose data." +msgstr "" + +msgid "Alternative: text files, Git and email" +msgstr "" + +msgid "" +"Why not do the same as documentation, and move tasks and bugs into the " +"repository itself?" +msgstr "" + +msgid "" +"It requires no extra tool to be installed, and fits right in the already " +"existing workflow for source code and documentation." +msgstr "" + +msgid "" +"Any issues discussions are done in the mailing list, and a reference to a " +"discussion could be added to the ticket itself later on. External " +"contributors can file tickets by sending a patch." +msgstr "" + +msgid "" +"The good thing about this solution is that it works for 99% of projects out " +"there." +msgstr "" + +msgid "" +"For the other 1%, having Fossil's \"[tickets](https://fossil-" +"scm.org/home/doc/trunk/www/bugtheory.wiki)\" could be an alternative, but " +"you may not want to migrate your project to Fossil to get those niceties." +msgstr "" + +msgid "" +"Even though I keep a `TODOs.org` file on the main branch, you can have a " +"`tasks` branch with a `task-n.md` file for each task, or any other way you " +"like." +msgstr "" + +msgid "" +"These tools are familiar enough that you can adjust it to fit your workflow." +msgstr "" + +msgid "" +"I like to keep a " +"[`TODOs.org`](https://euandreh.xyz/mediator.git/tree/TODOs.org) file at the " +"repository top-level, with two relevant sections: \"tasks\" and \"bugs\". " +"Then when building the documentation I'll just [generate an HTML file from " +"it](https://euandreh.xyz/mediator.git/tree/scripts/build-" +"site.sh?id=db4a727bc24b54b50158827b34502de21dbf8948#n14), and " +"[publish](https://euandreh.xyz/mediator/TODOs.html) it alongside the static " +"website. All that is done on the main branch." +msgstr "" + +#~ msgid "" +#~ "I like to keep a " +#~ "[`TODOs.org`](https://euandreh.xyz/mediator.git/tree/TODOs.org) file at the " +#~ "repository top-level, with two relevant sections: \"tasks\" and \"bugs\". " +#~ "Then when building the documentation I'll just [generate an HTML file from " +#~ "it](https://euandreh.xyz/mediator.git/tree/scripts/build-" +#~ "site.sh?id=db4a727bc24b54b50158827b34502de21dbf8948#n14), and " +#~ "[publish](https://mediator.euandreh.xyz/tasks-and-bugs.html) it alongside " +#~ "the static website. All that is done on the main branch." +#~ msgstr "" + +#~ msgid "" +#~ "I like to keep a " +#~ "[`TODOs.org`](https://euandreh.xyz/mediator.git/tree/TODOs.org?id=110c0af4ef53faf6e1ebe87905ce16766548607e)" +#~ " file at the repository top-level, with two relevant sections: \"tasks\" and" +#~ " \"bugs\". Then when building the documentation I'll just [generate an HTML " +#~ "file from it](https://euandreh.xyz/mediator.git/tree/scripts/build-" +#~ "site.sh?id=db4a727bc24b54b50158827b34502de21dbf8948#n14), and " +#~ "[publish](https://mediator.euandreh.xyz/tasks-and-bugs.html) it alongside " +#~ "the static website. All that is done on the main branch." +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_articles/2020-11-08-the-next-paradigm-shift-in-programming-video-review.po b/po/fr/LC_MESSAGES/_articles/2020-11-08-the-next-paradigm-shift-in-programming-video-review.po new file mode 100644 index 0000000..953f769 --- /dev/null +++ b/po/fr/LC_MESSAGES/_articles/2020-11-08-the-next-paradigm-shift-in-programming-video-review.po @@ -0,0 +1,248 @@ +# +msgid "" +msgstr "" + +msgid "title: The Next Paradigm Shift in Programming - video review" +msgstr "" + +msgid "date: 2020-11-08" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: the-next-paradigm-shift-in-programming-video-review" +msgstr "" + +msgid "" +"This is a review with comments of \"[The Next Paradigm Shift in " +"Programming](https://www.youtube.com/watch?v=6YbK8o9rZfI)\", by Richard " +"Feldman." +msgstr "" + +msgid "" +"This video was *strongly* suggested to me by a colleague. I wanted to " +"discuss it with her, and when drafting my response I figured I could publish" +" it publicly instead." +msgstr "" + +msgid "" +"Before anything else, let me just be clear: I really like the talk, and I " +"think Richard is a great public speaker. I've watched several of his talks " +"over the years, and I feel I've followed his career at a distance, with much" +" respect. This isn't a piece criticizing him personally, and I agree with " +"almost everything he said. These are just some comments but also nitpicks on" +" a few topics I think he missed, or that I view differently." +msgstr "" + +msgid "Structured programming" +msgstr "" + +msgid "" +"The historical overview at the beginning is very good. In fact, the very " +"video I watched previously was about structured programming!" +msgstr "" + +msgid "" +"Kevlin Henney on \"[The Forgotten Art of Structured " +"Programming](https://www.youtube.com/watch?v=SFv8Wm2HdNM)\" does a deep-dive" +" on the topic of structured programming, and how on his view it is still " +"hidden in our code, when we do a `continue` or a `break` in some ways. Even " +"though it is less common to see an explicit `goto` in code these days, many " +"of the original arguments of Dijkstra against explicit `goto`s is applicable" +" to other constructs, too." +msgstr "" + +msgid "" +"This is a very mature view, and I like how he goes beyond the \"don't use " +"`goto`s\" heuristic and proposes and a much more nuanced understanding of " +"what \"structured programming\" means." +msgstr "" + +msgid "" +"In a few minutes, Richard is able to condense most of the significant bits " +"of Kevlin's talk in a didactical way. Good job." +msgstr "" + +msgid "OOP like a distributed system" +msgstr "" + +msgid "" +"Richard extrapolates Alan Kay's original vision of OOP, and he concludes " +"that it is more like a distributed system that how people think about OOP " +"these days. But he then states that this is a rather bad idea, and we " +"shouldn't pursue it, given that distributed systems are known to be hard." +msgstr "" + +msgid "" +"However, his extrapolation isn't really impossible, bad or an absurd. In " +"fact, it has been followed through by Erlang. Joe Armstrong used to say that" +" \"[Erlang might the only OOP " +"language](https://www.infoq.com/interviews/johnson-armstrong-oop/)\", since " +"it actually adopted this paradigm." +msgstr "" + +msgid "" +"But Erlang is a functional language. So this \"OOP as a distributed system\"" +" view is more about designing systems in the large than programs in the " +"small." +msgstr "" + +msgid "" +"There is a switch of levels in this comparison I'm making, as can be done " +"with any language or paradigm: you can have a functional-like system that is" +" built with an OOP language (like a compiler, that given the same input will" +" produce the same output), or an OOP-like system that is built with a " +"functional language (Rich Hickey calls it \"[OOP in the " +"large](https://www.youtube.com/watch?v=ROor6_NGIWU)\"[^the-language-of-the-" +"system])." +msgstr "" + +msgid "" +"So this jump from in-process paradigm to distributed paradigm is rather a " +"big one, and I don't think you he can argue that OOP has anything to say " +"about software distribution across nodes. You can still have Erlang actors " +"that run independently and send messages to each other without a network " +"between them. Any OTP application deployed on a single node effectively " +"works like that." +msgstr "" + +msgid "" +"I think he went a bit too far with this extrapolation. Even though I agree " +"it is a logical a fair one, it isn't evidently bad as he painted. I would be" +" fine working with a single-node OTP application and seeing someone call it " +"\"a *real* OOP program\"." +msgstr "" + +msgid "[^the-language-of-the-system]: From 24:05 to 27:45." +msgstr "" + +msgid "First class immutability" +msgstr "" + +msgid "" +"I agree with his view of languages moving towards the functional paradigm. " +"But I think you can narrow down the \"first-class immutability\" feature he " +"points out as present on modern functional programming languages to \"first-" +"class immutable data structures\"." +msgstr "" + +msgid "" +"I wouldn't categorize a language as \"supporting functional programming " +"style\" without a library for functional data structures it. By discipline " +"you can avoid side-effects, write pure functions as much as possible, and " +"pass functions as arguments around is almost every language these days, but " +"if when changing an element of a vector mutates things in-place, that is " +"still not functional programming." +msgstr "" + +msgid "" +"To avoid that, you end-up needing to make clones of objects to pass to a " +"function, using freezes or other workarounds. All those cases are when the " +"underlying mix of OOP and functional programming fail." +msgstr "" + +msgid "" +"There are some languages with third-party libraries that provide functional " +"data structures, like [immer](https://sinusoid.es/immer/) for C++, or " +"[ImmutableJS](https://immutable-js.github.io/immutable-js/) for JavaScript." +msgstr "" + +msgid "" +"But functional programming is more easily achievable in languages that have " +"them built-in, like Erlang, Elm and Clojure." +msgstr "" + +msgid "Managed side-effects" +msgstr "" + +msgid "" +"His proposal of adopting managed side-effects as a first-class language " +"concept is really intriguing." +msgstr "" + +msgid "" +"I haven't worked with a language with managed side-effects at scale, and I " +"don't feel this is a problem with Clojure or Erlang. But is this me finding " +"a flaw in his argument or not acknowledging a benefit unknown to me? This is" +" a provocative question I ask myself." +msgstr "" + +msgid "What about declarative programming?" +msgstr "" + +msgid "Conclusion" +msgstr "" + +msgid "" +"Beyond all Richard said, I also hear often bring up functional programming " +"when talking about utilizing all cores of a computer, and how FP can help " +"with that." +msgstr "" + +msgid "" +"Rich Hickey makes a great case for single-process FP on his famous talk " +"\"[Simple Made Easy](https://www.infoq.com/presentations/Simple-Made-" +"Easy/)\"." +msgstr "" + +msgid "" +"This is something you can achieve with a library, like " +"[Redux](https://redux.js.org/) for JavaScript or [re-" +"frame](https://github.com/Day8/re-frame) for Clojure." +msgstr "" + +msgid "" +"Also all FP languages with managed side-effects I know are statically-typed," +" and all dynamically-typed FP languages I know don't have managed side-" +"effects baked in." +msgstr "" + +msgid "" +"In \"[Out of the Tar " +"Pit](http://curtclifton.net/papers/MoseleyMarks06a.pdf)\", B. Moseley and P." +" Marks go beyond his view of functional programming as the basis, and name a" +" possible \"functional relational programming\" as an even better solution. " +"They explicitly call out some flaws in most of the modern functional " +"programming languages, and instead pick declarative programming as an even " +"better starting paradigm." +msgstr "" + +msgid "" +"If the next paradigm shift is towards functional programming, will the " +"following shift be towards declarative programming?" +msgstr "" + +msgid "eu_categories: video review" +msgstr "" + +#~ msgid "category: video review" +#~ msgstr "" + +#~ msgid "" +#~ "This is something you can achieve with a library, like " +#~ "[Redux](https://redux.js.org/) for JavaScript or re-frame for Clojure." +#~ msgstr "" + +#~ msgid "" +#~ "Also all languages with managed side-effects I know are statically-typed, " +#~ "and all dynamically-typed languages I know don't have managed side-effects " +#~ "baked in." +#~ msgstr "" + +#~ msgid "" +#~ "\"[Out of the Tar Pit](http://curtclifton.net/papers/MoseleyMarks06a.pdf)\" " +#~ "by B. Moseley and P. Marks goes beyond his view of functional programming, " +#~ "and name a possible \"functional relational programming\" as an even better " +#~ "solution. They explicitly call out some flaws in most of the modern " +#~ "functional programming languages, and instead pick declarative programming " +#~ "as an even better starting paradigm." +#~ msgstr "" + +#~ msgid "" +#~ "If functional programming is the next paradigm shift, is declarative " +#~ "programming the next next paradigm shift?" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.po b/po/fr/LC_MESSAGES/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.po new file mode 100644 index 0000000..15005ad --- /dev/null +++ b/po/fr/LC_MESSAGES/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.po @@ -0,0 +1,416 @@ +# +msgid "" +msgstr "" + +msgid "" +"title: Durable persistent trees and parser combinators - building a database" +msgstr "" + +msgid "date: 2020-11-12" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "" +"ref: durable-persistent-trees-and-parser-combinators-building-a-database" +msgstr "" + +msgid "" +"I've received with certain frequency messages from people wanting to know if" +" I've made any progress on the database project [I've written about]({% link" +" _articles/2020-08-31-the-database-i-wish-i-had.md %})." +msgstr "" + +msgid "" +"There are a few areas where I've made progress, and here's a public post on " +"it." +msgstr "" + +msgid "Proof-of-concept: DAG log" +msgstr "" + +msgid "" +"The main thing I wanted to validate with a concrete implementation was the " +"concept of modeling a DAG on a sequence of datoms." +msgstr "" + +msgid "" +"The notion of a *datom* is a rip-off from Datomic, which models data with " +"time aware *facts*, which come from RDF. RDF's fact is a triple of subject-" +"predicate-object, and Datomic's datoms add a time component to it: subject-" +"predicate-object-time, A.K.A. entity-attribute-value-transaction:" +msgstr "" + +msgid "" +"[[person :likes \"pizza\" 0 true]\n" +" [person :likes \"bread\" 1 true]\n" +" [person :likes \"pizza\" 1 false]]\n" +msgstr "" + +msgid "The above datoms say:" +msgstr "" + +msgid "at time 0, `person` like pizza;" +msgstr "" + +msgid "at time 1, `person` stopped liking pizza, and started to like bread." +msgstr "" + +msgid "" +"Datomic ensures total consistency of this ever growing log by having a " +"single writer, the transactor, that will enforce it when writing." +msgstr "" + +msgid "" +"In order to support disconnected clients, I needed a way to allow multiple " +"writers, and I chose to do it by making the log not a list, but a directed " +"acyclic graph (DAG):" +msgstr "" + +msgid "" +"The extra datoms above add more information to build the directionality to " +"the log, and instead of a single consistent log, the DAG could have multiple" +" leaves that coexist, much like how different Git branches can have " +"different \"latest\" commits." +msgstr "" + +msgid "" +"In order to validate this idea, I started with a Clojure implementation. The" +" goal was not to write the actual final code, but to make a proof-of-concept" +" that would allow me to test and stretch the idea itself." +msgstr "" + +msgid "" +"This code [already " +"exists](https://euandreh.xyz/mediator.git/tree/src/core/clojure/src/mediator.clj?id=db4a727bc24b54b50158827b34502de21dbf8948#n1)," +" but is yet fairly incomplete:" +msgstr "" + +msgid "" +"the building of the index isn't done yet (with some [commented " +"code](https://euandreh.xyz/mediator.git/tree/src/core/clojure/src/mediator.clj?id=db4a727bc24b54b50158827b34502de21dbf8948#n295)" +" on the next step to be implemented)" +msgstr "" + +msgid "" +"the indexing is extremely inefficient, with " +"[more](https://euandreh.xyz/mediator.git/tree/src/core/clojure/src/mediator.clj?id=db4a727bc24b54b50158827b34502de21dbf8948#n130)" +" " +"[than](https://euandreh.xyz/mediator.git/tree/src/core/clojure/src/mediator.clj?id=db4a727bc24b54b50158827b34502de21dbf8948#n146)" +" " +"[one](https://euandreh.xyz/mediator.git/tree/src/core/clojure/src/mediator.clj?id=db4a727bc24b54b50158827b34502de21dbf8948#n253)" +" occurrence of `O²` functions;" +msgstr "" + +msgid "no query support yet." +msgstr "" + +msgid "Top-down *and* bottom-up" +msgstr "" + +msgid "" +"However, as time passed and I started looking at what the final " +"implementation would look like, I started to consider keeping the PoC " +"around." +msgstr "" + +msgid "" +"The top-down approach (Clojure PoC) was in fact helping guide me with the " +"bottom-up, and I now have \"promoted\" the Clojure PoC into a \"reference " +"implementation\". It should now be a finished implementation that says what " +"the expected behaviour is, and the actual code should match the behaviour." +msgstr "" + +msgid "" +"The good thing about a reference implementation is that it has no " +"performance of resources boundary, so if it ends up being 1000x slower and " +"using 500× more memory, it should be find. The code can be also 10x or 100x " +"simpler, too." +msgstr "" + +msgid "Top-down: durable persistent trees" +msgstr "" + +msgid "" +"In promoting the PoC into a reference implementation, this top-down approach" +" now needs to go beyond doing everything in memory, and the index data " +"structure now needs to be disk-based." +msgstr "" + +msgid "" +"Roughly speaking, most storage engines out there are based either on B-Trees" +" or LSM Trees, or some variations of those." +msgstr "" + +msgid "" +"But when building an immutable database, update-in-place B-Trees aren't an " +"option, as it doesn't accommodate keeping historical views of the tree. LSM " +"Trees may seem a better alternative, but duplication on the files with " +"compaction are also ways to delete old data which is indeed useful for a " +"historical view." +msgstr "" + +msgid "" +"I think the thing I'm after is a mix of a Copy-on-Write B-Tree, which would " +"keep historical versions with the write IO cost amortization of memtables of" +" LSM Trees. I don't know of any B-Tree variant out there that resembles " +"this, so I'll call it \"Flushing Copy-on-Write B-Tree\"." +msgstr "" + +msgid "" +"I haven't written any code for this yet, so all I have is a high-level view " +"of what it will look like:" +msgstr "" + +msgid "" +"like Copy-on-Write B-Trees, changing a leaf involves creating a new leaf and" +" building a new path from root to the leaf. The upside is that writes a lock" +" free, and no coordination is needed between readers and writers, ever;" +msgstr "" + +msgid "" +"the downside is that a single leaf update means at least `H` new nodes that " +"will have to be flushed to disk, where `H` is the height of the tree. To " +"avoid that, the writer creates these nodes exclusively on the in-memory " +"memtable, to avoid flushing to disk on every leaf update;" +msgstr "" + +msgid "" +"a background job will consolidate the memtable data every time it hits X MB," +" and persist it to disk, amortizing the cost of the Copy-on-Write B-Tree;" +msgstr "" + +msgid "" +"readers than will have the extra job of getting the latest relevant disk-" +"resident value and merge it with the memtable data." +msgstr "" + +msgid "" +"The key difference to existing Copy-on-Write B-Trees is that the new trees " +"are only periodically written to disk, and the intermediate values are kept " +"in memory. Since no node is ever updated, the page utilization is maximum as" +" it doesn't need to keep space for future inserts and updates." +msgstr "" + +msgid "" +"And the key difference to existing LSM Trees is that no compaction is run: " +"intermediate values are still relevant as the database grows. So this leaves" +" out tombstones and value duplication done for write performance." +msgstr "" + +msgid "" +"One can delete intermediate index values to reclaim space, but no data is " +"lost on the process, only old B-Tree values. And if the database ever comes " +"back to that point (like when doing a historical query), the B-Tree will " +"have to be rebuilt from a previous value. After all, the database *is* a set" +" of datoms, and everything else is just derived data." +msgstr "" + +msgid "" +"Right now I'm still reading about other data structures that storage engines" +" use, and I'll start implementing the \"Flushing Copy-on-Write B-Tree\" as I" +" learn more[^learn-more-db] and mature it more." +msgstr "" + +msgid "" +"[^learn-more-db]: If you are interested in learning more about this too, the" +" very best two resources on this subject are Andy Pavlo's \"[Intro to " +"Database " +"Systems](https://www.youtube.com/playlist?list=PLSE8ODhjZXjbohkNBWQs_otTrBTrjyohi)\"" +" course and Alex Petrov's \"[Database " +"Internals](https://www.databass.dev/)\" book." +msgstr "" + +msgid "Bottom-up: parser combinators and FFI" +msgstr "" + +msgid "I chose Rust as it has the best WebAssembly tooling support." +msgstr "" + +msgid "" +"My goal is not to build a Rust database, but a database that happens to be " +"in Rust. In order to reach client platforms, the primary API is the FFI one." +msgstr "" + +msgid "" +"I'm not very happy with current tools for exposing Rust code via FFI to the " +"external world: they either mix C with C++, which I don't want to do, or " +"provide no access to the intermediate representation of the FFI, which would" +" be useful for generating binding for any language that speaks FFI." +msgstr "" + +msgid "" +"I like better the path that the author of " +"[cbindgen](https://github.com/eqrion/cbindgen) crate " +"[proposes](https://blog.eqrion.net/future-directions-for-cbindgen/): " +"emitting an data representation of the Rust C API (the author calls is a " +"`ffi.json` file), and than building transformers from the data " +"representation to the target language. This way you could generate a C API " +"*and* the node-ffi bindings for JavaScript automatically from the Rust code." +msgstr "" + +msgid "" +"So the first thing to be done before moving on is an FFI exporter that " +"doesn't mix C and C++, and generates said `ffi.json`, and than build a few " +"transformers that take this `ffi.json` and generate the language bindings, " +"be it C, C++, JavaScript, TypeScript, Kotlin, Swift, Dart, *etc*[^ffi-" +"langs]." +msgstr "" + +msgid "" +"[^ffi-langs]: Those are, specifically, the languages I'm more interested on." +" My goal is supporting client applications, and those languages are the most" +" relevant for doing so: C for GTK, C++ for Qt, JavaScript and TypeScript for" +" Node.js and browser, Kotlin for Android and Swing, Swift for iOS, and Dart " +"for Flutter." +msgstr "" + +msgid "" +"I think the best way to get there is by taking the existing code for " +"cbindgen, which uses the [syn](https://github.com/dtolnay/syn) crate to " +"parse the Rust code[^rust-syn], and adapt it to emit the metadata." +msgstr "" + +msgid "" +"[^rust-syn]: The fact that syn is an external crate to the Rust compiler " +"points to a big warning: procedural macros are not first class in Rust. They" +" are just like Babel plugins in JavaScript land, with the extra shortcoming " +"that there is no specification for the Rust syntax, unlike JavaScript." +msgstr "" + +msgid "" +"As flawed as this may be, it seems to be generally acceptable and adopted,\n" +"which works against building a solid ecosystem for Rust.\n" +"\n" +"The alternative that rust-ffi implements relies on internals of the Rust\n" +"compiler, which isn't actually worst, just less common and less accepted.\n" +msgstr "" + +msgid "" +"After \"finishing\" ParsecC I'll have a good notion of what a good C API is," +" and I'll have a better direction towards how to expose code from libedn to " +"other languages, and work on x-bindgen then." +msgstr "" + +msgid "" +"What both libedn and ParsecC are missing right now are proper error " +"reporting, and property-based testing for libedn." +msgstr "" + +msgid "Conclusion" +msgstr "" + +msgid "" +"I've learned a lot already, and I feel the journey I'm on is worth going " +"through." +msgstr "" + +msgid "" +"If any of those topics interest you, message me to discuss more or " +"contribute! Patches welcome!" +msgstr "" + +msgid "eu_categories: mediator" +msgstr "" + +msgid "" +"[[person :likes \"pizza\" 0 true]\n" +" [0 :parent :db/root 0 true]\n" +" [person :likes \"bread\" 1 true]\n" +" [person :likes \"pizza\" 1 false]\n" +" [1 :parent 0 1 true]]\n" +msgstr "" + +msgid "updated_at: 2021-02-09" +msgstr "" + +msgid "" +"I've started a fork of cbindgen: ~~x-bindgen~~[^x-bindgen]. Right now it is " +"just a copy of cbindgen verbatim, and I plan to remove all C and C++ " +"emitting code from it, and add a IR emitting code instead." +msgstr "" + +msgid "" +"[^x-bindgen]: *EDIT*: now archived, the experimentation was fun. I've " +"started to move more towards C, so this effort became deprecated." +msgstr "" + +msgid "" +"When starting working on x-bindgen, I realized I didn't know what to look " +"for in a header file, as I haven't written any C code in many years. So as I" +" was writing [libedn](https://euandreh.xyz/libedn.git/), I didn't know how " +"to build a good C API to expose. So I tried porting the code to C, and right" +" now I'm working on building a *good* C API for a JSON parser using parser " +"combinators: ~~ParsecC~~ [^parsecc]." +msgstr "" + +msgid "[^parsecc]: *EDIT*: now also archived." +msgstr "" + +#~ msgid "" +#~ "I've started a fork of cbindgen: " +#~ "[x-bindgen](https://euandreh.xyz/x-bindgen.git/). Right now it is just a " +#~ "copy of cbindgen verbatim, and I plan to remove all C and C++ emitting code " +#~ "from it, and add a IR emitting code instead." +#~ msgstr "" + +#~ msgid "" +#~ "When starting working on x-bindgen, I realized I didn't know what to look " +#~ "for in a header file, as I haven't written any C code in many years. So as I" +#~ " was writing [libedn](https://euandreh.xyz/libedn.git/), I didn't know how " +#~ "to build a good C API to expose. So I tried porting the code to C, and right" +#~ " now I'm working on building a *good* C API for a JSON parser using parser " +#~ "combinators: ~~ParsecC~~ *EDIT*: now archived, the experimentation was fun." +#~ msgstr "" + +#~ msgid "updated_at: 2020-11-14" +#~ msgstr "" + +#~ msgid "" +#~ "When starting working on x-bindgen, I realized I didn't know what to look " +#~ "for in a header file, as I haven't written any C code in many years. So as I" +#~ " was writing [libedn](https://euandreh.xyz/libedn.git/), I didn't know how " +#~ "to build a good C API to expose. So I tried porting the code to C, and right" +#~ " now I'm working on building a *good* C API for a JSON parser using parser " +#~ "combinators: [ParsecC](https://euandreh.xyz/parsecc.git/)." +#~ msgstr "" + +#~ msgid "" +#~ "I've started a fork of cbindgen: " +#~ "[x-bindgen](https://euandreh.xyz/x-bindgen.git/). Right now it is just a " +#~ "copy of cbindgen verbatim, and I plan to remove all C and C++ emitting code " +#~ "from it, and add a IR emitting code instead." +#~ msgstr "" + +#~ msgid "" +#~ "When starting working on x-bindgen, I realized I didn't know what to look " +#~ "for in a header file, as I haven't written any C code in many years. So as I" +#~ " was writing [libedn](https://euandreh.xyz/libedn.git/), I didn't know how " +#~ "to build a good C API to expose. So I tried porting the code to C, and right" +#~ " now I'm working on building a *good* C API for a JSON parser using parser " +#~ "combinators: [ParsecC](https://euandreh.xyz/parsecc.git/)." +#~ msgstr "" + +#~ msgid "" +#~ "When starting working on x-bindgen, I realized I didn't know what to look " +#~ "for in a header file, as I haven't written any C code in many years. So as I" +#~ " was writing [libedn](https://euandreh.xyz/libedn.git/), I didn't know how " +#~ "to build a good C API to expose. So I tried porting the code to C, and right" +#~ " now I'm working on building a *good* C API for a JSON parser using parser " +#~ "combinators: [ParsecC](https://euandreh.xyz/parsecc.git/)." +#~ msgstr "" + +#~ msgid "" +#~ "[[person :likes \"pizza\" 0 true]\n" +#~ " [0 :parent null 0 true]\n" +#~ " [person :likes \"bread\" 1 true]\n" +#~ " [person :likes \"pizza\" 1 false]\n" +#~ " [1 :parent 0 1 true]]\n" +#~ msgstr "" + +#~ msgid "category: mediator" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_articles/2020-11-14-local-first-software-you-own-your-data-in-spite-of-the-cloud-article-review.po b/po/fr/LC_MESSAGES/_articles/2020-11-14-local-first-software-you-own-your-data-in-spite-of-the-cloud-article-review.po new file mode 100644 index 0000000..03ca2c6 --- /dev/null +++ b/po/fr/LC_MESSAGES/_articles/2020-11-14-local-first-software-you-own-your-data-in-spite-of-the-cloud-article-review.po @@ -0,0 +1,514 @@ +# +msgid "" +msgstr "" + +msgid "" +"title: \"Local-First Software: You Own Your Data, in spite of the Cloud - " +"article review\"" +msgstr "" + +msgid "date: 2020-11-14" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "" +"ref: local-first-software-you-own-your-data-in-spite-of-the-cloud-article-" +"review" +msgstr "" + +msgid "eu_categories: presentation,article review" +msgstr "" + +msgid "" +"*This article is derived from a [presentation][presentation] given at a " +"Papers We Love meetup on the same subject.*" +msgstr "" + +msgid "" +"This is a review of the article \"[Local-First Software: You Own Your Data, " +"in spite of the Cloud][article-pdf]\", by M. Kleppmann, A. Wiggins, P. Van " +"Hardenberg and M. F. McGranaghan." +msgstr "" + +msgid "Offline-first, local-first" +msgstr "" + +msgid "" +"The \"local-first\" term they use isn't new, and I have used it myself in " +"the past to refer to this types of application, where the data lives " +"primarily on the client, and there are conflict resolution algorithms that " +"reconcile data created on different instances." +msgstr "" + +msgid "" +"Sometimes I see confusion with this idea and \"client-side\", \"offline-" +"friendly\", \"syncable\", etc. I have myself used this terms, also." +msgstr "" + +msgid "" +"There exists, however, already the \"offline-first\" term, which conveys " +"almost all of that meaning. In my view, \"local-first\" doesn't extend " +"\"offline-first\" in any aspect, rather it gives a well-defined meaning to " +"it instead. I could say that \"local-first\" is just \"offline-first\", but " +"with 7 well-defined ideals instead of community best practices." +msgstr "" + +msgid "" +"[presentation]: {% link _slides/2020-11-14-on-local-first-beyond-the-crdt-" +"silver-bullet.slides %} [article-pdf]: " +"https://martin.kleppmann.com/papers/local-first.pdf" +msgstr "" + +msgid "Software licenses" +msgstr "" + +msgid "" +"On a footnote of the 7th ideal (\"You Retain Ultimate Ownership and " +"Control\"), the authors say:" +msgstr "" + +msgid "" +"In our opinion, maintaining control and ownership of data does not mean that" +" the software must necessarily be open source. (...) as long as it does not " +"artificially restrict what users can do with their files." +msgstr "" + +msgid "" +"#!/bin/sh\n" +"\n" +"TODAY=$(date +%s)\n" +"LICENSE_EXPIRATION=$(date -d 2020-11-15 +%s)\n" +"\n" +"if [ $TODAY -ge $LICENSE_EXPIRATION ]; then\n" +" echo 'License expired!'\n" +" exit 1\n" +"fi\n" +"\n" +"echo $((2 + 2))\n" +msgstr "" + +msgid "Now when using this very useful program:" +msgstr "" + +msgid "" +"# today\n" +"$ ./useful-adder.sh\n" +"4\n" +"# tomorrow\n" +"$ ./useful-adder.sh\n" +"License expired!\n" +msgstr "" + +msgid "" +"This is obviously an intentional restriction, and it goes against the 5th " +"ideal (\"The Long Now\"). This software would only be useful as long as the " +"embedded license expiration allowed. Sure you could change the clock on the " +"computer, but there are many other ways that this type of intentional " +"restriction is in conflict with that ideal." +msgstr "" + +msgid "" +"However, what about unintentional restrictions? What if a software had an " +"equal or similar restriction, and stopped working after days pass? Or what " +"if the programmer added a constant to make the development simpler, and this" +" led to unintentionally restricting the user?" +msgstr "" + +msgid "" +"# today\n" +"$ useful-program\n" +"# ...useful output...\n" +"\n" +"# tomorrow, with more data\n" +"$ useful-program\n" +"ERROR: Panic! Stack overflow!\n" +msgstr "" + +msgid "" +"An open specification could serve as a blueprint to other implementations, " +"making the data format more friendly to reverse-engineering. But the re-" +"implementation still has to exist, at which point the original software " +"failed to achieve \"The Long Now\"." +msgstr "" + +msgid "It is less bad, but still not quite there yet." +msgstr "" + +msgid "Denial of existing solutions" +msgstr "" + +msgid "" +"When describing \"Existing Data Storage and Sharing Models\", on a " +"footnote[^devil] the authors say:" +msgstr "" + +msgid "" +"[^devil]: This is the second aspect that I'm picking on the article from a " +"footnote. I guess the devil really is on the details." +msgstr "" + +msgid "" +"In principle it is possible to collaborate without a repository service, " +"e.g. by sending patch files by email, but the majority of Git users rely on " +"GitHub." +msgstr "" + +msgid "" +"The authors go to a great length to talk about usability of cloud apps, and " +"even point to research they've done on it, but they've missed learning more " +"from local-first solutions that already exist." +msgstr "" + +msgid "" +"Say the automerge CRDT proves to be even more useful than what everybody " +"imagined. Say someone builds a local-first repository service using it. How " +"will it change anything of the Git/GitHub model? What is different about it " +"that prevents people in the future writing a paper saying:" +msgstr "" + +msgid "" +"In principle it is possible to collaborate without a repository service, " +"e.g. by using automerge and platform X, but the majority of Git users rely " +"on GitHub." +msgstr "" + +msgid "How is this any better?" +msgstr "" + +msgid "" +"If it is already [possible](https://drewdevault.com/2018/07/23/Git-is-" +"already-distributed.html) to have a local-first development workflow, why " +"don't people use it? Is it just fashion, or there's a fundamental problem " +"with it? If so, what is it, and how to avoid it?" +msgstr "" + +msgid "" +"If sending patches by emails is perfectly possible but out of fashion, why " +"even talk about Git/GitHub? Isn't this a problem that people are putting " +"themselves in? How can CRDTs possibly prevent people from doing that?" +msgstr "" + +msgid "" +"My impression is that the authors envision a better future, where " +"development is fully decentralized unlike today, and somehow CRDTs will make" +" that happen. If more people think this way, \"CRDT\" is next in line to the" +" buzzword list that solves everything, like \"containers\", \"blockchain\" " +"or \"machine learning\"." +msgstr "" + +msgid "" +"Rather than picturing an imaginary service that could be described like " +"\"GitHub+CRDTs\" and people would adopt it, I'd rather better understand why" +" people don't do it already, since Git is built to work like that." +msgstr "" + +msgid "Ditching of web applications" +msgstr "" + +msgid "" +"The authors put web application in a worse position for building local-first" +" application, claiming that:" +msgstr "" + +msgid "" +"(...) the architecture of web apps remains fundamentally server-centric. " +"Offline support is an afterthought in most web apps, and the result is " +"accordingly fragile." +msgstr "" + +msgid "Well, I disagree." +msgstr "" + +msgid "" +"The problem isn't inherit to the web platform, but instead how people use " +"it." +msgstr "" + +msgid "" +"I have myself built offline-first applications, leveraging IndexedDB, App " +"Cache, *etc*. I wanted to build an offline-first application on the web, and" +" so I did." +msgstr "" + +msgid "" +"In fact, many people choose [PouchDB](https://pouchdb.com/) *because* of " +"that, since it is a good tool for offline-first web applications. The " +"problem isn't really the technology, but how much people want their " +"application to be local-first." +msgstr "" + +msgid "" +"Contrast it with Android [Instant " +"Apps](https://developer.android.com/topic/google-play-instant), where " +"applications are sent to the phone in small parts. Since this requires an " +"internet connection to move from a part of the app bundle to another, a " +"subset of the app isn't local-first, despite being an app." +msgstr "" + +msgid "" +"The point isn't the technology, but how people are using it. Local-first web" +" applications are perfectly possible, just like non-local-first native " +"applications are possible." +msgstr "" + +msgid "Costs are underrated" +msgstr "" + +msgid "" +"I think the costs of \"old-fashioned apps\" over \"cloud apps\" are " +"underrated, mainly regarding storage, and that this costs can vary a lot by " +"application." +msgstr "" + +msgid "" +"Say a person writes online articles for their personal website, and puts " +"everything into Git. Since there isn't supposed to be any collaboration, all" +" of the relevant ideals of local-first are achieved." +msgstr "" + +msgid "" +"Now another person creates videos instead of articles. They could try " +"keeping everything local, but after some time the storage usage fills the " +"entire disk. This person's local-first setup would be much more complex, and" +" would cost much more on maintenance, backup and storage." +msgstr "" + +msgid "" +"Even though both have similar needs, a local-first video repository is much " +"more demanding. So the local-first thinking here isn't \"just keep " +"everything local\", but \"how much time and money am I willing to spend to " +"keep everything local\"." +msgstr "" + +msgid "" +"The convenience of \"cloud apps\" becomes so attractive that many don't even" +" have a local copy of their videos, and rely exclusively on service " +"providers to maintain, backup and store their content." +msgstr "" + +msgid "" +"The dial measuring \"cloud apps\" and \"old-fashioned apps\" needs to be " +"specific to use-cases." +msgstr "" + +msgid "Real-time collaboration is optional" +msgstr "" + +msgid "" +"If I were the one making the list of ideals, I wouldn't focus so much on " +"real-time collaboration." +msgstr "" + +msgid "" +"Even though seamless collaboration is desired, it being real-time depends on" +" the network being available for that. But ideal 3 states that \"The Network" +" is Optional\", so real-time collaboration is also optional." +msgstr "" + +msgid "" +"The fundamentals of a local-first system should enable real-time " +"collaboration when network is available, but shouldn't focus on it." +msgstr "" + +msgid "" +"On many places when discussing applications being offline, it is common for " +"me to find people saying that their application works \"even on a plane, " +"subway or elevator\". That is a reflection of when said developers have to " +"deal with networks being unavailable." +msgstr "" + +msgid "" +"When discussing \"working offline\", I'd rather keep this type of person in " +"mind, then the subset of people who are offline when on the elevator will " +"naturally be included." +msgstr "" + +msgid "On CRDTs and developer experience" +msgstr "" + +msgid "" +"When discussing developer experience, the authors bring up some questions to" +" be answered further, like:" +msgstr "" + +msgid "" +"For an app developer, how does the use of a CRDT-based data layer compare to" +" existing storage layers like a SQL database, a filesystem, or CoreData? Is " +"a distributed system harder to write software for?" +msgstr "" + +msgid "That is an easy one: yes." +msgstr "" + +msgid "" +"A distributed system *is* harder to write software for, being a distributed " +"system." +msgstr "" + +msgid "Conclusion" +msgstr "" + +msgid "" +"I liked a lot the article, as it took the \"offline-first\" philosophy and " +"ran with it." +msgstr "" + +msgid "" +"But I think the authors' view of adding CRDTs and things becoming local-" +"first is a bit too magical." +msgstr "" + +msgid "" +"It is a step forward, and given the number of times I've seen the paper " +"shared around I think there's a chance people will prefer saying \"local-" +"first\" in *lieu* of \"offline-first\" from now on." +msgstr "" + +msgid "" +"They give examples of artificial restrictions, like this artificial " +"restriction I've come up with:" +msgstr "" + +msgid "" +"Just as easily as I can come up with ways to intentionally restrict users, I" +" can do the same for unintentionally restrictions. A program can stop " +"working for a variety of reasons." +msgstr "" + +msgid "" +"If it stops working due do, say, data growth, what are the options? " +"Reverting to an earlier backup, and making it read-only? That isn't really a" +" \"Long Now\", but rather a \"Long Now as long as the software keeps working" +" as expected\"." +msgstr "" + +msgid "" +"A colleague has challenged my view, arguing that the software doesn't really" +" need to be free, as long as there is an specification of the file format. " +"This way if the software stops working, the format can still be processed by" +" other programs. But this doesn't apply in practice: if you have a document " +"that you write to, and software stops working, you still want to write to " +"the document. An external tool that navigates the content and shows it to " +"you won't allow you to keep writing, and when it does that tool is now " +"starting to re-implement the software." +msgstr "" + +msgid "" +"But this leaves out a big chunk of the world where internet connection is " +"intermittent, or only works every other day or only once a week, or stops " +"working when it rains, *etc*. For this audience, living without network " +"connectivity isn't such a discrete moment in time, but part of every day " +"life. I like the fact that the authors acknowledge that." +msgstr "" + +msgid "" +"Adding a large layer of data structures and algorithms will make it more " +"complex to write software for, naturally. And if trying to make this layer " +"transparent to the programmer, so they can pretend that layer doesn't exist " +"is a bad idea, as RPC frameworks have tried, and failed." +msgstr "" + +msgid "" +"See \"[A Note on Distributed " +"Computing](https://web.archive.org/web/20130116163535/http://labs.oracle.com/techrep/1994/smli_tr-94-29.pdf)\"" +" for a critique on RPC frameworks trying to make the network invisible, " +"which I think also applies in equivalence for making the CRDTs layer " +"invisible." +msgstr "" + +msgid "" +"This particular area is one that I have large interest on, and I wish to see" +" more being done on the \"local-first\" space." +msgstr "" + +msgid "" +"The point is: if the software isn't free, \"The Long Now\" isn't achievable " +"without a lot of wishful thinking. Maybe the authors were trying to be more " +"friendly towards business who don't like free software, but in doing so " +"they've proposed a contradiction by reconciling \"The Long Now\" with " +"proprietary software." +msgstr "" + +msgid "" +"It isn't the same as saying that any free software achieves that ideal, " +"either. The license can still be free, but the source code can become " +"unavailable due to cloud rot. Or maybe the build is undocumented, or the " +"build tools had specific configuration that one has to guess. A piece of " +"free software can still fail to achieve \"The Long Now\". Being free doesn't" +" guarantee it, just makes it possible." +msgstr "" + +#~ msgid "" +#~ "The point is: if the software isn't free/libre, \"The Long Now\" isn't " +#~ "achievable without a lot of wishful thinking. Maybe the authors were trying " +#~ "to be more friendly towards business who don't like libre software, but in " +#~ "doing so they've proposed a contradiction by reconciling \"The Long Now\" " +#~ "with proprietary software." +#~ msgstr "" + +#~ msgid "" +#~ "It isn't the same as saying that any free/libre software achieves that " +#~ "ideal, either. The license can still be free, but the source code can become" +#~ " unavailable due to cloud rot. Or maybe the build is undocumented, or the " +#~ "build tools had specific configuration that one has to guess. A piece of " +#~ "free/libre software can still fail to achieve \"The Long Now\". Being free " +#~ "doesn't guarantee it, just makes it possible." +#~ msgstr "" + +#~ msgid "They give examples of artificial restrictions, like this one:" +#~ msgstr "" + +#~ msgid "" +#~ "Just as easily as I can come up with ways to intentionally restrict users, " +#~ "just as easily I can do the same for unintentionally restricting users. A " +#~ "program can stop working for a variety of reasons." +#~ msgstr "" + +#~ msgid "" +#~ "If it stops working due do data growth, what are the options? Reverting to " +#~ "an earlier backup, and making it read-only? That isn't really a \"Long " +#~ "Now\", but rather a \"Long Now as long as the software keeps working as " +#~ "expected\"." +#~ msgstr "" + +#~ msgid "" +#~ "A colleague has challenged my view, arguing that the software doesn't really" +#~ " need to be free, as long as there is an specification of the file format. " +#~ "This way is the software stops working, the format can still be processed by" +#~ " other programs. But this doesn't apply in practice: if you have a document " +#~ "that you write to, and software stops working, you still want to write to " +#~ "the document. An external tool that navigates the content and shows it to " +#~ "you won't allow you to keep writing, and when it does that tool is now " +#~ "starting to re-implement the software." +#~ msgstr "" + +#~ msgid "" +#~ "But this leaves out a big chunk of the world where internet connection is " +#~ "intermittent, or only work every other day or only once a week, or stops " +#~ "working when it rains, *etc*. For this audience, living without network " +#~ "connectivity isn't such a discrete moment in time, but part of every day " +#~ "life. I like the fact that the authors acknowledge that." +#~ msgstr "" + +#~ msgid "" +#~ "Adding a large layer of data structures and algorithms will make it more " +#~ "complex to write software for, naturally. And if trying to make this layer " +#~ "transparent to the programmer, so they can pretend that layer doesn't exist " +#~ "is a bad idea, as RPC frameworks have tried, and failed. See \"[A Note on " +#~ "Distributed " +#~ "Computing](https://web.archive.org/web/20130116163535/http://labs.oracle.com/techrep/1994/smli_tr-94-29.pdf)\"" +#~ " for a critique on RPC frameworks trying to make the network invisible, " +#~ "which I think also applies in equivalence for making the CRDTs layer " +#~ "invisible." +#~ msgstr "" + +#~ msgid "" +#~ "It is a step forward, and given the number of times I've seen the paper " +#~ "shared around I think there's a chance people will prefer saying \"local-" +#~ "first\" in lieu of \"offline-first\" from now on." +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_articles/2021-01-26-ann-remembering-add-memory-to-dmenu-fzf-and-similar-tools.po b/po/fr/LC_MESSAGES/_articles/2021-01-26-ann-remembering-add-memory-to-dmenu-fzf-and-similar-tools.po new file mode 100644 index 0000000..f71c98f --- /dev/null +++ b/po/fr/LC_MESSAGES/_articles/2021-01-26-ann-remembering-add-memory-to-dmenu-fzf-and-similar-tools.po @@ -0,0 +1,302 @@ +# +msgid "" +msgstr "" + +msgid "title: \"ANN: remembering - Add memory to dmenu, fzf and similar tools\"" +msgstr "" + +msgid "date: 2021-01-26" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: ann-remembering-add-memory-to-dmenu-fzf-and-similar-tools" +msgstr "" + +msgid "Previous solution" +msgstr "" + +msgid "" +"I previously used [yeganesh](http://dmwit.com/yeganesh/) fill this gap, but " +"as I started to rely less on Emacs, I added fzf as my go-to tool for doing " +"fuzzy searching on the terminal. But I didn't like that fzf always showed " +"the same order of things, when I would only need 3 or 4 commonly used files." +msgstr "" + +msgid "" +"For those who don't know: yeganesh is a wrapper around dmenu that will " +"remember your most used programs and put them on the beginning of the list " +"of executables. This is very convenient for interactive prolonged use, as " +"with time the things you usually want are right at the very beginning." +msgstr "" + +msgid "" +"But now I had this thing, yeganesh, that solved this problem for dmenu, but " +"didn't for fzf." +msgstr "" + +msgid "" +"I initially considered patching yeganesh to support it, but I found it more " +"coupled to dmenu than I would desire. I'd rather have something that knows " +"nothing about dmenu, fzf or anything, but enhances tools like those in a " +"useful way." +msgstr "" + +msgid "Implementation" +msgstr "" + +msgid "" +"Other than being decoupled from dmenu, another improvement I though that " +"could be made on top of yeganesh is the programming language choice. Instead" +" of Haskell, I went with POSIX sh. Sticking to POSIX sh makes it require " +"less build-time dependencies. There aren't any, actually. Packaging is made " +"much easier due to that." +msgstr "" + +msgid "" +"The good thing is that the program itself is small enough ([119 " +"lines](https://euandreh.xyz/remembering.git/tree/remembering?id=v0.1.0) on " +"v0.1.0) that POSIX sh does the job just fine, combined with other POSIX " +"utilities such as " +"[getopts](http://www.opengroup.org/onlinepubs/9699919799/utilities/getopts.html)," +" [sort](http://www.opengroup.org/onlinepubs/9699919799/utilities/sort.html) " +"and " +"[awk](http://www.opengroup.org/onlinepubs/9699919799/utilities/awk.html)." +msgstr "" + +msgid "" +"The behaviour is: given a program that will read from STDIN and write a " +"single entry to STDOUT, `remembering` wraps that program, and rearranges " +"STDIN so that previous choices appear at the beginning." +msgstr "" + +msgid "Where you would do:" +msgstr "" + +msgid "" +"$ seq 5 | fzf\n" +"\n" +" 5\n" +" 4\n" +" 3\n" +" 2\n" +"> 1\n" +" 5/5\n" +">\n" +msgstr "" + +msgid "And every time get the same order of numbers, now you can write:" +msgstr "" + +msgid "" +"$ seq 5 | remembering -p seq-fzf -c fzf\n" +"\n" +" 5\n" +" 4\n" +" 3\n" +" 2\n" +"> 1\n" +" 5/5\n" +">\n" +msgstr "" + +msgid "" +"On the first run, everything is the same. If you picked 4 on the previous " +"example, the following run would be different:" +msgstr "" + +msgid "" +"$ seq 5 | remembering -p seq-fzf -c fzf\n" +"\n" +" 5\n" +" 3\n" +" 2\n" +" 1\n" +"> 4\n" +" 5/5\n" +">\n" +msgstr "" + +msgid "" +"As time passes, the list would adjust based on the frequency of your " +"choices." +msgstr "" + +msgid "" +"I aimed for reusability, so that I could wrap diverse commands with " +"`remembering` and it would be able to work. To accomplish that, a " +"\"profile\" (the `-p something` part) stores data about different runs " +"separately." +msgstr "" + +msgid "" +"I took the idea of building something small with few dependencies to other " +"places too:" +msgstr "" + +msgid "the tests are just more POSIX sh files;" +msgstr "" + +msgid "and a POSIX Makefile to `check` and `install`." +msgstr "" + +msgid "" +"I was aware of the value of sticking to coding to standards, but I had past " +"experience mostly with programming language standards, such as ECMAScript, " +"Common Lisp, Scheme, or with IndexedDB or DOM APIs. It felt good to " +"rediscover these nice POSIX tools, which makes me remember of a quote by " +"[Henry Spencer](https://en.wikipedia.org/wiki/Henry_Spencer#cite_note-3):" +msgstr "" + +msgid "Those who do not understand Unix are condemned to reinvent it, poorly." +msgstr "" + +msgid "Usage examples" +msgstr "" + +msgid "Here are some functions I wrote myself that you may find useful:" +msgstr "" + +msgid "Run a command with fzf on `$PWD`" +msgstr "" + +msgid "" +"f() {\n" +" profile=\"$f-shell-function(pwd | sed -e 's_/_-_g')\"\n" +" file=\"$(git ls-files | \\\n" +" remembering -p \"$profile\" \\\n" +" -c \"fzf --select-1 --exit -0 --query \\\"$2\\\" --preview 'cat {}'\")\"\n" +" if [ -n \"$file\" ]; then\n" +" # shellcheck disable=2068\n" +" history -s f $@\n" +" history -s \"$1\" \"$file\"\n" +" \"$1\" \"$file\"\n" +"fi\n" +"}\n" +msgstr "" + +msgid "" +"This way I can run `f vi` or `f vi config` at the root of a repository, and " +"the list of files will always appear on the most used order. Adding `pwd` to" +" the profile allows it to not mix data for different repositories." +msgstr "" + +msgid "Copy password to clipboard" +msgstr "" + +msgid "" +"choice=\"$(find \"$HOME/.password-store\" -type f | \\\n" +" grep -Ev '(.git|.gpg-id)' | \\\n" +" sed -e \"s|$HOME/.password-store/||\" -e 's/\\.gpg$//' | \\\n" +" remembering -p password-store \\\n" +" -c 'dmenu -l 20 -i')\"\n" +"\n" +"\n" +"if [ -n \"$choice\" ]; then\n" +" pass show \"$choice\" -c\n" +"fi\n" +msgstr "" + +msgid "" +"Adding the above to a file and binding it to a keyboard shortcut, I can " +"access the contents of my [password store](https://www.passwordstore.org/), " +"with the entries ordered by usage." +msgstr "" + +msgid "Replacing yeganesh" +msgstr "" + +msgid "Where I previously had:" +msgstr "" + +msgid "exe=$(yeganesh -x) && exec $exe\n" +msgstr "" + +msgid "Now I have:" +msgstr "" + +msgid "exe=$(dmenu_path | remembering -p dmenu-exec -c dmenu) && exec $exe\n" +msgstr "" + +msgid "This way, the executables appear on order of usage." +msgstr "" + +msgid "" +"If you don't have `dmenu_path`, you can get just the underlying `stest` tool" +" that looks at the executables available in your `$PATH`. Here's a juicy " +"one-liner to do it:" +msgstr "" + +msgid "" +"$ wget -O- https://dl.suckless.org/tools/dmenu-5.0.tar.gz | \\\n" +" tar Ozxf - dmenu-5.0/arg.h dmenu-5.0/stest.c | \\\n" +" sed 's|^#include \"arg.h\"$|// #include \"arg.h\"|' | \\\n" +" cc -xc - -o stest\n" +msgstr "" + +msgid "" +"With the `stest` utility you'll be able to list executables in your `$PATH` " +"and pipe them to dmenu or something else yourself:" +msgstr "" + +msgid "" +"$ (IFS=:; ./stest -flx $PATH;) | sort -u | remembering -p another-dmenu-exec" +" -c dmenu | sh\n" +msgstr "" + +msgid "In fact, the code for `dmenu_path` is almost just like that." +msgstr "" + +msgid "Conclusion" +msgstr "" + +msgid "Patches welcome!" +msgstr "" + +msgid "the manpages are written in troff directly;" +msgstr "" + +msgid "" +"For my personal use, I've [packaged](https://euandreh.xyz/package-.git" +"repository/) `remembering` for GNU Guix and Nix. Packaging it to any other " +"distribution should be trivial, or just downloading the tarball and running " +"`[sudo] make install`." +msgstr "" + +msgid "" +"Today I pushed v0.1.0 of [remembering](https://euandreh.xyz/remembering/), a" +" tool to enhance the interactive usability of menu-like tools, such as " +"[dmenu](https://tools.suckless.org/dmenu/) and " +"[fzf](https://github.com/junegunn/fzf)." +msgstr "" + +#~ msgid "" +#~ "Today I pushed v0.1.0 of [remembering](https://remembering.euandreh.xyz), a " +#~ "tool to enhance the interactive usability of menu-like tools, such as " +#~ "[dmenu](https://tools.suckless.org/dmenu/) and " +#~ "[fzf](https://github.com/junegunn/fzf)." +#~ msgstr "" + +#~ msgid "" +#~ "For my personal use, I've packaged `remembering` for [GNU " +#~ "Guix](https://euandreh.xyz/euandreh-guix-channel.git/) and " +#~ "[Nix](https://euandreh.xyz/dotfiles.git/tree/nixos/not-on-" +#~ "nixpkgs/remembering.nix?id=0831444f745cf908e940407c3e00a61f6152961f). " +#~ "Packaging it to any other distribution should be trivial, or just " +#~ "downloading the tarball and running `[sudo] make install`." +#~ msgstr "" + +#~ msgid "the man pages are written in troff directly;" +#~ msgstr "" + +#~ msgid "" +#~ "Today I pushed v0.1.0 of " +#~ "[remembering](https://euandreh.xyz/remembering.git/), a tool to enhance the " +#~ "interactive usability of menu-like tools, such as " +#~ "[dmenu](https://tools.suckless.org/dmenu/) and " +#~ "[fzf](https://github.com/junegunn/fzf)." +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_articles/2021-02-16-ann-fallible-fault-injection-library-for-stress-testing-failure-scenarios.po b/po/fr/LC_MESSAGES/_articles/2021-02-16-ann-fallible-fault-injection-library-for-stress-testing-failure-scenarios.po new file mode 100644 index 0000000..de3453b --- /dev/null +++ b/po/fr/LC_MESSAGES/_articles/2021-02-16-ann-fallible-fault-injection-library-for-stress-testing-failure-scenarios.po @@ -0,0 +1,383 @@ +# +msgid "" +msgstr "" + +msgid "" +"title: \"ANN: fallible - Fault injection library for stress-testing failure " +"scenarios\"" +msgstr "" + +msgid "date: 2021-02-16" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "" +"ref: ann-fallible-fault-injection-library-for-stress-testing-failure-" +"scenarios" +msgstr "" + +msgid "" +"Yesterday I pushed v0.1.0 of [fallible](https://fallible.euandreh.xyz), a " +"miniscule library for fault-injection and stress-testing C programs." +msgstr "" + +msgid "Existing solutions" +msgstr "" + +msgid "" +"Writing robust code can be challenging, and tools like static analyzers, " +"fuzzers and friends can help you get there with more certainty. As I would " +"try to improve some of my C code and make it more robust, in order to handle" +" system crashes, filled disks, out-of-memory and similar scenarios, I didn't" +" find existing tooling to help me get there as I expected to find. I " +"couldn't find existing tools to help me explicitly stress-test those failure" +" scenarios." +msgstr "" + +msgid "" +"Take the \"[Writing Robust " +"Programs](https://www.gnu.org/prep/standards/standards.html#Semantics)\" " +"section of the GNU Coding Standards:" +msgstr "" + +msgid "" +"Check every system call for an error return, unless you know you wish to " +"ignore errors. (...) Check every call to malloc or realloc to see if it " +"returned NULL." +msgstr "" + +msgid "" +"From a robustness standpoint, this is a reasonable stance: if you want to " +"have a robust program that knows how to fail when you're out of memory and " +"`malloc` returns `NULL`, than you ought to check every call to `malloc`." +msgstr "" + +msgid "Take a sample code snippet for clarity:" +msgstr "" + +msgid "" +"At a first glance, this code is unsafe: if any of the calls to `malloc` " +"returns `NULL`, `strcpy` will be given a `NULL` pointer." +msgstr "" + +msgid "My first instinct was to change this code to something like this:" +msgstr "" + +msgid "" +"@@ -1,7 +1,15 @@\n" +" void a_function() {\n" +" char *s1 = malloc(A_NUMBER);\n" +"+ if (!s1) {\n" +"+ fprintf(stderr, \"out of memory, exitting\\n\");\n" +"+ exit(1);\n" +"+ }\n" +" strcpy(s1, \"some string\");\n" +"\n" +" char *s2 = malloc(A_NUMBER);\n" +"+ if (!s2) {\n" +"+ fprintf(stderr, \"out of memory, exitting\\n\");\n" +"+ exit(1);\n" +"+ }\n" +" strcpy(s2, \"another string\");\n" +" }\n" +msgstr "" + +msgid "" +"As I later found out, there are at least 2 problems with this approach:" +msgstr "" + +msgid "" +"**it gives up instead of handling failures**: the actual handling goes a bit" +" beyond stopping. What about open file handles, in-memory caches, unflushed " +"bytes, etc.?" +msgstr "" + +msgid "" +"If you could force only the second call to `malloc` to fail, " +"[Valgrind](https://www.valgrind.org/) would correctly complain that the " +"program exitted with unfreed memory." +msgstr "" + +msgid "So the last change to make the best version of the above code is:" +msgstr "" + +msgid "" +"@@ -1,15 +1,14 @@\n" +"-void a_function() {\n" +"+bool a_function() {\n" +" char *s1 = malloc(A_NUMBER);\n" +" if (!s1) {\n" +"- fprintf(stderr, \"out of memory, exitting\\n\");\n" +"- exit(1);\n" +"+ return false;\n" +" }\n" +" strcpy(s1, \"some string\");\n" +"\n" +" char *s2 = malloc(A_NUMBER);\n" +" if (!s2) {\n" +"- fprintf(stderr, \"out of memory, exitting\\n\");\n" +"- exit(1);\n" +"+ free(s1);\n" +"+ return false;\n" +" }\n" +" strcpy(s2, \"another string\");\n" +" }\n" +msgstr "" + +msgid "" +"Instead of returning `void`, `a_function` now returns `bool` to indicate " +"whether an error ocurred during its execution. If `a_function` returned a " +"pointer to something, the return value could be `NULL`, or an `int` that " +"represents an error code." +msgstr "" + +msgid "" +"The code is now a) safe and b) failing gracefully, returning the control to " +"the caller to properly handle the error case." +msgstr "" + +msgid "" +"After seeing similar patterns on well designed APIs, I adopted this practice" +" for my own code, but was still left with manually verifying the correctness" +" and robustness of it." +msgstr "" + +msgid "" +"How could I add assertions around my code that would help me make sure the " +"`free(s1);` exists, before getting an error report? How do other people and " +"projects solve this?" +msgstr "" + +msgid "" +"From what I could see, either people a) hope for the best, b) write safe " +"code but don't strees-test it or c) write ad-hoc code to stress it." +msgstr "" + +msgid "" +"When searching for it online, an [interesting " +"thread](https://stackoverflow.com/questions/1711170/unit-testing-for-failed-" +"malloc) caught my atention: fail the call to `malloc` for each time it is " +"called, and when the same stacktrace appears again, allow it to proceed." +msgstr "" + +msgid "Implementation" +msgstr "" + +msgid "" +"A working implementation of that already exists: " +"[mallocfail](https://github.com/ralight/mallocfail). It uses `LD_PRELOAD` to" +" replace `malloc` at run-time, computes the SHA of the stacktrace and fails " +"once for each SHA." +msgstr "" + +msgid "" +"I initially envisioned and started implementing something very similar to " +"mallocfail. However I wanted it to go beyond out-of-memory scenarios, and " +"using `LD_PRELOAD` for every possible corner that could fail wasn't a good " +"idea on the long run." +msgstr "" + +msgid "" +"Also, mallocfail won't work together with tools such as Valgrind, who want " +"to do their own override of `malloc` with `LD_PRELOAD`." +msgstr "" + +msgid "" +"I instead went with less automatic things: starting with a " +"`fallible_should_fail(char *filename, int lineno)` function that fails once " +"for each `filename`+`lineno` combination, I created macro wrappers around " +"common functions such as `malloc`:" +msgstr "" + +msgid "" +"void *fallible_malloc(size_t size, const char *const filename, int lineno) {\n" +"#ifdef FALLIBLE\n" +" if (fallible_should_fail(filename, lineno)) {\n" +" return NULL;\n" +" }\n" +"#else\n" +" (void)filename;\n" +" (void)lineno;\n" +"#endif\n" +" return malloc(size);\n" +"}\n" +"\n" +"#define MALLOC(size) fallible_malloc(size, __FILE__, __LINE__)\n" +msgstr "" + +msgid "" +"With this definition, I could replace the calls to `malloc` with `MALLOC` " +"(or any other name that you want to `#define`):" +msgstr "" + +msgid "" +"--- 3.c\t2021-02-17 00:15:38.019706074 -0300\n" +"+++ 4.c\t2021-02-17 00:44:32.306885590 -0300\n" +"@@ -1,11 +1,11 @@\n" +" bool a_function() {\n" +"- char *s1 = malloc(A_NUMBER);\n" +"+ char *s1 = MALLOC(A_NUMBER);\n" +" if (!s1) {\n" +" return false;\n" +" }\n" +" strcpy(s1, \"some string\");\n" +"\n" +"- char *s2 = malloc(A_NUMBER);\n" +"+ char *s2 = MALLOC(A_NUMBER);\n" +" if (!s2) {\n" +" free(s1);\n" +" return false;\n" +msgstr "" + +msgid "" +"The price for such fine-grained control is that this approach requires more " +"manual work." +msgstr "" + +msgid "Usage examples" +msgstr "" + +msgid "`MALLOC` from the `README.md`" +msgstr "" + +msgid "" +"// leaky.c\n" +"#include <string.h>\n" +"#include <fallible_alloc.h>\n" +"\n" +"int main() {\n" +" char *aaa = MALLOC(100);\n" +" if (!aaa) {\n" +" return 1;\n" +" }\n" +" strcpy(aaa, \"a safe use of strcpy\");\n" +"\n" +" char *bbb = MALLOC(100);\n" +" if (!bbb) {\n" +" // free(aaa);\n" +" return 1;\n" +" }\n" +" strcpy(bbb, \"not unsafe, but aaa is leaking\");\n" +"\n" +" free(bbb);\n" +" free(aaa);\n" +" return 0;\n" +"}\n" +msgstr "" + +msgid "" +"Compile with `-DFALLIBLE` and run [`fallible-" +"check.1`](https:/fallible.euandreh.xyz/fallible-check.1.html):" +msgstr "" + +msgid "" +"$ c99 -DFALLIBLE -o leaky leaky.c -lfallible\n" +"$ fallible-check ./leaky\n" +"Valgrind failed when we did not expect it to:\n" +"(...suppressed output...)\n" +"# exit status is 1\n" +msgstr "" + +msgid "Conclusion" +msgstr "" + +msgid "" +"For my personal use, I'll [package](https://euandreh.xyz/package-.git" +"repository/) them for GNU Guix and Nix. Packaging it to any other " +"distribution should be trivial, or just downloading the tarball and running " +"`[sudo] make install`." +msgstr "" + +msgid "Patches welcome!" +msgstr "" + +msgid "" +"With this change, if the program gets compiled with the `-DFALLIBLE` flag " +"the fault-injection mechanism will run, and `MALLOC` will fail once for each" +" `filename`+`lineno` combination. When the flag is missing, `MALLOC` is a " +"very thin wrapper around `malloc`, which compilers could remove entirely, " +"and the `-lfallible` flags can be omitted." +msgstr "" + +msgid "" +"The actual code is just this single function, " +"[`fallible_should_fail`](https://euandreh.xyz/fallible.git/tree/src/fallible.c?id=v0.1.0#n16)," +" which ended-up taking only ~40 lines. In fact, there are more lines of " +"either Makefile (111), README.md (82) or troff (306) on this first version." +msgstr "" + +msgid "" +"void a_function() {\n" +" char *s1 = malloc(A_NUMBER);\n" +" strcpy(s1, \"some string\");\n" +"\n" +" char *s2 = malloc(A_NUMBER);\n" +" strcpy(s2, \"another string\");\n" +"}\n" +msgstr "" + +msgid "" +"**it doesn't compose**: this could arguably work if `a_function` was `main`." +" But if `a_function` lives inside a library, an `exit(1);` is a inelegant " +"way of handling failures, and will catch the top-level `main` consuming the " +"library by surprise;" +msgstr "" + +msgid "" +"The most proeminent case of c) is SQLite: it has a few wrappers around the " +"familiar `malloc` to do fault injection, check for memory limits, add " +"warnings, create shim layers for other environments, etc. All of that, " +"however, is tightly couple with SQLite itself, and couldn't be easily pulled" +" off for using somewhere else." +msgstr "" + +msgid "" +"This applies not only to `malloc` or other `stdlib.h` functions. If " +"`a_function` is important or relevant, I could add a wrapper around it too, " +"that checks if `fallible_should_fail` to exercise if its callers are also " +"doing the proper clean-up." +msgstr "" + +#~ msgid "" +#~ "void a_function() {\n" +#~ " char *s1 = malloc(A_NUMBER);\n" +#~ " strcpy(s1, \"some string\");\n" +#~ "\n" +#~ " char *s2 = malloc(A_NUMBER);\n" +#~ " strcpy(s2, \"another string\");\n" +#~ "}\n" +#~ msgstr "" + +#~ msgid "" +#~ "**it doesn't compose**: this could arguably work if `a_function` was `main`." +#~ " But if `a_function` lives inside a library, an `exit(1)` is a inelegant way" +#~ " of handling failures, and will catch the top-level `main` consuming the " +#~ "library by surprise;" +#~ msgstr "" + +#~ msgid "" +#~ "The most proeminent one is SQLite: it has a few wrapeers around the familiar" +#~ " `malloc` to do fault injection, check for memory limits, add warnings, " +#~ "create shim layers for other environments, etc. All of that, however, is " +#~ "tightly couple with SQLite itself, and couldn't be easily pulled off for " +#~ "using somewhere else." +#~ msgstr "" + +#~ msgid "" +#~ "This applies not only to `malloc` of other system calls. If `a_function` is " +#~ "important or relevant, I could add a wrapper around it too, that checks if " +#~ "`fallible_should_fail` to exercise if its callers are also doing the proper " +#~ "clean-up." +#~ msgstr "" + +#~ msgid "" +#~ "With this change, if the program gets compiled with the `-DFALLIBLE` flag " +#~ "the fault-injection mechanism will run, and `MALLOC` will fail once for each" +#~ " `filename`+`lineno` combination. When the flag is missing, `MALLOC` is a " +#~ "very thin wrapper around `malloc`, which compilers could remove entirely." +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_articles/2021-02-17-ann-fallible-fault-injection-library-for-stress-testing-failure-scenarios.po b/po/fr/LC_MESSAGES/_articles/2021-02-17-ann-fallible-fault-injection-library-for-stress-testing-failure-scenarios.po new file mode 100644 index 0000000..a4f1ed8 --- /dev/null +++ b/po/fr/LC_MESSAGES/_articles/2021-02-17-ann-fallible-fault-injection-library-for-stress-testing-failure-scenarios.po @@ -0,0 +1,386 @@ +# +msgid "" +msgstr "" + +msgid "" +"title: \"ANN: fallible - Fault injection library for stress-testing failure " +"scenarios\"" +msgstr "" + +msgid "date: 2021-02-17" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "" +"ref: ann-fallible-fault-injection-library-for-stress-testing-failure-" +"scenarios" +msgstr "" + +msgid "Existing solutions" +msgstr "" + +msgid "" +"Writing robust code can be challenging, and tools like static analyzers, " +"fuzzers and friends can help you get there with more certainty. As I would " +"try to improve some of my C code and make it more robust, in order to handle" +" system crashes, filled disks, out-of-memory and similar scenarios, I didn't" +" find existing tooling to help me get there as I expected to find. I " +"couldn't find existing tools to help me explicitly stress-test those failure" +" scenarios." +msgstr "" + +msgid "" +"Take the \"[Writing Robust " +"Programs](https://www.gnu.org/prep/standards/standards.html#Semantics)\" " +"section of the GNU Coding Standards:" +msgstr "" + +msgid "" +"Check every system call for an error return, unless you know you wish to " +"ignore errors. (...) Check every call to malloc or realloc to see if it " +"returned NULL." +msgstr "" + +msgid "" +"From a robustness standpoint, this is a reasonable stance: if you want to " +"have a robust program that knows how to fail when you're out of memory and " +"`malloc` returns `NULL`, than you ought to check every call to `malloc`." +msgstr "" + +msgid "Take a sample code snippet for clarity:" +msgstr "" + +msgid "" +"void a_function() {\n" +" char *s1 = malloc(A_NUMBER);\n" +" strcpy(s1, \"some string\");\n" +"\n" +" char *s2 = malloc(A_NUMBER);\n" +" strcpy(s2, \"another string\");\n" +"}\n" +msgstr "" + +msgid "" +"At a first glance, this code is unsafe: if any of the calls to `malloc` " +"returns `NULL`, `strcpy` will be given a `NULL` pointer." +msgstr "" + +msgid "My first instinct was to change this code to something like this:" +msgstr "" + +msgid "" +"@@ -1,7 +1,15 @@\n" +" void a_function() {\n" +" char *s1 = malloc(A_NUMBER);\n" +"+ if (!s1) {\n" +"+ fprintf(stderr, \"out of memory, exitting\\n\");\n" +"+ exit(1);\n" +"+ }\n" +" strcpy(s1, \"some string\");\n" +"\n" +" char *s2 = malloc(A_NUMBER);\n" +"+ if (!s2) {\n" +"+ fprintf(stderr, \"out of memory, exitting\\n\");\n" +"+ exit(1);\n" +"+ }\n" +" strcpy(s2, \"another string\");\n" +" }\n" +msgstr "" + +msgid "" +"As I later found out, there are at least 2 problems with this approach:" +msgstr "" + +msgid "" +"**it doesn't compose**: this could arguably work if `a_function` was `main`." +" But if `a_function` lives inside a library, an `exit(1);` is a inelegant " +"way of handling failures, and will catch the top-level `main` consuming the " +"library by surprise;" +msgstr "" + +msgid "" +"**it gives up instead of handling failures**: the actual handling goes a bit" +" beyond stopping. What about open file handles, in-memory caches, unflushed " +"bytes, etc.?" +msgstr "" + +msgid "" +"If you could force only the second call to `malloc` to fail, " +"[Valgrind](https://www.valgrind.org/) would correctly complain that the " +"program exitted with unfreed memory." +msgstr "" + +msgid "So the last change to make the best version of the above code is:" +msgstr "" + +msgid "" +"@@ -1,15 +1,14 @@\n" +"-void a_function() {\n" +"+bool a_function() {\n" +" char *s1 = malloc(A_NUMBER);\n" +" if (!s1) {\n" +"- fprintf(stderr, \"out of memory, exitting\\n\");\n" +"- exit(1);\n" +"+ return false;\n" +" }\n" +" strcpy(s1, \"some string\");\n" +"\n" +" char *s2 = malloc(A_NUMBER);\n" +" if (!s2) {\n" +"- fprintf(stderr, \"out of memory, exitting\\n\");\n" +"- exit(1);\n" +"+ free(s1);\n" +"+ return false;\n" +" }\n" +" strcpy(s2, \"another string\");\n" +" }\n" +msgstr "" + +msgid "" +"Instead of returning `void`, `a_function` now returns `bool` to indicate " +"whether an error ocurred during its execution. If `a_function` returned a " +"pointer to something, the return value could be `NULL`, or an `int` that " +"represents an error code." +msgstr "" + +msgid "" +"The code is now a) safe and b) failing gracefully, returning the control to " +"the caller to properly handle the error case." +msgstr "" + +msgid "" +"After seeing similar patterns on well designed APIs, I adopted this practice" +" for my own code, but was still left with manually verifying the correctness" +" and robustness of it." +msgstr "" + +msgid "" +"How could I add assertions around my code that would help me make sure the " +"`free(s1);` exists, before getting an error report? How do other people and " +"projects solve this?" +msgstr "" + +msgid "" +"From what I could see, either people a) hope for the best, b) write safe " +"code but don't strees-test it or c) write ad-hoc code to stress it." +msgstr "" + +msgid "" +"The most proeminent case of c) is SQLite: it has a few wrappers around the " +"familiar `malloc` to do fault injection, check for memory limits, add " +"warnings, create shim layers for other environments, etc. All of that, " +"however, is tightly couple with SQLite itself, and couldn't be easily pulled" +" off for using somewhere else." +msgstr "" + +msgid "" +"When searching for it online, an [interesting " +"thread](https://stackoverflow.com/questions/1711170/unit-testing-for-failed-" +"malloc) caught my atention: fail the call to `malloc` for each time it is " +"called, and when the same stacktrace appears again, allow it to proceed." +msgstr "" + +msgid "Implementation" +msgstr "" + +msgid "" +"A working implementation of that already exists: " +"[mallocfail](https://github.com/ralight/mallocfail). It uses `LD_PRELOAD` to" +" replace `malloc` at run-time, computes the SHA of the stacktrace and fails " +"once for each SHA." +msgstr "" + +msgid "" +"I initially envisioned and started implementing something very similar to " +"mallocfail. However I wanted it to go beyond out-of-memory scenarios, and " +"using `LD_PRELOAD` for every possible corner that could fail wasn't a good " +"idea on the long run." +msgstr "" + +msgid "" +"Also, mallocfail won't work together with tools such as Valgrind, who want " +"to do their own override of `malloc` with `LD_PRELOAD`." +msgstr "" + +msgid "" +"I instead went with less automatic things: starting with a " +"`fallible_should_fail(char *filename, int lineno)` function that fails once " +"for each `filename`+`lineno` combination, I created macro wrappers around " +"common functions such as `malloc`:" +msgstr "" + +msgid "" +"void *fallible_malloc(size_t size, const char *const filename, int lineno) {\n" +"#ifdef FALLIBLE\n" +" if (fallible_should_fail(filename, lineno)) {\n" +" return NULL;\n" +" }\n" +"#else\n" +" (void)filename;\n" +" (void)lineno;\n" +"#endif\n" +" return malloc(size);\n" +"}\n" +"\n" +"#define MALLOC(size) fallible_malloc(size, __FILE__, __LINE__)\n" +msgstr "" + +msgid "" +"With this definition, I could replace the calls to `malloc` with `MALLOC` " +"(or any other name that you want to `#define`):" +msgstr "" + +msgid "" +"With this change, if the program gets compiled with the `-DFALLIBLE` flag " +"the fault-injection mechanism will run, and `MALLOC` will fail once for each" +" `filename`+`lineno` combination. When the flag is missing, `MALLOC` is a " +"very thin wrapper around `malloc`, which compilers could remove entirely, " +"and the `-lfallible` flags can be omitted." +msgstr "" + +msgid "" +"This applies not only to `malloc` or other `stdlib.h` functions. If " +"`a_function` is important or relevant, I could add a wrapper around it too, " +"that checks if `fallible_should_fail` to exercise if its callers are also " +"doing the proper clean-up." +msgstr "" + +msgid "" +"The actual code is just this single function, " +"[`fallible_should_fail`](https://euandreh.xyz/fallible.git/tree/src/fallible.c?id=v0.1.0#n16)," +" which ended-up taking only ~40 lines. In fact, there are more lines of " +"either Makefile (111), README.md (82) or troff (306) on this first version." +msgstr "" + +msgid "" +"The price for such fine-grained control is that this approach requires more " +"manual work." +msgstr "" + +msgid "Usage examples" +msgstr "" + +msgid "`MALLOC` from the `README.md`" +msgstr "" + +msgid "" +"// leaky.c\n" +"#include <string.h>\n" +"#include <fallible_alloc.h>\n" +"\n" +"int main() {\n" +" char *aaa = MALLOC(100);\n" +" if (!aaa) {\n" +" return 1;\n" +" }\n" +" strcpy(aaa, \"a safe use of strcpy\");\n" +"\n" +" char *bbb = MALLOC(100);\n" +" if (!bbb) {\n" +" // free(aaa);\n" +" return 1;\n" +" }\n" +" strcpy(bbb, \"not unsafe, but aaa is leaking\");\n" +"\n" +" free(bbb);\n" +" free(aaa);\n" +" return 0;\n" +"}\n" +msgstr "" + +msgid "" +"$ c99 -DFALLIBLE -o leaky leaky.c -lfallible\n" +"$ fallible-check ./leaky\n" +"Valgrind failed when we did not expect it to:\n" +"(...suppressed output...)\n" +"# exit status is 1\n" +msgstr "" + +msgid "Conclusion" +msgstr "" + +msgid "" +"For my personal use, I'll [package](https://euandreh.xyz/package-.git" +"repository/) them for GNU Guix and Nix. Packaging it to any other " +"distribution should be trivial, or just downloading the tarball and running " +"`[sudo] make install`." +msgstr "" + +msgid "Patches welcome!" +msgstr "" + +msgid "" +"--- 3.c 2021-02-17 00:15:38.019706074 -0300\n" +"+++ 4.c 2021-02-17 00:44:32.306885590 -0300\n" +"@@ -1,11 +1,11 @@\n" +" bool a_function() {\n" +"- char *s1 = malloc(A_NUMBER);\n" +"+ char *s1 = MALLOC(A_NUMBER);\n" +" if (!s1) {\n" +" return false;\n" +" }\n" +" strcpy(s1, \"some string\");\n" +"\n" +"- char *s2 = malloc(A_NUMBER);\n" +"+ char *s2 = MALLOC(A_NUMBER);\n" +" if (!s2) {\n" +" free(s1);\n" +" return false;\n" +msgstr "" + +msgid "" +"Yesterday I pushed v0.1.0 of [fallible](https://euandreh.xyz/fallible/), a " +"miniscule library for fault-injection and stress-testing C programs." +msgstr "" + +msgid "" +"Compile with `-DFALLIBLE` and run [`fallible-" +"check.1`](https://euandreh.xyz/fallible/fallible-check.1.html):" +msgstr "" + +msgid "updated_at: 2021-02-17" +msgstr "" + +msgid "*EDIT*" +msgstr "" + +msgid "" +"2021-06-12: As of [0.3.0](https://euandreh.xyz/fallible/CHANGELOG.html) (and" +" beyond), the macro interface improved and is a bit different from what is " +"presented in this article. If you're interested, I encourage you to take a " +"look at it." +msgstr "" + +#~ msgid "" +#~ "Yesterday I pushed v0.1.0 of [fallible](https://fallible.euandreh.xyz), a " +#~ "miniscule library for fault-injection and stress-testing C programs." +#~ msgstr "" + +#~ msgid "" +#~ "Compile with `-DFALLIBLE` and run [`fallible-" +#~ "check.1`](https:/fallible.euandreh.xyz/fallible-check.1.html):" +#~ msgstr "" + +#~ msgid "" +#~ "--- 3.c\t2021-02-17 00:15:38.019706074 -0300\n" +#~ "+++ 4.c\t2021-02-17 00:44:32.306885590 -0300\n" +#~ "@@ -1,11 +1,11 @@\n" +#~ " bool a_function() {\n" +#~ "- char *s1 = malloc(A_NUMBER);\n" +#~ "+ char *s1 = MALLOC(A_NUMBER);\n" +#~ " if (!s1) {\n" +#~ " return false;\n" +#~ " }\n" +#~ " strcpy(s1, \"some string\");\n" +#~ "\n" +#~ "- char *s2 = malloc(A_NUMBER);\n" +#~ "+ char *s2 = MALLOC(A_NUMBER);\n" +#~ " if (!s2) {\n" +#~ " free(s1);\n" +#~ " return false;\n" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_articles/2021-04-29-a-relational-model-of-data-for-large-shared-data-banks-article-review.po b/po/fr/LC_MESSAGES/_articles/2021-04-29-a-relational-model-of-data-for-large-shared-data-banks-article-review.po new file mode 100644 index 0000000..6a98ab5 --- /dev/null +++ b/po/fr/LC_MESSAGES/_articles/2021-04-29-a-relational-model-of-data-for-large-shared-data-banks-article-review.po @@ -0,0 +1,211 @@ +# +msgid "" +msgstr "" + +msgid "" +"title: A Relational Model of Data for Large Shared Data Banks - article-" +"review" +msgstr "" + +msgid "date: 2021-04-29" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "" +"ref: a-relational-model-of-data-for-large-shared-data-banks-article-review" +msgstr "" + +msgid "" +"This is a review of the article \"[A Relational Model of Data for Large " +"Shared Data Banks](https://www.seas.upenn.edu/~zives/03f/cis550/codd.pdf)\"," +" by E. F. Codd." +msgstr "" + +msgid "Data Independence" +msgstr "" + +msgid "" +"Codd brings the idea of *data independence* as a better approach to use on " +"databases. This is contrast with the existing approaches, namely " +"hierarquical (tree-based) and network-based." +msgstr "" + +msgid "" +"His main argument is that queries in applications shouldn't depende and be " +"coupled with how the data is represented internally by the database system. " +"This key idea is very powerful, and something that we strive for in many " +"other places: decoupling the interface from the implementation." +msgstr "" + +msgid "" +"If the database system has this separation, it can kep the querying " +"interface stable, while having the freedom to change its internal " +"representation at will, for better performance, less storage, etc." +msgstr "" + +msgid "" +"This is true for most modern database systems. They can change from B-Trees " +"with leafs containing pointers to data, to B-Trees with leafs containing the" +" raw data , to hash tables. All that without changing the query interface, " +"only its performance." +msgstr "" + +msgid "" +"Codd mentions that, from an information representation standpoint, any index" +" is a duplication, but useful for perfomance." +msgstr "" + +msgid "" +"This data independence also impacts ordering (a *relation* doesn't rely on " +"the insertion order)." +msgstr "" + +msgid "Duplicates" +msgstr "" + +msgid "" +"His definition of relational data is a bit differente from most modern " +"database systems, namely **no duplicate rows**." +msgstr "" + +msgid "" +"I couldn't find a reason behind this restriction, though. For practical " +"purposes, I find it useful to have it." +msgstr "" + +msgid "Relational Data" +msgstr "" + +msgid "" +"In the article, Codd doesn't try to define a language, and today's most " +"popular one is SQL." +msgstr "" + +msgid "" +"However, there is no restriction that says that \"SQL database\" and " +"\"relational database\" are synonyms. One could have a relational database " +"without using SQL at all, and it would still be a relational one." +msgstr "" + +msgid "" +"The main one that I have in mind, and the reason that led me to reading this" +" paper in the first place, is Datomic." +msgstr "" + +msgid "" +"Is uses an [edn]-based representation for datalog queries[^edn-queries], and" +" a particular schema used to represent data." +msgstr "" + +msgid "" +"Even though it looks very weird when coming from SQL, I'd argue that it " +"ticks all the boxes (except for \"no duplicates\") that defines a relational" +" database, since building relations and applying operations on them is " +"possible." +msgstr "" + +msgid "" +"Compare and contrast a contrived example of possible representations of SQL " +"and datalog of the same data:" +msgstr "" + +msgid "" +"-- create schema\n" +"CREATE TABLE people (\n" +" id UUID PRIMARY KEY,\n" +" name TEXT NOT NULL,\n" +" manager_id UUID,\n" +" FOREIGN KEY (manager_id) REFERENCES people (id)\n" +");\n" +"\n" +"-- insert data\n" +"INSERT INTO people (id, name, manager_id) VALUES\n" +" (\"d3f29960-ccf0-44e4-be66-1a1544677441\", \"Foo\", \"076356f4-1a0e-451c-b9c6-a6f56feec941\"),\n" +" (\"076356f4-1a0e-451c-b9c6-a6f56feec941\", \"Bar\");\n" +"\n" +"-- query data, make a relation\n" +"\n" +"SELECT employees.name AS 'employee-name',\n" +" managers.name AS 'manager-name'\n" +"FROM people employees\n" +"INNER JOIN people managers ON employees.manager_id = managers.id;\n" +msgstr "" + +msgid "{% raw %}" +msgstr "" + +msgid "" +";; create schema\n" +"#{ {:db/ident :person/id\n" +" :db/valueType :db.type/uuid\n" +" :db/cardinality :db.cardinality/one\n" +" :db/unique :db.unique/value}\n" +" {:db/ident :person/name\n" +" :db/valueType :db.type/string\n" +" :db/cardinality :db.cardinality/one}\n" +" {:db/ident :person/manager\n" +" :db/valueType :db.type/ref\n" +" :db/cardinality :db.cardinality/one}}\n" +"\n" +";; insert data\n" +"#{ {:person/id #uuid \"d3f29960-ccf0-44e4-be66-1a1544677441\"\n" +" :person/name \"Foo\"\n" +" :person/manager [:person/id #uuid \"076356f4-1a0e-451c-b9c6-a6f56feec941\"]}\n" +" {:person/id #uuid \"076356f4-1a0e-451c-b9c6-a6f56feec941\"\n" +" :person/name \"Bar\"}}\n" +"\n" +";; query data, make a relation\n" +"{:find [?employee-name ?manager-name]\n" +" :where [[?person :person/name ?employee-name]\n" +" [?person :person/manager ?manager]\n" +" [?manager :person/name ?manager-name]]}\n" +msgstr "" + +msgid "{% endraw %}" +msgstr "" + +msgid "" +"(forgive any errors on the above SQL and datalog code, I didn't run them to " +"check. Patches welcome!)" +msgstr "" + +msgid "" +"This employee example comes from the paper, and both SQL and datalog " +"representations match the paper definition of \"relational\"." +msgstr "" + +msgid "" +"Both \"Foo\" and \"Bar\" are employees, and the data is normalized. SQL " +"represents data as tables, and Datomic as datoms, but relations could be " +"derived from both, which we could view as:" +msgstr "" + +msgid "" +"employee_name | manager_name\n" +"----------------------------\n" +"\"Foo\" | \"Bar\"\n" +msgstr "" + +msgid "" +"[^edn-queries]: You can think of it as JSON, but with a Clojure taste. " +"[edn]: https://github.com/edn-format/edn" +msgstr "" + +msgid "Conclusion" +msgstr "" + +msgid "" +"The article also talks about operators, consistency and normalization, which" +" are now so widespread and well-known that it feels a bit weird seeing " +"someone advocating for it." +msgstr "" + +msgid "" +"I also stablish that `relational != SQL`, and other databases such as " +"Datomic are also relational, following Codd's original definition." +msgstr "" diff --git a/po/fr/LC_MESSAGES/_pastebins/2016-04-05-rpn-macro-setup.po b/po/fr/LC_MESSAGES/_pastebins/2016-04-05-rpn-macro-setup.po new file mode 100644 index 0000000..4a234ad --- /dev/null +++ b/po/fr/LC_MESSAGES/_pastebins/2016-04-05-rpn-macro-setup.po @@ -0,0 +1,53 @@ +# +msgid "" +msgstr "" + +msgid "" +"(defmacro rpn (body)\n" +" (rpn-expander body))\n" +"\n" +"(defun rpn-expander (body)\n" +" (mapcar (lambda (x)\n" +" (if (listp x)\n" +" (rpn-expander x)\n" +" x))\n" +" (reverse body)))\n" +"\n" +"(rpn ((2 1 +) 2 *))\n" +"; => 6\n" +"\n" +"#|\n" +"Just a quick stub.\n" +"\n" +"One could easily improve #'RPN-EXPANDER in order to better suit one's needs.\n" +"|#\n" +msgstr "" + +msgid "title: RPN macro setup" +msgstr "" + +msgid "date: 2016-04-05" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: rpn-macro-setup" +msgstr "" + +#~ msgid "" +#~ "title: RPN macro setup\n" +#~ "date: 2016-04-05\n" +#~ "layout: post\n" +#~ "lang: en" +#~ msgstr "" + +#~ msgid "" +#~ "title: RPN macro setup\n" +#~ "date: 2016-04-05\n" +#~ "layout: pastebin\n" +#~ "lang: en" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_pastebins/2018-07-11-nix-pinning.po b/po/fr/LC_MESSAGES/_pastebins/2018-07-11-nix-pinning.po new file mode 100644 index 0000000..72220c2 --- /dev/null +++ b/po/fr/LC_MESSAGES/_pastebins/2018-07-11-nix-pinning.po @@ -0,0 +1,54 @@ +# +msgid "" +msgstr "" + +msgid "" +"let\n" +" # Pin the nixpkgs version\n" +" stdenv = pkgs.stdenv;\n" +" pkgsOriginal = import <nixpkgs> {};\n" +" pkgsSrc = pkgsOriginal.fetchzip {\n" +" url = \"https://github.com/NixOS/nixpkgs/archive/18.03.zip\";\n" +" sha256 = \"0hk4y2vkgm1qadpsm4b0q1vxq889jhxzjx3ragybrlwwg54mzp4f\";\n" +" };\n" +"\n" +" pkgs = import (pkgsSrc) {};\n" +"\n" +" buildNodeJS = pkgs.callPackage <nixpkgs/pkgs/development/web/nodejs/nodejs.nix> {};\n" +"\n" +"in rec {\n" +" nodeFromNVMRC = buildNodeJS {\n" +" version = \"8.7.0\";\n" +" sha256 = \"16mml3cwjnq7yf9yd67d2dybav3nvbnk89fkixs1wz7fd26d05ss\";\n" +" patches = [];\n" +" };\n" +"}\n" +msgstr "" + +msgid "title: Nix pinning" +msgstr "" + +msgid "date: 2018-07-11" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "eu_categories: nix" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "ref: nix-pinning" +msgstr "" + +#~ msgid "layout: pastebin" +#~ msgstr "" + +#~ msgid "" +#~ "title: Nix pinning\n" +#~ "date: 2018-07-11\n" +#~ "layout: pastebin\n" +#~ "lang: en" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_pastebins/2018-07-13-gnu-guix-systemd-daemon-for-nixos.po b/po/fr/LC_MESSAGES/_pastebins/2018-07-13-gnu-guix-systemd-daemon-for-nixos.po new file mode 100644 index 0000000..6a20af4 --- /dev/null +++ b/po/fr/LC_MESSAGES/_pastebins/2018-07-13-gnu-guix-systemd-daemon-for-nixos.po @@ -0,0 +1,49 @@ +# +msgid "" +msgstr "" + +msgid "" +" # Derived from Guix guix-daemon.service.in\n" +" # https://git.savannah.gnu.org/cgit/guix.git/tree/etc/guix-daemon.service.in?id=00c86a888488b16ce30634d3a3a9d871ed6734a2\n" +" systemd.services.guix-daemon = {\n" +" enable = true;\n" +" description = \"Build daemon for GNU Guix\";\n" +" serviceConfig = {\n" +" ExecStart = \"/var/guix/profiles/per-user/root/guix-profile/bin/guix-daemon --build-users-group=guixbuild\";\n" +" Environment=\"GUIX_LOCPATH=/root/.guix-profile/lib/locale\";\n" +" RemainAfterExit=\"yes\";\n" +" StandardOutput=\"syslog\";\n" +" StandardError=\"syslog\";\n" +" TaskMax= 8192;\n" +" };\n" +" wantedBy = [ \"multi-user.target\" ];\n" +" };\n" +msgstr "" + +msgid "title: GNU Guix systemd daemon for NixOS" +msgstr "" + +msgid "date: 2018-07-13" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "eu_categories: nix,guix" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "ref: gnu-guix-systemd-daemon-for-nixos" +msgstr "" + +#~ msgid "layout: pastebin" +#~ msgstr "" + +#~ msgid "" +#~ "title: GNU Guix systemd daemon for NixOS\n" +#~ "date: 2018-07-13\n" +#~ "layout: pastebin\n" +#~ "lang: en" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_pastebins/2018-07-13-guix-builder-user-creation-commands.po b/po/fr/LC_MESSAGES/_pastebins/2018-07-13-guix-builder-user-creation-commands.po new file mode 100644 index 0000000..d3b709b --- /dev/null +++ b/po/fr/LC_MESSAGES/_pastebins/2018-07-13-guix-builder-user-creation-commands.po @@ -0,0 +1,42 @@ +# +msgid "" +msgstr "" + +msgid "" +"groupadd --system guixbuild\n" +"for i in `seq -w 1 10`;\n" +"do\n" +" useradd -g guixbuild -G guixbuild \\\n" +" -d /var/empty -s `which nologin` \\\n" +" -c \"Guix build user $i\" --system \\\n" +" guixbuilder$i;\n" +"done\n" +msgstr "" + +msgid "title: Guix builder user creation commands" +msgstr "" + +msgid "date: 2018-07-13" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "eu_categories: guix" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "ref: guix-builder-user-creation-commands" +msgstr "" + +#~ msgid "layout: pastebin" +#~ msgstr "" + +#~ msgid "" +#~ "title: Guix builder user creation commands\n" +#~ "date: 2018-07-13\n" +#~ "layout: pastebin\n" +#~ "lang: en" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_pastebins/2018-07-13-guix-users-in-nixos-system-configuration.po b/po/fr/LC_MESSAGES/_pastebins/2018-07-13-guix-users-in-nixos-system-configuration.po new file mode 100644 index 0000000..2c14d50 --- /dev/null +++ b/po/fr/LC_MESSAGES/_pastebins/2018-07-13-guix-users-in-nixos-system-configuration.po @@ -0,0 +1,69 @@ +# +msgid "" +msgstr "" + +msgid "" +" users = {\n" +" mutableUsers = false;\n" +"\n" +" extraUsers =\n" +" let\n" +" andrehUser = {\n" +" andreh = {\n" +" # my custom user config\n" +" };\n" +" };\n" +" # From the Guix manual:\n" +" # https://www.gnu.org/software/guix/manual/en/html_node/Build-Environment-Setup.html#Build-Environment-Setup\n" +" buildUser = (i:\n" +" {\n" +" \"guixbuilder${i}\" = { # guixbuilder$i\n" +" group = \"guixbuild\"; # -g guixbuild\n" +" extraGroups = [\"guixbuild\"]; # -G guixbuild\n" +" home = \"/var/empty\"; # -d /var/empty\n" +" shell = pkgs.nologin; # -s `which nologin`\n" +" description = \"Guix build user ${i}\"; # -c \"Guix buid user $i\"\n" +" isSystemUser = true; # --system\n" +" };\n" +" }\n" +" );\n" +" in\n" +" # merge all users\n" +" pkgs.lib.fold (str: acc: acc // buildUser str)\n" +" andrehUser\n" +" # for i in `seq -w 1 10`\n" +" (map (pkgs.lib.fixedWidthNumber 2) (builtins.genList (n: n+1) 10));\n" +"\n" +" extraGroups.guixbuild = {\n" +" name = \"guixbuild\";\n" +" };\n" +" };\n" +msgstr "" + +msgid "title: Guix users in NixOS system configuration" +msgstr "" + +msgid "date: 2018-07-13" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "eu_categories: nix,guix" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "ref: guix-users-in-nixos-system-configuration" +msgstr "" + +#~ msgid "layout: pastebin" +#~ msgstr "" + +#~ msgid "" +#~ "title: Guix users in NixOS system configuration\n" +#~ "date: 2018-07-13\n" +#~ "layout: pastebin\n" +#~ "lang: en" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_pastebins/2018-07-13-nix-string-padding.po b/po/fr/LC_MESSAGES/_pastebins/2018-07-13-nix-string-padding.po new file mode 100644 index 0000000..cfc4dc9 --- /dev/null +++ b/po/fr/LC_MESSAGES/_pastebins/2018-07-13-nix-string-padding.po @@ -0,0 +1,34 @@ +# +msgid "" +msgstr "" + +msgid "padString = (n: if n < 10 then \"0\" + toString n else toString n)\n" +msgstr "" + +msgid "title: Nix string padding" +msgstr "" + +msgid "date: 2018-07-13" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "eu_categories: nix" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "ref: nix-string-padding" +msgstr "" + +#~ msgid "layout: pastebin" +#~ msgstr "" + +#~ msgid "" +#~ "title: Nix string padding\n" +#~ "date: 2018-07-13\n" +#~ "layout: pastebin\n" +#~ "lang: en" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_pastebins/2018-07-25-nix-exps.po b/po/fr/LC_MESSAGES/_pastebins/2018-07-25-nix-exps.po new file mode 100644 index 0000000..6be9fcc --- /dev/null +++ b/po/fr/LC_MESSAGES/_pastebins/2018-07-25-nix-exps.po @@ -0,0 +1,77 @@ +# +msgid "" +msgstr "" + +msgid "" +"let\n" +" pkgsOriginal = import <nixpkgs> {};\n" +" pkgsSrc = pkgsOriginal.fetchzip {\n" +" url = \"https://github.com/NixOS/nixpkgs/archive/18.03.zip\";\n" +" sha256 = \"0hk4y2vkgm1qadpsm4b0q1vxq889jhxzjx3ragybrlwwg54mzp4f\";\n" +" };\n" +" pkgs = import (pkgsSrc) {};\n" +" stdenv = pkgs.stdenv;\n" +"\n" +" # Taken from:\n" +" # http://www.cs.yale.edu/homes/lucas.paul/posts/2017-04-10-hakyll-on-nix.html\n" +" websiteBuilder = pkgs.stdenv.mkDerivation {\n" +" name = \"website-builder\";\n" +" src = ./hakyll;\n" +" phases = \"unpackPhase buildPhase\";\n" +" buildInputs = [\n" +" (pkgs.haskellPackages.ghcWithPackages (p: with p; [ hakyll ]))\n" +" ];\n" +" buildPhase = ''\n" +" mkdir -p $out/bin\n" +" ghc -O2 -dynamic --make Main.hs -o $out/bin/generate-site\n" +" '';\n" +" };\n" +"in rec {\n" +" euandrehWebsite = stdenv.mkDerivation rec {\n" +" name = \"euandreh-website\";\n" +" src = ./site;\n" +" phases = \"unpackPhase buildPhase\";\n" +" # version = \"0.1\";\n" +" buildInputs = [ websiteBuilder ];\n" +" buildPhase = ''\n" +" export LOCALE_ARCHIVE=\"${pkgs.glibcLocales}/lib/locale/locale-archive\";\n" +" export LANG=en_US.UTF-8\n" +" generate-site build\n" +"\n" +" mkdir $out\n" +" cp -r _site/* $out\n" +" '';\n" +" };\n" +"}\n" +msgstr "" + +msgid "date: 2018-07-25" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "eu_categories: nix" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "title: Nix exps" +msgstr "" + +msgid "ref: nix-exps" +msgstr "" + +#~ msgid "title: Nix Stuff" +#~ msgstr "" + +#~ msgid "layout: pastebin" +#~ msgstr "" + +#~ msgid "" +#~ "title: Nix Stuff\n" +#~ "date: 2018-07-25\n" +#~ "layout: pastebin\n" +#~ "lang: en" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_pastebins/2018-07-25-nix-show-derivation-sample-output.po b/po/fr/LC_MESSAGES/_pastebins/2018-07-25-nix-show-derivation-sample-output.po new file mode 100644 index 0000000..b2ed237 --- /dev/null +++ b/po/fr/LC_MESSAGES/_pastebins/2018-07-25-nix-show-derivation-sample-output.po @@ -0,0 +1,92 @@ +# +msgid "" +msgstr "" + +msgid "title: nix show-derivation sample output" +msgstr "" + +msgid "date: 2018-07-25" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "eu_categories: nix" +msgstr "" + +msgid "ref: nix-show-derivation-sample-output" +msgstr "" + +msgid "" +"$ nix show-derivation /nix/store/zzz9cl2ly0mb2njr7vwa5528fxmn29m8-combofont-0.2.drv\n" +"{\n" +" \"/nix/store/zzz9cl2ly0mb2njr7vwa5528fxmn29m8-combofont-0.2.drv\": {\n" +" \"outputs\": {\n" +" \"out\": {\n" +" \"path\": \"/nix/store/dc897j29s5pl5mcw064n5b07bydacfm5-combofont-0.2\",\n" +" \"hashAlgo\": \"r:sha1\",\n" +" \"hash\": \"06be9cab7176fe6d99dd773315d9ec5c62f6a71b\"\n" +" }\n" +" },\n" +" \"inputSrcs\": [\n" +" \"/nix/store/b6ill8amfg0gki49zapm4asrrw9zzgz9-builder.sh\"\n" +" ],\n" +" \"inputDrvs\": {\n" +" \"/nix/store/3s0crp8826gwvfap6kjjyh9a7wq92awk-stdenv.drv\": [\n" +" \"out\"\n" +" ],\n" +" \"/nix/store/fafsh2hx1xxqgm8gwkj3bw3czz6dcvvw-mirrors-list.drv\": [\n" +" \"out\"\n" +" ],\n" +" \"/nix/store/qqla9sd8p8qwgl2a1wpn75bwp2vw70mm-bash-4.4-p12.drv\": [\n" +" \"out\"\n" +" ],\n" +" \"/nix/store/v8fxvb0wlsa5pmrfawa3dg501mglw43c-curl-7.59.0.drv\": [\n" +" \"dev\"\n" +" ]\n" +" },\n" +" \"platform\": \"x86_64-linux\",\n" +" \"builder\": \"/nix/store/lw7xaqhakk0i1c631m3cvac3x4lc5gr5-bash-4.4-p12/bin/bash\",\n" +" \"args\": [\n" +" \"-e\",\n" +" \"/nix/store/b6ill8amfg0gki49zapm4asrrw9zzgz9-builder.sh\"\n" +" ],\n" +" \"env\": {\n" +" \"buildInputs\": \"\",\n" +" \"builder\": \"/nix/store/lw7xaqhakk0i1c631m3cvac3x4lc5gr5-bash-4.4-p12/bin/bash\",\n" +" \"configureFlags\": \"\",\n" +" \"curlOpts\": \"\",\n" +" \"depsBuildBuild\": \"\",\n" +" \"depsBuildBuildPropagated\": \"\",\n" +" \"depsBuildTarget\": \"\",\n" +" \"depsBuildTargetPropagated\": \"\",\n" +" \"depsHostBuild\": \"\",\n" +" \"depsHostBuildPropagated\": \"\",\n" +" \"depsTargetTarget\": \"\",\n" +" \"depsTargetTargetPropagated\": \"\",\n" +" \"downloadToTemp\": \"1\",\n" +" \"executable\": \"\",\n" +" \"impureEnvVars\": \"http_proxy https_proxy ftp_proxy all_proxy no_proxy NIX_CURL_FLAGS NIX_HASHED_MIRRORS NIX_CONNECT_TIMEOUT NIX_MIRRORS_apache NIX_MIRRORS_bioc NIX_MIRRORS_bitlbee NIX_MIRRORS_cpan NIX_MIRRORS_debian NIX_MIRRORS_fedora NIX_MIRRORS_gcc NIX_MIRRORS_gentoo NIX_MIRRORS_gnome NIX_MIRRORS_gnu NIX_MIRRORS_gnupg NIX_MIRRORS_hackage NIX_MIRRORS_hashedMirrors NIX_MIRRORS_imagemagick NIX_MIRRORS_kde NIX_MIRRORS_kernel NIX_MIRRORS_maven NIX_MIRRORS_metalab NIX_MIRRORS_mozilla NIX_MIRRORS_mysql NIX_MIRRORS_oldsuse NIX_MIRRORS_openbsd NIX_MIRRORS_opensuse NIX_MIRRORS_postgresql NIX_MIRRORS_pypi NIX_MIRRORS_roy NIX_MIRRORS_sagemath NIX_MIRRORS_samba NIX_MIRRORS_savannah NIX_MIRRORS_sourceforge NIX_MIRRORS_sourceforgejp NIX_MIRRORS_steamrt NIX_MIRRORS_ubuntu NIX_MIRRORS_xfce NIX_MIRRORS_xorg\",\n" +" \"mirrorsFile\": \"/nix/store/36pk3fz566c2zj6bj8qy7gxl1z14xc4f-mirrors-list\",\n" +" \"name\": \"combofont-0.2\",\n" +" \"nativeBuildInputs\": \"/nix/store/hgv54iw72sgpqmzgv30s6gsfc4rd4wzp-curl-7.59.0-dev\",\n" +" \"out\": \"/nix/store/dc897j29s5pl5mcw064n5b07bydacfm5-combofont-0.2\",\n" +" \"outputHash\": \"3fkzcqjwxkciacvpvncnvzknf6mrrgh6\",\n" +" \"outputHashAlgo\": \"sha1\",\n" +" \"outputHashMode\": \"recursive\",\n" +" \"postFetch\": \"mkdir \\\"$out\\\";tar -xf $downloadedFile \\\\\\n '--strip-components=0' \\\\\\n -C \\\"$out\\\" --anchored --exclude=tlpkg --keep-old-files\\n\",\n" +" \"preferHashedMirrors\": \"1\",\n" +" \"preferLocalBuild\": \"1\",\n" +" \"propagatedBuildInputs\": \"\",\n" +" \"propagatedNativeBuildInputs\": \"\",\n" +" \"showURLs\": \"\",\n" +" \"stdenv\": \"/nix/store/i3kgk0nibrbpgmzdwdfi2ym50i8m3lww-stdenv\",\n" +" \"system\": \"x86_64-linux\",\n" +" \"urls\": \"http://146.185.144.154/texlive-2017/combofont.tar.xz http://gateway.ipfs.io/ipfs/QmRLK45EC828vGXv5YDaBsJBj2LjMjjA2ReLVrXsasRzy7/texlive-2017/combofont.tar.xz\"\n" +" }\n" +" }\n" +"}\n" +msgstr "" diff --git a/po/fr/LC_MESSAGES/_pastebins/2018-07-25-nix-show-derivation.po b/po/fr/LC_MESSAGES/_pastebins/2018-07-25-nix-show-derivation.po new file mode 100644 index 0000000..0dfe220 --- /dev/null +++ b/po/fr/LC_MESSAGES/_pastebins/2018-07-25-nix-show-derivation.po @@ -0,0 +1,99 @@ +# +msgid "" +msgstr "" + +msgid "" +"$ nix show-derivation /nix/store/zzz9cl2ly0mb2njr7vwa5528fxmn29m8-combofont-0.2.drv\n" +"{\n" +" \"/nix/store/zzz9cl2ly0mb2njr7vwa5528fxmn29m8-combofont-0.2.drv\": {\n" +" \"outputs\": {\n" +" \"out\": {\n" +" \"path\": \"/nix/store/dc897j29s5pl5mcw064n5b07bydacfm5-combofont-0.2\",\n" +" \"hashAlgo\": \"r:sha1\",\n" +" \"hash\": \"06be9cab7176fe6d99dd773315d9ec5c62f6a71b\"\n" +" }\n" +" },\n" +" \"inputSrcs\": [\n" +" \"/nix/store/b6ill8amfg0gki49zapm4asrrw9zzgz9-builder.sh\"\n" +" ],\n" +" \"inputDrvs\": {\n" +" \"/nix/store/3s0crp8826gwvfap6kjjyh9a7wq92awk-stdenv.drv\": [\n" +" \"out\"\n" +" ],\n" +" \"/nix/store/fafsh2hx1xxqgm8gwkj3bw3czz6dcvvw-mirrors-list.drv\": [\n" +" \"out\"\n" +" ],\n" +" \"/nix/store/qqla9sd8p8qwgl2a1wpn75bwp2vw70mm-bash-4.4-p12.drv\": [\n" +" \"out\"\n" +" ],\n" +" \"/nix/store/v8fxvb0wlsa5pmrfawa3dg501mglw43c-curl-7.59.0.drv\": [\n" +" \"dev\"\n" +" ]\n" +" },\n" +" \"platform\": \"x86_64-linux\",\n" +" \"builder\": \"/nix/store/lw7xaqhakk0i1c631m3cvac3x4lc5gr5-bash-4.4-p12/bin/bash\",\n" +" \"args\": [\n" +" \"-e\",\n" +" \"/nix/store/b6ill8amfg0gki49zapm4asrrw9zzgz9-builder.sh\"\n" +" ],\n" +" \"env\": {\n" +" \"buildInputs\": \"\",\n" +" \"builder\": \"/nix/store/lw7xaqhakk0i1c631m3cvac3x4lc5gr5-bash-4.4-p12/bin/bash\",\n" +" \"configureFlags\": \"\",\n" +" \"curlOpts\": \"\",\n" +" \"depsBuildBuild\": \"\",\n" +" \"depsBuildBuildPropagated\": \"\",\n" +" \"depsBuildTarget\": \"\",\n" +" \"depsBuildTargetPropagated\": \"\",\n" +" \"depsHostBuild\": \"\",\n" +" \"depsHostBuildPropagated\": \"\",\n" +" \"depsTargetTarget\": \"\",\n" +" \"depsTargetTargetPropagated\": \"\",\n" +" \"downloadToTemp\": \"1\",\n" +" \"executable\": \"\",\n" +" \"impureEnvVars\": \"http_proxy https_proxy ftp_proxy all_proxy no_proxy NIX_CURL_FLAGS NIX_HASHED_MIRRORS NIX_CONNECT_TIMEOUT NIX_MIRRORS_apache NIX_MIRRORS_bioc NIX_MIRRORS_bitlbee NIX_MIRRORS_cpan NIX_MIRRORS_debian NIX_MIRRORS_fedora NIX_MIRRORS_gcc NIX_MIRRORS_gentoo NIX_MIRRORS_gnome NIX_MIRRORS_gnu NIX_MIRRORS_gnupg NIX_MIRRORS_hackage NIX_MIRRORS_hashedMirrors NIX_MIRRORS_imagemagick NIX_MIRRORS_kde NIX_MIRRORS_kernel NIX_MIRRORS_maven NIX_MIRRORS_metalab NIX_MIRRORS_mozilla NIX_MIRRORS_mysql NIX_MIRRORS_oldsuse NIX_MIRRORS_openbsd NIX_MIRRORS_opensuse NIX_MIRRORS_postgresql NIX_MIRRORS_pypi NIX_MIRRORS_roy NIX_MIRRORS_sagemath NIX_MIRRORS_samba NIX_MIRRORS_savannah NIX_MIRRORS_sourceforge NIX_MIRRORS_sourceforgejp NIX_MIRRORS_steamrt NIX_MIRRORS_ubuntu NIX_MIRRORS_xfce NIX_MIRRORS_xorg\",\n" +" \"mirrorsFile\": \"/nix/store/36pk3fz566c2zj6bj8qy7gxl1z14xc4f-mirrors-list\",\n" +" \"name\": \"combofont-0.2\",\n" +" \"nativeBuildInputs\": \"/nix/store/hgv54iw72sgpqmzgv30s6gsfc4rd4wzp-curl-7.59.0-dev\",\n" +" \"out\": \"/nix/store/dc897j29s5pl5mcw064n5b07bydacfm5-combofont-0.2\",\n" +" \"outputHash\": \"3fkzcqjwxkciacvpvncnvzknf6mrrgh6\",\n" +" \"outputHashAlgo\": \"sha1\",\n" +" \"outputHashMode\": \"recursive\",\n" +" \"postFetch\": \"mkdir \\\"$out\\\";tar -xf $downloadedFile \\\\\\n '--strip-components=0' \\\\\\n -C \\\"$out\\\" --anchored --exclude=tlpkg --keep-old-files\\n\",\n" +" \"preferHashedMirrors\": \"1\",\n" +" \"preferLocalBuild\": \"1\",\n" +" \"propagatedBuildInputs\": \"\",\n" +" \"propagatedNativeBuildInputs\": \"\",\n" +" \"showURLs\": \"\",\n" +" \"stdenv\": \"/nix/store/i3kgk0nibrbpgmzdwdfi2ym50i8m3lww-stdenv\",\n" +" \"system\": \"x86_64-linux\",\n" +" \"urls\": \"http://146.185.144.154/texlive-2017/combofont.tar.xz http://gateway.ipfs.io/ipfs/QmRLK45EC828vGXv5YDaBsJBj2LjMjjA2ReLVrXsasRzy7/texlive-2017/combofont.tar.xz\"\n" +" }\n" +" }\n" +"}\n" +msgstr "" + +msgid "title: nix show-derivation sample output" +msgstr "" + +msgid "date: 2018-07-25" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "eu_categories: nix" +msgstr "" + +msgid "layout: post" +msgstr "" + +#~ msgid "layout: pastebin" +#~ msgstr "" + +#~ msgid "" +#~ "title: nix show-derivation sample output\n" +#~ "date: 2018-07-25\n" +#~ "layout: pastebin\n" +#~ "lang: en" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_pastebins/2019-06-08-inconsistent-hash-of-buildgomodule.po b/po/fr/LC_MESSAGES/_pastebins/2019-06-08-inconsistent-hash-of-buildgomodule.po new file mode 100644 index 0000000..6be1e7f --- /dev/null +++ b/po/fr/LC_MESSAGES/_pastebins/2019-06-08-inconsistent-hash-of-buildgomodule.po @@ -0,0 +1,1104 @@ +# +msgid "" +msgstr "" + +msgid "Offending derivation:" +msgstr "" + +msgid "Local build:" +msgstr "" + +msgid "Build [on CI](https://builds.sr.ht/~euandreh/job/67836#task-setup-0):" +msgstr "" + +msgid "" +"The `setup.sh` script contains a call to `nix-shell` which in turns build " +"the same `terraform-godaddy` derivation:" +msgstr "" + +msgid "" +"terraform-godaddy = pkgs.buildGoModule rec {\n" +" name = \"terraform-godaddy-${version}\";\n" +" version = \"1.6.4\";\n" +" src = pkgs.fetchFromGitHub {\n" +" owner = \"n3integration\";\n" +" repo = \"terraform-godaddy\";\n" +" rev = \"v${version}\";\n" +" sha256 = \"00blqsan74s53dk9ab4hxi1kzxi46k57dr65dmbiradfa3yz3852\";\n" +" };\n" +" modSha256 = \"0p81wqw2n8vraxk20xwg717582ijwq2k7v5j3n13y4cd5bxd8hhz\";\n" +" postInstall =\n" +" \"mv $out/bin/terraform-godaddy $out/bin/terraform-provider-godaddy\";\n" +"};\n" +msgstr "" + +msgid "" +"$ nix-build -A terraform-godaddy\n" +"these derivations will be built:\n" +" /nix/store/3hs274i9qdsg3hsgp05j7i5cqxsvpcqx-terraform-godaddy-1.6.4-go-modules.drv\n" +" /nix/store/y5961vv6y9c0ps2sbd8xfnpqvk0q7qhq-terraform-godaddy-1.6.4.drv\n" +"building '/nix/store/3hs274i9qdsg3hsgp05j7i5cqxsvpcqx-terraform-godaddy-1.6.4-go-modules.drv'...\n" +"unpacking sources\n" +"unpacking source archive /nix/store/m62ydk4wy6818sysfys0qz20cx5nzj7h-source\n" +"source root is source\n" +"patching sources\n" +"configuring\n" +"building\n" +"go: finding github.com/mitchellh/copystructure v1.0.0\n" +"go: finding github.com/blang/semver v3.5.1+incompatible\n" +"go: finding github.com/posener/complete v1.2.1\n" +"go: finding github.com/apparentlymart/go-cidr v1.0.0\n" +"go: finding github.com/agext/levenshtein v1.2.1\n" +"go: finding github.com/mitchellh/reflectwalk v1.0.0\n" +"go: finding github.com/mitchellh/mapstructure v1.1.2\n" +"go: finding github.com/hashicorp/hil v0.0.0-20170627220502-fa9f258a9250\n" +"go: finding github.com/bgentry/go-netrc v0.0.0-20140422174119-9fd32a8b3d3d\n" +"go: finding github.com/bgentry/speakeasy v0.1.0\n" +"go: finding github.com/jmespath/go-jmespath v0.0.0-20180206201540-c2b33e8439af\n" +"go: finding github.com/hashicorp/errwrap v1.0.0\n" +"go: finding github.com/hashicorp/hcl2 v0.0.0-20181220012050-6631d7cd0a68\n" +"go: finding google.golang.org/grpc v1.17.0\n" +"go: finding golang.org/x/crypto v0.0.0-20181203042331-505ab145d0a9\n" +"go: finding github.com/hashicorp/go-version v1.0.0\n" +"go: finding google.golang.org/appengine v1.4.0\n" +"go: finding golang.org/x/sync v0.0.0-20181221193216-37e7f081c4d4\n" +"go: finding honnef.co/go/tools v0.0.0-20180920025451-e3ad64cb4ed3\n" +"go: finding github.com/hashicorp/terraform v0.11.11\n" +"go: finding google.golang.org/genproto v0.0.0-20181221175505-bd9b4fb69e2f\n" +"go: finding github.com/mitchellh/go-wordwrap v1.0.0\n" +"go: finding github.com/hashicorp/go-cleanhttp v0.5.0\n" +"go: finding github.com/kylelemons/godebug v0.0.0-20170820004349-d65d576e9348\n" +"go: finding golang.org/x/oauth2 v0.0.0-20181203162652-d668ce993890\n" +"go: finding github.com/mitchellh/go-wordwrap v0.0.0-20150314170334-ad45545899c7\n" +"go: finding github.com/kr/pty v1.1.3\n" +"go: finding github.com/hashicorp/yamux v0.0.0-20181012175058-2f1d1f20f75d\n" +"go: finding github.com/aws/aws-sdk-go v1.16.11\n" +"go: finding cloud.google.com/go v0.26.0\n" +"go: finding google.golang.org/genproto v0.0.0-20180817151627-c66870c02cf8\n" +"go: finding github.com/sergi/go-diff v1.0.0\n" +"go: finding golang.org/x/sys v0.0.0-20181228144115-9a3f9b0469bb\n" +"go: finding github.com/go-ini/ini v1.40.0\n" +"go: finding github.com/golang/protobuf v1.2.0\n" +"go: finding github.com/satori/go.uuid v1.2.0\n" +"go: finding github.com/mitchellh/cli v1.0.0\n" +"go: finding google.golang.org/appengine v1.1.0\n" +"go: finding honnef.co/go/tools v0.0.0-20180728063816-88497007e858\n" +"go: finding golang.org/x/sync v0.0.0-20180314180146-1d60e4601c6f\n" +"go: finding github.com/mitchellh/iochan v1.0.0\n" +"go: finding github.com/mitchellh/go-homedir v1.0.0\n" +"go: finding github.com/spf13/pflag v1.0.2\n" +"go: finding github.com/kr/pretty v0.1.0\n" +"go: finding github.com/go-test/deep v1.0.1\n" +"go: finding github.com/hashicorp/go-multierror v1.0.0\n" +"go: finding github.com/spf13/pflag v1.0.3\n" +"go: finding github.com/onsi/ginkgo v1.7.0\n" +"go: finding github.com/onsi/gomega v1.4.3\n" +"go: finding github.com/zclconf/go-cty v0.0.0-20181218225846-4fe1e489ee06\n" +"go: finding gopkg.in/yaml.v2 v2.2.2\n" +"go: finding github.com/mitchellh/gox v0.4.0\n" +"go: finding github.com/zclconf/go-cty v0.0.0-20181129180422-88fbe721e0f8\n" +"go: finding golang.org/x/crypto v0.0.0-20180816225734-aabede6cba87\n" +"go: finding golang.org/x/net v0.0.0-20181220203305-927f97764cc3\n" +"go: finding golang.org/x/net v0.0.0-20180826012351-8a410e7b638d\n" +"go: finding github.com/google/go-cmp v0.2.0\n" +"go: finding golang.org/x/sys v0.0.0-20180830151530-49385e6e1522\n" +"go: finding github.com/onsi/ginkgo v1.6.0\n" +"go: finding gopkg.in/fsnotify.v1 v1.4.7\n" +"go: finding gopkg.in/yaml.v2 v2.2.1\n" +"go: finding github.com/hashicorp/go-plugin v0.0.0-20181212150838-f444068e8f5a\n" +"go: finding github.com/armon/go-radix v1.0.0\n" +"go: finding golang.org/x/oauth2 v0.0.0-20180821212333-d2e6202438be\n" +"go: finding github.com/golang/mock v1.1.1\n" +"go: finding github.com/ulikunitz/xz v0.5.5\n" +"go: finding golang.org/x/tools v0.0.0-20180828015842-6cd1fcedba52\n" +"go: finding github.com/davecgh/go-spew v1.1.1\n" +"go: finding golang.org/x/net v0.0.0-20180906233101-161cd47e91fd\n" +"go: finding gopkg.in/check.v1 v0.0.0-20161208181325-20d25e280405\n" +"go: finding github.com/hpcloud/tail v1.0.0\n" +"go: finding golang.org/x/lint v0.0.0-20181217174547-8f45f776aaf1\n" +"go: finding github.com/mattn/go-colorable v0.0.9\n" +"go: finding google.golang.org/grpc v1.16.0\n" +"go: finding github.com/vmihailenco/msgpack v3.3.3+incompatible\n" +"go: finding github.com/posener/complete v1.1.1\n" +"go: finding github.com/mitchellh/go-testing-interface v1.0.0\n" +"go: finding github.com/golang/protobuf v1.1.0\n" +"go: finding github.com/mattn/go-isatty v0.0.3\n" +"go: finding github.com/kr/text v0.1.0\n" +"go: finding golang.org/x/net v0.0.0-20181106065722-10aee1819953\n" +"go: finding github.com/hashicorp/go-hclog v0.0.0-20181001195459-61d530d6c27f\n" +"go: finding github.com/oklog/run v1.0.0\n" +"go: finding github.com/mitchellh/hashstructure v1.0.0\n" +"go: finding golang.org/x/tools v0.0.0-20181221235234-d00ac6d27372\n" +"go: finding github.com/hashicorp/go-getter v0.0.0-20181213035916-be39683deade\n" +"go: finding github.com/kisielk/gotool v1.0.0\n" +"go: finding howett.net/plist v0.0.0-20181124034731-591f970eefbb\n" +"go: finding github.com/vmihailenco/msgpack v4.0.1+incompatible\n" +"go: finding golang.org/x/sync v0.0.0-20181108010431-42b317875d0f\n" +"go: finding golang.org/x/net v0.0.0-20180724234803-3673e40ba225\n" +"go: finding gopkg.in/tomb.v1 v1.0.0-20141024135613-dd632973f1e7\n" +"go: finding github.com/fatih/color v1.7.0\n" +"go: finding cloud.google.com/go v0.34.0\n" +"go: finding github.com/hashicorp/yamux v0.0.0-20180604194846-3520598351bb\n" +"go: finding github.com/hashicorp/hcl v1.0.0\n" +"go: finding github.com/hashicorp/go-uuid v1.0.0\n" +"go: finding github.com/hashicorp/go-multierror v0.0.0-20180717150148-3d5d8f294aa0\n" +"go: finding github.com/mattn/go-isatty v0.0.4\n" +"go: finding github.com/hashicorp/errwrap v0.0.0-20180715044906-d6c0cd880357\n" +"go: finding github.com/armon/go-radix v0.0.0-20180808171621-7fddfc383310\n" +"go: finding golang.org/x/net v0.0.0-20180811021610-c39426892332\n" +"go: finding github.com/fsnotify/fsnotify v1.4.7\n" +"go: finding github.com/bsm/go-vlq v0.0.0-20150828105119-ec6e8d4f5f4e\n" +"go: finding github.com/golang/mock v1.2.0\n" +"go: finding golang.org/x/net v0.0.0-20181129055619-fae4c4e3ad76\n" +"go: finding github.com/apparentlymart/go-dump v0.0.0-20180507223929-23540a00eaa3\n" +"go: finding github.com/aws/aws-sdk-go v1.15.78\n" +"go: finding github.com/golang/lint v0.0.0-20180702182130-06c8688daad7\n" +"go: finding golang.org/x/text v0.3.0\n" +"go: finding github.com/pmezard/go-difflib v1.0.0\n" +"go: finding golang.org/x/sys v0.0.0-20180823144017-11551d06cbcc\n" +"go: finding github.com/kr/pty v1.1.1\n" +"go: finding github.com/client9/misspell v0.3.4\n" +"go: finding github.com/golang/glog v0.0.0-20160126235308-23def4e6c14b\n" +"go: finding golang.org/x/lint v0.0.0-20181026193005-c67002cb31c3\n" +"go: finding gopkg.in/check.v1 v1.0.0-20180628173108-788fd7840127\n" +"go: finding github.com/jessevdk/go-flags v1.4.0\n" +"go: finding github.com/stretchr/testify v1.2.2\n" +"go: finding github.com/hashicorp/go-hclog v0.0.0-20180709165350-ff2cf002a8dd\n" +"go: finding golang.org/x/net v0.0.0-20181114220301-adae6a3d119a\n" +"go: finding github.com/apparentlymart/go-textseg v1.0.0\n" +"go: finding golang.org/x/sys v0.0.0-20180909124046-d0be0721c37e\n" +"go: finding github.com/mitchellh/go-testing-interface v0.0.0-20171004221916-a61a99592b77\n" +"go: finding google.golang.org/grpc v1.14.0\n" +"go: finding golang.org/x/lint v0.0.0-20180702182130-06c8688daad7\n" +"go: finding github.com/hashicorp/go-safetemp v1.0.0\n" +"go: finding github.com/jmespath/go-jmespath v0.0.0-20160202185014-0b12d6b521d8\n" +"installing\n" +"hash mismatch in fixed-output derivation '/nix/store/jgbfkhlsz6bmq724p5cqqcgfyc7l6sdv-terraform-godaddy-1.6.4-go-modules':\n" +" wanted: sha256:0p81wqw2n8vraxk20xwg717582ijwq2k7v5j3n13y4cd5bxd8hhz\n" +" got: sha256:10n2dy7q9kk1ly58sw965n6qa8l0nffh8vyd1vslx0gdlyj25xxs\n" +"cannot build derivation '/nix/store/y5961vv6y9c0ps2sbd8xfnpqvk0q7qhq-terraform-godaddy-1.6.4.drv': 1 dependencies couldn't be built\n" +"error: build of '/nix/store/y5961vv6y9c0ps2sbd8xfnpqvk0q7qhq-terraform-godaddy-1.6.4.drv' failed\n" +msgstr "" + +msgid "" +"$ cd vps/\n" +"$ ./scripts/ci/setup.sh\n" +"warning: Nix search path entry '/nix/var/nix/profiles/per-user/root/channels' does not exist, ignoring\n" +"these derivations will be built:\n" +" /nix/store/as9r3n55czsdiq82iacs0hq12alxb2m0-remove-references-to.drv\n" +" /nix/store/fdh1ahjdh3fgsz4qz386klsa9bsqil48-source.drv\n" +" /nix/store/x7r5kh20ajlnj6vw6fg649w0iypcg1ga-terraform-godaddy-1.6.4-go-modules.drv\n" +" /nix/store/w4ghinrmpq524k3617ikfc8i42aa0dbb-terraform-godaddy-1.6.4.drv\n" +"these paths will be fetched (868.72 MiB download, 4262.91 MiB unpacked):\n" +" /nix/store/01aggsi1ndjhnr93gcy8c4s1xbxab8dn-unzip-6.0\n" +" /nix/store/02nzlzdw0kiici9368jp5s84cpbqxkva-python3.7-certifi-2018.11.29\n" +" /nix/store/0bdf1xn7p6xzk008yr6cahq3wjlvah5g-terraform-provider-flexibleengine-1.5.0-bin\n" +" /nix/store/0jl2dhydfh3jbfpkgkrixisqkhj12d4y-libffi-3.2.1-dev\n" +" /nix/store/0jwyd55g8nfhm25a0bh1j1by6afdriic-perl5.28.2-File-Listing-6.04\n" +" /nix/store/0rc1jyfbxwffmsphyv2pfnxd6smysc1l-terraform-provider-ansible-0.0.4-bin\n" +" /nix/store/0w6l8kh3d30kg3nxc8xyi84gmrfxjnns-git-2.21.0\n" +" /nix/store/0z8i6sq8mg138qnifr1z37y780xkk8hf-terraform-provider-cloudstack-0.2.0-bin\n" +" /nix/store/15fv1623h1vcn5z0nq42v5rgjirbp5r0-terraform-provider-rancher-1.2.1-bin\n" +" /nix/store/18rr3rg32imsnfyx6zb6s8lc8qpkdr74-nghttp2-1.38.0-bin\n" +" /nix/store/1dydqkwswavzkyvr1qr62zmx3nqpmpp4-gnutls-3.6.7\n" +" /nix/store/1fl7yd9chgswnabbsvva7xvg5ak1q44p-terraform-provider-vault-1.8.0-bin\n" +" /nix/store/1hml3hx7qlbkv139khazb24jh69nngcd-terraform-provider-bigip-0.12.2-bin\n" +" /nix/store/1kz91g5mfj271lj5kxz2m1axcs2yqafy-thin-provisioning-tools-0.7.6\n" +" /nix/store/1wh5wgw6a3w91mk2avvn9ssw32nlw9kd-terraform-provider-openstack-1.18.0-bin\n" +" /nix/store/206dvjl6595dk40dli12ziv393ww54wl-bzip2-1.0.6.0.1\n" +" /nix/store/20wmykp8fj2izxdj8lic8ggcfpdid5ka-tzdata-2019a\n" +" /nix/store/2ar3zk5fjr34ys2dqnsfbb678x6fdlj4-openssh-7.9p1\n" +" /nix/store/2dfjlvp38xzkyylwpavnh61azi0d168b-binutils-2.31.1\n" +" /nix/store/2j9jm3jaxfn2g6wxak61wkhmrg6c4nn5-unbound-1.9.1-lib\n" +" /nix/store/2k46270d0h3gqj1c0wgx8prnj51jqryd-db-5.3.28\n" +" /nix/store/2lh08897y86kxvyjdd1vlnkg8fz88nkd-terraform-provider-rundeck-0.1.0-bin\n" +" /nix/store/2xhsrw4ws6kc4x3983wdwwlnim27c6iz-shadow-4.6\n" +" /nix/store/2yy3pv77rwbxk7b2mpysmiqdzhmgmphg-terraform-provider-http-1.1.1-bin\n" +" /nix/store/31l04a1yxxdbdpzdp8mpfk96rhj3bg2c-python3.7-netaddr-0.7.19\n" +" /nix/store/35mdgd1wc67g60azsrghzgn4fjhr5d2r-zfs-user-0.7.13-lib\n" +" /nix/store/3mgn9jnjzj1rgxclbixk5xa0kkx9xpw3-openssl-1.0.2r-dev\n" +" /nix/store/3qjz5kfri8sa0dj1213rap75alpqsm2l-terraform-provider-mailgun-0.1.0-bin\n" +" /nix/store/3s4fr71ykyw54kyyqavd0ba42klg0bhf-libXcursor-1.2.0\n" +" /nix/store/3xq3w5fgz99rhp3rxfkbp0ahg37mgmly-pango-1.43.0\n" +" /nix/store/3xzkc4wyadr3vrva2q320axjr6cyb43n-python-2.7.16\n" +" /nix/store/43i41p1n1sxssmqpf9jp5x4gcy6r2fl6-git-2.21.0\n" +" /nix/store/479dvd7q6c18l3jl2myhfxmfsjbqjjch-python3.7-dopy-2016-01-04\n" +" /nix/store/4i1mw6av3d6pr9bqggb4hnv6cykbrhhi-kexec-tools-2.0.19\n" +" /nix/store/4jw2677fvb11aj1bal9a2iksqz0mk80m-expat-2.2.6\n" +" /nix/store/4qq5hh1r6sqb0kpxc305rb468s45j4aw-libICE-1.0.9\n" +" /nix/store/4z62pandn85xhcc5vazmi29cs2yps47b-iproute2-5.0.0\n" +" /nix/store/50gfgyi2rxi4n25if8cqvlxlh5czl0wd-yajl-2.1.0\n" +" /nix/store/50rywa1m6asdz1y78a6dpa0xf98vm01v-perl5.28.2-LWP-MediaTypes-6.04\n" +" /nix/store/50wggbbr0wdg21hrvl4icwlppvk4464b-terraform-provider-opc-1.3.6-bin\n" +" /nix/store/5b0s7hhp52vq4psmicf8m8y2jr5jsiaz-terraform-provider-ucloud-1.6.0-bin\n" +" /nix/store/5k67y2lglsnswrya21z51d4h87a081k5-terraform-provider-kubernetes-1.6.2-bin\n" +" /nix/store/5l3967kll8m6s66zprzwb2p6vf2mh5yd-libtasn1-4.13\n" +" /nix/store/5lcz7p2xz1zp8iyd9yjmrg1kxw5yygnx-terraform-provider-panos-1.5.1-bin\n" +" /nix/store/5nkxpwdgpxs97yqh2fxz9y0rm80rc280-terraform-provider-heroku-1.9.0-bin\n" +" /nix/store/5pjazw71xk4kysxrzacgjl4iai691k25-curl-7.64.1\n" +" /nix/store/5qnlfx9qncn0fcw6mbfj6j58pz0cv0p3-binutils-wrapper-2.31.1\n" +" /nix/store/5x1551gw825apcsnwx8gzfnmiapbz8yl-perl5.28.2-IO-HTML-1.001\n" +" /nix/store/5ydkc9jcaaxlz58dr7gvyhi3gcmafsfy-python3.7-pyparsing-2.3.1\n" +" /nix/store/5ygnx64lyv5a8pnpmlj7bs8s2dz2hkxd-terraform-provider-spotinst-1.13.2-bin\n" +" /nix/store/5z3s6zbi98gh8cfliaplnmv15j568c46-terraform-provider-null-2.1.2-bin\n" +" /nix/store/61shjilahl0d237fg9b3z3chza2lgms4-patchelf-0.9\n" +" /nix/store/63gjp25l4cmdkl63zy0rcgmsvd2p2p34-terraform-0.11.14\n" +" /nix/store/63k736kr346ncpzv5yiqiyyyiqpa2h8m-terraform-provider-bitbucket-1.0.0-bin\n" +" /nix/store/6554dpyahvcs49dmv434aky6bfkmqb30-gnumake-4.2.1\n" +" /nix/store/69msrhi85iay3cb7c3nksr0s8l0xpsc7-util-linux-2.33.2\n" +" /nix/store/69vq0a9sqynmz335apm8zgyjdmq34s5j-libX11-1.6.7\n" +" /nix/store/6b2jabk1scwhhk9bz7wjzycvmkiw419d-libapparmor-2.13.1\n" +" /nix/store/6brahzfjri338n3fggplfrsmf63mrwnx-terraform-provider-nutanix-1.0.1-bin\n" +" /nix/store/6bvd29jny80ka8df9prr5hrl5yz7d98k-systemd-239.20190219\n" +" /nix/store/6hv1yfwyydyg2lzqcllwjb68xl4mrppw-terraform-provider-tencentcloud-1.5.0-bin\n" +" /nix/store/6hwdmzpspbnb7ix5z6m9h60jyy42kj90-dbus-1.12.12-lib\n" +" /nix/store/6mz512j183wj7qas2qm6zkrks5k8rh00-gettext-0.19.8.1\n" +" /nix/store/6whclwjzwg46s0dkxwk1xz8cdcxnkd3y-db-4.8.30\n" +" /nix/store/715lcljfyp8grxlmaf51pn0n3ml3dwgg-bash-interactive-4.4-p23\n" +" /nix/store/7256h1y98mmzsckwk2x7i3v3cxmvgrmq-python3.7-pyOpenSSL-19.0.0-dev\n" +" /nix/store/749qksf79hvn0aprcznd9bwfv550qwh3-go-1.12.1\n" +" /nix/store/7axz4xwz0vfrdgjyk59xg998bdqbvg5x-terraform-provider-random-2.1.2-bin\n" +" /nix/store/7b7nbb0w2iwskwhzjhfwrif631h4smia-libpciaccess-0.14\n" +" /nix/store/7crry947d1xvp1f15c6q089l0gcy5hpc-stdenv-linux\n" +" /nix/store/7fd40sykaxj6dvya7mvif3f16wrqijr9-terraform-provider-terraform-1.0.2-bin\n" +" /nix/store/7gwvcm8dc24vnphbx85q1afaxhfhac28-perl5.28.2-HTTP-Cookies-6.04\n" +" /nix/store/7k3hvg4sfpr6y2bg8b7x9mkb0d2p3scr-terraform-provider-clc-0.1.0-bin\n" +" /nix/store/7mmn8ri08z48vfj69c2h66f3g349ilq1-mailcap-2.1.48\n" +" /nix/store/7mqpbfs391s9hbnfzkpgw3inj8mkldr8-terraform-provider-azurerm-1.27.1-bin\n" +" /nix/store/85hh7apv9n3gganpnnq36zvlwm126mdh-openssl-1.0.2r-bin\n" +" /nix/store/89wg3f6hk41gxm4n6cikj6r7gr2k7h8j-terraform-provider-nixos-0.0.1-bin\n" +" /nix/store/8aylwgi9nb6hsgz6620fzsllbc7h2rx1-c-ares-1.15.0\n" +" /nix/store/8bxvyvd3ky0w5gk3k0lq2fmvj30fbzj8-zfs-user-0.7.13\n" +" /nix/store/8dl5c7n4555lr6qipki2424652gf8az8-ebtables-2.0.10-4\n" +" /nix/store/8gn2b5vvlazg608cj1y5l4igp9rckmnq-dejavu-fonts-minimal-2.37\n" +" /nix/store/8krs5vbid0ic6vvlvjvndvjb815q8hbd-terraform-provider-ns1-1.3.1-bin\n" +" /nix/store/8ndwixznskf4zbf6h96ww4j8ap4j8067-fribidi-1.0.5\n" +" /nix/store/8vqr6vbvyzlpsk6q0mnj93sf5j1wr5qa-perl5.28.2-Test-RequiresInternet-0.05\n" +" /nix/store/8xy69pkisipvdmrpm1nmbi6qa2c6lhn0-bash-interactive-4.4-p23-info\n" +" /nix/store/8yy3wngrdcpmjyw2ryas1y4wwhbd1356-patch-2.7.6\n" +" /nix/store/8z5vplmgshflm7yixhp8q7hy11xxxd8a-terraform-provider-elasticsearch-0.6.0-bin\n" +" /nix/store/91a8wnca647kfw67sk0iykdbyjpr8430-perl5.28.2-libwww-perl-6.38\n" +" /nix/store/920nr51iw7qaplqjlqrlnql9g5ljq3vp-gdbm-1.18.1\n" +" /nix/store/93rldbdly90q16lzk7hzilhk4qkdpqfq-keyutils-1.6-lib\n" +" /nix/store/94nrq9paz335s155x9za8n7kb0q3y211-libgcrypt-1.8.4\n" +" /nix/store/95rd64vii9j6h31fcr9lba8m8940zfpj-terraform-provider-github-2.0.0-bin\n" +" /nix/store/97d3r4a7v1nal53x0gv17hrbbcp0rb21-util-linux-2.33.2-bin\n" +" /nix/store/9dk1gh07pwkvg62rns4k670h54bhfhgh-zlib-1.2.11-dev\n" +" /nix/store/9fvjgcjn1d0c9476qlr05psvwljwzq59-python3.7-cryptography-2.6.1\n" +" /nix/store/9gjpg5lsdhgrhi805948c648nhn39l8z-terraform-provider-template-2.1.2-bin\n" +" /nix/store/9hysgvp7qrfcil4b5qhwdq2vm9hism13-libxcb-1.13.1\n" +" /nix/store/9pa3p1rqhnvlrngaqsx09766cl1j6zf3-python3.7-httpretty-0.9.6\n" +" /nix/store/9xb22l3577nznvd6dqqis6ixgmwq9ygh-python3.7-pycparser-2.19\n" +" /nix/store/9yb9whkdgf3zyy85xac248kwq1wm6qd6-harfbuzz-2.3.1\n" +" /nix/store/a185xh0jcx7il7hw2gfh0pmvrah3x67y-systemd-239.20190219-lib\n" +" /nix/store/a2cg0faxbwnicf41vwmw467jw7i9ix46-pinentry-1.1.0\n" +" /nix/store/a2rr0irv2ssvvphvafgrxy4di0pkkagn-audit-2.8.5\n" +" /nix/store/ag3fp30cz58ijm2yyy5adp1f3kw814b5-libXcomposite-0.4.5\n" +" /nix/store/amlnqi4vvmpb9gjmyh1vr5hr2py12ss2-terraform-provider-docker-1.1.1-bin\n" +" /nix/store/ap4sr1n0wlgmybxbw3pvq8klh8snc3n8-sqlite-3.28.0\n" +" /nix/store/apcaggi0q3vrb4ha1b07cjxiim2li5ly-gcc-7.4.0\n" +" /nix/store/apjv9g35sklrab9lzz9r9rq7lnczv2wy-terraform-provider-triton-0.5.1-bin\n" +" /nix/store/aqgl1dqd6lr7jr9knqsyyq09bm0ibw7s-python3.7-cffi-1.12.3\n" +" /nix/store/aqp0mrdbhvkm8rl1z0p2rkqnz6pbclhq-libXfixes-5.0.3\n" +" /nix/store/b2rwzjp56yzd4jg2csx568h2dgj1l3l2-perl5.28.2-Try-Tiny-0.30\n" +" /nix/store/b2wy5p5bykcnkwz5q1w8qq4qfzr4arc7-python3.7-MarkupSafe-1.1.1\n" +" /nix/store/b6pdz8g070kbf0rdavjz6rip7sx06r8h-libkrb5-1.17-dev\n" +" /nix/store/b77nn2r1c8cqpr9prh1ldwr3m6xdrkpa-openldap-2.4.47\n" +" /nix/store/b7w6bpx5z0ncy35kqxvmpg4lwrnc8jf2-libxml2-2.9.9\n" +" /nix/store/bd1hz6m8gh9m91hikjhq7aiq2khdkx2r-fontconfig-2.12.6\n" +" /nix/store/bf26sh99bngrnpzrj7gyz0689b060vak-terraform-provider-skytap-0.9.0-bin\n" +" /nix/store/bh412cii40qpzc20pzd48dq45jv9xm5a-perl5.28.2-HTTP-Date-6.02\n" +" /nix/store/bvsihhp4jv61hz6mc17mn1sar03k0i8d-terraform-provider-telefonicaopencloud-1.0.0-bin\n" +" /nix/store/bxps2h6axpqrjxcmib344a3immy3gvhd-readline-6.3p08\n" +" /nix/store/byxya0m4656ylf5imvs2v9p2c1av1kjl-terraform-provider-matchbox-0.2.3-bin\n" +" /nix/store/c7jkmfjhl3jkgnkrhh021vrqry7zplc1-linux-headers-4.19.16\n" +" /nix/store/caa29d4y2zip0ly9mcc7f4w94blw8k60-lz4-1.9.1\n" +" /nix/store/cd09qv56inq4gwa89656r4n0lq0vgidw-libXi-1.7.9\n" +" /nix/store/ch6pz5kfg0bd3sfyf1813cpskg7lidns-python3.7-urllib3-1.24.2\n" +" /nix/store/ck0lifb2jgkmg6c7frz7fxqwz5fbdnxk-terraform-provider-ultradns-0.1.0-bin\n" +" /nix/store/cncad2f4lfxfxnwd9lfhjjd89x3anxqr-terraform-provider-yandex-0.5.2-bin\n" +" /nix/store/csajl6aq80s9v2xbkmlzgfxlilmbzff6-terraform-provider-influxdb-1.1.0-bin\n" +" /nix/store/d0wcd9mid6067i6va19lwiv29hln6n2j-python3.7-requests-2.21.0\n" +" /nix/store/d7rh74cch3ybp9r239j5c2c1rb0kx3pa-terraform-provider-chef-0.1.0-bin\n" +" /nix/store/daizqdqrm7g4favv814hnijmqhay8hs4-dbus-1.12.12\n" +" /nix/store/di6rrbw1kbdrwxiymq91dgdvp2rvk1xv-dnsmasq-2.80\n" +" /nix/store/drdzgwhnqjvq4g1aqsyz56c04k6dxnbi-bash-interactive-4.4-p23-doc\n" +" /nix/store/ds1prvgw3i3ic8c7axyrw4lwm3d0gqab-gcc-wrapper-7.4.0\n" +" /nix/store/dvsw0fhfzqf4xg0q2idhs02rhwn4k8cv-libXrender-0.9.10\n" +" /nix/store/dy437h3f5i500gv6znll974c87grzh3l-libXft-2.3.3\n" +" /nix/store/dy5wi2sqnhbnlpvjr8a0z96id1mq243j-python3.7-six-1.12.0\n" +" /nix/store/dz9dqcnz8v9cy54x5hax599zjwckp0kd-terraform-provider-gitlab-1.3.0-bin\n" +" /nix/store/f11valqiyik1ggdlnhg3ibwgrj1imidb-numactl-2.0.12\n" +" /nix/store/f39sk2aim9xz7dzn7qvqh442xm58v77w-nfs-utils-2.3.3\n" +" /nix/store/f3rbnn0jhm549mcp7k9ysjcq26j8fvyy-terraform-provider-segment-0.2.0-bin\n" +" /nix/store/f7zcmzqcavbj7bp1dlfk86f9bkqvk9p3-bridge-utils-1.5\n" +" /nix/store/f7zh0d0n2dj4dcig903zd5jgb2cpaxf6-terraform-provider-ignition-1.0.1-bin\n" +" /nix/store/fhgiisqjpzwl8z4fchgc07avg1azmp0r-cyrus-sasl-2.1.27\n" +" /nix/store/fky41n197z9n737kbih4j7ncnh7cngnz-perl5.28.2-Net-HTTP-6.18\n" +" /nix/store/fq4765nh9p0si8mh9cnywsq48zr1qc27-terraform-provider-runscope-0.5.0-bin\n" +" /nix/store/fwvdxglj9asp4f90ihry29n2fm8a6i09-terraform-provider-aws-2.9.0-bin\n" +" /nix/store/g4qqgmrm254axgndybnpwg7s780bxy1a-numad-0.5\n" +" /nix/store/g63hwfkd4yjncqh81ndn9vbmghdv41ng-terraform-provider-digitalocean-1.3.0\n" +" /nix/store/gg469jh0m4dk4b0x6s44ziad69czbv22-python3.7-pycrypto-3.7.3\n" +" /nix/store/gkpa27fykskx0dd52dca515gd91qhhgf-terraform-provider-local-1.2.2-bin\n" +" /nix/store/glrnpb3rkribnrjh5gzs24nmvl3m00cg-parted-3.2\n" +" /nix/store/gn5cd1z252aip0rvds71g9mgfhh6i8p7-fontconfig-2.12.6-lib\n" +" /nix/store/gsl1dw8ycrdvlzczsl59mkz0qpbwcmz1-iptables-1.8.2\n" +" /nix/store/gydzhj2y5j1ggbainbilvpxi5glw5hmf-terraform-provider-alicloud-1.41.0-bin\n" +" /nix/store/h02lb0p8krj1smsrid2n44ak058bbd82-expand-response-params\n" +" /nix/store/h40ib0qsa07b6ld1pv4x76xx2g7xgik6-terraform-provider-newrelic-1.5.0-bin\n" +" /nix/store/h8898ysg2s23k6palhxy9a5sbgrvvrcy-nfs-utils-2.3.3-lib\n" +" /nix/store/hbs2vrw1y8y1qz1hi71jaz0j3pl95qfs-terraform-provider-helm-0.9.1-bin\n" +" /nix/store/hg863b95fxv9zlk008qjyf87qgyx58h1-libseccomp-2.4.1-lib\n" +" /nix/store/hl8lzq90qjhq0n710lm5n17lc9i80vsh-terraform-provider-oraclepaas-1.5.2-bin\n" +" /nix/store/hnvmacd16kzmwcsavzkssrqj2kiryy2p-perl5.28.2-WWW-RobotRules-6.02\n" +" /nix/store/hpmni5y805q7a07q9sn3nwjk4i2m2jl5-libkrb5-1.17\n" +" /nix/store/hps5ziw9zq6mcjh9b7naaxawnqymws4m-jasper-2.0.16\n" +" /nix/store/hy2xn2jxm4wp7j86p08m9xdpxncskdgv-terraform-provider-pagerduty-1.2.1-bin\n" +" /nix/store/i10riha5s5dgafznk3gwn36fyr3cpxb4-libXinerama-1.1.4\n" +" /nix/store/i3kh8yq4kgkfn234pnwxnvxbrcgcckc8-curl-7.64.1-dev\n" +" /nix/store/i652w9gqbmc6k48lz3b02ncv7hpgc7nv-perl5.28.2-HTTP-Message-6.18\n" +" /nix/store/i8859i082xqnrhzg7h6gz2ylc5wbw5pa-libnl-3.4.0\n" +" /nix/store/id798ngchr83gc0mmqd3zlviljshjhvb-terraform-provider-nomad-1.3.0-bin\n" +" /nix/store/im1940h7b6pjlnh38q6lasdn8iybsv4v-python3.7-jmespath-0.9.4\n" +" /nix/store/in7wgxanbdycb9wpq1j29928gllc0ap6-terraform-provider-profitbricks-1.4.4-bin\n" +" /nix/store/irqcza91k5smn6f4dyvqzw0zjn50d58f-libssh2-1.8.2\n" +" /nix/store/isdbs6d2jk75kj0qk4s3prwlwcgkgalf-tf-plugin-env\n" +" /nix/store/ixycmxkr0wrz3gfxrnrdgcsk4gcyirpv-terraform-provider-azurestack-0.6.0-bin\n" +" /nix/store/j1px1l6vk39i3chghlwy9222jcjdfdq0-libcap-ng-0.7.9\n" +" /nix/store/jf6lfawjvwr6ggnd4lhc5w4dp9v3kgh4-libXdmcp-1.1.3\n" +" /nix/store/jjld4xam968mz645xh4g7i5zrnhsfyp9-terraform-provider-cobbler-1.0.1-bin\n" +" /nix/store/jn0bddfc3fzhnf5ns4s2khhzclswvzb2-libpcap-1.9.0\n" +" /nix/store/jsg4bi31drwy614hdkkwf32m4wz3im6g-libassuan-2.5.3\n" +" /nix/store/jszvy5lyyjbfi7mjr7s9bnbq9cyq858v-terraform-provider-external-1.1.2-bin\n" +" /nix/store/jvfc6r03a95aignzbfg987kspa04s0md-perl5.28.2-HTTP-Daemon-6.01\n" +" /nix/store/jwwkky1pn1fw3yiaxmc5k3brb0rqlwvq-graphite2-1.3.6\n" +" /nix/store/k1xlz5zy7rm2a428byz850c1igc2j1z8-readline-7.0p5\n" +" /nix/store/k3qhzd0x8a1z6h5kyifnv3axbfs7fy66-terraform-provider-statuscake-0.2.0-bin\n" +" /nix/store/k4v5havnf7pmcv40xadh8mb7b0nbcgxz-libglvnd-1.0.0\n" +" /nix/store/k59h7bs9307y7rb0z70vasvj8hd5pcn5-perl5.28.2-HTML-Tagset-3.20\n" +" /nix/store/k5vljkz5p59nrh50vx5k2790ksqcxjpc-terraform-provider-dme-0.1.0-bin\n" +" /nix/store/k7g175rls2pk34m23wqhplv8mbnsc0lc-pixman-0.38.4\n" +" /nix/store/kccb2k5hdjhdyxbxsri9lwwc4z1pvx6z-cups-2.2.11-lib\n" +" /nix/store/kds827ryxx16rwhrsdn9wnr2pxf5qaxm-terraform-provider-google-2.6.0-bin\n" +" /nix/store/kh18cbdb9f79gl58axwr8qq6c7bd0bl0-terraform-provider-acme-1.1.2-bin\n" +" /nix/store/kh2h5rnmm4gvjm8z7w2y511h15i7nhk9-gnum4-1.4.18\n" +" /nix/store/kmscm0qm9j480wpd1yh42b1g0zc6qbmv-nghttp2-1.38.0-lib\n" +" /nix/store/kqmg1xxd3vi37bqh7gdvi61bkp7wb9hi-terraform-provider-circonus-0.2.0-bin\n" +" /nix/store/kvjcl6plvmkm6i2lzd7wrkbiis3b4vhg-terraform-provider-mysql-1.5.1-bin\n" +" /nix/store/kvy2sz5lvi89lnh4rmw1df4jsnhqf1ay-libnftnl-1.1.2\n" +" /nix/store/l6ns1zcd18j9708y3agxgi0kihs4zc7i-terraform-provider-softlayer-0.0.1-bin\n" +" /nix/store/l8zqmzg19i62iz4argyjjr071rid3q9b-terraform-provider-cloudflare-1.13.0-bin\n" +" /nix/store/l9821zngvlh8bd6mlyzvi1mc754dyhjz-terraform-provider-libvirt-0.5.1-bin\n" +" /nix/store/lgrhsbfmpf1cjbpig8llxfrfb6xhz7xv-terraform-provider-scaleway-1.9.2-bin\n" +" /nix/store/lnzh3cjjcbafh6wsivw10wl60g7xplxj-libXrandr-1.5.2\n" +" /nix/store/lr9yhdbn8a3la69j56cz0vi1qva973dv-kbd-2.0.4\n" +" /nix/store/lswf09qbkkrqd0rgzaqyrkr44lf78y9x-libXext-1.3.4\n" +" /nix/store/lvqp39d4hx776nkw3a0qfnvvjmnj49hc-procps-3.3.15\n" +" /nix/store/m2n4drah6566qlccaabjhnnl4slql3cd-python3.7-pysocks-1.6.8\n" +" /nix/store/m65jki67b02la5k5r9vgddcp13l32lw5-python3.7-httplib2-0.12.3\n" +" /nix/store/m6hisb1d7q1c4z0s3icax40gynz4f8fl-gmp-6.1.2\n" +" /nix/store/mmjbmvw64yl2756y1zvsxk0ic0nhzq2a-libnfnetlink-1.0.1\n" +" /nix/store/mn0nzy294n07x1b92m9n0rwrv7z1441m-libunistring-0.9.10\n" +" /nix/store/mp1hzpgp3sa6xac8dc7rldh5rab8lk2w-perl5.28.2-Test-Needs-0.002006\n" +" /nix/store/mpnl3p6mzm71vci81r0h346jywm6863s-perl5.28.2-Encode-Locale-1.05\n" +" /nix/store/mrclkdxryhjd6i36hlad6fwahjd14fmg-libpng-apng-1.6.37\n" +" /nix/store/msa690459q4n9fiq125gsfambbd62qb4-libdaemon-0.14\n" +" /nix/store/msfkr5yqdxjx5cm24pvn3q1552rsjn8h-libev-4.25\n" +" /nix/store/mvmjdim7dn589inb8dsjxap08h4ip4h5-terraform-provider-huaweicloud-1.4.0-bin\n" +" /nix/store/n1dcmv0ii513dhlnllc790vfn8i9j9lj-python3.7-Jinja2-2.10.1\n" +" /nix/store/n1mrfbzlh3cjm9mfyrp48pybl3sg4717-terraform-provider-vsphere-1.10.0-bin\n" +" /nix/store/n1y9i0bv0sg8n8759zd6smr2zjyn8jf3-python3.7-paramiko-2.4.2\n" +" /nix/store/n2mzl8vljdksdqybihdy9mm5v7hm19q5-python3.7-idna-2.8\n" +" /nix/store/n3rakrhhvi3bb0ffnjs51drmy157p51q-terraform-provider-vcd-2.1.0-bin\n" +" /nix/store/n6z00dm6a5fdv935v8bv59909ra51xli-npth-1.6\n" +" /nix/store/n7wdfylfi5wnrjdg4im9v2q9gnl99mmb-terraform-provider-archive-1.2.2-bin\n" +" /nix/store/nc8x0pwchcc9xiv1nsj9idvpnfvkhh8p-terraform-provider-datadog-1.9.0-bin\n" +" /nix/store/ndbpc44lv43k7jnb0ip1qwk8f0slx685-bash-interactive-4.4-p23-dev\n" +" /nix/store/ndjjyr4rqibzkgs8w55bx2idhnckh39p-libidn2-2.1.1a\n" +" /nix/store/nfn8wgiqf418y444fch4bpf2ay6ca55i-curl-7.64.1-man\n" +" /nix/store/ni4nc256xs4f5hmhlhybxl8k40fwi5m3-libedit-20190324-3.1\n" +" /nix/store/np4ikymr5fq5iknjfrwrgqmcsid4dmw9-terraform-provider-consul-2.3.0-bin\n" +" /nix/store/nq2x9w3rjd5l2yvlv328i19ljar8bdab-libidn-1.35\n" +" /nix/store/nvyhmkghwxh5f1wiid27vzxa0ddx929p-python3.7-packaging-19.0\n" +" /nix/store/nwhvl00i2wa4ms26lszk36vwir90jd3x-libvirt-4.10.0\n" +" /nix/store/p00q64lbln1z9kfgpd2r6qhk0kc7i7w7-terraform-provider-oneandone-1.3.0-bin\n" +" /nix/store/p19dhs366b9zbbhs61xfw7d77sk9mkjr-terraform-provider-cloudscale-1.1.0-bin\n" +" /nix/store/p8s6295x84d594sxvzml8rsxqjdghmc5-cairo-1.16.0\n" +" /nix/store/p9rjwvja55djz5g2qxyc9wzcpmska0ql-terraform-provider-dyn-1.1.0-bin\n" +" /nix/store/pb6r7dllpfw5cbhpmv2v2kms9a57r4v5-terraform-provider-tls-2.0.1-bin\n" +" /nix/store/pfd5p3pyfrkwxh42j491kkqgl8n9aa67-perl5.28.2-TermReadKey-2.38\n" +" /nix/store/pk6r8sd18gmxns8r73qi2yrmzf4f4cp0-terraform-provider-arukas-1.1.0-bin\n" +" /nix/store/pknq6p5h43zm4r0dgjnfywql04hdv3js-atk-2.32.0\n" +" /nix/store/pvsfn6d0byl3hfwnyfg21yivyj8iff8s-terraform-provider-opentelekomcloud-1.8.0-bin\n" +" /nix/store/pvzbhdzqm4i20v3flr5mf7yfs7n2lrvg-python3.7-dnspython-1.16.0\n" +" /nix/store/pwkjsnbgb4mw0x5r5zh8s7c9wqryhmbl-dmidecode-3.2\n" +" /nix/store/pwnppsfjfxibhwhf598l7mx31i8154j9-bison-3.3.2\n" +" /nix/store/q0ndxs1vqdy5r749h5hhhbixgyf5yasx-terraform-provider-opsgenie-0.1.0-bin\n" +" /nix/store/qbwcp86aslamyhhmf2xx0l5d17dyg2jh-libmnl-1.0.4\n" +" /nix/store/qd4j58ykdkg9yvy8kvgh0i00gacy0ldm-perl-5.28.2\n" +" /nix/store/qgr66z24rfbb8cc965rr2sklh38p083n-git-crypt-0.6.0\n" +" /nix/store/qhad1pgmn3z406pgk345281xb5zjqrkm-libelf-0.8.13\n" +" /nix/store/qpj9rsal85rc94pizrkwb3c5nkivlfcl-p11-kit-0.23.14\n" +" /nix/store/qq59cnpcbnp4p054ipbs54fv946r4qr8-python3.7-boto-2.49.0\n" +" /nix/store/r3x6y48q13qwl9x1wwz37002b7fhyidv-python3.7-asn1crypto-0.24.0\n" +" /nix/store/r54ql4g0hcxzp15sfjiagd1dmxh4s8n6-python3.7-bcrypt-3.1.6\n" +" /nix/store/r6mrgd9k1jzzqrhphrg1qgxvgvbka7p8-pcre2-10.33\n" +" /nix/store/r7lhx3aqyils26h7wbxbgf376c0n4ab5-libssh2-1.8.2-dev\n" +" /nix/store/rcn9d2q4mpapxf4qd54hkqz32ljhv0rw-util-linux-2.33.2\n" +" /nix/store/rf104cwz7kaa51s49n4c2aar0jrrj8px-nghttp2-1.38.0-dev\n" +" /nix/store/ricz15lpkjrasc5cpzp6l60iwlc87wv3-avahi-0.7\n" +" /nix/store/rj8xd9ajm3wqjz1vfkignlp011fss53q-bzip2-1.0.6.0.1-bin\n" +" /nix/store/rk78bh2s5yjpmgdhzqlf1hnj6ij0h20n-terraform-provider-tfe-0.8.2-bin\n" +" /nix/store/rl2z4bb7wkfp0g12ccqffh287qal1109-kmod-26\n" +" /nix/store/rs21a235ix9v8y4hgazkzi6g1x5dqf7v-terraform-provider-netlify-0.1.0-bin\n" +" /nix/store/ryinn9xa3g8bn55nj1h54ypnlp9naq6i-stdenv-linux\n" +" /nix/store/rzfzb501miszas14xq6cr3c04m8kkdrb-terraform-0.11.14-bin\n" +" /nix/store/s3m5z3wxm94c0bfyjxmqf6i0gf1bpx90-libaio-0.3.110\n" +" /nix/store/s5f3vpmig33nk4zyk228q55wdydd3pc2-python3-3.7.3\n" +" /nix/store/s7p4iij8p4hi6bmc2bf3flyf6wa6yzrj-terraform-provider-dns-2.1.1-bin\n" +" /nix/store/s7rqxrfb631i53dfl90gac35095jyypq-util-linux-2.33.2-bin\n" +" /nix/store/scdscan356g79qb7cf776gy7src22zbl-terraform-provider-grafana-1.3.0-bin\n" +" /nix/store/sfrh0r54ykfzv62h17gi8hm6778j7k0l-libyaml-0.2.1\n" +" /nix/store/shf6d1928fzxcaz6zh0bhcqv3xhvxhjd-terraform-provider-linode-1.6.0-bin\n" +" /nix/store/skkpbcqavjd8q0zmd94js6nz7pgbvpfl-mirrors-list\n" +" /nix/store/sm4yylq92rip64wdk3iniy91w48a90ia-openssl-1.0.2r\n" +" /nix/store/sn2cydjzikl3rws2nfa7pdvayb45brrd-terraform-provider-logicmonitor-1.2.0-bin\n" +" /nix/store/ssr1y1736h7c6p8vs76iyxwg5h889x7d-terraform-provider-dnsimple-0.1.0-bin\n" +" /nix/store/sw6n4yz49cz5vm4ggpk2l5j1vngac8j2-terraform-provider-secret-1.0.0-bin\n" +" /nix/store/sw6vlm5g6r6sivlncz7vh8ps7v7r22aa-terraform-provider-brightbox-1.1.2-bin\n" +" /nix/store/v31bag67wm17wkdg7zr9yi62c5028y59-libXau-1.0.9\n" +" /nix/store/v5q3cnkjfy8rfacsjqn1nza93mbczgd5-gdk-pixbuf-2.38.1\n" +" /nix/store/v69ld4vcgkr4i4giv1nzl4kax9zx1fpa-python3.7-pyasn1-0.4.5\n" +" /nix/store/vbp6wnr2gyj50nabxgclkbqblmnwcnbg-terraform-provider-azuread-0.3.1-bin\n" +" /nix/store/vckbx0p1isjvmgjh7ppni3h87imazbzb-libcap-2.27-lib\n" +" /nix/store/vin4cp4m5af1mxkb2jqqi8xkf98ca2sv-python3.7-ansible-2.7.9\n" +" /nix/store/vkdh5ibsmzj6p53krnqqz1pv620f42r0-terraform-provider-logentries-1.0.0-bin\n" +" /nix/store/vqvmd2r9pf9f74jqipbhrn7wksiiy1jf-pcsclite-1.8.25-bin\n" +" /nix/store/vrrs5p13mykyniglgfdsn8xii9b7s850-terraform-provider-powerdns-0.1.0-bin\n" +" /nix/store/vzjwz11r1yy02xv07vx2577pqizzx83n-nettle-3.4.1\n" +" /nix/store/vzs0x1kaliybgk7yr9lrf6ad4x5v1k9y-libjpeg-turbo-2.0.2\n" +" /nix/store/wbbwikfkc7fbida822a5z9b4xmsnwm3d-python3.7-chardet-3.0.4\n" +" /nix/store/wccns8l8bav11z3xlhasmnkz383q1k9p-libnetfilter_conntrack-1.0.7\n" +" /nix/store/wf5nv1gzrx378icqmjgwl2isg7s8ly80-lvm2-2.03.01\n" +" /nix/store/wh8pg14c3ykmmnd342llbzjigahc54dw-terraform-provider-fastly-0.6.0-bin\n" +" /nix/store/wi2mn48l130r7wafvj757rvzfkla59if-pm-utils-1.4.1\n" +" /nix/store/wi4jm555w0rc1daiy2sz9iwrpk6cb2d8-terraform-provider-ibm-0.11.1-bin\n" +" /nix/store/wkby8pdmg4vpvbl0d85gynh103k2h1ky-nghttp2-1.38.0\n" +" /nix/store/wv8y2h4w7lxi9x6k8pzh3dxy7i4csfbm-terraform-provider-digitalocean-1.3.0-bin\n" +" /nix/store/wvccp35z40fj1v8xbz6czrm4bbiaqd45-perl5.28.2-HTTP-Negotiate-6.01\n" +" /nix/store/wxdxzvaj3mcmf3i9yqwinpcb26iz3pas-perl5.28.2-Test-Fatal-0.014\n" +" /nix/store/wy2alf2g85wym6i9n279d7a9nianx3is-curl-7.64.1-bin\n" +" /nix/store/wym0bhrfdx5ndfpx6y39c6j3pf2n6wak-libksba-1.3.5\n" +" /nix/store/x1idgjd7vs75nj9s3krimbfjvh27n06d-terraform-provider-librato-0.1.0-bin\n" +" /nix/store/x3rijvjjrch1fjs60lrw9xb7pidp817f-gtk+-2.24.32\n" +" /nix/store/x6zlzsjsd7m9mjkmxlp15vcay58g6a04-python3.7-pycryptodome-3.7.3\n" +" /nix/store/x987jpq3yswa2aj51d63vwszfdm3r8ld-terraform-provider-atlas-0.1.1-bin\n" +" /nix/store/xav1lh5jlgrz7amaz7b5ghrz0c273lji-python3.7-pyOpenSSL-19.0.0\n" +" /nix/store/xbcc8v50g7h7wqh892q7k22wb1ky8cg7-libevent-2.1.8\n" +" /nix/store/xbwr4gb4zgjmcrbx82zlcp1jfgcz75ya-python3.7-cryptography-2.6.1-dev\n" +" /nix/store/xdhh337yhl93x33vzd9davinrbr9x9iz-libmicrohttpd-0.9.63\n" +" /nix/store/xfgg45by0j5hxi1kdwh8x2pkfd67wwzd-nss-cacert-3.42.1\n" +" /nix/store/xkv7la24vsyn9n23wc1izcmmp7aifzb3-terraform-provider-packet-2.1.0-bin\n" +" /nix/store/xmy3chnan9iiag9apm7dd825cmlkiiij-libusb-1.0.22\n" +" /nix/store/xn8xmzxjx7i8wwfvbiwfgmv9mn4n45dk-terraform-provider-icinga2-0.2.0-bin\n" +" /nix/store/xs2k8driha83f9k017bkgch8lcl4z7w0-python3.7-ply-3.11\n" +" /nix/store/xv9pfis6ixrsv7z1jrmgagi25qljvg0d-python3.7-pynacl-1.3.0\n" +" /nix/store/xxwqa4rwfi97az8a6dl6vhqiyjvmnm9v-libsecret-0.18.8\n" +" /nix/store/xyx7dm2b6ylcdp38pfwcip9ssx0fdzga-libtool-2.4.6-lib\n" +" /nix/store/xzzf5h2f02bwjcph28vly4wklp13wb0g-perl5.28.2-HTML-Parser-3.72\n" +" /nix/store/y1v3g4m9bmmmvmw4z84m5fpmdy42lbr4-terraform-provider-selectel-2.1.0-bin\n" +" /nix/store/y20bvdwb0s95wa4gzhkkxd1xcc4c8whx-terraform-provider-postgresql-0.3.0-bin\n" +" /nix/store/y3x0fvlz4a30iajw3vd1rkg45vl3k15c-pcsclite-1.8.25\n" +" /nix/store/y48is3y65apgyjwlwiyzjay1dw19l19a-dns-root-data-2019-01-11\n" +" /nix/store/y5gfmqjp68h4fqq8z4p219pimm7ws49j-python3.7-cffi-1.12.3-dev\n" +" /nix/store/ybj0i3axzbkb4n4c4a5gz5lr3z70v7h3-bash-interactive-4.4-p23-man\n" +" /nix/store/ybsmcpfglj9fm5kjxyykbnwfjmhxrwfv-terraform-provider-google-beta-2.6.0-bin\n" +" /nix/store/yf4i32dx953p2dv2agfdyxdwg6ba0l61-python3.7-setuptools-41.0.1\n" +" /nix/store/yfmvcf5cslq4f9kv0vlmxksdgvick22d-libgpg-error-1.36\n" +" /nix/store/yh1w64xprl0rxmj8nvxpmikp6x3qvgdb-libffi-3.2.1\n" +" /nix/store/yi01h84z709wf02id8hsb170z53wvk7r-glibc-2.27-dev\n" +" /nix/store/yik0kf8fgxjj1rj3s4bsrx1y6smz8rhx-cdrtools-3.02a06\n" +" /nix/store/yjdcrd1lkzp8c7cawcpy40c4p3ngaw12-terraform-provider-rightscale-1.3.0-bin\n" +" /nix/store/ymn53mhfkkhs26qw708yv7bd7jmbp636-terraform-provider-nsxt-1.1.0-bin\n" +" /nix/store/yn7smb316b6d99wjw2v9fgxzbrqnq9jm-terraform-provider-gandi-1.0.0-bin\n" +" /nix/store/yr6qv6j9qrc03gl7bknw6p1fx1pzk0l9-terraform-provider-hcloud-1.9.0-bin\n" +" /nix/store/yrmrvha03pvdyi9ww2bi6xjpk5930sf8-glib-2.60.1\n" +" /nix/store/yvqaj61p81kd4bq3dyw64idqj61rwpka-terraform-provider-hedvig-1.0.3-bin\n" +" /nix/store/z0sqda5bg0l4p0851nw05h7hii0jj1kr-python3.7-PyYAML-5.1\n" +" /nix/store/z2darh83lb4rmsfnnyjc0hll51fyvj49-libSM-1.2.3\n" +" /nix/store/z4vgv1w5cmd6p90grfgr1k6m87fydr3g-terraform-provider-ovh-0.3.0-bin\n" +" /nix/store/z68464p6aafah8b8xcybkwyhmqdf0jgx-gnupg-2.2.15\n" +" /nix/store/z7jh25by0vv378gacjd01idi52dj688h-libtiff-4.0.10\n" +" /nix/store/z7n5a3kwjylsgnc1d271j4dn41m6shpz-libtirpc-1.1.4\n" +" /nix/store/z9fv0x6vwlx3xkcac3lg6v8g0figkx39-ncurses-6.1-20190112\n" +" /nix/store/za8dm1xsfslzdk4j434w869bngrygici-perl5.28.2-URI-1.76\n" +" /nix/store/zaq3w03j96qqhzpcfs9yacwa98sdsmiv-terraform-provider-oci-3.24.1-bin\n" +" /nix/store/zckvgwnyah69mmwn0g5vr4y85rmzwld9-libsodium-1.0.17\n" +" /nix/store/zdfchj49phsp0sahcvdfp8ipc0chakg3-terraform-provider-rabbitmq-1.0.0-bin\n" +" /nix/store/zh1q7yvyaxlcmj3n6g0rrdaq0v73pp90-linux-pam-1.3.1\n" +" /nix/store/znjkmjz0pgckxxzq0m9d17isnsd9s03q-cracklib-2.9.7\n" +" /nix/store/zxdnpb673bf27hcqzvssv5629m4x5bjv-freetype-2.10.0\n" +"copying path '/nix/store/drdzgwhnqjvq4g1aqsyz56c04k6dxnbi-bash-interactive-4.4-p23-doc' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/a2rr0irv2ssvvphvafgrxy4di0pkkagn-audit-2.8.5' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/8xy69pkisipvdmrpm1nmbi6qa2c6lhn0-bash-interactive-4.4-p23-info' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/ybj0i3axzbkb4n4c4a5gz5lr3z70v7h3-bash-interactive-4.4-p23-man' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/2dfjlvp38xzkyylwpavnh61azi0d168b-binutils-2.31.1' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/f7zcmzqcavbj7bp1dlfk86f9bkqvk9p3-bridge-utils-1.5' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/206dvjl6595dk40dli12ziv393ww54wl-bzip2-1.0.6.0.1' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/8aylwgi9nb6hsgz6620fzsllbc7h2rx1-c-ares-1.15.0' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/rj8xd9ajm3wqjz1vfkignlp011fss53q-bzip2-1.0.6.0.1-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/znjkmjz0pgckxxzq0m9d17isnsd9s03q-cracklib-2.9.7' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/nfn8wgiqf418y444fch4bpf2ay6ca55i-curl-7.64.1-man' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/6whclwjzwg46s0dkxwk1xz8cdcxnkd3y-db-4.8.30' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/2k46270d0h3gqj1c0wgx8prnj51jqryd-db-5.3.28' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/8gn2b5vvlazg608cj1y5l4igp9rckmnq-dejavu-fonts-minimal-2.37' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/pwkjsnbgb4mw0x5r5zh8s7c9wqryhmbl-dmidecode-3.2' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/y48is3y65apgyjwlwiyzjay1dw19l19a-dns-root-data-2019-01-11' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/8dl5c7n4555lr6qipki2424652gf8az8-ebtables-2.0.10-4' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/h02lb0p8krj1smsrid2n44ak058bbd82-expand-response-params' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/4jw2677fvb11aj1bal9a2iksqz0mk80m-expat-2.2.6' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/bd1hz6m8gh9m91hikjhq7aiq2khdkx2r-fontconfig-2.12.6' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/8ndwixznskf4zbf6h96ww4j8ap4j8067-fribidi-1.0.5' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/920nr51iw7qaplqjlqrlnql9g5ljq3vp-gdbm-1.18.1' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/m6hisb1d7q1c4z0s3icax40gynz4f8fl-gmp-6.1.2' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/kh2h5rnmm4gvjm8z7w2y511h15i7nhk9-gnum4-1.4.18' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/6554dpyahvcs49dmv434aky6bfkmqb30-gnumake-4.2.1' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/pwnppsfjfxibhwhf598l7mx31i8154j9-bison-3.3.2' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/jwwkky1pn1fw3yiaxmc5k3brb0rqlwvq-graphite2-1.3.6' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/6mz512j183wj7qas2qm6zkrks5k8rh00-gettext-0.19.8.1' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/4i1mw6av3d6pr9bqggb4hnv6cykbrhhi-kexec-tools-2.0.19' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/93rldbdly90q16lzk7hzilhk4qkdpqfq-keyutils-1.6-lib' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/rl2z4bb7wkfp0g12ccqffh287qal1109-kmod-26' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/4qq5hh1r6sqb0kpxc305rb468s45j4aw-libICE-1.0.9' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/v31bag67wm17wkdg7zr9yi62c5028y59-libXau-1.0.9' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/jf6lfawjvwr6ggnd4lhc5w4dp9v3kgh4-libXdmcp-1.1.3' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/s3m5z3wxm94c0bfyjxmqf6i0gf1bpx90-libaio-0.3.110' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/6b2jabk1scwhhk9bz7wjzycvmkiw419d-libapparmor-2.13.1' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/vckbx0p1isjvmgjh7ppni3h87imazbzb-libcap-2.27-lib' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/j1px1l6vk39i3chghlwy9222jcjdfdq0-libcap-ng-0.7.9' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/yik0kf8fgxjj1rj3s4bsrx1y6smz8rhx-cdrtools-3.02a06' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/msa690459q4n9fiq125gsfambbd62qb4-libdaemon-0.14' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/qhad1pgmn3z406pgk345281xb5zjqrkm-libelf-0.8.13' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/msfkr5yqdxjx5cm24pvn3q1552rsjn8h-libev-4.25' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/yh1w64xprl0rxmj8nvxpmikp6x3qvgdb-libffi-3.2.1' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/yfmvcf5cslq4f9kv0vlmxksdgvick22d-libgpg-error-1.36' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/0jl2dhydfh3jbfpkgkrixisqkhj12d4y-libffi-3.2.1-dev' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/jsg4bi31drwy614hdkkwf32m4wz3im6g-libassuan-2.5.3' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/94nrq9paz335s155x9za8n7kb0q3y211-libgcrypt-1.8.4' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/nq2x9w3rjd5l2yvlv328i19ljar8bdab-libidn-1.35' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/vzs0x1kaliybgk7yr9lrf6ad4x5v1k9y-libjpeg-turbo-2.0.2' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/hpmni5y805q7a07q9sn3nwjk4i2m2jl5-libkrb5-1.17' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/hps5ziw9zq6mcjh9b7naaxawnqymws4m-jasper-2.0.16' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/b6pdz8g070kbf0rdavjz6rip7sx06r8h-libkrb5-1.17-dev' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/wym0bhrfdx5ndfpx6y39c6j3pf2n6wak-libksba-1.3.5' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/qbwcp86aslamyhhmf2xx0l5d17dyg2jh-libmnl-1.0.4' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/mmjbmvw64yl2756y1zvsxk0ic0nhzq2a-libnfnetlink-1.0.1' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/kvy2sz5lvi89lnh4rmw1df4jsnhqf1ay-libnftnl-1.1.2' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/wccns8l8bav11z3xlhasmnkz383q1k9p-libnetfilter_conntrack-1.0.7' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/i8859i082xqnrhzg7h6gz2ylc5wbw5pa-libnl-3.4.0' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/jn0bddfc3fzhnf5ns4s2khhzclswvzb2-libpcap-1.9.0' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/7b7nbb0w2iwskwhzjhfwrif631h4smia-libpciaccess-0.14' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/gsl1dw8ycrdvlzczsl59mkz0qpbwcmz1-iptables-1.8.2' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/mrclkdxryhjd6i36hlad6fwahjd14fmg-libpng-apng-1.6.37' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/4z62pandn85xhcc5vazmi29cs2yps47b-iproute2-5.0.0' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/zxdnpb673bf27hcqzvssv5629m4x5bjv-freetype-2.10.0' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/hg863b95fxv9zlk008qjyf87qgyx58h1-libseccomp-2.4.1-lib' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/gn5cd1z252aip0rvds71g9mgfhh6i8p7-fontconfig-2.12.6-lib' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/zckvgwnyah69mmwn0g5vr4y85rmzwld9-libsodium-1.0.17' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/5l3967kll8m6s66zprzwb2p6vf2mh5yd-libtasn1-4.13' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/z7jh25by0vv378gacjd01idi52dj688h-libtiff-4.0.10' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/z7n5a3kwjylsgnc1d271j4dn41m6shpz-libtirpc-1.1.4' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/xyx7dm2b6ylcdp38pfwcip9ssx0fdzga-libtool-2.4.6-lib' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/mn0nzy294n07x1b92m9n0rwrv7z1441m-libunistring-0.9.10' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/9hysgvp7qrfcil4b5qhwdq2vm9hism13-libxcb-1.13.1' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/ndjjyr4rqibzkgs8w55bx2idhnckh39p-libidn2-2.1.1a' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/69vq0a9sqynmz335apm8zgyjdmq34s5j-libX11-1.6.7' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/b7w6bpx5z0ncy35kqxvmpg4lwrnc8jf2-libxml2-2.9.9' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/ag3fp30cz58ijm2yyy5adp1f3kw814b5-libXcomposite-0.4.5' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/lswf09qbkkrqd0rgzaqyrkr44lf78y9x-libXext-1.3.4' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/aqp0mrdbhvkm8rl1z0p2rkqnz6pbclhq-libXfixes-5.0.3' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/cd09qv56inq4gwa89656r4n0lq0vgidw-libXi-1.7.9' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/i10riha5s5dgafznk3gwn36fyr3cpxb4-libXinerama-1.1.4' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/dvsw0fhfzqf4xg0q2idhs02rhwn4k8cv-libXrender-0.9.10' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/k4v5havnf7pmcv40xadh8mb7b0nbcgxz-libglvnd-1.0.0' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/3s4fr71ykyw54kyyqavd0ba42klg0bhf-libXcursor-1.2.0' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/dy437h3f5i500gv6znll974c87grzh3l-libXft-2.3.3' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/lnzh3cjjcbafh6wsivw10wl60g7xplxj-libXrandr-1.5.2' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/sfrh0r54ykfzv62h17gi8hm6778j7k0l-libyaml-0.2.1' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/c7jkmfjhl3jkgnkrhh021vrqry7zplc1-linux-headers-4.19.16' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/zh1q7yvyaxlcmj3n6g0rrdaq0v73pp90-linux-pam-1.3.1' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/yi01h84z709wf02id8hsb170z53wvk7r-glibc-2.27-dev' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/lr9yhdbn8a3la69j56cz0vi1qva973dv-kbd-2.0.4' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/5qnlfx9qncn0fcw6mbfj6j58pz0cv0p3-binutils-wrapper-2.31.1' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/apcaggi0q3vrb4ha1b07cjxiim2li5ly-gcc-7.4.0' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/caa29d4y2zip0ly9mcc7f4w94blw8k60-lz4-1.9.1' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/ds1prvgw3i3ic8c7axyrw4lwm3d0gqab-gcc-wrapper-7.4.0' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/7mmn8ri08z48vfj69c2h66f3g349ilq1-mailcap-2.1.48' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/skkpbcqavjd8q0zmd94js6nz7pgbvpfl-mirrors-list' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/z9fv0x6vwlx3xkcac3lg6v8g0figkx39-ncurses-6.1-20190112' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/vzjwz11r1yy02xv07vx2577pqizzx83n-nettle-3.4.1' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/ni4nc256xs4f5hmhlhybxl8k40fwi5m3-libedit-20190324-3.1' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/h8898ysg2s23k6palhxy9a5sbgrvvrcy-nfs-utils-2.3.3-lib' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/wkby8pdmg4vpvbl0d85gynh103k2h1ky-nghttp2-1.38.0' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/kmscm0qm9j480wpd1yh42b1g0zc6qbmv-nghttp2-1.38.0-lib' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/n6z00dm6a5fdv935v8bv59909ra51xli-npth-1.6' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/xfgg45by0j5hxi1kdwh8x2pkfd67wwzd-nss-cacert-3.42.1' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/f11valqiyik1ggdlnhg3ibwgrj1imidb-numactl-2.0.12' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/g4qqgmrm254axgndybnpwg7s780bxy1a-numad-0.5' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/sm4yylq92rip64wdk3iniy91w48a90ia-openssl-1.0.2r' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/qpj9rsal85rc94pizrkwb3c5nkivlfcl-p11-kit-0.23.14' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/fhgiisqjpzwl8z4fchgc07avg1azmp0r-cyrus-sasl-2.1.27' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/xbcc8v50g7h7wqh892q7k22wb1ky8cg7-libevent-2.1.8' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/irqcza91k5smn6f4dyvqzw0zjn50d58f-libssh2-1.8.2' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/18rr3rg32imsnfyx6zb6s8lc8qpkdr74-nghttp2-1.38.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/5pjazw71xk4kysxrzacgjl4iai691k25-curl-7.64.1' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/r7lhx3aqyils26h7wbxbgf376c0n4ab5-libssh2-1.8.2-dev' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/wy2alf2g85wym6i9n279d7a9nianx3is-curl-7.64.1-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/rf104cwz7kaa51s49n4c2aar0jrrj8px-nghttp2-1.38.0-dev' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/b77nn2r1c8cqpr9prh1ldwr3m6xdrkpa-openldap-2.4.47' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/2ar3zk5fjr34ys2dqnsfbb678x6fdlj4-openssh-7.9p1' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/8yy3wngrdcpmjyw2ryas1y4wwhbd1356-patch-2.7.6' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/61shjilahl0d237fg9b3z3chza2lgms4-patchelf-0.9' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/r6mrgd9k1jzzqrhphrg1qgxvgvbka7p8-pcre2-10.33' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/qd4j58ykdkg9yvy8kvgh0i00gacy0ldm-perl-5.28.2' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/mpnl3p6mzm71vci81r0h346jywm6863s-perl5.28.2-Encode-Locale-1.05' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/85hh7apv9n3gganpnnq36zvlwm126mdh-openssl-1.0.2r-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/k59h7bs9307y7rb0z70vasvj8hd5pcn5-perl5.28.2-HTML-Tagset-3.20' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/3mgn9jnjzj1rgxclbixk5xa0kkx9xpw3-openssl-1.0.2r-dev' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/xzzf5h2f02bwjcph28vly4wklp13wb0g-perl5.28.2-HTML-Parser-3.72' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/bh412cii40qpzc20pzd48dq45jv9xm5a-perl5.28.2-HTTP-Date-6.02' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/5x1551gw825apcsnwx8gzfnmiapbz8yl-perl5.28.2-IO-HTML-1.001' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/0jwyd55g8nfhm25a0bh1j1by6afdriic-perl5.28.2-File-Listing-6.04' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/50rywa1m6asdz1y78a6dpa0xf98vm01v-perl5.28.2-LWP-MediaTypes-6.04' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/pfd5p3pyfrkwxh42j491kkqgl8n9aa67-perl5.28.2-TermReadKey-2.38' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/mp1hzpgp3sa6xac8dc7rldh5rab8lk2w-perl5.28.2-Test-Needs-0.002006' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/8vqr6vbvyzlpsk6q0mnj93sf5j1wr5qa-perl5.28.2-Test-RequiresInternet-0.05' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/b2rwzjp56yzd4jg2csx568h2dgj1l3l2-perl5.28.2-Try-Tiny-0.30' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/za8dm1xsfslzdk4j434w869bngrygici-perl5.28.2-URI-1.76' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/wxdxzvaj3mcmf3i9yqwinpcb26iz3pas-perl5.28.2-Test-Fatal-0.014' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/i652w9gqbmc6k48lz3b02ncv7hpgc7nv-perl5.28.2-HTTP-Message-6.18' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/fky41n197z9n737kbih4j7ncnh7cngnz-perl5.28.2-Net-HTTP-6.18' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/7gwvcm8dc24vnphbx85q1afaxhfhac28-perl5.28.2-HTTP-Cookies-6.04' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/jvfc6r03a95aignzbfg987kspa04s0md-perl5.28.2-HTTP-Daemon-6.01' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/wvccp35z40fj1v8xbz6czrm4bbiaqd45-perl5.28.2-HTTP-Negotiate-6.01' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/hnvmacd16kzmwcsavzkssrqj2kiryy2p-perl5.28.2-WWW-RobotRules-6.02' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/k7g175rls2pk34m23wqhplv8mbnsc0lc-pixman-0.38.4' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/91a8wnca647kfw67sk0iykdbyjpr8430-perl5.28.2-libwww-perl-6.38' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/xav1lh5jlgrz7amaz7b5ghrz0c273lji-python3.7-pyOpenSSL-19.0.0' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/43i41p1n1sxssmqpf9jp5x4gcy6r2fl6-git-2.21.0' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/bxps2h6axpqrjxcmib344a3immy3gvhd-readline-6.3p08' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/k1xlz5zy7rm2a428byz850c1igc2j1z8-readline-7.0p5' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/2xhsrw4ws6kc4x3983wdwwlnim27c6iz-shadow-4.6' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/715lcljfyp8grxlmaf51pn0n3ml3dwgg-bash-interactive-4.4-p23' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/ap4sr1n0wlgmybxbw3pvq8klh8snc3n8-sqlite-3.28.0' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/ndbpc44lv43k7jnb0ip1qwk8f0slx685-bash-interactive-4.4-p23-dev' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/3xzkc4wyadr3vrva2q320axjr6cyb43n-python-2.7.16' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/s5f3vpmig33nk4zyk228q55wdydd3pc2-python3-3.7.3' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/0w6l8kh3d30kg3nxc8xyi84gmrfxjnns-git-2.21.0' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/aqgl1dqd6lr7jr9knqsyyq09bm0ibw7s-python3.7-cffi-1.12.3' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/9fvjgcjn1d0c9476qlr05psvwljwzq59-python3.7-cryptography-2.6.1' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/yf4i32dx953p2dv2agfdyxdwg6ba0l61-python3.7-setuptools-41.0.1' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/7crry947d1xvp1f15c6q089l0gcy5hpc-stdenv-linux' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/b2wy5p5bykcnkwz5q1w8qq4qfzr4arc7-python3.7-MarkupSafe-1.1.1' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/z0sqda5bg0l4p0851nw05h7hii0jj1kr-python3.7-PyYAML-5.1' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/n1dcmv0ii513dhlnllc790vfn8i9j9lj-python3.7-Jinja2-2.10.1' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/r3x6y48q13qwl9x1wwz37002b7fhyidv-python3.7-asn1crypto-0.24.0' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/02nzlzdw0kiici9368jp5s84cpbqxkva-python3.7-certifi-2018.11.29' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/wbbwikfkc7fbida822a5z9b4xmsnwm3d-python3.7-chardet-3.0.4' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/pvzbhdzqm4i20v3flr5mf7yfs7n2lrvg-python3.7-dnspython-1.16.0' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/m65jki67b02la5k5r9vgddcp13l32lw5-python3.7-httplib2-0.12.3' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/n2mzl8vljdksdqybihdy9mm5v7hm19q5-python3.7-idna-2.8' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/31l04a1yxxdbdpzdp8mpfk96rhj3bg2c-python3.7-netaddr-0.7.19' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/xs2k8driha83f9k017bkgch8lcl4z7w0-python3.7-ply-3.11' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/v69ld4vcgkr4i4giv1nzl4kax9zx1fpa-python3.7-pyasn1-0.4.5' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/im1940h7b6pjlnh38q6lasdn8iybsv4v-python3.7-jmespath-0.9.4' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/9xb22l3577nznvd6dqqis6ixgmwq9ygh-python3.7-pycparser-2.19' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/x6zlzsjsd7m9mjkmxlp15vcay58g6a04-python3.7-pycryptodome-3.7.3' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/y5gfmqjp68h4fqq8z4p219pimm7ws49j-python3.7-cffi-1.12.3-dev' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/gg469jh0m4dk4b0x6s44ziad69czbv22-python3.7-pycrypto-3.7.3' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/5ydkc9jcaaxlz58dr7gvyhi3gcmafsfy-python3.7-pyparsing-2.3.1' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/m2n4drah6566qlccaabjhnnl4slql3cd-python3.7-pysocks-1.6.8' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/dy5wi2sqnhbnlpvjr8a0z96id1mq243j-python3.7-six-1.12.0' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/ryinn9xa3g8bn55nj1h54ypnlp9naq6i-stdenv-linux' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/r54ql4g0hcxzp15sfjiagd1dmxh4s8n6-python3.7-bcrypt-3.1.6' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/9pa3p1rqhnvlrngaqsx09766cl1j6zf3-python3.7-httpretty-0.9.6' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/nvyhmkghwxh5f1wiid27vzxa0ddx929p-python3.7-packaging-19.0' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/xv9pfis6ixrsv7z1jrmgagi25qljvg0d-python3.7-pynacl-1.3.0' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/xbwr4gb4zgjmcrbx82zlcp1jfgcz75ya-python3.7-cryptography-2.6.1-dev' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/1kz91g5mfj271lj5kxz2m1axcs2yqafy-thin-provisioning-tools-0.7.6' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/n1y9i0bv0sg8n8759zd6smr2zjyn8jf3-python3.7-paramiko-2.4.2' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/7256h1y98mmzsckwk2x7i3v3cxmvgrmq-python3.7-pyOpenSSL-19.0.0-dev' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/20wmykp8fj2izxdj8lic8ggcfpdid5ka-tzdata-2019a' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/ch6pz5kfg0bd3sfyf1813cpskg7lidns-python3.7-urllib3-1.24.2' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/749qksf79hvn0aprcznd9bwfv550qwh3-go-1.12.1' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/d0wcd9mid6067i6va19lwiv29hln6n2j-python3.7-requests-2.21.0' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/rzfzb501miszas14xq6cr3c04m8kkdrb-terraform-0.11.14-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/qq59cnpcbnp4p054ipbs54fv946r4qr8-python3.7-boto-2.49.0' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/479dvd7q6c18l3jl2myhfxmfsjbqjjch-python3.7-dopy-2016-01-04' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/kh18cbdb9f79gl58axwr8qq6c7bd0bl0-terraform-provider-acme-1.1.2-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/vin4cp4m5af1mxkb2jqqi8xkf98ca2sv-python3.7-ansible-2.7.9' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/gydzhj2y5j1ggbainbilvpxi5glw5hmf-terraform-provider-alicloud-1.41.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/0rc1jyfbxwffmsphyv2pfnxd6smysc1l-terraform-provider-ansible-0.0.4-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/n7wdfylfi5wnrjdg4im9v2q9gnl99mmb-terraform-provider-archive-1.2.2-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/pk6r8sd18gmxns8r73qi2yrmzf4f4cp0-terraform-provider-arukas-1.1.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/x987jpq3yswa2aj51d63vwszfdm3r8ld-terraform-provider-atlas-0.1.1-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/fwvdxglj9asp4f90ihry29n2fm8a6i09-terraform-provider-aws-2.9.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/vbp6wnr2gyj50nabxgclkbqblmnwcnbg-terraform-provider-azuread-0.3.1-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/7mqpbfs391s9hbnfzkpgw3inj8mkldr8-terraform-provider-azurerm-1.27.1-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/ixycmxkr0wrz3gfxrnrdgcsk4gcyirpv-terraform-provider-azurestack-0.6.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/1hml3hx7qlbkv139khazb24jh69nngcd-terraform-provider-bigip-0.12.2-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/63k736kr346ncpzv5yiqiyyyiqpa2h8m-terraform-provider-bitbucket-1.0.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/sw6vlm5g6r6sivlncz7vh8ps7v7r22aa-terraform-provider-brightbox-1.1.2-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/d7rh74cch3ybp9r239j5c2c1rb0kx3pa-terraform-provider-chef-0.1.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/kqmg1xxd3vi37bqh7gdvi61bkp7wb9hi-terraform-provider-circonus-0.2.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/7k3hvg4sfpr6y2bg8b7x9mkb0d2p3scr-terraform-provider-clc-0.1.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/l8zqmzg19i62iz4argyjjr071rid3q9b-terraform-provider-cloudflare-1.13.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/p19dhs366b9zbbhs61xfw7d77sk9mkjr-terraform-provider-cloudscale-1.1.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/0z8i6sq8mg138qnifr1z37y780xkk8hf-terraform-provider-cloudstack-0.2.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/jjld4xam968mz645xh4g7i5zrnhsfyp9-terraform-provider-cobbler-1.0.1-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/np4ikymr5fq5iknjfrwrgqmcsid4dmw9-terraform-provider-consul-2.3.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/nc8x0pwchcc9xiv1nsj9idvpnfvkhh8p-terraform-provider-datadog-1.9.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/wv8y2h4w7lxi9x6k8pzh3dxy7i4csfbm-terraform-provider-digitalocean-1.3.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/k5vljkz5p59nrh50vx5k2790ksqcxjpc-terraform-provider-dme-0.1.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/g63hwfkd4yjncqh81ndn9vbmghdv41ng-terraform-provider-digitalocean-1.3.0' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/s7p4iij8p4hi6bmc2bf3flyf6wa6yzrj-terraform-provider-dns-2.1.1-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/ssr1y1736h7c6p8vs76iyxwg5h889x7d-terraform-provider-dnsimple-0.1.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/amlnqi4vvmpb9gjmyh1vr5hr2py12ss2-terraform-provider-docker-1.1.1-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/p9rjwvja55djz5g2qxyc9wzcpmska0ql-terraform-provider-dyn-1.1.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/8z5vplmgshflm7yixhp8q7hy11xxxd8a-terraform-provider-elasticsearch-0.6.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/jszvy5lyyjbfi7mjr7s9bnbq9cyq858v-terraform-provider-external-1.1.2-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/wh8pg14c3ykmmnd342llbzjigahc54dw-terraform-provider-fastly-0.6.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/0bdf1xn7p6xzk008yr6cahq3wjlvah5g-terraform-provider-flexibleengine-1.5.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/yn7smb316b6d99wjw2v9fgxzbrqnq9jm-terraform-provider-gandi-1.0.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/95rd64vii9j6h31fcr9lba8m8940zfpj-terraform-provider-github-2.0.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/dz9dqcnz8v9cy54x5hax599zjwckp0kd-terraform-provider-gitlab-1.3.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/kds827ryxx16rwhrsdn9wnr2pxf5qaxm-terraform-provider-google-2.6.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/ybsmcpfglj9fm5kjxyykbnwfjmhxrwfv-terraform-provider-google-beta-2.6.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/scdscan356g79qb7cf776gy7src22zbl-terraform-provider-grafana-1.3.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/yr6qv6j9qrc03gl7bknw6p1fx1pzk0l9-terraform-provider-hcloud-1.9.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/yvqaj61p81kd4bq3dyw64idqj61rwpka-terraform-provider-hedvig-1.0.3-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/hbs2vrw1y8y1qz1hi71jaz0j3pl95qfs-terraform-provider-helm-0.9.1-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/5nkxpwdgpxs97yqh2fxz9y0rm80rc280-terraform-provider-heroku-1.9.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/2yy3pv77rwbxk7b2mpysmiqdzhmgmphg-terraform-provider-http-1.1.1-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/mvmjdim7dn589inb8dsjxap08h4ip4h5-terraform-provider-huaweicloud-1.4.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/wi4jm555w0rc1daiy2sz9iwrpk6cb2d8-terraform-provider-ibm-0.11.1-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/xn8xmzxjx7i8wwfvbiwfgmv9mn4n45dk-terraform-provider-icinga2-0.2.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/f7zh0d0n2dj4dcig903zd5jgb2cpaxf6-terraform-provider-ignition-1.0.1-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/csajl6aq80s9v2xbkmlzgfxlilmbzff6-terraform-provider-influxdb-1.1.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/5k67y2lglsnswrya21z51d4h87a081k5-terraform-provider-kubernetes-1.6.2-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/x1idgjd7vs75nj9s3krimbfjvh27n06d-terraform-provider-librato-0.1.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/shf6d1928fzxcaz6zh0bhcqv3xhvxhjd-terraform-provider-linode-1.6.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/gkpa27fykskx0dd52dca515gd91qhhgf-terraform-provider-local-1.2.2-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/vkdh5ibsmzj6p53krnqqz1pv620f42r0-terraform-provider-logentries-1.0.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/sn2cydjzikl3rws2nfa7pdvayb45brrd-terraform-provider-logicmonitor-1.2.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/3qjz5kfri8sa0dj1213rap75alpqsm2l-terraform-provider-mailgun-0.1.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/byxya0m4656ylf5imvs2v9p2c1av1kjl-terraform-provider-matchbox-0.2.3-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/kvjcl6plvmkm6i2lzd7wrkbiis3b4vhg-terraform-provider-mysql-1.5.1-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/rs21a235ix9v8y4hgazkzi6g1x5dqf7v-terraform-provider-netlify-0.1.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/h40ib0qsa07b6ld1pv4x76xx2g7xgik6-terraform-provider-newrelic-1.5.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/89wg3f6hk41gxm4n6cikj6r7gr2k7h8j-terraform-provider-nixos-0.0.1-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/id798ngchr83gc0mmqd3zlviljshjhvb-terraform-provider-nomad-1.3.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/8krs5vbid0ic6vvlvjvndvjb815q8hbd-terraform-provider-ns1-1.3.1-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/ymn53mhfkkhs26qw708yv7bd7jmbp636-terraform-provider-nsxt-1.1.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/5z3s6zbi98gh8cfliaplnmv15j568c46-terraform-provider-null-2.1.2-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/6brahzfjri338n3fggplfrsmf63mrwnx-terraform-provider-nutanix-1.0.1-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/zaq3w03j96qqhzpcfs9yacwa98sdsmiv-terraform-provider-oci-3.24.1-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/p00q64lbln1z9kfgpd2r6qhk0kc7i7w7-terraform-provider-oneandone-1.3.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/50wggbbr0wdg21hrvl4icwlppvk4464b-terraform-provider-opc-1.3.6-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/1wh5wgw6a3w91mk2avvn9ssw32nlw9kd-terraform-provider-openstack-1.18.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/pvsfn6d0byl3hfwnyfg21yivyj8iff8s-terraform-provider-opentelekomcloud-1.8.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/q0ndxs1vqdy5r749h5hhhbixgyf5yasx-terraform-provider-opsgenie-0.1.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/hl8lzq90qjhq0n710lm5n17lc9i80vsh-terraform-provider-oraclepaas-1.5.2-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/z4vgv1w5cmd6p90grfgr1k6m87fydr3g-terraform-provider-ovh-0.3.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/xkv7la24vsyn9n23wc1izcmmp7aifzb3-terraform-provider-packet-2.1.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/hy2xn2jxm4wp7j86p08m9xdpxncskdgv-terraform-provider-pagerduty-1.2.1-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/5lcz7p2xz1zp8iyd9yjmrg1kxw5yygnx-terraform-provider-panos-1.5.1-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/y20bvdwb0s95wa4gzhkkxd1xcc4c8whx-terraform-provider-postgresql-0.3.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/vrrs5p13mykyniglgfdsn8xii9b7s850-terraform-provider-powerdns-0.1.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/in7wgxanbdycb9wpq1j29928gllc0ap6-terraform-provider-profitbricks-1.4.4-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/zdfchj49phsp0sahcvdfp8ipc0chakg3-terraform-provider-rabbitmq-1.0.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/15fv1623h1vcn5z0nq42v5rgjirbp5r0-terraform-provider-rancher-1.2.1-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/7axz4xwz0vfrdgjyk59xg998bdqbvg5x-terraform-provider-random-2.1.2-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/yjdcrd1lkzp8c7cawcpy40c4p3ngaw12-terraform-provider-rightscale-1.3.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/2lh08897y86kxvyjdd1vlnkg8fz88nkd-terraform-provider-rundeck-0.1.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/fq4765nh9p0si8mh9cnywsq48zr1qc27-terraform-provider-runscope-0.5.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/lgrhsbfmpf1cjbpig8llxfrfb6xhz7xv-terraform-provider-scaleway-1.9.2-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/sw6n4yz49cz5vm4ggpk2l5j1vngac8j2-terraform-provider-secret-1.0.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/f3rbnn0jhm549mcp7k9ysjcq26j8fvyy-terraform-provider-segment-0.2.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/y1v3g4m9bmmmvmw4z84m5fpmdy42lbr4-terraform-provider-selectel-2.1.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/bf26sh99bngrnpzrj7gyz0689b060vak-terraform-provider-skytap-0.9.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/l6ns1zcd18j9708y3agxgi0kihs4zc7i-terraform-provider-softlayer-0.0.1-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/5ygnx64lyv5a8pnpmlj7bs8s2dz2hkxd-terraform-provider-spotinst-1.13.2-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/k3qhzd0x8a1z6h5kyifnv3axbfs7fy66-terraform-provider-statuscake-0.2.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/bvsihhp4jv61hz6mc17mn1sar03k0i8d-terraform-provider-telefonicaopencloud-1.0.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/9gjpg5lsdhgrhi805948c648nhn39l8z-terraform-provider-template-2.1.2-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/6hv1yfwyydyg2lzqcllwjb68xl4mrppw-terraform-provider-tencentcloud-1.5.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/7fd40sykaxj6dvya7mvif3f16wrqijr9-terraform-provider-terraform-1.0.2-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/rk78bh2s5yjpmgdhzqlf1hnj6ij0h20n-terraform-provider-tfe-0.8.2-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/pb6r7dllpfw5cbhpmv2v2kms9a57r4v5-terraform-provider-tls-2.0.1-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/apjv9g35sklrab9lzz9r9rq7lnczv2wy-terraform-provider-triton-0.5.1-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/5b0s7hhp52vq4psmicf8m8y2jr5jsiaz-terraform-provider-ucloud-1.6.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/ck0lifb2jgkmg6c7frz7fxqwz5fbdnxk-terraform-provider-ultradns-0.1.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/1fl7yd9chgswnabbsvva7xvg5ak1q44p-terraform-provider-vault-1.8.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/n3rakrhhvi3bb0ffnjs51drmy157p51q-terraform-provider-vcd-2.1.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/n1mrfbzlh3cjm9mfyrp48pybl3sg4717-terraform-provider-vsphere-1.10.0-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/cncad2f4lfxfxnwd9lfhjjd89x3anxqr-terraform-provider-yandex-0.5.2-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/2j9jm3jaxfn2g6wxak61wkhmrg6c4nn5-unbound-1.9.1-lib' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/01aggsi1ndjhnr93gcy8c4s1xbxab8dn-unzip-6.0' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/1dydqkwswavzkyvr1qr62zmx3nqpmpp4-gnutls-3.6.7' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/69msrhi85iay3cb7c3nksr0s8l0xpsc7-util-linux-2.33.2' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/xdhh337yhl93x33vzd9davinrbr9x9iz-libmicrohttpd-0.9.63' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/rcn9d2q4mpapxf4qd54hkqz32ljhv0rw-util-linux-2.33.2' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/50gfgyi2rxi4n25if8cqvlxlh5czl0wd-yajl-2.1.0' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/yrmrvha03pvdyi9ww2bi6xjpk5930sf8-glib-2.60.1' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/z2darh83lb4rmsfnnyjc0hll51fyvj49-libSM-1.2.3' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/pknq6p5h43zm4r0dgjnfywql04hdv3js-atk-2.32.0' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/p8s6295x84d594sxvzml8rsxqjdghmc5-cairo-1.16.0' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/v5q3cnkjfy8rfacsjqn1nza93mbczgd5-gdk-pixbuf-2.38.1' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/9yb9whkdgf3zyy85xac248kwq1wm6qd6-harfbuzz-2.3.1' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/xxwqa4rwfi97az8a6dl6vhqiyjvmnm9v-libsecret-0.18.8' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/3xq3w5fgz99rhp3rxfkbp0ahg37mgmly-pango-1.43.0' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/a185xh0jcx7il7hw2gfh0pmvrah3x67y-systemd-239.20190219-lib' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/s7rqxrfb631i53dfl90gac35095jyypq-util-linux-2.33.2-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/6hwdmzpspbnb7ix5z6m9h60jyy42kj90-dbus-1.12.12-lib' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/xmy3chnan9iiag9apm7dd825cmlkiiij-libusb-1.0.22' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/ricz15lpkjrasc5cpzp6l60iwlc87wv3-avahi-0.7' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/di6rrbw1kbdrwxiymq91dgdvp2rvk1xv-dnsmasq-2.80' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/kccb2k5hdjhdyxbxsri9lwwc4z1pvx6z-cups-2.2.11-lib' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/vqvmd2r9pf9f74jqipbhrn7wksiiy1jf-pcsclite-1.8.25-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/x3rijvjjrch1fjs60lrw9xb7pidp817f-gtk+-2.24.32' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/y3x0fvlz4a30iajw3vd1rkg45vl3k15c-pcsclite-1.8.25' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/a2cg0faxbwnicf41vwmw467jw7i9ix46-pinentry-1.1.0' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/lvqp39d4hx776nkw3a0qfnvvjmnj49hc-procps-3.3.15' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/z68464p6aafah8b8xcybkwyhmqdf0jgx-gnupg-2.2.15' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/6bvd29jny80ka8df9prr5hrl5yz7d98k-systemd-239.20190219' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/qgr66z24rfbb8cc965rr2sklh38p083n-git-crypt-0.6.0' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/daizqdqrm7g4favv814hnijmqhay8hs4-dbus-1.12.12' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/wf5nv1gzrx378icqmjgwl2isg7s8ly80-lvm2-2.03.01' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/97d3r4a7v1nal53x0gv17hrbbcp0rb21-util-linux-2.33.2-bin' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/glrnpb3rkribnrjh5gzs24nmvl3m00cg-parted-3.2' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/f39sk2aim9xz7dzn7qvqh442xm58v77w-nfs-utils-2.3.3' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/wi2mn48l130r7wafvj757rvzfkla59if-pm-utils-1.4.1' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/35mdgd1wc67g60azsrghzgn4fjhr5d2r-zfs-user-0.7.13-lib' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/9dk1gh07pwkvg62rns4k670h54bhfhgh-zlib-1.2.11-dev' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/8bxvyvd3ky0w5gk3k0lq2fmvj30fbzj8-zfs-user-0.7.13' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/i3kh8yq4kgkfn234pnwxnvxbrcgcckc8-curl-7.64.1-dev' from 'https://cache.nixos.org'...\n" +"copying path '/nix/store/nwhvl00i2wa4ms26lszk36vwir90jd3x-libvirt-4.10.0' from 'https://cache.nixos.org'...\n" +"building '/nix/store/as9r3n55czsdiq82iacs0hq12alxb2m0-remove-references-to.drv'...\n" +"copying path '/nix/store/l9821zngvlh8bd6mlyzvi1mc754dyhjz-terraform-provider-libvirt-0.5.1-bin' from 'https://cache.nixos.org'...\n" +"building '/nix/store/fdh1ahjdh3fgsz4qz386klsa9bsqil48-source.drv'...\n" +"\n" +"trying https://github.com/n3integration/terraform-godaddy/archive/v1.6.4.tar.gz\n" +" % Total % Received % Xferd Average Speed Time Time Time Current\n" +" Dload Upload Total Spent Left Speed\n" +"100 139 0 139 0 0 863 0 --:--:-- --:--:-- --:--:-- 858\n" +"100 19326 0 19326 0 0 59282 0 --:--:-- --:--:-- --:--:-- 59282\n" +"unpacking source archive /build/v1.6.4.tar.gz\n" +"copying path '/nix/store/isdbs6d2jk75kj0qk4s3prwlwcgkgalf-tf-plugin-env' from 'https://cache.nixos.org'...\n" +"building '/nix/store/x7r5kh20ajlnj6vw6fg649w0iypcg1ga-terraform-godaddy-1.6.4-go-modules.drv'...\n" +"unpacking sources\n" +"unpacking source archive /nix/store/m62ydk4wy6818sysfys0qz20cx5nzj7h-source\n" +"source root is source\n" +"patching sources\n" +"configuring\n" +"building\n" +"go: finding github.com/mitchellh/gox v0.4.0\n" +"go: finding github.com/hashicorp/go-hclog v0.0.0-20181001195459-61d530d6c27f\n" +"go: finding github.com/hashicorp/go-getter v0.0.0-20181213035916-be39683deade\n" +"go: finding github.com/mitchellh/go-testing-interface v1.0.0\n" +"go: finding github.com/jmespath/go-jmespath v0.0.0-20180206201540-c2b33e8439af\n" +"go: finding github.com/agext/levenshtein v1.2.1\n" +"go: finding github.com/apparentlymart/go-cidr v1.0.0\n" +"go: finding github.com/bgentry/go-netrc v0.0.0-20140422174119-9fd32a8b3d3d\n" +"go: finding github.com/hashicorp/hil v0.0.0-20170627220502-fa9f258a9250\n" +"go: finding github.com/posener/complete v1.2.1\n" +"go: finding github.com/mitchellh/copystructure v1.0.0\n" +"go: finding github.com/hashicorp/errwrap v1.0.0\n" +"go: finding github.com/hashicorp/hcl2 v0.0.0-20181220012050-6631d7cd0a68\n" +"go: finding github.com/hashicorp/go-version v1.0.0\n" +"go: finding github.com/mitchellh/reflectwalk v1.0.0\n" +"go: finding golang.org/x/net v0.0.0-20181220203305-927f97764cc3\n" +"go: finding golang.org/x/sync v0.0.0-20181221193216-37e7f081c4d4\n" +"go: finding golang.org/x/tools v0.0.0-20181221235234-d00ac6d27372\n" +"go: finding github.com/golang/protobuf v1.2.0\n" +"go: finding github.com/hashicorp/go-multierror v1.0.0\n" +"go: finding github.com/mitchellh/go-homedir v1.0.0\n" +"go: finding github.com/apparentlymart/go-textseg v1.0.0\n" +"go: finding github.com/hashicorp/go-uuid v1.0.0\n" +"go: finding github.com/satori/go.uuid v1.2.0\n" +"go: finding github.com/mitchellh/cli v1.0.0\n" +"go: finding github.com/mitchellh/mapstructure v1.1.2\n" +"go: finding golang.org/x/lint v0.0.0-20181217174547-8f45f776aaf1\n" +"go: finding golang.org/x/crypto v0.0.0-20181203042331-505ab145d0a9\n" +"go: finding google.golang.org/appengine v1.4.0\n" +"go: finding golang.org/x/net v0.0.0-20181114220301-adae6a3d119a\n" +"go: finding golang.org/x/sys v0.0.0-20180823144017-11551d06cbcc\n" +"go: finding honnef.co/go/tools v0.0.0-20180920025451-e3ad64cb4ed3\n" +"go: finding github.com/hashicorp/terraform v0.11.11\n" +"go: finding github.com/aws/aws-sdk-go v1.15.78\n" +"go: finding github.com/onsi/ginkgo v1.7.0\n" +"go: finding github.com/kr/pty v1.1.3\n" +"go: finding github.com/mattn/go-isatty v0.0.3\n" +"go: finding github.com/onsi/gomega v1.4.3\n" +"go: finding github.com/bgentry/speakeasy v0.1.0\n" +"go: finding gopkg.in/yaml.v2 v2.2.2\n" +"go: finding gopkg.in/yaml.v2 v2.2.1\n" +"go: finding github.com/fatih/color v1.7.0\n" +"go: finding github.com/zclconf/go-cty v0.0.0-20181129180422-88fbe721e0f8\n" +"go: finding github.com/mitchellh/go-wordwrap v0.0.0-20150314170334-ad45545899c7\n" +"go: finding golang.org/x/text v0.3.0\n" +"go: finding github.com/sergi/go-diff v1.0.0\n" +"go: finding github.com/armon/go-radix v1.0.0\n" +"go: finding github.com/fsnotify/fsnotify v1.4.7\n" +"go: finding golang.org/x/sys v0.0.0-20180909124046-d0be0721c37e\n" +"go: finding golang.org/x/net v0.0.0-20181129055619-fae4c4e3ad76\n" +"go: finding github.com/kr/pretty v0.1.0\n" +"go: finding github.com/hashicorp/go-cleanhttp v0.5.0\n" +"go: finding github.com/mattn/go-isatty v0.0.4\n" +"go: finding gopkg.in/check.v1 v1.0.0-20180628173108-788fd7840127\n" +"go: finding github.com/go-test/deep v1.0.1\n" +"go: finding cloud.google.com/go v0.34.0\n" +"go: finding github.com/kylelemons/godebug v0.0.0-20170820004349-d65d576e9348\n" +"go: finding howett.net/plist v0.0.0-20181124034731-591f970eefbb\n" +"go: finding github.com/hashicorp/errwrap v0.0.0-20180715044906-d6c0cd880357\n" +"go: finding golang.org/x/crypto v0.0.0-20180816225734-aabede6cba87\n" +"go: finding golang.org/x/net v0.0.0-20180724234803-3673e40ba225\n" +"go: finding github.com/mattn/go-colorable v0.0.9\n" +"go: finding github.com/hashicorp/yamux v0.0.0-20181012175058-2f1d1f20f75d\n" +"go: finding github.com/go-ini/ini v1.40.0\n" +"go: finding github.com/mitchellh/iochan v1.0.0\n" +"go: finding golang.org/x/sys v0.0.0-20181228144115-9a3f9b0469bb\n" +"go: finding github.com/jessevdk/go-flags v1.4.0\n" +"go: finding github.com/posener/complete v1.1.1\n" +"go: finding github.com/spf13/pflag v1.0.3\n" +"go: finding github.com/stretchr/testify v1.2.2\n" +"go: finding golang.org/x/oauth2 v0.0.0-20181203162652-d668ce993890\n" +"go: finding github.com/davecgh/go-spew v1.1.1\n" +"go: finding golang.org/x/net v0.0.0-20180906233101-161cd47e91fd\n" +"go: finding golang.org/x/sync v0.0.0-20181108010431-42b317875d0f\n" +"go: finding github.com/bsm/go-vlq v0.0.0-20150828105119-ec6e8d4f5f4e\n" +"go: finding gopkg.in/tomb.v1 v1.0.0-20141024135613-dd632973f1e7\n" +"go: finding github.com/mitchellh/go-wordwrap v1.0.0\n" +"go: finding github.com/ulikunitz/xz v0.5.5\n" +"go: finding github.com/hashicorp/hcl v1.0.0\n" +"go: finding github.com/hashicorp/go-multierror v0.0.0-20180717150148-3d5d8f294aa0\n" +"go: finding gopkg.in/check.v1 v0.0.0-20161208181325-20d25e280405\n" +"go: finding golang.org/x/sync v0.0.0-20180314180146-1d60e4601c6f\n" +"go: finding github.com/google/go-cmp v0.2.0\n" +"go: finding github.com/golang/mock v1.2.0\n" +"go: finding gopkg.in/fsnotify.v1 v1.4.7\n" +"go: finding github.com/onsi/ginkgo v1.6.0\n" +"go: finding github.com/golang/protobuf v1.1.0\n" +"go: finding github.com/aws/aws-sdk-go v1.16.11\n" +"go: finding github.com/hpcloud/tail v1.0.0\n" +"go: finding google.golang.org/grpc v1.17.0\n" +"go: finding github.com/blang/semver v3.5.1+incompatible\n" +"go: finding github.com/vmihailenco/msgpack v3.3.3+incompatible\n" +"go: finding github.com/armon/go-radix v0.0.0-20180808171621-7fddfc383310\n" +"go: finding golang.org/x/net v0.0.0-20180811021610-c39426892332\n" +"go: finding github.com/zclconf/go-cty v0.0.0-20181218225846-4fe1e489ee06\n" +"go: finding github.com/jmespath/go-jmespath v0.0.0-20160202185014-0b12d6b521d8\n" +"go: finding github.com/hashicorp/go-plugin v0.0.0-20181212150838-f444068e8f5a\n" +"go: finding github.com/pmezard/go-difflib v1.0.0\n" +"go: finding github.com/spf13/pflag v1.0.2\n" +"go: finding github.com/hashicorp/go-safetemp v1.0.0\n" +"go: finding github.com/vmihailenco/msgpack v4.0.1+incompatible\n" +"go: finding google.golang.org/genproto v0.0.0-20181221175505-bd9b4fb69e2f\n" +"go: finding golang.org/x/tools v0.0.0-20180828015842-6cd1fcedba52\n" +"go: finding github.com/kr/text v0.1.0\n" +"go: finding golang.org/x/net v0.0.0-20180826012351-8a410e7b638d\n" +"go: finding golang.org/x/lint v0.0.0-20181026193005-c67002cb31c3\n" +"go: finding github.com/apparentlymart/go-dump v0.0.0-20180507223929-23540a00eaa3\n" +"go: finding github.com/golang/glog v0.0.0-20160126235308-23def4e6c14b\n" +"go: finding github.com/golang/mock v1.1.1\n" +"go: finding cloud.google.com/go v0.26.0\n" +"go: finding github.com/oklog/run v1.0.0\n" +"go: finding golang.org/x/oauth2 v0.0.0-20180821212333-d2e6202438be\n" +"go: finding google.golang.org/genproto v0.0.0-20180817151627-c66870c02cf8\n" +"go: finding github.com/hashicorp/go-hclog v0.0.0-20180709165350-ff2cf002a8dd\n" +"go: finding google.golang.org/grpc v1.14.0\n" +"go: finding github.com/client9/misspell v0.3.4\n" +"go: finding github.com/kr/pty v1.1.1\n" +"go: finding google.golang.org/appengine v1.1.0\n" +"go: finding honnef.co/go/tools v0.0.0-20180728063816-88497007e858\n" +"go: finding golang.org/x/sys v0.0.0-20180830151530-49385e6e1522\n" +"go: finding github.com/hashicorp/yamux v0.0.0-20180604194846-3520598351bb\n" +"go: finding github.com/kisielk/gotool v1.0.0\n" +"go: finding github.com/mitchellh/go-testing-interface v0.0.0-20171004221916-a61a99592b77\n" +"go: finding github.com/mitchellh/hashstructure v1.0.0\n" +"go: finding golang.org/x/net v0.0.0-20181106065722-10aee1819953\n" +"go: finding google.golang.org/grpc v1.16.0\n" +"go: finding golang.org/x/lint v0.0.0-20180702182130-06c8688daad7\n" +"go: finding github.com/golang/lint v0.0.0-20180702182130-06c8688daad7\n" +"installing\n" +"hash mismatch in fixed-output derivation '/nix/store/q8y0mzjl78hfhazjgq2sc84i7dp9wnh0-terraform-godaddy-1.6.4-go-modules':\n" +" wanted: sha256:10n2dy7q9kk1ly58sw965n6qa8l0nffh8vyd1vslx0gdlyj25xxs\n" +" got: sha256:0p81wqw2n8vraxk20xwg717582ijwq2k7v5j3n13y4cd5bxd8hhz\n" +"cannot build derivation '/nix/store/w4ghinrmpq524k3617ikfc8i42aa0dbb-terraform-godaddy-1.6.4.drv': 1 dependencies couldn't be built\n" +"copying path '/nix/store/63gjp25l4cmdkl63zy0rcgmsvd2p2p34-terraform-0.11.14' from 'https://cache.nixos.org'...\n" +"error: build of '/nix/store/9drkn1qxkkcrz5g3413lpmbc2xysa582-terraform-0.11.14.drv', '/nix/store/w4ghinrmpq524k3617ikfc8i42aa0dbb-terraform-godaddy-1.6.4.drv' failed\n" +msgstr "" + +msgid "title: Inconsistent hash of buildGoModule" +msgstr "" + +msgid "date: 2019-06-08" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "" +"The [commit that made this " +"visible](https://euandreh.xyz/vps.git/commit?id=6ba76140238b5e3c7009c201f9f80ac86063f438)." +msgstr "" + +msgid "" +"[Full source code on the " +"repository](https://euandreh.xyz/vps.git/tree/default.nix?id=6ba76140238b5e3c7009c201f9f80ac86063f438#n3):" +msgstr "" + +msgid "" +"FIXED: See https://discourse.nixos.org/t/inconsistent-hash-of-" +"buildgomodule/3127/2" +msgstr "" + +msgid "eu_categories: nix" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "ref: inconsistent-hash-of-buildgomodule" +msgstr "" + +#~ msgid "layout: pastebin" +#~ msgstr "" + +#~ msgid "" +#~ "[FIXED](https://discourse.nixos.org/t/inconsistent-hash-of-" +#~ "buildgomodule/3127/2)." +#~ msgstr "" + +#~ msgid "" +#~ "[Full source code on " +#~ "sr.ht](https://euandreh.xyz/vps.git/tree/default.nix?id=6ba76140238b5e3c7009c201f9f80ac86063f438#n3):" +#~ msgstr "" + +#~ msgid "" +#~ "title: Inconsistent hash of buildGoModule\n" +#~ "date: 2019-06-08\n" +#~ "layout: pastebin\n" +#~ "lang: en" +#~ msgstr "" + +#~ msgid "" +#~ "The [commit that made this " +#~ "visible](https://git.sr.ht/~euandreh/vps/commit/6ba76140238b5e3c7009c201f9f80ac86063f438)." +#~ msgstr "" + +#~ msgid "" +#~ "[Full source code on " +#~ "sr.ht](https://git.sr.ht/~euandreh/vps/tree/6ba76140238b5e3c7009c201f9f80ac86063f438/default.nix#L3-15):" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_pastebins/2019-12-29-raku-tuple-type-annotation.po b/po/fr/LC_MESSAGES/_pastebins/2019-12-29-raku-tuple-type-annotation.po new file mode 100644 index 0000000..e2a4d04 --- /dev/null +++ b/po/fr/LC_MESSAGES/_pastebins/2019-12-29-raku-tuple-type-annotation.po @@ -0,0 +1,57 @@ +# +msgid "" +msgstr "" + +msgid "Error log is:" +msgstr "" + +msgid "" +"# Single Str return value: this works\n" +"sub f1(Str $in --> Str) {\n" +" $in;\n" +"}\n" +"\n" +"# Tuple of Str as return value: this works\n" +"sub f2(Str $in) {\n" +" ($in, $in);\n" +"}\n" +"\n" +"# Tuple of Str as return value with type annotation: this doesn't works\n" +"sub f2(Str $in --> (Str, Str)) {\n" +" ($in, $in);\n" +"}\n" +msgstr "" + +msgid "" +"===SORRY!=== Error while compiling /path/to/my/file\n" +"Malformed return value\n" +msgstr "" + +msgid "title: Raku tuple type annotation" +msgstr "" + +msgid "date: 2019-12-29" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: raku-tuple-type-annotation" +msgstr "" + +#~ msgid "" +#~ "title: Raku tuple type annotation\n" +#~ "date: 2019-12-29\n" +#~ "layout: post\n" +#~ "lang: en" +#~ msgstr "" + +#~ msgid "" +#~ "title: Raku tuple type annotation\n" +#~ "date: 2019-12-29\n" +#~ "layout: pastebin\n" +#~ "lang: en" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_pastebins/2020-01-04-failure-on-guix-tex-live-importer.po b/po/fr/LC_MESSAGES/_pastebins/2020-01-04-failure-on-guix-tex-live-importer.po new file mode 100644 index 0000000..fe0200a --- /dev/null +++ b/po/fr/LC_MESSAGES/_pastebins/2020-01-04-failure-on-guix-tex-live-importer.po @@ -0,0 +1,63 @@ +# +msgid "" +msgstr "" + +msgid "" +"$ guix import texlive fontspec\n" +"redirection vers « https://ctan.org/xml/1.2/pkg/fontspec »...\n" +"Backtrace:\n" +" 11 (primitive-load \"/home/andreh/.config/guix/current/bin/…\")\n" +"In guix/ui.scm:\n" +" 1806:12 10 (run-guix-command _ . _)\n" +"In guix/scripts/import.scm:\n" +" 116:11 9 (guix-import . _)\n" +"In guix/scripts/import/texlive.scm:\n" +" 91:19 8 (guix-import-texlive . _)\n" +"In guix/memoization.scm:\n" +" 98:0 7 (_ #<hash-table 7fe80e6c1480 0/31> (\"fontspec\" \"latex\") _)\n" +"In unknown file:\n" +" 6 (_ #<procedure 7fe80e6e4de0 at guix/memoization.scm:17…> …)\n" +"In guix/store.scm:\n" +" 625:10 5 (call-with-store #<procedure 7fe80e714a60 at guix/impor…>)\n" +"In guix/import/texlive.scm:\n" +" 148:23 4 (_ #<store-connection 256.99 7fe811f3c960>)\n" +"In guix/utils.scm:\n" +" 664:8 3 (call-with-temporary-directory #<procedure 7fe80cac1b40…>)\n" +"In guix/svn-download.scm:\n" +" 160:14 2 (_ \"/tmp/guix-directory.WtLohP\")\n" +"In guix/build/svn.scm:\n" +" 39:2 1 (svn-fetch _ _ _ #:svn-command _ #:recursive? _ # _ # _)\n" +"In guix/build/utils.scm:\n" +" 652:6 0 (invoke _ . _)\n" +"\n" +"guix/build/utils.scm:652:6: In procedure invoke:\n" +"Throw to key `srfi-34' with args `(#<condition &invoke-error [program: \"svn\" arguments: (\"export\" \"--non-interactive\" \"--trust-server-cert\" \"-r\" \"49435\" \"svn://www.tug.org/texlive/tags/texlive-2018.2/Master/texmf-dist/source/latex/fontspec\" \"/tmp/guix-directory.WtLohP\") exit-status: 1 term-signal: #f stop-signal: #f] 7fe80d229c80>)'.\n" +msgstr "" + +msgid "title: Failure on Guix TeX Live importer" +msgstr "" + +msgid "date: 2020-01-04" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "eu_categories: guix" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "ref: failure-on-guix-tex-live-importer" +msgstr "" + +#~ msgid "layout: pastebin" +#~ msgstr "" + +#~ msgid "" +#~ "title: Failure on Guix TeX Live importer\n" +#~ "date: 2020-01-04\n" +#~ "layout: pastebin\n" +#~ "lang: en" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_pastebins/2020-02-14-guix-shebang.po b/po/fr/LC_MESSAGES/_pastebins/2020-02-14-guix-shebang.po new file mode 100644 index 0000000..ec1d205 --- /dev/null +++ b/po/fr/LC_MESSAGES/_pastebins/2020-02-14-guix-shebang.po @@ -0,0 +1,39 @@ +# +msgid "" +msgstr "" + +msgid "" +"#!/usr/bin/env -S guix environment --ad-hoc bash -- bash\n" +"set -Eeuo pipefail\n" +"cd \"$(dirname \"${BASH_SOURCE[0]}\")\"\n" +"\n" +"pwd\n" +msgstr "" + +msgid "title: Guix shebang" +msgstr "" + +msgid "date: 2020-02-14" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "eu_categories: guix" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "ref: guix-shebang" +msgstr "" + +#~ msgid "layout: pastebin" +#~ msgstr "" + +#~ msgid "" +#~ "title: Guix shebang\n" +#~ "date: 2020-02-14\n" +#~ "layout: pastebin\n" +#~ "lang: en" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_pastebins/2020-11-27-guix-build-local-module.po b/po/fr/LC_MESSAGES/_pastebins/2020-11-27-guix-build-local-module.po new file mode 100644 index 0000000..cf0b7f3 --- /dev/null +++ b/po/fr/LC_MESSAGES/_pastebins/2020-11-27-guix-build-local-module.po @@ -0,0 +1,81 @@ +# +msgid "" +msgstr "" + +msgid "Inside a file named `build.scm`:" +msgstr "" + +msgid "" +"(define-module (build)\n" +" #:use-module (guix packages)\n" +" #:use-module (guix download)\n" +" #:use-module (guix build-system gnu)\n" +" #:use-module (guix licenses))\n" +"\n" +"(define-public my-hello\n" +" (package\n" +" (name \"hello\")\n" +" (version \"2.10\")\n" +" (source (origin\n" +" (method url-fetch)\n" +" (uri (string-append \"mirror://gnu/hello/hello-\" version\n" +" \".tar.gz\"))\n" +" (sha256\n" +" (base32\n" +" \"0ssi1wpaf7plaswqqjwigppsg5fyh99vdlb9kzl7c9lng89ndq1i\"))))\n" +" (build-system gnu-build-system)\n" +" (synopsis \"\")\n" +" (description \"\")\n" +" (home-page \"\")\n" +" (license gpl3+)))\n" +"\n" +msgstr "" + +msgid "A plain build command didn't work:" +msgstr "" + +msgid "" +"$ guix build -L. my-hello\n" +"guix build: error: my-hello : paquet inconnu\n" +msgstr "" + +msgid "But with an eval expression it did:" +msgstr "" + +msgid "" +"$ guix build -L. -e '(@ (build) my-hello)'\n" +"# works\n" +msgstr "" + +msgid "" +"FIXED: rename `name` on line 9 of the first snippet, and use `\"my-hello\"` " +"instead of `\"hello\"`." +msgstr "" + +msgid "title: Guix build local module" +msgstr "" + +msgid "date: 2020-11-27" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "eu_categories: guix" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "ref: guix-build-local-module" +msgstr "" + +#~ msgid "layout: pastebin" +#~ msgstr "" + +#~ msgid "" +#~ "title: Guix build local module\n" +#~ "date: 2020-11-27\n" +#~ "layout: pastebin\n" +#~ "lang: en" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_pastebins/2020-12-15-failure-with-relocatable-guix-pack-tarball.po b/po/fr/LC_MESSAGES/_pastebins/2020-12-15-failure-with-relocatable-guix-pack-tarball.po new file mode 100644 index 0000000..7aac2e5 --- /dev/null +++ b/po/fr/LC_MESSAGES/_pastebins/2020-12-15-failure-with-relocatable-guix-pack-tarball.po @@ -0,0 +1,114 @@ +# +msgid "" +msgstr "" + +msgid "FIXED: Use `GUIX_PROFILE= source etc/profile`" +msgstr "" + +msgid "" +"The example from the [blog post](https://guix.gnu.org/blog/2018/tarballs-" +"the-ultimate-container-image-format/) fails." +msgstr "" + +msgid "" +"$ tar xf `guix pack --relocatable -S /bin=bin -S /etc=etc guile gnutls guile-json`\n" +"$ source etc/profile\n" +"$ bin/guile -c '(use-modules (json))'\n" +"guile: warning: failed to install locale\n" +"Backtrace:\n" +"In ice-9/boot-9.scm:\n" +" 1736:10 13 (with-exception-handler _ _ #:unwind? _ # _)\n" +"In unknown file:\n" +" 12 (apply-smob/0 #<thunk 7f9d240ca740>)\n" +"In ice-9/boot-9.scm:\n" +" 718:2 11 (call-with-prompt (\"prompt\") #<procedure 7f9d240db740 ?> ?)\n" +"In ice-9/eval.scm:\n" +" 619:8 10 (_ #(#(#<directory (guile-user) 7f9d23d00f00>)))\n" +"In ice-9/command-line.scm:\n" +" 185:18 9 (_ #<input: string 7f9d23cfaa10>)\n" +"In unknown file:\n" +" 8 (eval (use-modules (json)) #<directory (guile-user) 7f9?>)\n" +"In ice-9/eval.scm:\n" +" 721:20 7 (primitive-eval (use-modules (json)))\n" +"In ice-9/psyntax.scm:\n" +" 1241:36 6 (expand-top-sequence ((use-modules (json))) _ _ #f _ _ _)\n" +" 1233:19 5 (parse _ ((\"placeholder\" placeholder)) ((top) #(# # ?)) ?)\n" +" 285:10 4 (parse _ ((\"placeholder\" placeholder)) (()) _ c&e (eval) ?)\n" +"In ice-9/boot-9.scm:\n" +" 3898:20 3 (process-use-modules _)\n" +" 222:17 2 (map1 (((json))))\n" +" 3899:31 1 (_ ((json)))\n" +" 3300:6 0 (resolve-interface (json) #:select _ #:hide _ #:prefix _ ?)\n" +"\n" +"ice-9/boot-9.scm:3300:6: In procedure resolve-interface:\n" +"no code for module (json)\n" +"$ bin/guile -c '(use-modules (gnutls))'\n" +"guile: warning: failed to install locale\n" +"Backtrace:\n" +"In ice-9/boot-9.scm:\n" +" 1736:10 13 (with-exception-handler _ _ #:unwind? _ # _)\n" +"In unknown file:\n" +" 12 (apply-smob/0 #<thunk 7f7fe607a7c0>)\n" +"In ice-9/boot-9.scm:\n" +" 718:2 11 (call-with-prompt (\"prompt\") #<procedure 7f7fe6085940 ?> ?)\n" +"In ice-9/eval.scm:\n" +" 619:8 10 (_ #(#(#<directory (guile-user) 7f7fe5ca8f00>)))\n" +"In ice-9/command-line.scm:\n" +" 185:18 9 (_ #<input: string 7f7fe5ca2a10>)\n" +"In unknown file:\n" +" 8 (eval (use-modules (gnutls)) #<directory (guile-user) 7?>)\n" +"In ice-9/eval.scm:\n" +" 721:20 7 (primitive-eval (use-modules (gnutls)))\n" +"In ice-9/psyntax.scm:\n" +" 1241:36 6 (expand-top-sequence ((use-modules (gnutls))) _ _ #f _ _ ?)\n" +" 1233:19 5 (parse _ ((\"placeholder\" placeholder)) ((top) #(# # ?)) ?)\n" +" 285:10 4 (parse _ ((\"placeholder\" placeholder)) (()) _ c&e (eval) ?)\n" +"In ice-9/boot-9.scm:\n" +" 3898:20 3 (process-use-modules _)\n" +" 222:17 2 (map1 (((gnutls))))\n" +" 3899:31 1 (_ ((gnutls)))\n" +" 3300:6 0 (resolve-interface (gnutls) #:select _ #:hide _ #:prefix ?)\n" +"\n" +"ice-9/boot-9.scm:3300:6: In procedure resolve-interface:\n" +"no code for module (gnutls)\n" +msgstr "" + +msgid "My Guix version if fairly recent:" +msgstr "" + +msgid "" +"$ guix describe\n" +"Génération 83 14 déc. 2020 00:28:16 (actuelle)\n" +" guix 41807eb\n" +" URL du dépôt : https://git.savannah.gnu.org/git/guix.git\n" +" branche: master\n" +" commit : 41807eb5329299b8c45cd49356a4ead01ce0d469\n" +msgstr "" + +msgid "title: Failure with relocatable Guix pack tarball" +msgstr "" + +msgid "date: 2020-12-15" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "eu_categories: guix" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "ref: failure-with-relocatable-guix-pack-tarball" +msgstr "" + +#~ msgid "layout: pastebin" +#~ msgstr "" + +#~ msgid "" +#~ "title: Failure with relocatable Guix pack tarball\n" +#~ "date: 2020-12-15\n" +#~ "layout: pastebin\n" +#~ "lang: en" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_pastebins/2021-04-03-javascript-naive-slugify.po b/po/fr/LC_MESSAGES/_pastebins/2021-04-03-javascript-naive-slugify.po new file mode 100644 index 0000000..f6e087b --- /dev/null +++ b/po/fr/LC_MESSAGES/_pastebins/2021-04-03-javascript-naive-slugify.po @@ -0,0 +1,70 @@ +# +msgid "" +msgstr "" + +msgid "title: JavaScript naive slugify" +msgstr "" + +msgid "date: 2021-04-03" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: javascript-naive-slugify" +msgstr "" + +msgid "" +"const s = \"Pézão: açaí, saci-pererê.\";\n" +"\n" +"function slugify(s) {\n" +" return s\n" +" .toLowerCase()\n" +" .replaceAll(\":\", \"\")\n" +" .replaceAll(\".\", \"\")\n" +" .replaceAll(\",\", \"\")\n" +" .replaceAll(\"-\", \"\")\n" +" .replaceAll(\"á\", \"a\")\n" +" .replaceAll(\"ã\", \"a\")\n" +" .replaceAll(\"à\", \"a\")\n" +" .replaceAll(\"é\", \"e\")\n" +" .replaceAll(\"ê\", \"e\")\n" +" .replaceAll(\"í\", \"i\")\n" +" .replaceAll(\"ó\", \"o\")\n" +" .replaceAll(\"ô\", \"o\")\n" +" .replaceAll(\"ú\", \"u\")\n" +" .replaceAll(\"ü\", \"u\")\n" +" .replaceAll(\"ç\", \"c\");\n" +"}\n" +"\n" +"console.log(slugify(s));\n" +msgstr "" + +#~ msgid "" +#~ "const s = \"Pézão: açaí, saci-pererê.\";\n" +#~ "\n" +#~ "function slugify(s) {\n" +#~ " return s\n" +#~ " .toLowerCase()\n" +#~ " .replaceAll(\":\", \"\")\n" +#~ " .replaceAll(\".\", \"\")\n" +#~ " .replaceAll(\",\", \"\")\n" +#~ " .replaceAll(\"-\", \"\")\n" +#~ " .replaceAll(\"á\", \"a\")\n" +#~ " .replaceAll(\"ã\", \"a\")\n" +#~ " .replaceAll(\"à\", \"a\")\n" +#~ " .replaceAll(\"é\", \"e\")\n" +#~ " .replaceAll(\"ê\", \"e\")\n" +#~ " .replaceAll(\"í\", \"i\")\n" +#~ " .replaceAll(\"ó\", \"o\")\n" +#~ " .replaceAll(\"ô\", \"o\")\n" +#~ " .replaceAll(\"ú\", \"u\")\n" +#~ " .replaceAll(\"ü\", \"u\")\n" +#~ " .replaceAll(\"ç\", \"c\");\n" +#~ "}\n" +#~ "\n" +#~ "console.log(slugify(s));\n" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_pastebins/2021-06-08-debit-reading-session-sicp-solutions-pt-1.po b/po/fr/LC_MESSAGES/_pastebins/2021-06-08-debit-reading-session-sicp-solutions-pt-1.po new file mode 100644 index 0000000..1a8be0e --- /dev/null +++ b/po/fr/LC_MESSAGES/_pastebins/2021-06-08-debit-reading-session-sicp-solutions-pt-1.po @@ -0,0 +1,83 @@ +# +msgid "" +msgstr "" + +msgid "title: Debit Reading Session - SICP solutions pt.1" +msgstr "" + +msgid "date: 2021-06-08" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: debit-reading-session-sicp-solutions-pt-1" +msgstr "" + +msgid "" +";; 1.41\n" +"(define (double f)\n" +" (lambda (x)\n" +" (f (f x))))\n" +"\n" +"\n" +":;; 1.42\n" +"(define (compose f g)\n" +" (lambda (x)\n" +" (f (g x))))\n" +"\n" +"\n" +";;; 1.43\n" +"(define (repeated f n)\n" +" (if (= 1 n)\n" +" identity\n" +" (comp (repeated f (dec n)))))\n" +"\n" +"\n" +";;; 2.27\n" +"(define (map-tree node-fn leaf-fn tree)\n" +" (cond\n" +" ((null? tree) tree)\n" +" ((not (pair? tree)) (leaf-fn tree))\n" +" (else\n" +" (node-fn\n" +" (cons (map-tree node-fn leaf-fn (car tree))\n" +" (map-tree node-fn leaf-fn (cdr tree)))))))\n" +"\n" +"(define (map-nodes f tree)\n" +" (map-tree f identity tree))\n" +"\n" +"(define (deep-reverse x)\n" +" (map-nodes reverse x))\n" +"\n" +"\n" +";;; 2.28\n" +"(define (flatten tree)\n" +" (define (rec acc t)\n" +" (cond\n" +" ((null? t) acc)\n" +" ((not (pair? t)) (cons t acc))\n" +" (else\n" +" (rec (rec (cdr t) acc)\n" +" (car t)))))\n" +" (rec nil tree))\n" +"\n" +"\n" +";;; 2.30\n" +"(define (square-tree tree)\n" +" (map-leaves square tree))\n" +"\n" +"\n" +";;; 2.31\n" +"(define square-tree map-leaves) ; ha!\n" +"\n" +"\n" +";;; 2.32\n" +"TODO\n" +msgstr "" + +msgid "FYI: I just typed those in, I didn't yet test them yet." +msgstr "" diff --git a/po/fr/LC_MESSAGES/_podcasts/2020-12-19-a-test-entry.po b/po/fr/LC_MESSAGES/_podcasts/2020-12-19-a-test-entry.po new file mode 100644 index 0000000..c2aac12 --- /dev/null +++ b/po/fr/LC_MESSAGES/_podcasts/2020-12-19-a-test-entry.po @@ -0,0 +1,128 @@ +# +msgid "" +msgstr "" + +msgid "title: A test entry" +msgstr "" + +msgid "date: 2020-12-19" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: a-test-entry" +msgstr "" + +msgid "slug: a-test-entry" +msgstr "" + +msgid "audio: true" +msgstr "" + +msgid "After." +msgstr "" + +msgid "A link to [home](https://euandre.org)." +msgstr "" + +msgid "Another link to home: https://euandre.org" +msgstr "" + +msgid "A code block:" +msgstr "" + +msgid "" +"$ l\n" +"total 372K\n" +"drwxr-xr-x 23 andreh users 4,0K déc. 19 10:44 ./\n" +"drwxr-xr-x 30 andreh users 4,0K déc. 14 17:28 ../\n" +"-rw-r--r-- 1 andreh users 565 déc. 15 17:24 about.md\n" +"-rw-r--r-- 1 andreh users 330 déc. 19 10:04 aja.md\n" +"-rw-r--r-- 1 andreh users 125 déc. 19 10:04 aja-par-categorie.md\n" +"-rw-r--r-- 1 andreh users 496 déc. 19 10:04 a-propos.md\n" +"drwxr-xr-x 2 andreh users 4,0K déc. 16 04:36 _articles/\n" +"-rw-r--r-- 1 andreh users 136 déc. 15 17:04 articles-by-category.md\n" +"-rw-r--r-- 1 andreh users 139 déc. 19 10:04 articles-par-categorie.md\n" +"-rw-r--r-- 1 andreh users 137 déc. 19 10:04 artigos-por-categoria.md\n" +"-rw-r--r-- 1 andreh users 140 déc. 19 10:04 artikoloj-lau-kategorio.md\n" +"-rw-r--r-- 1 andreh users 508 oct. 23 09:35 .build.yml\n" +"-rw-r--r-- 1 andreh users 9,0K déc. 19 10:09 _config.yml\n" +"-rw-r--r-- 1 andreh users 34K déc. 18 22:48 COPYING\n" +"-rw-r--r-- 1 andreh users 2,4K déc. 19 09:28 default.nix\n" +"-rw-r--r-- 1 andreh users 41 déc. 4 13:43 description\n" +"-rw-r--r-- 1 andreh users 134 déc. 19 10:04 diapositives.md\n" +"-rw-r--r-- 1 andreh users 139 déc. 19 10:04 diapositives-par-categorie.md\n" +"drwxr-xr-x 2 andreh users 4,0K nov. 15 20:01 en/\n" +"drwxr-xr-x 2 andreh users 4,0K nov. 15 20:08 eo/\n" +"-rw-r--r-- 1 andreh users 159 déc. 19 10:04 episodes-de-podcast-par-categorie.md\n" +"-rw-r--r-- 1 andreh users 159 déc. 19 10:04 episodios-do-podcast-por-categoria.md\n" +"-rw-r--r-- 1 andreh users 130 déc. 19 10:04 eslaides.md\n" +"-rw-r--r-- 1 andreh users 134 déc. 19 10:04 eslaides-por-categoria.md\n" +"-rw-r--r-- 1 andreh users 1,2K nov. 15 20:01 favicon.ico\n" +"drwxr-xr-x 2 andreh users 4,0K nov. 15 20:08 fr/\n" +"-rw-r--r-- 1 andreh users 54 déc. 6 13:57 Gemfile\n" +"-rw-r--r-- 1 andreh users 1,6K déc. 6 13:57 Gemfile.lock\n" +"drwxr-xr-x 11 andreh users 4,0K déc. 19 10:44 .git/\n" +"-rw-r--r-- 1 andreh users 75 oct. 16 07:05 .gitignore\n" +"-rw-r--r-- 1 andreh users 100 oct. 14 06:42 .gitmodules\n" +"-rw-r--r-- 1 andreh users 317 déc. 19 10:04 hea.md\n" +"-rw-r--r-- 1 andreh users 124 déc. 19 10:04 hea-por-categoria.md\n" +"-rw-r--r-- 1 andreh users 125 déc. 19 10:04 hml-lau-kategorio.md\n" +"-rw-r--r-- 1 andreh users 309 déc. 19 10:04 hml.md\n" +"-rw-r--r-- 1 andreh users 27 nov. 14 13:51 .ignore\n" +"drwxr-xr-x 2 andreh users 4,0K déc. 19 10:44 _includes/\n" +"-rw-r--r-- 1 andreh users 123 nov. 15 20:01 index.md\n" +"drwxr-xr-x 3 andreh users 4,0K déc. 19 03:02 .jekyll-cache/\n" +"drwxr-xr-x 2 andreh users 4,0K déc. 19 09:29 _layouts/\n" +"drwxr-xr-x 5 andreh users 4,0K nov. 15 20:07 locale/\n" +"-rw-r--r-- 1 andreh users 136 déc. 19 10:04 lumbildoj-lau-kategorio.md\n" +"-rw-r--r-- 1 andreh users 131 déc. 19 10:04 lumbildoj.md\n" +"drwxr-xr-x 2 andreh users 4,0K nov. 4 17:26 nix/\n" +"drwxr-xr-x 2 andreh users 4,0K déc. 19 03:20 _pastebins/\n" +"-rw-r--r-- 1 andreh users 139 déc. 15 17:08 pastebins-by-category.md\n" +"-rw-r--r-- 1 andreh users 140 nov. 15 20:01 pastebins.en.md\n" +"-rw-r--r-- 1 andreh users 140 déc. 19 10:04 pastebins.eo.md\n" +"-rw-r--r-- 1 andreh users 140 déc. 19 10:04 pastebins.fr.md\n" +"-rw-r--r-- 1 andreh users 142 déc. 19 10:04 pastebins-lau-kategorio.md\n" +"-rw-r--r-- 1 andreh users 142 déc. 19 10:04 pastebins-par-categorie.md\n" +"-rw-r--r-- 1 andreh users 141 déc. 19 10:04 pastebins-por-categoria.md\n" +"-rw-r--r-- 1 andreh users 140 déc. 19 10:04 pastebins.pt.md\n" +"drwxr-xr-x 2 andreh users 4,0K déc. 19 09:04 _plugins/\n" +"-rw-r--r-- 1 andreh users 134 déc. 19 09:29 podcast.en.md\n" +"-rw-r--r-- 1 andreh users 152 déc. 19 09:29 podcast-episodes-by-category.md\n" +"-rw-r--r-- 1 andreh users 134 déc. 19 10:04 podcast.fr.md\n" +"-rw-r--r-- 1 andreh users 134 déc. 19 10:04 podcast.pt.md\n" +"drwxr-xr-x 2 andreh users 4,0K déc. 19 10:45 _podcasts/\n" +"-rw-r--r-- 1 andreh users 151 déc. 19 10:04 podkastajoj-lau-kategorio.md\n" +"-rw-r--r-- 1 andreh users 135 déc. 19 10:04 podkasto.md\n" +"-rw-r--r-- 1 andreh users 471 déc. 19 10:04 pri.md\n" +"drwxr-xr-x 2 andreh users 4,0K nov. 15 20:08 pt/\n" +"-rw-r--r-- 1 andreh users 3,8K nov. 15 20:01 public-key.txt\n" +"-rw-r--r-- 1 andreh users 58 oct. 23 09:54 README\n" +"drwxr-xr-x 3 andreh users 4,0K déc. 19 09:00 resources/\n" +"lrwxrwxrwx 1 andreh users 54 déc. 19 10:44 result -> /nix/store/czw8d9gcim51k76ixcgmdpi9kpvysc9d-publish.sh/\n" +"drwxr-xr-x 3 andreh users 4,0K déc. 19 10:35 scripts/\n" +"-rw-r--r-- 1 andreh users 29 juil. 23 18:37 shell.nix\n" +"drwxr-xr-x 17 andreh users 4,0K déc. 19 10:35 _site/\n" +"-rw-r--r-- 1 andreh users 3,9K déc. 19 10:29 site.json\n" +"-rw-r--r-- 1 andreh users 1,9K nov. 15 20:01 sitemap.xml\n" +"drwxr-xr-x 2 andreh users 4,0K déc. 16 04:36 _slides/\n" +"-rw-r--r-- 1 andreh users 130 déc. 15 17:08 slides-by-category.md\n" +"-rw-r--r-- 1 andreh users 25 nov. 15 20:01 slides.css\n" +"-rw-r--r-- 1 andreh users 128 nov. 15 20:01 slides.md\n" +"-rw-r--r-- 1 andreh users 471 déc. 19 10:04 sobre.md\n" +"drwxr-xr-x 2 andreh users 4,0K déc. 19 09:04 static/\n" +"-rw-r--r-- 1 andreh users 2,4K déc. 15 16:06 styles.css\n" +"-rwxr-xr-x 1 andreh users 265 nov. 6 10:16 tests.sh\n" +"-rw-r--r-- 1 andreh users 122 déc. 15 17:41 til-by-category.md\n" +"-rw-r--r-- 1 andreh users 265 nov. 15 20:01 til.md\n" +"drwxr-xr-x 2 andreh users 4,0K déc. 16 04:03 _tils/\n" +"drwxr-xr-x 3 andreh users 4,0K oct. 10 09:20 vendor/\n" +msgstr "" + +msgid "layout: post" +msgstr "" + +#~ msgid "layout: cast" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_screencasts/2020-12-24-sample-screencast.po b/po/fr/LC_MESSAGES/_screencasts/2020-12-24-sample-screencast.po new file mode 100644 index 0000000..fd199dc --- /dev/null +++ b/po/fr/LC_MESSAGES/_screencasts/2020-12-24-sample-screencast.po @@ -0,0 +1,33 @@ +# +msgid "" +msgstr "" + +msgid "title: Sample screencast" +msgstr "" + +msgid "date: 2020-12-24" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: sample-screencast" +msgstr "" + +msgid "slug: sample-screencast" +msgstr "" + +msgid "video: true" +msgstr "" + +msgid "An screencast." +msgstr "" + +msgid "$ seq\n" +msgstr "" + +msgid "layout: post" +msgstr "" + +#~ msgid "layout: cast" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_screencasts/2021-02-07-autoqemu-automate-installation-and-ssh-setup-of-iso-os-images.po b/po/fr/LC_MESSAGES/_screencasts/2021-02-07-autoqemu-automate-installation-and-ssh-setup-of-iso-os-images.po new file mode 100644 index 0000000..b0c24a9 --- /dev/null +++ b/po/fr/LC_MESSAGES/_screencasts/2021-02-07-autoqemu-automate-installation-and-ssh-setup-of-iso-os-images.po @@ -0,0 +1,97 @@ +# +msgid "" +msgstr "" + +msgid "title: AutoQEMU - automate installation and SSH setup of ISO OS images" +msgstr "" + +msgid "date: 2021-02-07" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: autoqemu-automate-installation-and-ssh-setup-of-iso-os-images" +msgstr "" + +msgid "video: true" +msgstr "" + +msgid "" +"After reading begriffs \"[Tips for stable and portable " +"software](https://begriffs.com/posts/2020-08-31-portable-stable-" +"software.html)\", the \"Begriffs Buildfarm?\" section caught my attention, " +"as this is something I would be interested in." +msgstr "" + +msgid "" +"After emailing the author, a [public " +"thread](https://talk.begriffs.com/pipermail/friends/2021-February/001263.html)" +" began on the subject." +msgstr "" + +msgid "" +"As we discussed how it could be done, I decided to experiment with the idea " +"of automating the setup of virtual environments with QEMU." +msgstr "" + +msgid "" +"As of this writing, I just worked on it for 2~3 days, so everything is still" +" pretty ad-hoc." +msgstr "" + +msgid "The commands from the screencast were[^script-command]:" +msgstr "" + +msgid "" +"[^script-command]: Only now, writing again what I ran on the screencast I " +"thought that I should have tried something like " +"[script](https://www.man7.org/linux/man-pages/man1/script.1.html). Maybe " +"next time (thanks [klaatu](https://gnuworldorder.info/) for the tip!)." +msgstr "" + +msgid "It assumes that `$HOME/.local/bin` is in `$PATH`." +msgstr "" + +msgid "" +"pushd `mktemp -d`\n" +"git clone https://euandreh.xyz/autoqemu.git .\n" +"make\n" +"make install PREFIX=$HOME/.local\n" +"autoqemu ssh alpine\n" +msgstr "" + +msgid "" +"This screencast is a simple demo of automating the installation of Alpine " +"Linux 3.12.3 standard x86_64 with " +"[AutoQEMU](https://euandreh.xyz/autoqemu.git/about), which is nothing more " +"than POSIX sh, [expect](https://core.tcl-lang.org/expect/index) scripts and " +"Makefiles glued together." +msgstr "" + +#~ msgid "" +#~ "This screencast is a simple demo of automating the installation of Alpine " +#~ "Linux 3.12.3 standard x86_64 with " +#~ "[AutoQEMU](https://euandreh.xyz/autoqemu.git/), which is nothing more than " +#~ "POSIX sh, [expect](https://core.tcl-lang.org/expect/index) scripts and " +#~ "Makefiles glued together." +#~ msgstr "" + +#~ msgid "" +#~ "pushd `mktemp -d`\n" +#~ "git clone https://euandreh.xyz/autoqemu.git .\n" +#~ "./configure --prefix=$HOME/.local\n" +#~ "make install\n" +#~ "autoqemu ssh alpine\n" +#~ msgstr "" + +#~ msgid "" +#~ "This screencast is a simple demo of automating the installation of Alpine " +#~ "Linux 3.12.3 standard x86_64 with " +#~ "[AutoQEMU](https://euandreh.xyz/autoqemu.git), which is nothing more than " +#~ "POSIX sh, [expect](https://core.tcl-lang.org/expect/index) scripts and " +#~ "Makefiles glued together." +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_slides/2020-10-19-rollout-feature-flag-experiment-operational-toggle.slides.po b/po/fr/LC_MESSAGES/_slides/2020-10-19-rollout-feature-flag-experiment-operational-toggle.slides.po new file mode 100644 index 0000000..065fb90 --- /dev/null +++ b/po/fr/LC_MESSAGES/_slides/2020-10-19-rollout-feature-flag-experiment-operational-toggle.slides.po @@ -0,0 +1,456 @@ +# +msgid "" +msgstr "" + +msgid "Rollout, feature flag, experiment, operational toggle" +msgstr "" + +msgid "Different use cases for **backend**, **frontend** and **mobile**" +msgstr "" + +msgid "" +"\"Feature flags\" tend to come up when talking about **continuous " +"deployment**" +msgstr "" + +msgid "???" +msgstr "" + +msgid "I'm using \"quotes\" because I'm mixing up different meanings of \"rollout\"" +msgstr "" + +msgid "CI" +msgstr "" + +msgid "continuous integration" +msgstr "" + +msgid "CD" +msgstr "" + +msgid "continuous delivery" +msgstr "" + +msgid "**continuous deployment**" +msgstr "" + +msgid "Background: build vocabulary, why are feature flags related to CD" +msgstr "" + +msgid "CI solves: manual integration of long-lived branches" +msgstr "" + +msgid "CD solves: automation of deployment process" +msgstr "" + +msgid "CD solves: releases as frequent as possible" +msgstr "" + +msgid "That's where the \"GoCD\" name comes from" +msgstr "" + +msgid "Types:" +msgstr "" + +msgid "rollout" +msgstr "" + +msgid "feature flag" +msgstr "" + +msgid "experiment" +msgstr "" + +msgid "operational toggle" +msgstr "" + +msgid "For *rolling out* a new version of software" +msgstr "" + +msgid "**Short-lived** using **percentages**" +msgstr "" + +msgid "" +"a [new deployment of " +"k8s](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#creating-" +"a-deployment)" +msgstr "" + +msgid "" +"new [APK released to the Play " +"Store](https://support.google.com/googleplay/android-" +"developer/answer/6346149?hl=en)" +msgstr "" + +msgid "Relevant as long as the new code is deployed" +msgstr "" + +msgid "For turning a feature *on* or *off*" +msgstr "" + +msgid "" +"**Medium-lived** using **allow list**, **A/B test**, **percentage**, **app " +"version**, *etc*." +msgstr "" + +msgid "`:new-chargeback-flow`" +msgstr "" + +msgid "`:new-debit-card-activation-screen`" +msgstr "" + +msgid "Relevant as long as the new code is being developed" +msgstr "" + +msgid "For analyzing behaviour" +msgstr "" + +msgid "**Medium-lived** using **allow list** and **A/B test**" +msgstr "" + +msgid "`:debit-withdrawal-test`" +msgstr "" + +msgid "For disabling features in `#crash`-like situations" +msgstr "" + +msgid "**Long-lived** using **percentage**" +msgstr "" + +msgid "`:bank-barcode-payment`" +msgstr "" + +msgid "`:savings-bank-barcode-query-provider`" +msgstr "" + +msgid "Lives for as long as the code is in production." +msgstr "" + +msgid "It feels like a system-level circuit breaker." +msgstr "" + +msgid "We now know about the types" +msgstr "" + +msgid "" +"But they have different relevance for **backend**, **frontend** and " +"**mobile**" +msgstr "" + +msgid "backend" +msgstr "" + +msgid "**experiment**: `common-xp`" +msgstr "" + +msgid "" +"This is a bit why common-rollout isn't called *common-feature-flag*: it was " +"initially designed with backend usage of mostly *rollouts* in mind, and just" +" a bit *feature flags*." +msgstr "" + +msgid "" +"Avoid using configuration for doing operational toggles: it is less dynamic," +" so it defeats the purpose." +msgstr "" + +msgid "frontend" +msgstr "" + +msgid "**rollout**: CDN and page refreshes" +msgstr "" + +msgid "" +"**feature flag**: percentages and maybe IPs (no `:customer/id` on the " +"website)" +msgstr "" + +msgid "**experiment**: via dynamic backend control" +msgstr "" + +msgid "**operational toggle**: via dynamic backend control" +msgstr "" + +msgid "mobile" +msgstr "" + +msgid "**rollout**: app stores" +msgstr "" + +msgid "**feature flag**: via dynamic backend control" +msgstr "" + +msgid "Key differentiator is" +msgstr "" + +msgid "How much **control** we have over the **environment**" +msgstr "" + +msgid "**backend**" +msgstr "" + +msgid "Full control" +msgstr "" + +msgid "🎉" +msgstr "" + +msgid "Can edit, update and even delete rollouts as desired." +msgstr "" + +msgid "Mix and match at will!" +msgstr "" + +msgid "**frontend**" +msgstr "" + +msgid "Partial control" +msgstr "" + +msgid "When choose when to make a new version available" +msgstr "" + +msgid "" +"We can control when a new version is available, partially when someone will " +"upgrade it." +msgstr "" + +msgid "But it is easy to fallback to \"reload the page and try again\"." +msgstr "" + +msgid "**mobile**" +msgstr "" + +msgid "Very limited control" +msgstr "" + +msgid "app stores can restrict updates (worse for iOS)" +msgstr "" + +msgid "customers still have to download new versions" +msgstr "" + +msgid "Costs" +msgstr "" + +msgid "more complex code" +msgstr "" + +msgid "compatibility with old app versions" +msgstr "" + +msgid "nesting is exponential" +msgstr "" + +msgid "Benefits" +msgstr "" + +msgid "dynamicity" +msgstr "" + +msgid "Best practices" +msgstr "" + +msgid "Dynamic content > feature flag" +msgstr "" + +msgid "Always true for **mobile**, almost always for **frontend**" +msgstr "" + +msgid "Use `:include-list` for named groups" +msgstr "" + +msgid "Always true for **backend**, **frontend** and **mobile**" +msgstr "" + +msgid "{% raw %}" +msgstr "" + +msgid "" +"{:rules\n" +" #{{:type :include-list\n" +" :content {:filename \"debit-team-members.txt\"}}}}\n" +msgstr "" + +msgid "{% endraw %}" +msgstr "" + +msgid "Always use `:app-version`" +msgstr "" + +msgid "only for **mobile**" +msgstr "" + +msgid "" +"{:rules\n" +" #{{:type :app-version\n" +" :content {:min-version #{{:platform :android\n" +" :code 1000000}\n" +" {:platform :ios\n" +" :code 2000000}}}}}}\n" +msgstr "" + +msgid "That's how `:include-list`, `:app-version`, *etc.* were born" +msgstr "" + +msgid "Beware of many nested feature flags" +msgstr "" + +msgid "True for **backend**, **frontend** and **mobile**" +msgstr "" + +msgid "Exponential growth of combinations" +msgstr "" + +msgid "Don't delete app-facing feature flags" +msgstr "" + +msgid "True for **mobile**" +msgstr "" + +msgid "This could break old app versions, only do this intentionally" +msgstr "" + +msgid "" +"We don't have (yet) a strategy for dealing with LTS of the app, and we just " +"say: \"we'll support every app version out there\"." +msgstr "" + +msgid "Include a feature flag on the whiteboarding phase" +msgstr "" + +msgid "Include deleting/retiring the feature flag at the end" +msgstr "" + +msgid "Avoid renaming a feature flag" +msgstr "" + +msgid "Use `:app-version` with `:min-version` instead" +msgstr "" + +msgid "And most importantly..." +msgstr "" + +msgid "***Always*** rely on a feature flag on the app" +msgstr "" + +msgid "Never do a hot fix, avoid expedited releases at all costs" +msgstr "" + +msgid "" +"The app is where we have less control, so the feature flag is how we get " +"some of that control back." +msgstr "" + +msgid "This doesn't mean you'll need 1 feature flag per PR" +msgstr "" + +msgid "" +"There's not such thing as: \"This is such a small thing, it doesn't need a " +"feature flag\"" +msgstr "" + +msgid "" +"You should ask yourself: \"It this crashes the app, am I OK with waiting for" +" the next release train?\"" +msgstr "" + +msgid "Thank you!" +msgstr "" + +msgid "References:" +msgstr "" + +msgid "" +"\"[Feature Toggles (aka Feature " +"Flags)](https://martinfowler.com/articles/feature-toggles.html)\", by Pete " +"Hodgson" +msgstr "" + +msgid "" +"\"[Continuous integration vs. continuous delivery vs. continuous " +"deployment](https://www.atlassian.com/continuous-" +"delivery/principles/continuous-integration-vs-delivery-vs-deployment)\", by " +"Sten Pittet" +msgstr "" + +msgid "" +"[Accelerate](https://itrevolution.com/book/accelerate/), by N. Forsgren, J. " +"Humble and G. Kim" +msgstr "" + +msgid "Weighting costs × benefits" +msgstr "" + +msgid "The less control we have, the more we value dynamicity" +msgstr "" + +msgid "backend: sometimes worth the cost" +msgstr "" + +msgid "frontend: almost always worth cost" +msgstr "" + +msgid "mobile: **always** worth cost" +msgstr "" + +msgid "title: Rollout, feature flag, experiment, operational toggle" +msgstr "" + +msgid "date: 2020-10-19" +msgstr "" + +msgid "layout: slides" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: rollout-feature-flag-experiment-operational-toggle" +msgstr "" + +msgid "" +"article: _articles/2020-10-19-feature-flags-differences-between-backend-" +"frontend-and-mobile.md" +msgstr "" + +msgid "" +"**rollout**: k8s blue/green, canary and ~~`common-rollout`~~ `common-xp`" +msgstr "" + +msgid "**feature flag**: ~~`common-rollout`~~ `common-xp` and datasets" +msgstr "" + +msgid "**operational toggle**: ~~`common-rollout`~~ `common-xp`" +msgstr "" + +msgid "Extend ~~`common-rollout`~~ `common-xp` if required" +msgstr "" + +#~ msgid "**rollout**: k8s blue/green, canary and `common-rollout`" +#~ msgstr "" + +#~ msgid "**feature flag**: `common-rollout` and datasets" +#~ msgstr "" + +#~ msgid "**operational toggle**: `common-rollout`" +#~ msgstr "" + +#~ msgid "Extend `common-rollout` if required" +#~ msgstr "" + +#~ msgid "" +#~ "title: Rollout, feature flag, experiment, operational toggle\n" +#~ "date: 2020-10-19\n" +#~ "layout: slides\n" +#~ "lang: en\n" +#~ "ref: rollout-feature-flag-experiment-operational-toggle" +#~ msgstr "" + +#~ msgid "these slides: [{{ site.tld }}/slides.html]({% link slides.md %})" +#~ msgstr "" + +#~ msgid "" +#~ "[prose version of this presentation]({% link _articles/2020-10-19-feature-" +#~ "flags-differences-between-backend-frontend-and-mobile.md %})" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_slides/2020-10-22-datomic-on-global-good-reasons-for-and-against-it.slides.po b/po/fr/LC_MESSAGES/_slides/2020-10-22-datomic-on-global-good-reasons-for-and-against-it.slides.po new file mode 100644 index 0000000..78298f6 --- /dev/null +++ b/po/fr/LC_MESSAGES/_slides/2020-10-22-datomic-on-global-good-reasons-for-and-against-it.slides.po @@ -0,0 +1,166 @@ +# +msgid "" +msgstr "" + +msgid "" +"title: \"Datomic on global: good reasons for and against it\"\n" +"date: 2020-10-22\n" +"layout: slides\n" +"lang: en\n" +"ref: datomic-on-global-good-reasons-for-and-against-it\n" +"published: false" +msgstr "" + +msgid "Datomic on global" +msgstr "" + +msgid "**Good** reasons for and against it" +msgstr "" + +msgid "When creating a new service..." +msgstr "" + +msgid "...which is, in my opinion, a poor heuristic." +msgstr "" + +msgid "notifications vs toasty" +msgstr "" + +msgid "jurassic-park vs auth" +msgstr "" + +msgid "Thank you!" +msgstr "" + +msgid "References:" +msgstr "" + +msgid "these slides: [{{ site.tld }}/slides.html]({% link slides.md %})" +msgstr "" + +msgid "" +"[prose version of this presentation]({% link _articles/2020-10-22-datomic-" +"on-global-good-reasons-for-and-against-it.md %})" +msgstr "" + +msgid "Premise" +msgstr "" + +msgid "Datomic's bottleneck is **write** throughput, not read" +msgstr "" + +msgid "" +"(defn database-for-service\n" +" [service]\n" +" (let [prototype (prototype-for-service service)]\n" +" (if (= :global prototype)\n" +" :datomic\n" +" #{:dynamodb :redis :nothing})))\n" +msgstr "" + +msgid "" +"The deciding factor shouldn't be the prototype, but the **cardinality**" +msgstr "" + +msgid "" +" (defn database-for-service\n" +" [service]\n" +"- (let [prototype (prototype-for-service service)]\n" +"- (if (= :global prototype)\n" +"- :datomic\n" +"- #{:dynamodb :redis :nothing})))\n" +"+ (let [cardinality (cardinality-for-service service)]\n" +"+ (if (= :too-high cardinality)\n" +"+ #{:dynamodb :redis :nothing\n" +"+ :datomic))))\n" +msgstr "" + +msgid "" +"(defn database-for-service\n" +" [service]\n" +" (let [cardinality (cardinality-for-service service)]\n" +" (if (= :too-high cardinality)\n" +" #{:dynamodb :redis :nothing\n" +" :datomic))))\n" +msgstr "" + +msgid "But how to determine when the cardinality is" +msgstr "" + +msgid "**`:too-high`**?" +msgstr "" + +msgid "Let's think about the cardinality of existing services we know" +msgstr "" + +msgid "What is the cardinality of..." +msgstr "" + +msgid "savings-accounts" +msgstr "" + +msgid "inductor" +msgstr "" + +msgid "crebito" +msgstr "" + +msgid "diablo" +msgstr "" + +msgid "lost-boy?" +msgstr "" + +msgid "hook?" +msgstr "" + +msgid "ledger" +msgstr "" + +msgid "blackleach" +msgstr "" + +msgid "notification" +msgstr "" + +msgid "toasty" +msgstr "" + +msgid "auth" +msgstr "" + +msgid "waypoint" +msgstr "" + +msgid "jurassic-park" +msgstr "" + +msgid "Compare the database choice of services with similar cardinalities:" +msgstr "" + +msgid "Compare different cardinalities for services on global prototype:" +msgstr "" + +msgid "" +"Compare different cardinality for different services inside the same domain:" +msgstr "" + +msgid "savings-accounts -> blackleach -> diablo -> ledger" +msgstr "" + +msgid "" +"\"[Understanding Database " +"Sharding](https://www.digitalocean.com/community/tutorials/understanding-" +"database-sharding)\"" +msgstr "" + +#~ msgid "" +#~ "(defn prototype->database\n" +#~ " [prototype]\n" +#~ " (if (= :global prototype)\n" +#~ " :datomic\n" +#~ " #{:dynamodb :redis :nothing}))\n" +#~ msgstr "" + +#~ msgid "blackleach -> diablo -> ledger" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_slides/2020-10-22-graphql-for-bffs-navigating-the-trade-offs.slides.po b/po/fr/LC_MESSAGES/_slides/2020-10-22-graphql-for-bffs-navigating-the-trade-offs.slides.po new file mode 100644 index 0000000..4765ffb --- /dev/null +++ b/po/fr/LC_MESSAGES/_slides/2020-10-22-graphql-for-bffs-navigating-the-trade-offs.slides.po @@ -0,0 +1,237 @@ +# +msgid "" +msgstr "" + +msgid "" +"title: \"GraphQL for BFFs: navigating the trade-offs\"\n" +"date: 2020-10-22\n" +"layout: slides\n" +"lang: en\n" +"ref: graphql-for-bffs-navigating-the-trade-offs\n" +"published: false" +msgstr "" + +msgid "GraphQL for BFFs" +msgstr "" + +msgid "Navigating the trade-offs" +msgstr "" + +msgid "???" +msgstr "" + +msgid "slides já estão online, com sugestões incorporadas" +msgstr "" + +msgid "artigo online" +msgstr "" + +msgid "tupy: começar pelos slides é mais fácil" +msgstr "" + +msgid "Mobile is **hard**" +msgstr "" + +msgid "Immature ecosystem" +msgstr "" + +msgid "" +"Compared to desktop, browser and server ecosystem, which are many years " +"older." +msgstr "" + +msgid "iOS SDK released on 2008, which is:" +msgstr "" + +msgid "the same year Python 3.0 was released;" +msgstr "" + +msgid "" +"1 year after Clojure's release and 13 years after Java's and JavaScript's " +"release;" +msgstr "" + +msgid "10 years after GTK release" +msgstr "" + +msgid "Almost no competition" +msgstr "" + +msgid "Effectively a duopoly, better than a monopoly, but meh." +msgstr "" + +msgid "Closed, walled gardens." +msgstr "" + +msgid "Less competition, lower quality." +msgstr "" + +msgid "Compare to: browser ecosystem, desktop ecosystem" +msgstr "" + +msgid "Little to no control over the environment" +msgstr "" + +msgid "Bad on Android, worse on iOS." +msgstr "" + +msgid "Our usage of GraphQL" +msgstr "" + +msgid "History goes here" +msgstr "" + +msgid "savings: React Native, GraphQL, TypeScript, stormshield" +msgstr "" + +msgid "Proposal" +msgstr "" + +msgid "Adopt GraphQL as the default for BFFs" +msgstr "" + +msgid "Target" +msgstr "" + +msgid "**data fetching** and **chaining**" +msgstr "" + +msgid "It is not about:" +msgstr "" + +msgid "over fetching" +msgstr "" + +msgid "different clients with different data requirements" +msgstr "" + +msgid "Goal" +msgstr "" + +msgid "" +"Move **complexity** out of mobile to the backend, get more **dynamicity** " +"out of it ???" +msgstr "" + +msgid "The complexity doesn't vanish or shrink, it just shifts." +msgstr "" + +msgid "" +"https://media.tenor.com/images/ce1962c14da22c969e664560e098b2bc/tenor.gif" +msgstr "" + +msgid "Alternatives" +msgstr "" + +msgid "AKA, why not \"just use a RESTful BFF\"?" +msgstr "" + +msgid "REST" +msgstr "" + +msgid "It doesn't address JOINs" +msgstr "" + +msgid "Fulcro" +msgstr "" + +msgid "For 10 reasons for using GraphQL, 8~9 are shared for Fulcro." +msgstr "" + +msgid "The other 1~2 aren't so relevant:" +msgstr "" + +msgid "data > syntax: already false for Swift, Kotlin, Dart" +msgstr "" + +msgid "attributes > aggregates: already false for Swift, Kotlin, Dart" +msgstr "" + +msgid "Falcor" +msgstr "" + +msgid "SOAP" +msgstr "" + +msgid "Implications" +msgstr "" + +msgid "Invalid arguments" +msgstr "" + +msgid "\"GraphQL isn't RESTful\"" +msgstr "" + +msgid "🤷" +msgstr "" + +msgid "Similar to saying \"REST isn't GraphQL\"" +msgstr "" + +msgid "\"GraphQL has a bad caching story\"" +msgstr "" + +msgid "True, but we don't do HTTP caching" +msgstr "" + +msgid "\"query-params can be used for selection in a BFF with REST\"" +msgstr "" + +msgid "👎" +msgstr "" + +msgid "This isn't RESTful, and is an *ad-hoc* querying format" +msgstr "" + +msgid "\"over-fetching isn't a problem\"" +msgstr "" + +msgid "That is not the main reason for GraphQL" +msgstr "" + +msgid "\"library X for GraphQL is bad\"" +msgstr "" + +msgid "Valid arguments" +msgstr "" + +msgid "\"Throttling by query complexity is hard\"" +msgstr "" + +msgid "Lessons learned" +msgstr "" + +msgid "Error handling" +msgstr "" + +msgid "Takeaways" +msgstr "" + +msgid "None of the points are specific to Flutter" +msgstr "" + +msgid "GraphQL enables declarative **dynamicity**" +msgstr "" + +msgid "Thank you!" +msgstr "" + +msgid "References:" +msgstr "" + +msgid "" +"[prose version of this presentation]({% link _articles/2020-10-22-graphql-" +"for-bffs-navigating-the-trade-offs.md %})" +msgstr "" + +msgid "" +"\"[Clients in control: building demand-driven systems with Om " +"Next](https://www.youtube.com/watch?v=Zb18iPjDgwM)\", by António Nuno " +"Monteiro" +msgstr "" + +msgid "\"[Om Next](https://www.youtube.com/watch?v=MDZpSIngwm4)\", by David Nolen" +msgstr "" + +msgid "these slides: [{{ site.tld }}/slides.html]({% link slides.md %})" +msgstr "" diff --git a/po/fr/LC_MESSAGES/_slides/2020-10-26-on-local-first-beyond-the-crdt-silver-bullet.slides.po b/po/fr/LC_MESSAGES/_slides/2020-10-26-on-local-first-beyond-the-crdt-silver-bullet.slides.po new file mode 100644 index 0000000..e34f58e --- /dev/null +++ b/po/fr/LC_MESSAGES/_slides/2020-10-26-on-local-first-beyond-the-crdt-silver-bullet.slides.po @@ -0,0 +1,339 @@ +# +msgid "" +msgstr "" + +msgid "On local-first" +msgstr "" + +msgid "Beyond the CRDT silver bullet" +msgstr "" + +msgid "Part 1" +msgstr "" + +msgid "Exposition" +msgstr "" + +msgid "\"cloud apps\" vs \"old-fashined apps\"" +msgstr "" + +msgid "Target" +msgstr "" + +msgid "documents" +msgstr "" + +msgid "files" +msgstr "" + +msgid "personal data repositories" +msgstr "" + +msgid "" +"Not: banking services, e-commerce, social networking, ride-sharing, *etc*." +msgstr "" + +msgid "7 Ideals for local-first software" +msgstr "" + +msgid "1 - No Spinners: Your Work at Your Fingertips" +msgstr "" + +msgid "2 - Your Work Is Not Trapped on One Device" +msgstr "" + +msgid "3 - The Network Is Optional" +msgstr "" + +msgid "4 - Seamless Collaboration with Your Colleagues" +msgstr "" + +msgid "5 - The Long Now" +msgstr "" + +msgid "6 - Security and Privacy by Default" +msgstr "" + +msgid "7 - You Retain Ultimate Ownership and Control" +msgstr "" + +msgid "Towards a Better Future" +msgstr "" + +msgid "" +"CRDTs (Conflict-free Replicated Data Types) as a Foundational Technology" +msgstr "" + +msgid "Use case" +msgstr "" + +msgid "" +"# in node A and node B\n" +"s = \"Hello, World\"\n" +"\n" +"# in node A\n" +"s = \"Hello, Alice\"\n" +"\n" +"# in node B\n" +"s = \"Hello, Bob\"\n" +msgstr "" + +msgid "How to reconcile those?" +msgstr "" + +msgid "`Hello, ABloibce`" +msgstr "" + +msgid "`Hello, AliceBob`" +msgstr "" + +msgid "`Hello, BobAlice`" +msgstr "" + +msgid "`Hello, Alice`" +msgstr "" + +msgid "`Hello, Bob`" +msgstr "" + +msgid "Existing CRDTs differ:" +msgstr "" + +msgid "performance" +msgstr "" + +msgid "storage" +msgstr "" + +msgid "compression" +msgstr "" + +msgid "metadata overhead" +msgstr "" + +msgid "Hint towards the \"automerge\" CRDT" +msgstr "" + +msgid "*show comparison table, page 9*" +msgstr "" + +msgid "Part 2" +msgstr "" + +msgid "Critique" +msgstr "" + +msgid "Software license" +msgstr "" + +msgid "" +"In our opinion, maintaining control and ownership of data does not mean that" +" the software must necessarily be open source." +msgstr "" + +msgid "Example 1 - intentional restriction" +msgstr "" + +msgid "" +"#!/bin/sh\n" +"\n" +"TODAY=$(date +%s)\n" +"LICENSE_EXPIRATION=$(date -d 2020-10-27 +%s)\n" +"\n" +"if [ $TODAY -ge $LICENSE_EXPIRATION ]; then\n" +" echo 'License expired!'\n" +" exit 1\n" +"fi\n" +"\n" +"echo $((2 + 2))\n" +msgstr "" + +msgid "" +"# today\n" +"$ ./useful-adder.sh\n" +"4\n" +"# tomorrow\n" +"$ ./useful-adder.sh\n" +"License expired!\n" +msgstr "" + +msgid "Example 2 - unintentional restriction" +msgstr "" + +msgid "" +"# today\n" +"$ useful-program\n" +"# ...useful output...\n" +"\n" +"# tomorrow, with more data\n" +"$ useful-program\n" +"ERROR: Panic! Stack overflow!\n" +msgstr "" + +msgid "local-first **requires** free/libre software" +msgstr "" + +msgid "Otherwise \"The Long Now\" (ideal nº5) is lost" +msgstr "" + +msgid "Denial of existing solutions" +msgstr "" + +msgid "" +"In principle it is possible to collaborate without a repository service, " +"e.g. by sending patch files by email, but the majority of Git users rely on " +"GitHub." +msgstr "" + +msgid "Solution: either GitHub+CRDTs or `git` **`send-email`**" +msgstr "" + +msgid "Plain text formats" +msgstr "" + +msgid "Git is highly optimized for code and similar line-based text file" +msgstr "" + +msgid "It even pulls software to the plain text direction, e.g.:" +msgstr "" + +msgid "delivery-templates" +msgstr "" + +msgid "`common-core.protocols.config`" +msgstr "" + +msgid "Why not exploit that more?" +msgstr "" + +msgid "Ditching of web applications" +msgstr "" + +msgid "The architecture of web apps remains fundamentally server-centric" +msgstr "" + +msgid "" +"Disagree. Constrast [PouchDB](https://pouchdb.com/) with Android [Instant " +"Apps](https://developer.android.com/topic/google-play-instant)" +msgstr "" + +msgid "???" +msgstr "" + +msgid "Talk on dynamic content" +msgstr "" + +msgid "Costs are underrated" +msgstr "" + +msgid "backups" +msgstr "" + +msgid "maintanence" +msgstr "" + +msgid "Example: blog vs vlog" +msgstr "" + +msgid "Real-time collaboration a bit overrated" +msgstr "" + +msgid "" +"It is only possible on the presence of reliable, medium-quality network " +"connection" +msgstr "" + +msgid "X also works when inside an elevator, subway or plane!" +msgstr "" + +msgid "On CRDTs and developer experience" +msgstr "" + +msgid "" +"For an app developer, how does the use of a CRDT-based data layer compare to" +" existing storage layers like a SQL database, a filesystem, or CoreData? Is " +"a distributed system harder to write software for?" +msgstr "" + +msgid "Yes." +msgstr "" + +msgid "" +"See \"[A Note on Distributed " +"Computing](https://web.archive.org/web/20130116163535/http://labs.oracle.com/techrep/1994/smli_tr-94-29.pdf)\"" +msgstr "" + +msgid "Conclusion" +msgstr "" + +msgid "Why this is a \"paper I love\": it took offline-first and ran with it." +msgstr "" + +msgid "But a pinch of CRDT won't make the world local-first." +msgstr "" + +msgid "The tricky part is the end of the sentence: \"**in spite of the Cloud**\"." +msgstr "" + +msgid "Thank you!" +msgstr "" + +msgid "References:" +msgstr "" + +msgid "these slides: [{{ site.tld }}/slides.html]({% link slides.md %})" +msgstr "" + +msgid "" +"\"[Local-First Software: You Own Your Data, in spite of the " +"Cloud](https://martin.kleppmann.com/papers/local-first.pdf)\", by M. " +"Kleppmann, A. Wiggins, P. Van Hardenberg and M. F. McGranaghan" +msgstr "" + +msgid "" +"[The Morning Paper](https://blog.acolyer.org/2019/11/20/local-first-" +"software/) article" +msgstr "" + +msgid "title: 'On \"local-first\": beyond the CRDT silver bullet'" +msgstr "" + +msgid "date: 2020-10-26" +msgstr "" + +msgid "layout: slides" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: on-local-first-beyond-the-crdt-silver-bullet" +msgstr "" + +msgid "published: false" +msgstr "" + +msgid "" +"[prose version of this presentation]({% link _articles/2020-10-26-local-" +"first-software-you-own-your-data-in-spite-of-the-cloud-article-review.md %})" +msgstr "" + +msgid "" +"\"[A Note on Distributed " +"Computing](https://web.archive.org/web/20130116163535/http://labs.oracle.com/techrep/1994/smli_tr-94-29.pdf)\"," +" by J. Waldo, G. Wyant, A. Wollrath and S Kendall" +msgstr "" + +#~ msgid "" +#~ "title: 'On \"local-first\": beyond the CRDT silver bullet'\n" +#~ "date: 2020-10-26\n" +#~ "layout: slides\n" +#~ "lang: en\n" +#~ "ref: on-local-first-beyond-the-crdt-silver-bullet\n" +#~ "published: false" +#~ msgstr "" + +#~ msgid "" +#~ "[prose version of this presentation]({% link _articles/2020-10-26-on-local-" +#~ "first-beyond-the-crdt-silver-bullet.md %})" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_slides/2020-11-14-on-local-first-beyond-the-crdt-silver-bullet.slides.po b/po/fr/LC_MESSAGES/_slides/2020-11-14-on-local-first-beyond-the-crdt-silver-bullet.slides.po new file mode 100644 index 0000000..61a7485 --- /dev/null +++ b/po/fr/LC_MESSAGES/_slides/2020-11-14-on-local-first-beyond-the-crdt-silver-bullet.slides.po @@ -0,0 +1,330 @@ +# +msgid "" +msgstr "" + +msgid "title: 'On \"local-first\": beyond the CRDT silver bullet'" +msgstr "" + +msgid "date: 2020-11-14" +msgstr "" + +msgid "layout: slides" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: on-local-first-beyond-the-crdt-silver-bullet" +msgstr "" + +msgid "On local-first" +msgstr "" + +msgid "Beyond the CRDT silver bullet" +msgstr "" + +msgid "Part 1" +msgstr "" + +msgid "Exposition" +msgstr "" + +msgid "\"cloud apps\" vs \"old-fashioned apps\"" +msgstr "" + +msgid "Target" +msgstr "" + +msgid "documents" +msgstr "" + +msgid "files" +msgstr "" + +msgid "personal data repositories" +msgstr "" + +msgid "" +"Not: banking services, e-commerce, social networking, ride-sharing, *etc*." +msgstr "" + +msgid "7 Ideals for local-first software" +msgstr "" + +msgid "1 - No Spinners: Your Work at Your Fingertips" +msgstr "" + +msgid "2 - Your Work Is Not Trapped on One Device" +msgstr "" + +msgid "3 - The Network Is Optional" +msgstr "" + +msgid "4 - Seamless Collaboration with Your Colleagues" +msgstr "" + +msgid "5 - The Long Now" +msgstr "" + +msgid "6 - Security and Privacy by Default" +msgstr "" + +msgid "7 - You Retain Ultimate Ownership and Control" +msgstr "" + +msgid "Towards a Better Future" +msgstr "" + +msgid "" +"CRDTs (Conflict-free Replicated Data Types) as a Foundational Technology" +msgstr "" + +msgid "Use case" +msgstr "" + +msgid "" +"# in node A and node B\n" +"s = \"Hello, World\"\n" +"\n" +"# in node A\n" +"s = \"Hello, Alice\"\n" +"\n" +"# in node B\n" +"s = \"Hello, Bob\"\n" +msgstr "" + +msgid "How to reconcile those?" +msgstr "" + +msgid "`Hello, ABloibce`" +msgstr "" + +msgid "`Hello, AliceBob`" +msgstr "" + +msgid "`Hello, BobAlice`" +msgstr "" + +msgid "`Hello, Alice`" +msgstr "" + +msgid "`Hello, Bob`" +msgstr "" + +msgid "Existing CRDTs differ:" +msgstr "" + +msgid "performance" +msgstr "" + +msgid "storage" +msgstr "" + +msgid "compression" +msgstr "" + +msgid "metadata overhead" +msgstr "" + +msgid "Hint towards the \"automerge\" CRDT" +msgstr "" + +msgid "*show comparison table, page 9*" +msgstr "" + +msgid "Part 2" +msgstr "" + +msgid "Critique" +msgstr "" + +msgid "Software license" +msgstr "" + +msgid "" +"In our opinion, maintaining control and ownership of data does not mean that" +" the software must necessarily be open source." +msgstr "" + +msgid "Example 1 - intentional restriction" +msgstr "" + +msgid "" +"#!/bin/sh\n" +"\n" +"TODAY=$(date +%s)\n" +"LICENSE_EXPIRATION=$(date -d 2020-10-27 +%s)\n" +"\n" +"if [ $TODAY -ge $LICENSE_EXPIRATION ]; then\n" +" echo 'License expired!'\n" +" exit 1\n" +"fi\n" +"\n" +"echo $((2 + 2))\n" +msgstr "" + +msgid "" +"# today\n" +"$ ./useful-adder.sh\n" +"4\n" +"# tomorrow\n" +"$ ./useful-adder.sh\n" +"License expired!\n" +msgstr "" + +msgid "Example 2 - unintentional restriction" +msgstr "" + +msgid "" +"# today\n" +"$ useful-program\n" +"# ...useful output...\n" +"\n" +"# tomorrow, with more data\n" +"$ useful-program\n" +"ERROR: Panic! Stack overflow!\n" +msgstr "" + +msgid "Otherwise \"The Long Now\" (ideal nº5) is lost" +msgstr "" + +msgid "Denial of existing solutions" +msgstr "" + +msgid "" +"In principle it is possible to collaborate without a repository service, " +"e.g. by sending patch files by email, but the majority of Git users rely on " +"GitHub." +msgstr "" + +msgid "Solution: either GitHub+CRDTs or `git` **`send-email`**" +msgstr "" + +msgid "Plain text formats" +msgstr "" + +msgid "Git is highly optimized for code and similar line-based text file" +msgstr "" + +msgid "It even pulls software to the plain text direction, e.g.:" +msgstr "" + +msgid "delivery-templates" +msgstr "" + +msgid "`common-core.protocols.config`" +msgstr "" + +msgid "Why not exploit that more?" +msgstr "" + +msgid "Ditching of web applications" +msgstr "" + +msgid "The architecture of web apps remains fundamentally server-centric" +msgstr "" + +msgid "" +"Disagree. Contrast [PouchDB](https://pouchdb.com/) with Android [Instant " +"Apps](https://developer.android.com/topic/google-play-instant)" +msgstr "" + +msgid "???" +msgstr "" + +msgid "Talk on dynamic content" +msgstr "" + +msgid "Costs are underrated" +msgstr "" + +msgid "backups" +msgstr "" + +msgid "maintenance" +msgstr "" + +msgid "Example: blog vs vlog" +msgstr "" + +msgid "Real-time collaboration a bit overrated" +msgstr "" + +msgid "" +"It is only possible on the presence of reliable, medium-quality network " +"connection" +msgstr "" + +msgid "X also works when inside an elevator, subway or plane!" +msgstr "" + +msgid "On CRDTs and developer experience" +msgstr "" + +msgid "" +"For an app developer, how does the use of a CRDT-based data layer compare to" +" existing storage layers like a SQL database, a filesystem, or CoreData? Is " +"a distributed system harder to write software for?" +msgstr "" + +msgid "Yes." +msgstr "" + +msgid "" +"See \"[A Note on Distributed " +"Computing](https://web.archive.org/web/20130116163535/http://labs.oracle.com/techrep/1994/smli_tr-94-29.pdf)\"" +msgstr "" + +msgid "Conclusion" +msgstr "" + +msgid "Why this is a \"paper I love\": it took offline-first and ran with it." +msgstr "" + +msgid "But a pinch of CRDT won't make the world local-first." +msgstr "" + +msgid "The tricky part is the end of the sentence: \"**in spite of the Cloud**\"." +msgstr "" + +msgid "Thank you!" +msgstr "" + +msgid "References:" +msgstr "" + +msgid "" +"\"[Local-First Software: You Own Your Data, in spite of the " +"Cloud](https://martin.kleppmann.com/papers/local-first.pdf)\", by M. " +"Kleppmann, A. Wiggins, P. Van Hardenberg and M. F. McGranaghan" +msgstr "" + +msgid "" +"[The Morning Paper](https://blog.acolyer.org/2019/11/20/local-first-" +"software/) article" +msgstr "" + +msgid "" +"\"[A Note on Distributed " +"Computing](https://web.archive.org/web/20130116163535/http://labs.oracle.com/techrep/1994/smli_tr-94-29.pdf)\"," +" by J. Waldo, G. Wyant, A. Wollrath and S Kendall" +msgstr "" + +msgid "" +"article: _articles/2020-11-14-local-first-software-you-own-your-data-in-" +"spite-of-the-cloud-article-review.md" +msgstr "" + +msgid "local-first **requires** free software" +msgstr "" + +#~ msgid "local-first **requires** free/libre software" +#~ msgstr "" + +#~ msgid "these slides: [{{ site.tld }}/slides.html]({% link slides.md %})" +#~ msgstr "" + +#~ msgid "" +#~ "[prose version of this presentation]({% link _articles/2020-11-14-local-" +#~ "first-software-you-own-your-data-in-spite-of-the-cloud-article-review.md %})" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_tils/2020-08-12-simple-filename-timestamp.po b/po/fr/LC_MESSAGES/_tils/2020-08-12-simple-filename-timestamp.po new file mode 100644 index 0000000..ef8e489 --- /dev/null +++ b/po/fr/LC_MESSAGES/_tils/2020-08-12-simple-filename-timestamp.po @@ -0,0 +1,68 @@ +# +msgid "" +msgstr "" + +msgid "" +"When writing Jekyll posts or creating log files with dates on them, I " +"usually struggle with finding a direct way of accomplishing that. There's a " +"simple solution: `date -I`." +msgstr "" + +msgid "" +"Using this built-in GNU/Linux tool allows you to `touch $(date -I).md` to " +"readily create a `2020-08-12.md` file." +msgstr "" + +msgid "" +"I always had to read `man date` or search the web over and over, and after " +"doing this repeatedly it became clear that both `date -I` and `date -Is` " +"(`s` here stands for seconds) are the thing that I'm looking for 95% of the " +"time:" +msgstr "" + +msgid "" +"Both date formats are hierarchical, having the bigger time intervals to the " +"left. This means that you can easily sort them (and even tab-complete them) " +"with no extra effort or tool required." +msgstr "" + +msgid "title: Simple filename timestamp" +msgstr "" + +msgid "date: 2020-08-12" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: simple-filename-timestamp" +msgstr "" + +msgid "updated_at:" +msgstr "" + +msgid "" +"./my-program.sh > my-program.$(date -I).log\n" +"cp post-template.md _posts/$(date -I)-post-slug.md\n" +msgstr "" + +msgid "" +"# inside my-program.sh\n" +"echo \"Program started at $(date -Is)\"\n" +"# output is:\n" +"# Program started at 2020-08-12T09:04:58-03:00\n" +msgstr "" + +msgid "eu_categories: shell" +msgstr "" + +#~ msgid "" +#~ "title: Simple filename timestamp\n" +#~ "date: 2020-08-12\n" +#~ "layout: post\n" +#~ "lang: en\n" +#~ "ref: simple-filename-timestamp" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_tils/2020-08-13-anchor-headers-and-code-lines-in-jekyll.po b/po/fr/LC_MESSAGES/_tils/2020-08-13-anchor-headers-and-code-lines-in-jekyll.po new file mode 100644 index 0000000..a11e17c --- /dev/null +++ b/po/fr/LC_MESSAGES/_tils/2020-08-13-anchor-headers-and-code-lines-in-jekyll.po @@ -0,0 +1,187 @@ +# +msgid "" +msgstr "" + +msgid "" +"title: Anchor headers and code lines in Jekyll\n" +"date: 2020-08-13\n" +"layout: post\n" +"lang: en\n" +"ref: anchor-headers-and-code-lines-in-jekyll" +msgstr "" + +msgid "" +"The default Jekyll toolbox ([Jekyll](https://jekyllrb.com/), " +"[kramdown](https://kramdown.gettalong.org/) and " +"[rouge](http://rouge.jneen.net/)) doesn't provide with a configuration " +"option to add anchors to headers and code blocks." +msgstr "" + +msgid "" +"The best way I found of doing this is by creating a simple Jekyll plugin, " +"more specifically, a [Jekyll " +"hook](https://jekyllrb.com/docs/plugins/hooks/). These allow you to jump in " +"to the Jekyll build and add a processing stage before of after Jekyll " +"performs something." +msgstr "" + +msgid "" +"All you have to do is add the code to `_plugins/my-jekyll-plugin-code.rb`, " +"and Jekyll knows to pick it up and call your code on the appropriate time." +msgstr "" + +msgid "Anchor on headers" +msgstr "" + +msgid "" +"Since I wanted to add anchors to headers in all documents, this Jekyll hook " +"works on `:documents` after they have been transformed into HTML, the " +"`:post_render` phase:" +msgstr "" + +msgid "" +"I've derived my implementations from two \"official\"[^official] hooks, " +"[jemoji](https://github.com/jekyll/jemoji) and [jekyll-" +"mentions](https://github.com/jekyll/jekyll-mentions)." +msgstr "" + +msgid "" +"[^official]: I don't know how official they are, I just assumed it because " +"they live in the same organization inside GitHub that Jekyll does." +msgstr "" + +msgid "" +"All I did was to wrap the header tag inside an `<a>`, and set the `href` of " +"that `<a>` to the existing id of the header. Before the hook the HTML looks " +"like:" +msgstr "" + +msgid "And after the hook should turn that into:" +msgstr "" + +msgid "" +"The used regexp tries to match only h1-h6 tags, and keep the rest of the " +"HTML attributes untouched, since this isn't a general HTML parser, but the " +"generated HTML is somewhat under your control. Use at your own risk because " +"[you shouldn't parse HTML with " +"regexps](https://stackoverflow.com/questions/1732348/regex-match-open-tags-" +"except-xhtml-self-contained-tags/1732454#1732454). Also I used this strategy" +" in my environment, where no other plugins are installed. I haven't " +"considered how this approach may conflict with other Jekyll plugins." +msgstr "" + +msgid "" +"In the new anchor tag you can add your custom CSS class to style it as you " +"wish." +msgstr "" + +msgid "Anchor on code blocks" +msgstr "" + +msgid "" +"Adding anchors to code blocks needs a little bit of extra work, because line" +" numbers themselves don't have preexisting ids, so we need to generate them " +"without duplications between multiple code blocks in the same page." +msgstr "" + +msgid "" +"Similarly, this Jekyll hook also works on `:documents` in the `:post_render`" +" phase:" +msgstr "" + +msgid "" +"This solution assumes the default Jekyll toolbox with code line numbers " +"turned on in `_config.yml`:" +msgstr "" + +msgid "" +"The anchors go from B1-L1 to BN-LN, using the `code_block_counter` to track " +"which code block we're in and don't duplicate anchor ids. Before the hook " +"the HTML looks like:" +msgstr "" + +msgid "Happy writing :)" +msgstr "" + +msgid "" +"Jekyll::Hooks.register :documents, :post_render do |doc|\n" +" if doc.output_ext == \".html\"\n" +" doc.output =\n" +" doc.output.gsub(\n" +" /<h([1-6])(.*?)id=\"([\\w-]+)\"(.*?)>(.*?)<\\/h[1-6]>/,\n" +" '<a href=\"#\\3\"><h\\1\\2id=\"\\3\"\\4>\\5</h\\1></a>'\n" +" )\n" +" end\n" +"end\n" +msgstr "" + +msgid "" +"...some unmodified text...\n" +"<h2 id=\"my-header\">\n" +" My header\n" +"</h2>\n" +"...more unmodified text...\n" +msgstr "" + +msgid "" +"...some unmodified text...\n" +"<a href=\"#my-header\">\n" +" <h2 id=\"my-header\">\n" +" My header\n" +" </h2>\n" +"</a>\n" +"...more unmodified text...\n" +msgstr "" + +msgid "" +"PREFIX = '<pre class=\"lineno\">'\n" +"POSTFIX = '</pre>'\n" +"Jekyll::Hooks.register :documents, :post_render do |doc|\n" +" if doc.output_ext == \".html\"\n" +" code_block_counter = 1\n" +" doc.output = doc.output.gsub(/<pre class=\"lineno\">[\\n0-9]+<\\/pre>/) do |match|\n" +" line_numbers = match\n" +" .gsub(/<pre class=\"lineno\">([\\n0-9]+)<\\/pre>/, '\\1')\n" +" .split(\"\\n\")\n" +"\n" +" anchored_line_numbers_array = line_numbers.map do |n|\n" +" id = \"B#{code_block_counter}-L#{n}\"\n" +" \"<a id=\\\"#{id}\\\" href=\\\"##{id}\\\">#{n}</a>\"\n" +" end\n" +" code_block_counter += 1\n" +"\n" +" PREFIX + anchored_line_numbers_array.join(\"\\n\") + POSTFIX\n" +" end\n" +" end\n" +"end\n" +msgstr "" + +msgid "" +"kramdown:\n" +" syntax_highlighter_opts:\n" +" span:\n" +" line_numbers: false\n" +" block:\n" +" line_numbers: true\n" +msgstr "" + +msgid "" +"...some unmodified text...\n" +"<pre class=\"lineno\">1\n" +"2\n" +"3\n" +"4\n" +"5\n" +"</pre>\n" +"...more unmodified text...\n" +msgstr "" + +msgid "" +"...some unmodified text...\n" +"<pre class=\"lineno\"><a id=\"B1-L1\" href=\"#B1-L1\">1</a>\n" +"<a id=\"B1-L2\" href=\"#B1-L2\">2</a>\n" +"<a id=\"B1-L3\" href=\"#B1-L3\">3</a>\n" +"<a id=\"B1-L4\" href=\"#B1-L4\">4</a>\n" +"<a id=\"B1-L5\" href=\"#B1-L5\">5</a></pre>\n" +"...more unmodified text...\n" +msgstr "" diff --git a/po/fr/LC_MESSAGES/_tils/2020-08-14-browse-a-git-repository-at-a-specific-commit.po b/po/fr/LC_MESSAGES/_tils/2020-08-14-browse-a-git-repository-at-a-specific-commit.po new file mode 100644 index 0000000..6030e0c --- /dev/null +++ b/po/fr/LC_MESSAGES/_tils/2020-08-14-browse-a-git-repository-at-a-specific-commit.po @@ -0,0 +1,119 @@ +# +msgid "" +msgstr "" + +msgid "" +"I commonly use tools like `git log` together with `git show` when inspecting" +" past changes in a repository:" +msgstr "" + +msgid "" +"But I also wanted to not only be able to look at the diff of a specific " +"commit, but to browse the whole repository at that specific commit." +msgstr "" + +msgid "" +"I used to accomplish it the \"brute force\" way: clone the whole repository " +"in another folder and checkout the commit there:" +msgstr "" + +msgid "" +"But git itself allows we to specific the directory of the checkout by using " +"the `--work-tree` global git flag. This is what `man git` says about it:" +msgstr "" + +msgid "" +"So it allows us to set the desired path of the working tree. So if we want " +"to copy the contents of the current working tree into `copy/`:" +msgstr "" + +msgid "" +"After that `copy/` will contain a replica of the code in HEAD. But to " +"checkout a specific, we need some extra parameters:" +msgstr "" + +msgid "" +"There's an extra `-- .` at the end, which initially looks like we're sending" +" Morse signals to git, but we're actually saying to `git-checkout` which sub" +" directory of `<my-commit>` we want to look at. Which means we can do " +"something like:" +msgstr "" + +msgid "" +"And with that `<dir>` will only contain what was inside `src/` at " +"`<commit>`." +msgstr "" + +msgid "" +"After any of those checkouts, you have to `git reset .` to reset your " +"current staging area back to what it was before the checkout." +msgstr "" + +msgid "" +"[GIT: Checkout to a specific folder](https://stackoverflow.com/a/16493707) " +"(StackOverflow)" +msgstr "" + +msgid "" +"git log\n" +"# search for a the commit I'm looking for\n" +"git show <my-commit>\n" +"# see the diff for the commit\n" +msgstr "" + +msgid "" +"git clone <original-repo> /tmp/tmp-repo-clone\n" +"cd /tmp-repo-clone\n" +"git checkout <my-commit>\n" +msgstr "" + +msgid "" +"--work-tree=<path>\n" +" Set the path to the working tree. It can be an absolute path or a path relative to the current working\n" +" directory. This can also be controlled by setting the GIT_WORK_TREE environment variable and the\n" +" core.worktree configuration variable (see core.worktree in git-config(1) for a more detailed\n" +" discussion).\n" +msgstr "" + +msgid "" +"mkdir copy\n" +"git --work-tree=copy/ checkout .\n" +msgstr "" + +msgid "git --work-tree=<dir> checkout <my-commit> -- .\n" +msgstr "" + +msgid "git --work-tree=<dir> checkout <my-commit> -- src/\n" +msgstr "" + +msgid "title: Browse a git repository at a specific commit" +msgstr "" + +msgid "date: 2020-08-14" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: browse-a-git-repository-at-a-specific-commit" +msgstr "" + +msgid "eu_categories: git" +msgstr "" + +msgid "References" +msgstr "" + +#~ msgid "References:" +#~ msgstr "" + +#~ msgid "" +#~ "title: Browse a git repository at a specific commit\n" +#~ "date: 2020-08-14\n" +#~ "layout: post\n" +#~ "lang: en\n" +#~ "ref: browse-a-git-repository-at-a-specific-commit" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_tils/2020-08-16-search-in-git.po b/po/fr/LC_MESSAGES/_tils/2020-08-16-search-in-git.po new file mode 100644 index 0000000..7b1c6cc --- /dev/null +++ b/po/fr/LC_MESSAGES/_tils/2020-08-16-search-in-git.po @@ -0,0 +1,89 @@ +# +msgid "" +msgstr "" + +msgid "Here's a useful trio to know about to help you search things in git:" +msgstr "" + +msgid "`git show <commit>`" +msgstr "" + +msgid "`git log --grep='<regexp>'`" +msgstr "" + +msgid "`git grep '<regexp>' [commit]`" +msgstr "" + +msgid "1. `git show <commit>`" +msgstr "" + +msgid "Show a specific commit and it's diff:" +msgstr "" + +msgid "2. `git log --grep='<regexp>'`" +msgstr "" + +msgid "Search through the commit messages:" +msgstr "" + +msgid "3. `git grep '<regexp>' [commit]`" +msgstr "" + +msgid "Search content in git history:" +msgstr "" + +msgid "" +"And if you find an occurrence of the regexp in a specific commit and you " +"want to browse the repository in that point in time, you can [use git " +"checkout for that][0]." +msgstr "" + +msgid "" +"[0]: {% link _tils/2020-08-14-browse-a-git-repository-at-a-specific-" +"commit.md %}" +msgstr "" + +msgid "" +"git show\n" +"# shows the latest commit\n" +"git show <commit>\n" +"# shows an specific <commit>\n" +"git show v1.2\n" +"# shows commit tagged with v1.2\n" +msgstr "" + +msgid "git log --grep='refactor'\n" +msgstr "" + +msgid "" +"git grep 'TODO'\n" +"# search the repository for the \"TODO\" string\n" +"git grep 'TODO' $(git rev-list --all)\n" +"# search the whole history for \"TODO\" string\n" +msgstr "" + +msgid "title: Search in git" +msgstr "" + +msgid "date: 2020-08-16" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: search-in-git" +msgstr "" + +msgid "eu_categories: git" +msgstr "" + +#~ msgid "" +#~ "title: Search in git\n" +#~ "date: 2020-08-16\n" +#~ "layout: post\n" +#~ "lang: en\n" +#~ "ref: search-in-git" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_tils/2020-08-28-grep-online-repositories.po b/po/fr/LC_MESSAGES/_tils/2020-08-28-grep-online-repositories.po new file mode 100644 index 0000000..a339bb6 --- /dev/null +++ b/po/fr/LC_MESSAGES/_tils/2020-08-28-grep-online-repositories.po @@ -0,0 +1,184 @@ +# +msgid "" +msgstr "" + +msgid "" +"I often find interesting source code repositories online that I want to grep" +" for some pattern but I can't, because either:" +msgstr "" + +msgid "" +"the repository is on [cgit](https://git.zx2c4.com/cgit/) or a similar code " +"repository that doesn't allow search in files, or;" +msgstr "" + +msgid "" +"the search function is really bad, and doesn't allow me to use regular " +"expressions for searching patterns in the code." +msgstr "" + +msgid "" +"Here's a simple script that allows you to overcome that problem easily:" +msgstr "" + +msgid "" +"It is a wrapper around `git grep` that downloads the repository when " +"missing. Save in a file called `git-search`, make the file executable and " +"add it to your path." +msgstr "" + +msgid "Overview:" +msgstr "" + +msgid "*lines 1~2*:" +msgstr "" + +msgid "" +"Bash shebang and the `set -eu` options to exit on error or undefined " +"variables." +msgstr "" + +msgid "*lines 4~30*:" +msgstr "" + +msgid "Usage text to be printed when providing less arguments than expected." +msgstr "" + +msgid "*line 33*:" +msgstr "" + +msgid "Extract the repository name from the URL, removing trailing slashes." +msgstr "" + +msgid "*lines 34~37*:" +msgstr "" + +msgid "Download the repository when missing and go to the folder." +msgstr "" + +msgid "*line 39*:" +msgstr "" + +msgid "Make the variable `$@` contain the rest of the unused arguments." +msgstr "" + +msgid "*line 40*:" +msgstr "" + +msgid "Perform `git grep`, forwarding the remaining arguments from `$@`." +msgstr "" + +msgid "Example output:" +msgstr "" + +msgid "" +"Subsequent greps on the same repository are faster because no download is " +"needed." +msgstr "" + +msgid "When no argument is provided, it prints the usage text:" +msgstr "" + +msgid "" +"#!/usr/bin/env bash\n" +"set -eu\n" +"\n" +"end=\"\\033[0m\"\n" +"red=\"\\033[0;31m\"\n" +"red() { echo -e \"${red}${1}${end}\"; }\n" +"\n" +"usage() {\n" +" red \"Missing argument $1.\\n\"\n" +" cat <<EOF\n" +"Usage:\n" +" $0 <REGEX_PATTERN> <REPOSITORY_URL>\n" +"\n" +" Arguments:\n" +" REGEX_PATTERN Regular expression that \"git grep\" can search\n" +" REPOSITORY_URL URL address that \"git clone\" can download the repository from\n" +"\n" +"Examples:\n" +" Searching \"make get-git\" in cgit repository:\n" +" git search 'make get-git' https://git.zx2c4.com/cgit/\n" +" git search 'make get-git' https://git.zx2c4.com/cgit/ -- \\$(git rev-list --all)\n" +"EOF\n" +" exit 2\n" +"}\n" +"\n" +"\n" +"REGEX_PATTERN=\"${1:-}\"\n" +"REPOSITORY_URL=\"${2:-}\"\n" +"[[ -z \"${REGEX_PATTERN}\" ]] && usage 'REGEX_PATTERN'\n" +"[[ -z \"${REPOSITORY_URL}\" ]] && usage 'REPOSITORY_URL'\n" +"\n" +"mkdir -p /tmp/git-search\n" +"DIRNAME=\"$(echo \"${REPOSITORY_URL%/}\" | rev | cut -d/ -f1 | rev)\"\n" +"if [[ ! -d \"/tmp/git-search/${DIRNAME}\" ]]; then\n" +" git clone \"${REPOSITORY_URL}\" \"/tmp/git-search/${DIRNAME}\"\n" +"fi\n" +"pushd \"/tmp/git-search/${DIRNAME}\"\n" +"\n" +"shift 3 || shift 2 # when \"--\" is missing\n" +"git grep \"${REGEX_PATTERN}\" \"${@}\"\n" +msgstr "" + +msgid "" +"$ git search 'make get-git' https://git.zx2c4.com/cgit/\n" +"Clonage dans '/tmp/git-search/cgit'...\n" +"remote: Enumerating objects: 542, done.\n" +"remote: Counting objects: 100% (542/542), done.\n" +"remote: Compressing objects: 100% (101/101), done.\n" +"warning: object 51dd1eff1edc663674df9ab85d2786a40f7ae3a5: gitmodulesParse: could not parse gitmodules blob\n" +"remote: Total 7063 (delta 496), reused 446 (delta 441), pack-reused 6521\n" +"Réception d'objets: 100% (7063/7063), 8.69 Mio | 5.39 Mio/s, fait.\n" +"Résolution des deltas: 100% (5047/5047), fait.\n" +"/tmp/git-search/cgit ~/dev/libre/songbooks/docs\n" +"README: $ make get-git\n" +"\n" +"$ git search 'make get-git' https://git.zx2c4.com/cgit/\n" +"/tmp/git-search/cgit ~/dev/libre/songbooks/docs\n" +"README: $ make get-git\n" +msgstr "" + +msgid "" +"$ git search\n" +"Missing argument REGEX_PATTERN.\n" +"\n" +"Usage:\n" +" /home/andreh/dev/libre/dotfiles/scripts/ad-hoc/git-search <REGEX_PATTERN> <REPOSITORY_URL>\n" +"\n" +" Arguments:\n" +" REGEX_PATTERN Regular expression that \"git grep\" can search\n" +" REPOSITORY_URL URL address that \"git clone\" can download the repository from\n" +"\n" +"Examples:\n" +" Searching \"make get-git\" in cgit repository:\n" +" git search 'make get-git' https://git.zx2c4.com/cgit/\n" +" git search 'make get-git' https://git.zx2c4.com/cgit/ -- $(git rev-list --all)\n" +msgstr "" + +msgid "title: Grep online repositories" +msgstr "" + +msgid "date: 2020-08-28" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: grep-online-repositories" +msgstr "" + +msgid "eu_categories: git" +msgstr "" + +#~ msgid "" +#~ "title: Grep online repositories\n" +#~ "date: 2020-08-28\n" +#~ "layout: post\n" +#~ "lang: en\n" +#~ "ref: grep-online-repositories" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_tils/2020-09-04-send-emails-using-the-command-line-for-fun-and-profit.po b/po/fr/LC_MESSAGES/_tils/2020-09-04-send-emails-using-the-command-line-for-fun-and-profit.po new file mode 100644 index 0000000..1409e61 --- /dev/null +++ b/po/fr/LC_MESSAGES/_tils/2020-09-04-send-emails-using-the-command-line-for-fun-and-profit.po @@ -0,0 +1,98 @@ +# +msgid "" +msgstr "" + +msgid "" +"title: Send emails using the command line for fun and profit!\n" +"date: 2020-09-04\n" +"layout: post\n" +"lang: en\n" +"ref: send-emails-using-the-command-line-for-fun-and-profit" +msgstr "" + +msgid "Here are a few reasons why:" +msgstr "" + +msgid "" +"send yourself and other people notification of cronjobs, scripts runs, CI " +"jobs, *etc.*" +msgstr "" + +msgid "leverage the POSIX pipe `|`, and pipe emails away!" +msgstr "" + +msgid "because you can." +msgstr "" + +msgid "Reason 3 is the fun part, reasons 1 and 2 are the profit part." +msgstr "" + +msgid "" +"First [install and configure " +"SSMTP](https://wiki.archlinux.org/index.php/SSMTP) for using, say, Gmail as " +"the email server:" +msgstr "" + +msgid "" +"Now install [GNU Mailutils](https://mailutils.org/) (`sudo apt-get install " +"mailutils` or the equivalent on your OS), and send yourself your first " +"email:" +msgstr "" + +msgid "" +"And that's about it, you've got mail. Here are some more places where it " +"might be applicable:" +msgstr "" + +msgid "...and so on." +msgstr "" + +msgid "" +"You may consider adding a `alias mail='mail -aFrom:email@example.com'` so " +"you don't keep re-entering the \"From: \" part." +msgstr "" + +msgid "Send yourself some emails to see it working!" +msgstr "" + +msgid "" +"# file /etc/ssmtp/ssmtp.conf\n" +"FromLineOverride=YES\n" +"MailHub=smtp.gmail.com:587\n" +"UseSTARTTLS=YES\n" +"UseTLS=YES\n" +"rewriteDomain=gmail.com\n" +"root=username@gmail.com\n" +"AuthUser=username\n" +"AuthPass=password\n" +msgstr "" + +msgid "echo body | mail -aFrom:email@example.com email@example.com -s subject\n" +msgstr "" + +msgid "" +"# report a backup cronjob, attaching logs\n" +"set -e\n" +"\n" +"finish() {\n" +" status=$?\n" +" if [[ $status = 0 ]]; then\n" +" STATUS=\"SUCCESS (status $status)\"\n" +" else\n" +" STATUS=\"FAILURE (status $status)\"\n" +" fi\n" +"\n" +" mail user@example.com \\\n" +" -s \"Backup job report on $(hostname): ${STATUS}\" \\\n" +" --content-type 'text/plain; charset=utf-8' \\\n" +" -A\"$LOG_FILE\" <<< 'The log report is in the attachment.'\n" +"}\n" +"trap finish EXIT\n" +"\n" +"do-long-backup-cmd-here\n" +msgstr "" + +msgid "" +"# share the output of a cmd with someone\n" +"some-program | mail someone@example.com -s \"The weird logs that I was talking about\"\n" +msgstr "" diff --git a/po/fr/LC_MESSAGES/_tils/2020-09-05-pull-requests-with-git-the-old-school-way.po b/po/fr/LC_MESSAGES/_tils/2020-09-05-pull-requests-with-git-the-old-school-way.po new file mode 100644 index 0000000..4b43e70 --- /dev/null +++ b/po/fr/LC_MESSAGES/_tils/2020-09-05-pull-requests-with-git-the-old-school-way.po @@ -0,0 +1,164 @@ +# +msgid "" +msgstr "" + +msgid "" +"It might be news to you, as it was to me, that \"pull requests\" that you " +"can create on a Git hosting provider's web UI[^pr-webui] like " +"GitLab/Bitbucket/GitHub actually comes from Git itself: `git request-pull`." +msgstr "" + +msgid "" +"[^pr-webui]: And maybe even using the Git hosting provider's API from the " +"command line!" +msgstr "" + +msgid "" +"At the very core, they accomplish the same thing: both the original and the " +"web UI ones are ways for you to request the project maintainers to pull in " +"your changes from your fork. It's like saying: \"hi there, I did some " +"changes on my clone of the repository, what do you think about bringing " +"those in?\"." +msgstr "" + +msgid "" +"The only difference is that you're working with only Git itself, so you're " +"not tied to any Git hosting provider: you can send pull requests across them" +" transparently! You could even use your own " +"[cgit](https://git.zx2c4.com/cgit/) installation. No need to be locked in by" +" any of them, putting the \"D\" back in \"DVCS\": it's a **distributed** " +"version control system." +msgstr "" + +msgid "`git request-pull` introduction" +msgstr "" + +msgid "Here's the raw output of a `git request-pull`:" +msgstr "" + +msgid "" +"That very first line is saying: \"create me a pull request with only a " +"single commit, defined by `HEAD`, and use the URL defined by `public-" +"origin`\"." +msgstr "" + +msgid "" +"Here's a pitfall: you may try using your `origin` remote at first where I " +"put `public-origin`, but that is many times pointing to something like " +"`git@example.com`, or `git.example.com:repo.git` (check that with `git " +"remote -v | grep origin`). On both cases those are addresses available for " +"interaction via SSH, and it would be better if your pull requests used an " +"address ready for public consumption." +msgstr "" + +msgid "" +"A simple solution for that is for you to add the `public-origin` alias as " +"the HTTPS alternative to the SSH version:" +msgstr "" + +msgid "Every Git hosting provider exposes repositories via HTTPS." +msgstr "" + +msgid "Experiment it yourself, and get acquainted with the CLI." +msgstr "" + +msgid "Delivering decentralized pull requests" +msgstr "" + +msgid "" +"Now that you can create the content of a pull request, you can just [deliver" +" it][cli-email] to the interested parties email:" +msgstr "" + +msgid "" +"[cli-email]: {% link _tils/2020-09-04-send-emails-using-the-command-line-" +"for-fun-and-profit.md %}" +msgstr "" + +msgid "Conclusion" +msgstr "" + +msgid "" +"In practice, I've never used or seen anyone use pull requests this way: " +"everybody is just [sending patches via " +"email](https://drewdevault.com/2018/07/23/Git-is-already-distributed.html)." +msgstr "" + +msgid "" +"If you stop to think about this model, the problem of \"Git hosting " +"providers becoming too centralized\" is a non-issue, and \"Git federation\" " +"proposals are a less attractive as they may sound initially." +msgstr "" + +msgid "" +"Using Git this way is not scary or so weird as the first impression may " +"suggest. It is actually how Git was designed to be used." +msgstr "" + +msgid "Check `git help request-pull` for more info." +msgstr "" + +msgid "" +"$ git request-pull HEAD public-origin\n" +"The following changes since commit 302c9f2f035c0360acd4e13142428c100a10d43f:\n" +"\n" +" db post: Add link to email exchange (2020-09-03 21:23:55 -0300)\n" +"\n" +"are available in the Git repository at:\n" +"\n" +" https://euandreh.xyz/website.git/\n" +"\n" +"for you to fetch changes up to 524c646cdac4153e54f2163e280176adbc4873fa:\n" +"\n" +" db post: better pinpoint sqlite unsuitability (2020-09-03 22:08:56 -0300)\n" +"\n" +"----------------------------------------------------------------\n" +"EuAndreh (1):\n" +" db post: better pinpoint sqlite unsuitability\n" +"\n" +" _posts/2020-08-31-the-database-i-wish-i-had.md | 12 ++++++------\n" +" 1 file changed, 6 insertions(+), 6 deletions(-)\n" +msgstr "" + +msgid "$ git remote add public-origin https://example.com/user/repo\n" +msgstr "" + +msgid "" +"# send a PR with your last commit to the author's email\n" +"git request-pull HEAD public-origin | mail author@example.com -s \"PR: Add thing to repo\"\n" +"\n" +"# send a PR with your last 5 commits to the project's mailing\n" +"# list, including the patch\n" +"git request-pull HEAD~5 public-origin -p | \\\n" +" mail list@example.com -s \"PR: Add another thing to repo\"\n" +"\n" +"# send every commit that is new in \"other-branch\"\n" +"git request-pull master public-origin other-branch | \\\n" +" mail list@example.com -s 'PR: All commits from my \"other-brach\"'\n" +msgstr "" + +msgid "title: Pull requests with Git, the old school way" +msgstr "" + +msgid "date: 2020-09-05" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: pull-requests-with-git-the-old-school-way" +msgstr "" + +msgid "eu_categories: git" +msgstr "" + +#~ msgid "" +#~ "title: Pull requests with Git, the old school way\n" +#~ "date: 2020-09-05\n" +#~ "layout: post\n" +#~ "lang: en\n" +#~ "ref: pull-requests-with-git-the-old-school-way" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_tils/2020-10-11-search-changes-to-a-filename-pattern-in-git-history.po b/po/fr/LC_MESSAGES/_tils/2020-10-11-search-changes-to-a-filename-pattern-in-git-history.po new file mode 100644 index 0000000..baa0d1f --- /dev/null +++ b/po/fr/LC_MESSAGES/_tils/2020-10-11-search-changes-to-a-filename-pattern-in-git-history.po @@ -0,0 +1,63 @@ +# +msgid "" +msgstr "" + +msgid "" +"This is [yet][git-til-1] [another][git-til-2] [\"search in Git\"][git-til-3]" +" TIL entry. You could say that Git has a unintuitive CLI, or that is it very" +" powerful." +msgstr "" + +msgid "" +"I wanted to search for an old file that I new that was in the history of the" +" repository, but was deleted some time ago. So I didn't really remember the " +"name, only bits of it." +msgstr "" + +msgid "" +"I immediately went to the list of TILs I had written on searching in Git, " +"but it wasn't readily obvious how to do it, so here it goes:" +msgstr "" + +msgid "" +"You could add globs before the pattern to match things on any directory, and" +" add our `-p` friend to promptly see the diffs:" +msgstr "" + +msgid "" +"[git-til-1]: {% link _tils/2020-08-14-browse-a-git-repository-at-a-specific-" +"commit.md %} [git-til-2]: {% link _tils/2020-08-16-search-in-git.md %} [git-" +"til-3]: {% link _tils/2020-08-28-grep-online-repositories.md %}" +msgstr "" + +msgid "git log -- *pattern*\n" +msgstr "" + +msgid "git log -p -- **/*pattern*\n" +msgstr "" + +msgid "title: Search changes to a filename pattern in Git history" +msgstr "" + +msgid "date: 2020-10-11" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: search-changes-to-a-filename-pattern-in-git-history" +msgstr "" + +msgid "eu_categories: git" +msgstr "" + +#~ msgid "" +#~ "title: Search changes to a filename pattern in Git history\n" +#~ "date: 2020-10-11\n" +#~ "layout: post\n" +#~ "lang: en\n" +#~ "ref: search-changes-to-a-filename-pattern-in-git-history" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_tils/2020-11-08-find-broken-symlinks-with-find.po b/po/fr/LC_MESSAGES/_tils/2020-11-08-find-broken-symlinks-with-find.po new file mode 100644 index 0000000..a61c474 --- /dev/null +++ b/po/fr/LC_MESSAGES/_tils/2020-11-08-find-broken-symlinks-with-find.po @@ -0,0 +1,51 @@ +# +msgid "" +msgstr "" + +msgid "The `find` command knows how to show broken symlinks:" +msgstr "" + +msgid "find . -xtype l\n" +msgstr "" + +msgid "" +"This was useful to me when combined with [Git Annex](https://git-" +"annex.branchable.com/). Its [`wanted`](https://git-annex.branchable.com/git-" +"annex-wanted/) option allows you to have a \"sparse\" checkout of the " +"content, and save space by not having to copy every annexed file locally:" +msgstr "" + +msgid "git annex wanted . 'exclude=Music/* and exclude=Videos/*'\n" +msgstr "" + +msgid "" +"You can `find` any broken symlinks outside those directories by querying " +"with Git Annex itself, but `find . -xtype l` works on other places too, " +"where broken symlinks might be a problem." +msgstr "" + +msgid "title: Find broken symlinks with \"find\"" +msgstr "" + +msgid "date: 2020-11-08" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: find-broken-symlinks-with-find" +msgstr "" + +msgid "eu_categories: shell" +msgstr "" + +#~ msgid "" +#~ "title: Find broken symlinks with \"find\"\n" +#~ "date: 2020-11-08\n" +#~ "layout: post\n" +#~ "lang: en\n" +#~ "ref: find-broken-symlinks-with-find" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_tils/2020-11-12-diy-bare-bones-ci-server-with-bash-and-nix.po b/po/fr/LC_MESSAGES/_tils/2020-11-12-diy-bare-bones-ci-server-with-bash-and-nix.po new file mode 100644 index 0000000..f1bf8af --- /dev/null +++ b/po/fr/LC_MESSAGES/_tils/2020-11-12-diy-bare-bones-ci-server-with-bash-and-nix.po @@ -0,0 +1,129 @@ +# +msgid "" +msgstr "" + +msgid "title: DIY bare bones CI server with Bash and Nix" +msgstr "" + +msgid "date: 2020-11-12 3" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: diy-bare-bones-ci-server-with-bash-and-nix" +msgstr "" + +msgid "" +"With a server with Nix installed (no need for NixOS), you can leverage its " +"build isolation for running CI jobs by adding a [post-receive](https://git-" +"scm.com/book/en/v2/Customizing-Git-Git-Hooks) Git hook to the server." +msgstr "" + +msgid "" +"In most of my project I like to keep a `test` attribute which runs the test " +"with `nix-build -A test`. This way, a post-receive hook could look like:" +msgstr "" + +msgid "" +"We initially (lines #5 to #8) create a log file, named after *when* the run " +"is running and for *which* commit it is running for. The `exec` and `tee` " +"combo allows the output of the script to go both to `stdout` *and* the log " +"file. This makes the logs output show up when you do a `git push`." +msgstr "" + +msgid "" +"Lines #10 to #13 create a fresh clone of the repository and line #20 runs " +"the test command." +msgstr "" + +msgid "Upsides" +msgstr "" + +msgid "No vendor lock-in, as all you need is a server with Nix installed." +msgstr "" + +msgid "" +"And if you pin the Nixpkgs version you're using, this very simple setup " +"yields extremely sandboxed runs on a very hermetic environment." +msgstr "" + +msgid "Downsides" +msgstr "" + +msgid "" +"Besides the many missing shiny features of this very simplistic CI, `nix-" +"build` can be very resource intensive. Specifically, it consumes too much " +"memory. So if it has to download too many things, or the build closure gets " +"too big, the server might very well run out of memory." +msgstr "" + +msgid "" +"#!/usr/bin/env bash\n" +"set -Eeuo pipefail\n" +"set -x\n" +"\n" +"LOGS_DIR=\"/data/static/ci-logs/libedn\"\n" +"mkdir -p \"$LOGS_DIR\"\n" +"LOGFILE=\"${LOGS_DIR}/$(date -Is)-$(git rev-parse master).log\"\n" +"exec &> >(tee -a \"${LOGFILE}\")\n" +"\n" +"unset GIT_DIR\n" +"CLONE=\"$(mktemp -d)\"\n" +"git clone . \"$CLONE\"\n" +"pushd \"$CLONE\"\n" +"\n" +"finish() {\n" +" printf \"\\n\\n>>> exit status was %s\\n\" \"$?\"\n" +"}\n" +"trap finish EXIT\n" +"\n" +"nix-build -A test\n" +msgstr "" + +msgid "eu_categories: ci" +msgstr "" + +msgid "" +"After using a similar post-receive hook for a while, I now even generate a " +"simple HTML file to make the logs available ([example " +"project](https://euandreh.xyz/remembering/ci.html)) through the browser." +msgstr "" + +#~ msgid "" +#~ "After using a similar post-receive hook for a while, I now even generate a " +#~ "simple HTML file to make the logs available ([example " +#~ "project](https://euandreh.xyz/remembering/)) through the browser." +#~ msgstr "" + +#~ msgid "" +#~ "After using a similar post-receive hook for a while, I now even generate a " +#~ "simple HTML file to make the [logs available](https://ci.euandreh.xyz/) " +#~ "through the browser." +#~ msgstr "" + +#~ msgid "" +#~ "#!/usr/bin/env bash\n" +#~ "set -Eeuo pipefail\n" +#~ "set -x\n" +#~ "\n" +#~ "LOGS_PREFIX=\"/data/static/ci-logs/libedn\"\n" +#~ "mkdir -p \"$LOGS_DIR\"\n" +#~ "LOGFILE=\"${LOGS_DIR}/$(date -Is)-$(git rev-parse master).log\"\n" +#~ "exec &> >(tee -a \"${LOGFILE}\")\n" +#~ "\n" +#~ "unset GIT_DIR\n" +#~ "CLONE=\"$(mktemp -d)\"\n" +#~ "git clone . \"$CLONE\"\n" +#~ "pushd \"$CLONE\"\n" +#~ "\n" +#~ "finish() {\n" +#~ " printf \"\\n\\n>>> exit status was %s\\n\" \"$?\"\n" +#~ "}\n" +#~ "trap finish EXIT\n" +#~ "\n" +#~ "nix-build -A test\n" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_tils/2020-11-12-git-bisect-automation.po b/po/fr/LC_MESSAGES/_tils/2020-11-12-git-bisect-automation.po new file mode 100644 index 0000000..09ec261 --- /dev/null +++ b/po/fr/LC_MESSAGES/_tils/2020-11-12-git-bisect-automation.po @@ -0,0 +1,53 @@ +# +msgid "" +msgstr "" + +msgid "title: Git bisect automation" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: git-bisect-automation" +msgstr "" + +msgid "" +"It is good to have an standardized way to run builds and tests on the " +"repository of a project, so that you can find when a bug was introduced by " +"using `git bisect run`." +msgstr "" + +msgid "" +"I've already been in the situation when a bug was introduced and I didn't " +"know how it even was occurring, and running Git bisect over hundreds of " +"commits to pinpoint the failing commit was very empowering:" +msgstr "" + +msgid "" +"$ GOOD_COMMIT_SHA=e1fd0a817d192c5a5df72dd7422e36558fa78e46\n" +"$ git bisect start HEAD $GOOD_COMMIT_SHA\n" +"$ git bisect run sn -c './build.sh && ./run-failing-case.sh'\n" +msgstr "" + +msgid "" +"Git will than do a binary search between the commits, and run the commands " +"you provide it with to find the failing commit." +msgstr "" + +msgid "" +"Instead of being afraid of doing a bisect, you should instead leverage it, " +"and make Git help you dig through the history of the repository to find the " +"bad code." +msgstr "" + +msgid "date: 2020-11-12 2" +msgstr "" + +msgid "eu_categories: git" +msgstr "" + +#~ msgid "date: 2020-11-12" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_tils/2020-11-12-useful-bash-variables.po b/po/fr/LC_MESSAGES/_tils/2020-11-12-useful-bash-variables.po new file mode 100644 index 0000000..6147dec --- /dev/null +++ b/po/fr/LC_MESSAGES/_tils/2020-11-12-useful-bash-variables.po @@ -0,0 +1,94 @@ +# +msgid "" +msgstr "" + +msgid "title: Useful Bash variables" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: useful-bash-variables" +msgstr "" + +msgid "" +"[GNU Bash](https://www.gnu.org/software/bash/) has a few two letter " +"variables that may be useful when typing on the terminal." +msgstr "" + +msgid "`!!`: the text of the last command" +msgstr "" + +msgid "" +"The [`!!` " +"variable](https://www.gnu.org/software/bash/manual/bash.html#Event-" +"Designators) refers to the previous command, and I find useful when " +"following chains for symlinks:" +msgstr "" + +msgid "" +"$ which git\n" +"/run/current-system/sw/bin/git\n" +"$ readlink $(!!)\n" +"readlink $(which git)\n" +"/nix/store/5bgr1xpm4m0r72h9049jbbhagxdyrnyb-git-2.28.0/bin/git\n" +msgstr "" + +msgid "" +"It is also useful when you forget to prefix `sudo` to a command that " +"requires it:" +msgstr "" + +msgid "" +"$ requires-sudo.sh\n" +"requires-sudo.sh: Permission denied\n" +"$ sudo !!\n" +"sudo ./requires-sudo.sh\n" +"# all good\n" +msgstr "" + +msgid "" +"Bash prints the command expansion before executing it, so it is better for " +"you to follow along what it is doing." +msgstr "" + +msgid "`$_`: most recent parameter" +msgstr "" + +msgid "" +"The [`$_` " +"variable](https://www.gnu.org/software/bash/manual/bash.html#Special-" +"Parameters) will give you the most recent parameter you provided to a " +"previous argument, which can save you typing sometimes:" +msgstr "" + +msgid "" +"# instead of...\n" +"$ mkdir -p a/b/c/d/\n" +"$ cd a/b/c/d/\n" +"\n" +"# ...you can:\n" +"$ mkdir -p a/b/c/d/\n" +"$ cd $_\n" +msgstr "" + +msgid "Conclusion" +msgstr "" + +msgid "" +"I wouldn't use those in a script, as it would make the script terser to " +"read, I find those useful shortcut that are handy when writing at the " +"interactive terminal." +msgstr "" + +msgid "date: 2020-11-12 1" +msgstr "" + +msgid "eu_categories: shell" +msgstr "" + +#~ msgid "date: 2020-11-12" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_tils/2020-11-14-gpodder-as-a-media-subscription-manager.po b/po/fr/LC_MESSAGES/_tils/2020-11-14-gpodder-as-a-media-subscription-manager.po new file mode 100644 index 0000000..141ee40 --- /dev/null +++ b/po/fr/LC_MESSAGES/_tils/2020-11-14-gpodder-as-a-media-subscription-manager.po @@ -0,0 +1,49 @@ +# +msgid "" +msgstr "" + +msgid "title: gPodder as a media subscription manager" +msgstr "" + +msgid "date: 2020-11-14" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: gpodder-as-a-media-subscription-manager" +msgstr "" + +msgid "" +"As we [re-discover](https://www.charlieharrington.com/unexpected-useless-" +"and-urgent) the value of Atom/RSS feeds, most useful feed clients I know of " +"don't support media, specifically audio and video." +msgstr "" + +msgid "[gPodder](https://gpodder.github.io/) does." +msgstr "" + +msgid "" +"It is mostly know as a desktop podcatcher. But the thing about podcasts is " +"that the feed is provided through an RSS/Atom feed. So you can just use " +"gPodder as your media feed client, where you have control of what you look " +"at." +msgstr "" + +msgid "" +"I audio and video providers I know of offer an RSS/Atom view of their " +"content, so you can, say, treat any YouTube channel like a feed on its own." +msgstr "" + +msgid "" +"gPodder will then managed your feeds, watched/unwatched, queue downloads, " +"etc." +msgstr "" + +msgid "" +"Being obvious now, it was a big finding for me. If it got you interested, I " +"recommend you giving gPodder a try." +msgstr "" diff --git a/po/fr/LC_MESSAGES/_tils/2020-11-30-storing-ci-data-on-git-notes.po b/po/fr/LC_MESSAGES/_tils/2020-11-30-storing-ci-data-on-git-notes.po new file mode 100644 index 0000000..e9cc227 --- /dev/null +++ b/po/fr/LC_MESSAGES/_tils/2020-11-30-storing-ci-data-on-git-notes.po @@ -0,0 +1,149 @@ +# +msgid "" +msgstr "" + +msgid "title: Storing CI data on Git notes" +msgstr "" + +msgid "date: 2020-11-30" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: storing-ci-data-on-git-notes" +msgstr "" + +msgid "" +"Extending the bare bones CI server I've [talked about before][previous-" +"article], divoplade on Freenode suggested storing CI artifacts on [Git " +"notes][git-notes], such as tarballs, binaries, logs, *etc*." +msgstr "" + +msgid "" +"I've written a small script that will put log files and CI job data on Git " +"notes, and make it visible on the porcelain log. It is a simple extension of" +" the previous article:" +msgstr "" + +msgid "" +"#!/usr/bin/env bash\n" +"set -Eeuo pipefail\n" +"set -x\n" +"\n" +"PREFIX='/srv/ci/vps'\n" +"mkdir -p \"$PREFIX\"\n" +"read -r _ SHA _ # oldrev newrev refname\n" +"FILENAME=\"$(date -Is)-$SHA.log\"\n" +"LOGFILE=\"$PREFIX/$FILENAME\"\n" +"exec &> >(tee -a \"$LOGFILE\")\n" +"\n" +"echo \"Starting CI job at: $(date -Is)\"\n" +"\n" +"finish() {\n" +" STATUS=\"$?\"\n" +" printf \"\\n\\n>>> exit status was %s\\n\" \"$STATUS\"\n" +" echo \"Finishing CI job at: $(date -Is)\"\n" +" popd\n" +" NOTE=$(cat <<EOF\n" +"See CI logs with:\n" +" git notes --ref=refs/notes/ci-logs show $SHA\n" +" git notes --ref=refs/notes/ci-data show $SHA\n" +"EOF\n" +")\n" +" git notes --ref=refs/notes/ci-data add -f -m \"$STATUS $FILENAME\"\n" +" git notes --ref=refs/notes/ci-logs add -f -F \"$LOGFILE\"\n" +" git notes add -f -m \"$NOTE\"\n" +" printf \"\\n\\n>>> CI logs added as Git note.\"\n" +"}\n" +"trap finish EXIT\n" +"\n" +"unset GIT_DIR\n" +"CLONE=\"$(mktemp -d)\"\n" +"git clone . \"$CLONE\"\n" +"pushd \"$CLONE\"\n" +"git config --global user.email git@euandre.org\n" +"git config --global user.name 'EuAndreh CI'\n" +"\n" +"./container make check site\n" +"./container make publish\n" +msgstr "" + +msgid "The important part is in the `finish()` function:" +msgstr "" + +msgid "" +"#25 stores the exit status and the generated filename separated by spaces;" +msgstr "" + +msgid "#26 adds the log file in a note using the `refs/notes/ci-logs` ref;" +msgstr "" + +msgid "#27 it adds a note to the commit saying how to see the logs." +msgstr "" + +msgid "" +"A commit now has an attached note, and shows it whenever you look at it:" +msgstr "" + +msgid "" +"$ git show 930ba1888f49f11e52a4a715438cd9f5f413dd9c\n" +"commit 930ba1888f49f11e52a4a715438cd9f5f413dd9c (oldvps/master)\n" +"Author: EuAndreh <eu@euandre.org>\n" +"Date: Mon Nov 30 01:11:38 2020 -0300\n" +"\n" +" vps.scm: Uncomment mcron job time marker\n" +"\n" +"Notes:\n" +" See CI logs with:\n" +" git notes --ref=refs/notes/ci-logs show 930ba1888f49f11e52a4a715438cd9f5f413dd9c\n" +" git notes --ref=refs/notes/ci-data show 930ba1888f49f11e52a4a715438cd9f5f413dd9c\n" +"\n" +"diff --git a/sync/vps.scm b/sync/vps.scm\n" +"index 3f6ca69..02b9cc6 100644\n" +"--- a/sync/vps.scm\n" +"+++ b/sync/vps.scm\n" +"@@ -280,7 +280,7 @@ pki \" mail-domain \" key \\\"\" (tls-priv-for mail-domain) \"\\\"\")))\n" +" tls-prefixes)))\n" +"\n" +" (define generate-ci-index-html-job\n" +"- #~(job \"* * * * *\" ;; \"*/5 * * * *\"\n" +"+ #~(job \"*/5 * * * *\"\n" +" #$(program-file\n" +" \"generate-ci-index-html.scm\"\n" +" (with-imported-modules (modules:source-module-closure\n" +msgstr "" + +msgid "" +"Other tools such as [cgit][cgit] will also show notes on the web interface: " +"[https://euandreh.xyz/vps.git/commit?id=930ba1888f49f11e52a4a715438cd9f5f413dd9c](https://euandreh.xyz/vps.git/commit?id=930ba1888f49f11e52a4a715438cd9f5f413dd9c)" +msgstr "" + +msgid "" +"You can go even further: since cgit can serve raw blob directly, you can " +"even serve such artifacts (log files, release artifacts, binaries) from cgit" +" itself:" +msgstr "" + +msgid "" +"$ SHA=\"$(git notes --ref=refs/notes/ci-logs list 930ba1888f49f11e52a4a715438cd9f5f413dd9c)\"\n" +"$ echo \"https://euandreh.xyz/vps.git/blob?id=$SHA\"\n" +"https://euandreh.xyz/vps.git/blob?id=b3a6438a0c7a47864c54c61359b6ef50e864dbff\n" +msgstr "" + +msgid "" +"And like that you'll have cgit serving the artifacts for you: " +"[https://euandreh.xyz/vps.git/blob?id=b3a6438a0c7a47864c54c61359b6ef50e864dbff](https://euandreh.xyz/vps.git/blob?id=b3a6438a0c7a47864c54c61359b6ef50e864dbff)" +msgstr "" + +msgid "" +"[previous-article]: {% link _tils/2020-11-12-diy-bare-bones-ci-server-with-" +"bash-and-nix.md %} [git-notes]: https://git-scm.com/docs/git-notes [cgit]: " +"https://git.zx2c4.com/cgit/" +msgstr "" + +msgid "eu_categories: git,ci" +msgstr "" diff --git a/po/fr/LC_MESSAGES/_tils/2020-12-15-awk-snippet-shellcheck-all-scripts-in-a-repository.po b/po/fr/LC_MESSAGES/_tils/2020-12-15-awk-snippet-shellcheck-all-scripts-in-a-repository.po new file mode 100644 index 0000000..e671224 --- /dev/null +++ b/po/fr/LC_MESSAGES/_tils/2020-12-15-awk-snippet-shellcheck-all-scripts-in-a-repository.po @@ -0,0 +1,240 @@ +# +msgid "" +msgstr "" + +msgid "" +"Inspired by Fred Herbert's \"[Awk in 20 Minutes](https://ferd.ca/awk-" +"in-20-minutes.html)\", here's a problem I just solved with a line of Awk: " +"run ShellCheck in all scripts of a repository." +msgstr "" + +msgid "" +"In my repositories I usually have Bash and POSIX scripts, which I want to " +"keep tidy with [ShellCheck](https://www.shellcheck.net/). Here's the first " +"version of `assert-shellcheck.sh`:" +msgstr "" + +msgid "" +"This is the type of script that I copy around to all repositories, and I " +"want it to be capable of working on any repository, without requiring a list" +" of files to run ShellCheck on." +msgstr "" + +msgid "" +"This first version worked fine, as all my scripts had the '.sh' ending. But " +"I recently added some scripts without any extension, so `assert-" +"shellcheck.sh` called for a second version. The first attempt was to try " +"grepping the shebang line:" +msgstr "" + +msgid "" +"$ grep '^#!/' assert-shellcheck.sh\n" +"#!/usr/sh\n" +msgstr "" + +msgid "" +"Good, we have a grep pattern on the first try. Let's try to find all the " +"matching files:" +msgstr "" + +msgid "" +"$ find . -type f | xargs grep -l '^#!/'\n" +"./TODOs.org\n" +"./.git/hooks/pre-commit.sample\n" +"./.git/hooks/pre-push.sample\n" +"./.git/hooks/pre-merge-commit.sample\n" +"./.git/hooks/fsmonitor-watchman.sample\n" +"./.git/hooks/pre-applypatch.sample\n" +"./.git/hooks/pre-push\n" +"./.git/hooks/prepare-commit-msg.sample\n" +"./.git/hooks/commit-msg.sample\n" +"./.git/hooks/post-update.sample\n" +"./.git/hooks/pre-receive.sample\n" +"./.git/hooks/applypatch-msg.sample\n" +"./.git/hooks/pre-rebase.sample\n" +"./.git/hooks/update.sample\n" +"./build-aux/with-guile-env.in\n" +"./build-aux/test-driver\n" +"./build-aux/missing\n" +"./build-aux/install-sh\n" +"./build-aux/install-sh~\n" +"./bootstrap\n" +"./scripts/assert-todos.sh\n" +"./scripts/songbooks\n" +"./scripts/compile-readme.sh\n" +"./scripts/ci-build.sh\n" +"./scripts/generate-tasks-and-bugs.sh\n" +"./scripts/songbooks.in\n" +"./scripts/with-container.sh\n" +"./scripts/assert-shellcheck.sh\n" +msgstr "" + +msgid "" +"This approach has a problem, though: it includes files ignored by Git, such " +"as `builld-aux/install-sh~`, and even goes into the `.git/` directory and " +"finds sample hooks in `.git/hooks/*`." +msgstr "" + +msgid "To list the files that Git is tracking we'll try `git ls-files`:" +msgstr "" + +msgid "" +"$ git ls-files | xargs grep -l '^#!/'\n" +"TODOs.org\n" +"bootstrap\n" +"build-aux/with-guile-env.in\n" +"old/scripts/assert-docs-spelling.sh\n" +"old/scripts/build-site.sh\n" +"old/scripts/builder.bats.sh\n" +"scripts/assert-shellcheck.sh\n" +"scripts/assert-todos.sh\n" +"scripts/ci-build.sh\n" +"scripts/compile-readme.sh\n" +"scripts/generate-tasks-and-bugs.sh\n" +"scripts/songbooks.in\n" +"scripts/with-container.sh\n" +msgstr "" + +msgid "" +"It looks to be almost there, but the `TODOs.org` entry shows a flaw in it: " +"grep is looking for a `'^#!/'` pattern on any part of the file. In my case, " +"`TODOs.org` had a snippet in the middle of the file where a line started " +"with `#!/bin/sh`." +msgstr "" + +msgid "" +"So what we actually want is to match the **first** line against the pattern." +" We could loop through each file, get the first line with `head -n 1` and " +"grep against that, but this is starting to look messy. I bet there is " +"another way of doing it concisely..." +msgstr "" + +msgid "" +"Let's try Awk. I need a way to select the line numbers to replace `head -n " +"1`, and to stop processing the file if the pattern matches. A quick search " +"points me to using `FNR` for the former, and `{ nextline }` for the latter. " +"Let's try it:" +msgstr "" + +msgid "" +"$ git ls-files | xargs awk 'FNR>1 { nextfile } /^#!\\// { print FILENAME; nextfile }'\n" +"bootstrap\n" +"build-aux/with-guile-env.in\n" +"old/scripts/assert-docs-spelling.sh\n" +"old/scripts/build-site.sh\n" +"old/scripts/builder.bats.sh\n" +"scripts/assert-shellcheck.sh\n" +"scripts/assert-todos.sh\n" +"scripts/ci-build.sh\n" +"scripts/compile-readme.sh\n" +"scripts/generate-tasks-and-bugs.sh\n" +"scripts/songbooks.in\n" +"scripts/with-container.sh\n" +msgstr "" + +msgid "" +"Great! Only `TODOs.org` is missing, but the script is much better: instead " +"of matching against any part of the file that may have a shebang-like line, " +"we only look for the first. Let's put it back into the `assert-" +"shellcheck.sh` file and use `NULL` for separators to accommodate files with " +"spaces in the name:" +msgstr "" + +msgid "" +"This is where I've stopped, but I imagine a likely improvement: match " +"against only `#!/bin/sh` and `#!/usr/bin/env bash` shebangs (the ones I use " +"most), to avoid running ShellCheck on Perl files, or other shebangs." +msgstr "" + +msgid "" +"Also when reviewing the text of this article, I found that `{ nextfile }` is" +" a GNU Awk extension. It would be an improvement if `assert-shellcheck.sh` " +"relied on the POSIX subset of Awk for working correctly." +msgstr "" + +msgid "title: 'Awk snippet: ShellCheck all scripts in a repository'" +msgstr "" + +msgid "date: 2020-12-15" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: awk-snippet-shellcheck-all-scripts-in-a-repository" +msgstr "" + +msgid "*Update*" +msgstr "" + +msgid "" +"After publishing, I could remove `{ nextfile }` and even make the script " +"simpler:" +msgstr "" + +msgid "Now both the shell and Awk usage are POSIX compatible." +msgstr "" + +msgid "eu_categories: shell" +msgstr "" + +msgid "updated_at: 2020-12-16" +msgstr "" + +msgid "" +"#!/bin/sh -eux\n" +"\n" +"find . -type f -name '*.sh' -print0 | xargs -0 shellcheck\n" +msgstr "" + +msgid "" +"#!/usr/sh -eux\n" +"\n" +"git ls-files -z | \\\n" +" xargs -0 awk 'FNR>1 { nextfile } /^#!\\// { print FILENAME; nextfile }' | \\\n" +" xargs shellcheck\n" +msgstr "" + +msgid "" +"#!/usr/sh -eux\n" +"\n" +"git ls-files -z | \\\n" +" xargs -0 awk 'FNR==1 && /^#!\\// { print FILENAME }' | \\\n" +" xargs shellcheck\n" +msgstr "" + +#~ msgid "" +#~ "#!/bin/sh\n" +#~ "set -eu\n" +#~ "\n" +#~ "find . -type f -name '*.sh' -print0 | xargs -0 shellcheck\n" +#~ msgstr "" + +#~ msgid "" +#~ "#!/usr/sh\n" +#~ "set -eu\n" +#~ "\n" +#~ "git ls-files -z | \\\n" +#~ " xargs -0 awk 'FNR>1 { nextfile } /^#!\\// { print FILENAME; nextfile }' | \\\n" +#~ " xargs shellcheck\n" +#~ msgstr "" + +#~ msgid "" +#~ "#!/usr/sh\n" +#~ "set -eu\n" +#~ "\n" +#~ "git ls-files -z | \\\n" +#~ " xargs -0 awk 'FNR==1 && /^#!\\// { print FILENAME }' | \\\n" +#~ " xargs shellcheck\n" +#~ msgstr "" + +#~ msgid "" +#~ "title: 'Awk snippet: ShellCheck all scripts in a repository'\n" +#~ "date: 2020-12-15\n" +#~ "layout: post\n" +#~ "lang: en\n" +#~ "ref: awk-snippet-shellcheck-all-scripts-in-a-repository" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_tils/2020-12-29-svg-favicon.po b/po/fr/LC_MESSAGES/_tils/2020-12-29-svg-favicon.po new file mode 100644 index 0000000..863f531 --- /dev/null +++ b/po/fr/LC_MESSAGES/_tils/2020-12-29-svg-favicon.po @@ -0,0 +1,168 @@ +# +msgid "" +msgstr "" + +msgid "" +"I've wanted to change this website's favicon from a plain `.ico` file to a " +"proper SVG. The problem I was trying to solve was to reuse the same image on" +" other places, such as avatars." +msgstr "" + +msgid "" +"Generating a PNG from the existing 16x16 icon was possible but bad: the " +"final image was blurry. Converting the `.ico` to an SVG was possible, but " +"sub-optimal: tools try to guess some vector paths, and the final SVG didn't " +"match the original." +msgstr "" + +msgid "" +"Instead I used a tool to draw the \"vector pixels\" as black squares, and " +"after getting the final result I manually cleaned-up the generated XML:" +msgstr "" + +msgid "" +"<?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"no\"?>\n" +"<svg xmlns=\"http://www.w3.org/2000/svg\" viewBox=\"0 0 16 16\" width=\"16\" height=\"16\">\n" +" <path d=\"M 0 8 L 1 8 L 1 9 L 0 9 L 0 8 Z\" />\n" +" <path d=\"M 0 13 L 1 13 L 1 14 L 0 14 L 0 13 Z\" />\n" +" <path d=\"M 1 8 L 2 8 L 2 9 L 1 9 L 1 8 Z\" />\n" +" <path d=\"M 1 13 L 2 13 L 2 14 L 1 14 L 1 13 Z\" />\n" +" <path d=\"M 2 8 L 3 8 L 3 9 L 2 9 L 2 8 Z\" />\n" +" <path d=\"M 2 13 L 3 13 L 3 14 L 2 14 L 2 13 Z\" />\n" +" <path d=\"M 3 8 L 4 8 L 4 9 L 3 9 L 3 8 Z\" />\n" +" <path d=\"M 3 13 L 4 13 L 4 14 L 3 14 L 3 13 Z\" />\n" +" <path d=\"M 4 7 L 5 7 L 5 8 L 4 8 L 4 7 Z\" />\n" +" <path d=\"M 4 8 L 5 8 L 5 9 L 4 9 L 4 8 Z\" />\n" +" <path d=\"M 4 13 L 5 13 L 5 14 L 4 14 L 4 13 Z\" />\n" +" <path d=\"M 5 6 L 6 6 L 6 7 L 5 7 L 5 6 Z\" />\n" +" <path d=\"M 5 7 L 6 7 L 6 8 L 5 8 L 5 7 Z\" />\n" +" <path d=\"M 5 13 L 6 13 L 6 14 L 5 14 L 5 13 Z\" />\n" +" <path d=\"M 6 5 L 7 5 L 7 6 L 6 6 L 6 5 Z\" />\n" +" <path d=\"M 6 6 L 7 6 L 7 7 L 6 7 L 6 6 Z\" />\n" +" <path d=\"M 6 14 L 7 14 L 7 15 L 6 15 L 6 14 Z\" />\n" +" <path d=\"M 7 1 L 8 1 L 8 2 L 7 2 L 7 1 Z\" />\n" +" <path d=\"M 7 14 L 8 14 L 8 15 L 7 15 L 7 14 Z\" />\n" +" <path d=\"M 7 15 L 8 15 L 8 16 L 7 16 L 7 15 Z\" />\n" +" <path d=\"M 7 2 L 8 2 L 8 3 L 7 3 L 7 2 Z\" />\n" +" <path d=\"M 7 3 L 8 3 L 8 4 L 7 4 L 7 3 Z\" />\n" +" <path d=\"M 7 4 L 8 4 L 8 5 L 7 5 L 7 4 Z\" />\n" +" <path d=\"M 7 5 L 8 5 L 8 6 L 7 6 L 7 5 Z\" />\n" +" <path d=\"M 8 1 L 9 1 L 9 2 L 8 2 L 8 1 Z\" />\n" +" <path d=\"M 8 15 L 9 15 L 9 16 L 8 16 L 8 15 Z\" />\n" +" <path d=\"M 9 1 L 10 1 L 10 2 L 9 2 L 9 1 Z\" />\n" +" <path d=\"M 9 2 L 10 2 L 10 3 L 9 3 L 9 2 Z\" />\n" +" <path d=\"M 9 6 L 10 6 L 10 7 L 9 7 L 9 6 Z\" />\n" +" <path d=\"M 9 15 L 10 15 L 10 16 L 9 16 L 9 15 Z\" />\n" +" <path d=\"M 10 2 L 11 2 L 11 3 L 10 3 L 10 2 Z\" />\n" +" <path d=\"M 10 3 L 11 3 L 11 4 L 10 4 L 10 3 Z\" />\n" +" <path d=\"M 10 4 L 11 4 L 11 5 L 10 5 L 10 4 Z\" />\n" +" <path d=\"M 10 5 L 11 5 L 11 6 L 10 6 L 10 5 Z\" />\n" +" <path d=\"M 10 6 L 11 6 L 11 7 L 10 7 L 10 6 Z\" />\n" +" <path d=\"M 11 6 L 12 6 L 12 7 L 11 7 L 11 6 Z\" />\n" +" <path d=\"M 11 8 L 12 8 L 12 9 L 11 9 L 11 8 Z\" />\n" +" <path d=\"M 10 15 L 11 15 L 11 16 L 10 16 L 10 15 Z\" />\n" +" <path d=\"M 11 10 L 12 10 L 12 11 L 11 11 L 11 10 Z\" />\n" +" <path d=\"M 11 12 L 12 12 L 12 13 L 11 13 L 11 12 Z\" />\n" +" <path d=\"M 11 14 L 12 14 L 12 15 L 11 15 L 11 14 Z\" />\n" +" <path d=\"M 11 15 L 12 15 L 12 16 L 11 16 L 11 15 Z\" />\n" +" <path d=\"M 12 6 L 13 6 L 13 7 L 12 7 L 12 6 Z\" />\n" +" <path d=\"M 12 8 L 13 8 L 13 9 L 12 9 L 12 8 Z\" />\n" +" <path d=\"M 12 10 L 13 10 L 13 11 L 12 11 L 12 10 Z\" />\n" +" <path d=\"M 12 12 L 13 12 L 13 13 L 12 13 L 12 12 Z\" />\n" +" <path d=\"M 12 14 L 13 14 L 13 15 L 12 15 L 12 14 Z\" />\n" +" <path d=\"M 13 6 L 14 6 L 14 7 L 13 7 L 13 6 Z\" />\n" +" <path d=\"M 13 8 L 14 8 L 14 9 L 13 9 L 13 8 Z\" />\n" +" <path d=\"M 13 10 L 14 10 L 14 11 L 13 11 L 13 10 Z\" />\n" +" <path d=\"M 13 12 L 14 12 L 14 13 L 13 13 L 13 12 Z\" />\n" +" <path d=\"M 13 13 L 14 13 L 14 14 L 13 14 L 13 13 Z\" />\n" +" <path d=\"M 13 14 L 14 14 L 14 15 L 13 15 L 13 14 Z\" />\n" +" <path d=\"M 14 7 L 15 7 L 15 8 L 14 8 L 14 7 Z\" />\n" +" <path d=\"M 14 8 L 15 8 L 15 9 L 14 9 L 14 8 Z\" />\n" +" <path d=\"M 14 9 L 15 9 L 15 10 L 14 10 L 14 9 Z\" />\n" +" <path d=\"M 14 10 L 15 10 L 15 11 L 14 11 L 14 10 Z\" />\n" +" <path d=\"M 14 11 L 15 11 L 15 12 L 14 12 L 14 11 Z\" />\n" +" <path d=\"M 14 12 L 15 12 L 15 13 L 14 13 L 14 12 Z\" />\n" +"</svg>\n" +msgstr "" + +msgid "" +"With the new favicon file, I now had to add to the templates' `<head>` a " +"`<link>` to this icon:" +msgstr "" + +msgid "" +"<head>\n" +" <meta charset=\"UTF-8\" />\n" +" <link rel=\"icon\" type=\"image/svg+xml\" href=\"/static/favicon.svg\">\n" +" ...\n" +msgstr "" + +msgid "" +"Still missing is a bitmap image for places that can't handle vector images. " +"I used Jekyll generator to create an PNG from the existing SVG:" +msgstr "" + +msgid "" +"module Jekyll\n" +" class FaviconGenerator < Generator\n" +" safe true\n" +" priority :high\n" +"\n" +" SIZE = 420\n" +"\n" +" def generate(site)\n" +" svg = 'static/favicon.svg'\n" +" png = 'static/favicon.png'\n" +" unless File.exist? png then\n" +" puts \"Missing '#{png}', generating...\"\n" +" puts `inkscape -o #{png} -w #{SIZE} -h #{SIZE} #{svg}`\n" +" end\n" +" end\n" +" end\n" +"end\n" +msgstr "" + +msgid "" +"I had to increase the priority of the generator so that it would run before " +"other places that would use a `{% link /static/favicon.png %}`, otherwise " +"the file would be considered missing." +msgstr "" + +msgid "title: SVG favicon" +msgstr "" + +msgid "date: 2020-12-29" +msgstr "" + +msgid "updated_at: 2021-01-12" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: svg-favicon" +msgstr "" + +msgid "" +"The good thing about this new favicon (at " +"[`/static/favicon.svg`](/static/favicon.svg)) is that a) it is simple enough" +" that I feel comfortable editing it manually and b) it is an SVG, which " +"means I can generate any desired size." +msgstr "" + +#~ msgid "" +#~ "title: SVG favicon\n" +#~ "date: 2020-12-29\n" +#~ "layout: post\n" +#~ "lang: en\n" +#~ "ref: svg-favicon" +#~ msgstr "" + +#~ msgid "" +#~ "The good thing about this new favicon is that a) it is simple enough that I " +#~ "feel comfortable editing it manually and b) it is an SVG, which means I can " +#~ "generate any desired size." +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_tils/2021-01-12-awk-snippet-send-email-to-multiple-recipients-with-curl.po b/po/fr/LC_MESSAGES/_tils/2021-01-12-awk-snippet-send-email-to-multiple-recipients-with-curl.po new file mode 100644 index 0000000..5ed4783 --- /dev/null +++ b/po/fr/LC_MESSAGES/_tils/2021-01-12-awk-snippet-send-email-to-multiple-recipients-with-curl.po @@ -0,0 +1,249 @@ +# +msgid "" +msgstr "" + +msgid "title: 'Awk snippet: send email to multiple recipients with cURL'" +msgstr "" + +msgid "date: 2021-01-12" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: awk-snippet-send-email-to-multiple-recipients-with-curl" +msgstr "" + +msgid "My requirements for the `sendmail` command were:" +msgstr "" + +msgid "store the email in a file, and send it later." +msgstr "" + +msgid "send from different addresses, using different SMTP servers;" +msgstr "" + +msgid "" +"I couldn't find an MTA that could accomplish that, but I was able to quickly" +" write a solution." +msgstr "" + +msgid "The first part was the easiest: store the email in a file:" +msgstr "" + +msgid "" +"# ~/.config/mutt/muttrc:\n" +"set sendmail=~/bin/enqueue-email.sh\n" +"\n" +"# ~/bin/enqueue-email.sh:\n" +"#!/bin/sh -eu\n" +"\n" +"cat - > \"$HOME/mbsync/my-queued-emails/$(date -Is)\"\n" +msgstr "" + +msgid "" +"Now that I had the email file store locally, I needed a program to send the " +"email from the file, so that I could create a cronjob like:" +msgstr "" + +msgid "" +"for f in ~/mbsync/my-queued-emails/*; do\n" +" ~/bin/dispatch-email.sh \"$f\" && rm \"$f\"\n" +"done\n" +msgstr "" + +msgid "" +"The `dispatch-email.sh` would have to look at the `From: ` header and decide" +" which SMTP server to use. As I [found " +"out](https://blog.edmdesigner.com/send-email-from-linux-command-line/) that " +"[curl](https://curl.se/) supports SMTP and is able to send emails, this is " +"what I ended up with:" +msgstr "" + +msgid "Most of curl flags used are self-explanatory, except for `$rcpt`." +msgstr "" + +msgid "" +"curl connects to the SMTP server, but doesn't set the recipient address by " +"looking at the message. My solution was to generate the curl flags, store " +"them in `$rcpt` and use it unquoted to leverage shell word splitting." +msgstr "" + +msgid "" +"To me, the most interesting part was building the `$rcpt` flags. My first " +"instinct was to try grep, but it couldn't print only matches in a regex. As " +"I started to turn towards sed, I envisioned needing something else to loop " +"over the sed output, and I then moved to Awk." +msgstr "" + +msgid "" +"$ H='To: to@example.com, to2@example.com\\nCc: cc@example.com, cc2@example.com\\nBcc: bcc@example.com,bcc2@example.com\\n'\n" +"$ printf \"$H\" | awk '/^To: .*$/ { print $0 }'\n" +"To: to@example.com, to2@example.com\n" +"$ printf \"$H\" | awk 'match($0, /^To: (.*)$/, m) { print m }'\n" +"awk: ligne de commande:1: (FILENAME=- FNR=1) fatal : tentative d'utilisation du tableau « m » dans un contexte scalaire\n" +"$ printf \"$H\" | awk 'match($0, /^To: (.*)$/, m) { print m[0] }'\n" +"To: to@example.com, to2@example.com\n" +"$ printf \"$H\" | awk 'match($0, /^To: (.*)$/, m) { print m[1] }'\n" +"to@example.com, to2@example.com\n" +"$ printf \"$H\" | awk 'match($0, /^To: (.*)$/, m) { split(m[1], tos, \" \"); print tos }'\n" +"awk: ligne de commande:1: (FILENAME=- FNR=1) fatal : tentative d'utilisation du tableau « tos » dans un contexte scalaire\n" +"$ printf \"$H\" | awk 'match($0, /^To: (.*)$/, m) { split(m[1], tos, \" \"); print tos[0] }'\n" +"\n" +"$ printf \"$H\" | awk 'match($0, /^To: (.*)$/, m) { split(m[1], tos, \" \"); print tos[1] }'\n" +"to@example.com,\n" +"$ printf \"$H\" | awk 'match($0, /^To: (.*)$/, m) { split(m[1], tos, \" \"); print tos[2] }'\n" +"to2@example.com\n" +"$ printf \"$H\" | awk 'match($0, /^To: (.*)$/, m) { split(m[1], tos, \" \"); print tos[3] }'\n" +"\n" +msgstr "" + +msgid "" +"(This isn't the verbatim interactive session, but a cleaned version to make " +"it more readable.)" +msgstr "" + +msgid "" +"At this point, I realized I needed a for loop over the `tos` array, and I " +"moved the Awk snippet into the `~/bin/dispatch-email.sh`. I liked the final " +"thing:" +msgstr "" + +msgid "" +"match($0, /^(To|Cc|Bcc): (.*)$/, m) {\n" +" split(m[2], tos, \",\")\n" +" for (i in tos) {\n" +" print \"--mail-rcpt \" tos[i]\n" +" }\n" +"}\n" +msgstr "" + +msgid "" +"As I learn more about Awk, I feel that it is too undervalued, as many people" +" turn to Perl or other programming languages when Awk suffices. The " +"advantage is pretty clear: writing programs that run on any POSIX system, " +"without extra dependencies required." +msgstr "" + +msgid "Coding to the standards is underrated." +msgstr "" + +msgid "" +"#!/bin/sh -eu\n" +"\n" +"F=\"$1\"\n" +"\n" +"rcpt=\"$(awk '\n" +" match($0, /^(To|Cc|Bcc): (.*)$/, m) {\n" +" split(m[2], tos, \",\")\n" +" for (i in tos) {\n" +" print \"--mail-rcpt \" tos[i]\n" +" }\n" +" }\n" +"' \"$F\")\"\n" +"\n" +"if grep -qE '^From: .*<addr@server1\\.org>$' \"$F\"; then\n" +" curl \\\n" +" -s \\\n" +" --url smtp://smtp.server1.org:587 \\\n" +" --ssl-reqd \\\n" +" --mail-from addr@server1.org \\\n" +" $rcpt \\\n" +" --user 'addr@server1.org:my-long-and-secure-passphrase' \\\n" +" --upload-file \"$F\"\n" +"elif grep -qE '^From: .*<addr@server2\\.org>$' \"$F\"; then\n" +" curl \\\n" +" -s \\\n" +" --url smtp://smtp.server2.org:587 \\\n" +" --ssl-reqd \\\n" +" --mail-from addr@server2.org \\\n" +" $rcpt \\\n" +" --user 'addr@server2.org:my-long-and-secure-passphrase' \\\n" +" --upload-file \"$F\"\n" +"else\n" +" echo 'Bad \"From: \" address'\n" +" exit 1\n" +"fi\n" +msgstr "" + +msgid "" +"In the short Awk snippet, 3 things were new to me: the `match(...)`, " +"`split(...)` and `for () {}`. The only other function I have ever used was " +"`gsub(...)`, but these new ones felt similar enough that I could almost " +"guess their behaviour and arguments. `match(...)` stores the matches of a " +"regex on the given array positionally, and `split(...)` stores the chunks in" +" the given array." +msgstr "" + +msgid "I even did it incrementally:" +msgstr "" + +msgid "" +"As I experiment with [Neomutt](https://neomutt.org/), I wanted to keep being" +" able to enqueue emails for sending later like my previous setup, so that I " +"didn't rely on having an internet connection." +msgstr "" + +#~ msgid "" +#~ "As I experimented with [Neomutt](https://neomutt.org/), I wanted to keep " +#~ "being able to enqueue emails for sending later like my previous setup, so " +#~ "that I didn't rely on having an internet connection." +#~ msgstr "" + +#~ msgid "I even did this incrementally:" +#~ msgstr "" + +#~ msgid "" +#~ "In the short Awk snippet, 3 things were new to me: the `match(...)`, " +#~ "`split(...)` and `for () {}`. The only other function I have ever used was " +#~ "`gsub(...)`, but these new felt similar enough that I could almost guess " +#~ "their behaviour. `match(...)` stores the matches of a regex on the given " +#~ "array positionally, and `split(...)` stores the chunks in the given array." +#~ msgstr "" + +#~ msgid "" +#~ "As I experimented with [Neomutt](https://neomutt.org/), I wanted to keep " +#~ "being able to enqueue emails for sending later, so that I didn't rely on " +#~ "having an internet connection." +#~ msgstr "" + +#~ msgid "" +#~ "#!/bin/sh -eu\n" +#~ "\n" +#~ "F=\"$1\"\n" +#~ "\n" +#~ "rcpt=\"$(awk '\n" +#~ " match($0, /^(To|Cc|Bcc): (.*)$/, m) {\n" +#~ " split(m[2], tos, \",\")\n" +#~ " for (i in tos) {\n" +#~ " print \"--mail-rcpt \" tos[i]\n" +#~ " }\n" +#~ " }\n" +#~ "' \"$F\")\"\n" +#~ "\n" +#~ "if grep -qE '^From: .*<addr@server1\\.org>$' \"$F\"; then\n" +#~ " curl \\\n" +#~ " -s \\\n" +#~ " --url smtp://smtp.server1.org:587 \\\n" +#~ " --ssl-reqd \\\n" +#~ " --mail-from addr@server1.org \\\n" +#~ " $rcpt \\\n" +#~ " --user 'addr@server1.org:my-long-and-secure-passphrase' \\\n" +#~ " --upload-file \"$F\"\n" +#~ "eliif grep -qE '^From: .*<addr@server2\\.org>$' \"$F\"; then\n" +#~ " curl \\\n" +#~ " -s \\\n" +#~ " --url smtp://smtp.server2.org:587 \\\n" +#~ " --ssl-reqd \\\n" +#~ " --mail-from addr@server2.org \\\n" +#~ " $rcpt \\\n" +#~ " --user 'addr@server2.org:my-long-and-secure-passphrase' \\\n" +#~ " --upload-file \"$F\"\n" +#~ "else\n" +#~ " echo 'Bad \"From: \" address'\n" +#~ " exit 1\n" +#~ "fi\n" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_tils/2021-01-17-posix-sh-and-shebangs.po b/po/fr/LC_MESSAGES/_tils/2021-01-17-posix-sh-and-shebangs.po new file mode 100644 index 0000000..e285d50 --- /dev/null +++ b/po/fr/LC_MESSAGES/_tils/2021-01-17-posix-sh-and-shebangs.po @@ -0,0 +1,97 @@ +# +msgid "" +msgstr "" + +msgid "title: POSIX sh and shebangs" +msgstr "" + +msgid "date: 2021-01-17" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: posix-sh-and-shebangs" +msgstr "" + +msgid "" +"As I [keep moving][posix-awk-0] [towards POSIX][posix-awk-1], I'm on the " +"process of migrating all my Bash scripts to POSIX sh." +msgstr "" + +msgid "" +"As I dropped `[[`, arrays and other Bashisms, I was left staring at the " +"first line of every script, wondering what to do: what is the POSIX sh " +"equivalent of `#!/usr/bin/env bash`? I already knew that POSIX says nothing " +"about shebangs, and that the portable way to call a POSIX sh script is `sh " +"script.sh`, but I didn't know what to do with that first line." +msgstr "" + +msgid "What I had previously was:" +msgstr "" + +msgid "" +"#!/usr/bin/env bash\n" +"set -Eeuo pipefail\n" +"cd \"$(dirname \"${BASH_SOURCE[0]}\")\"\n" +msgstr "" + +msgid "" +"Obviously, the `$BASH_SOURCE` would be gone, and I would have to adapt some " +"of my scripts to not rely on the script location. The `-E` and `-o pipefail`" +" options were also gone, and would be replaced by nothing." +msgstr "" + +msgid "I converted all of them to:" +msgstr "" + +msgid "#!/bin/sh -eu\n" +msgstr "" + +msgid "" +"I moved the `-eu` options to the shebang line itself, striving for " +"conciseness. But as I changed callers from `./script.sh` to `sh script.sh`, " +"things started to fail. Some tests that should fail reported errors, but " +"didn't return 1." +msgstr "" + +msgid "" +"My first reaction was to revert back to `./script.sh`, but the POSIX bug I " +"caught is a strong strain, and when I went back to it, I figured that the " +"callers were missing some flags. Specifically, `sh -eu script.sh`." +msgstr "" + +msgid "" +"Then it clicked: when running with `sh script.sh`, the shebang line with the" +" sh options is ignored, as it is a comment!" +msgstr "" + +msgid "Which means that the shebang most friendly with POSIX is:" +msgstr "" + +msgid "" +"#!/bin/sh\n" +"set -eu\n" +msgstr "" + +msgid "" +"when running via `./script.sh`, if the system has an executable at " +"`/bin/sh`, it will be used to run the script;" +msgstr "" + +msgid "" +"when running via `sh script.sh`, the sh options aren't ignored as " +"previously." +msgstr "" + +msgid "TIL." +msgstr "" + +msgid "" +"[posix-awk-0]: {% link _tils/2020-12-15-awk-snippet-shellcheck-all-scripts-" +"in-a-repository.md %} [posix-awk-1]: {% link _tils/2021-01-12-awk-snippet-" +"send-email-to-multiple-recipients-with-curl.md %}" +msgstr "" diff --git a/po/fr/LC_MESSAGES/_tils/2021-04-24-clojure-auto-curry.po b/po/fr/LC_MESSAGES/_tils/2021-04-24-clojure-auto-curry.po new file mode 100644 index 0000000..ab59a4f --- /dev/null +++ b/po/fr/LC_MESSAGES/_tils/2021-04-24-clojure-auto-curry.po @@ -0,0 +1,220 @@ +# +msgid "" +msgstr "" + +msgid "title: Clojure auto curry" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: clojure-auto-curry" +msgstr "" + +msgid "A naive `add` definition, alongside its usage and macroexpansion:" +msgstr "" + +msgid "" +"user=> (defcurry add\n" +" [a b c d e]\n" +" (+ 1 2 3 4 5))\n" +"#'user/add\n" +"\n" +"user=> (add 1)\n" +"#object[clojure.core$partial$fn__5857 0x2c708440 \"clojure.core$partial$fn__5857@2c708440\"]\n" +"\n" +"user=> (add 1 2 3 4)\n" +"#object[clojure.core$partial$fn__5863 0xf4c0e4e \"clojure.core$partial$fn__5863@f4c0e4e\"]\n" +"\n" +"user=> ((add 1) 2 3 4 5)\n" +"15\n" +"\n" +"user=> (((add 1) 2 3) 4 5)\n" +"15\n" +"\n" +"user=> (use 'clojure.pprint)\n" +"nil\n" +"\n" +"user=> (pprint\n" +" (macroexpand\n" +" '(defcurry add\n" +" [a b c d e]\n" +" (+ 1 2 3 4 5))))\n" +"(def\n" +" add\n" +" (clojure.core/fn\n" +" ([a b c d e] (+ 1 2 3 4 5))\n" +" ([a] (clojure.core/partial add a))\n" +" ([a b] (clojure.core/partial add a b))\n" +" ([a b c] (clojure.core/partial add a b c))\n" +" ([a b c d] (clojure.core/partial add a b c d))))\n" +"nil\n" +msgstr "" + +msgid "" +"This simplistic `defcurry` definition doesn't support optional parameters, " +"multi-arity, `&` rest arguments, docstrings, etc., but it could certainly " +"evolve to do so." +msgstr "" + +msgid "" +"I like how `defcurry` is so short, and abdicates the responsability of doing" +" the multi-arity logic to Clojure's built-in multi-arity support. Simple and" +" elegant." +msgstr "" + +msgid "Same Clojure as before, now with auto-currying via macros." +msgstr "" + +msgid "" +"Here's a simple macro defined by [Loretta " +"He](http://lorettahe.github.io/clojure/2016/09/22/clojure-auto-curry) to " +"create Clojure functions that are curried on all arguments, relying on " +"Clojure's multi-arity support:" +msgstr "" + +msgid "date: 2021-04-24 1" +msgstr "" + +msgid "" +"(defmacro defcurry\n" +" [name args & body]\n" +" (let [partials (map (fn [n]\n" +" `(~(subvec args 0 n) (partial ~name ~@(take n args))))\n" +" (range 1 (count args)))]\n" +" `(defn ~name\n" +" (~args ~@body)\n" +" ~@partials)))\n" +msgstr "" + +msgid "Comparison with Common Lisp" +msgstr "" + +msgid "My attempt at writing an equivalent for Common Lisp gives me:" +msgstr "" + +msgid "" +"(defun partial (fn &rest args)\n" +" (lambda (&rest args2)\n" +" (apply fn (append args args2))))\n" +"\n" +"(defun curry-n (n func)\n" +" (cond ((< n 0) (error \"Too many arguments\"))\n" +" ((zerop n) (funcall func))\n" +" (t (lambda (&rest rest)\n" +" (curry-n (- n (length rest))\n" +" (apply #'partial func rest))))))\n" +"\n" +"(defmacro defcurry (name args &body body)\n" +" `(defun ,name (&rest rest)\n" +" (let ((func (lambda ,args ,@body)))\n" +" (curry-n (- ,(length args) (length rest))\n" +" (apply #'partial func rest)))))\n" +msgstr "" + +msgid "" +"Without built-in multi-arity support, we have to do more work, like tracking" +" the number of arguments consumed so far. We also have to write `#'partial` " +"ourselves. That is, without dependending on any library, sticking to ANSI " +"Common Lisp." +msgstr "" + +msgid "The usage is pretty similar:" +msgstr "" + +msgid "" +"* (defcurry add (a b c d e)\n" +" (+ a b c d e))\n" +"ADD\n" +"\n" +"* (add 1)\n" +"#<FUNCTION (LAMBDA (&REST REST) :IN CURRY-N) {100216419B}>\n" +"\n" +"* (funcall (add 1) 2 3 4)\n" +"#<FUNCTION (LAMBDA (&REST REST) :IN CURRY-N) {100216537B}>\n" +"\n" +"* (funcall (add 1) 2 3 4 5)\n" +"15\n" +"\n" +"* (funcall (funcall (add 1) 2 3) 4 5)\n" +"15\n" +"\n" +"* (macroexpand-1\n" +" '(defcurry add (a b c d e)\n" +" (+ a b c d e)))\n" +"(DEFUN ADD (&REST REST)\n" +" (LET ((FUNC (LAMBDA (A B C D E) (+ A B C D E))))\n" +" (CURRY-N (- 5 (LENGTH REST)) (APPLY #'PARTIAL FUNC REST))))\n" +"T\n" +msgstr "" + +msgid "" +"This also require `funcall`s, since we return a `lambda` that doesn't live " +"in the function namespace." +msgstr "" + +msgid "" +"Like the Clojure one, it doesn't support optional parameters, `&rest` rest " +"arguments, docstrings, etc., but it also could evolve to do so." +msgstr "" + +msgid "updated_at: 2021-04-27" +msgstr "" + +#~ msgid "" +#~ "(defmacro defcurry\n" +#~ " [fname args & body]\n" +#~ " (let [partials (map (fn [n]\n" +#~ " `(~(subvec args 0 n) (partial ~fname ~@(take n args))))\n" +#~ " (range 1 (count args)))]\n" +#~ " `(defn ~fname\n" +#~ " (~args ~@body)\n" +#~ " ~@partials)))\n" +#~ msgstr "" + +#~ msgid "date: 2021-04-24" +#~ msgstr "" + +#~ msgid "" +#~ "A simple macro defined by [Loretta " +#~ "He](http://lorettahe.github.io/clojure/2016/09/22/clojure-auto-curry) to " +#~ "create Clojure functions that are curried on all arguments, relying on " +#~ "Clojure's multi-arity support:" +#~ msgstr "" + +#~ msgid "" +#~ "Without built-in multi-arity support, we have to do more work, like tracking" +#~ " the number of arguments consumed so far. That is, without dependending on " +#~ "any library, sticking to ANSI Common Lisp." +#~ msgstr "" + +#~ msgid "" +#~ "(defun curry-n (n fn)\n" +#~ " (if (= 0 n)\n" +#~ " (funcall fn)\n" +#~ " (lambda (&rest rest)\n" +#~ " (curry-n (something n) fn))))\n" +#~ "\n" +#~ "(defun add (a b c d e)\n" +#~ " (curry-n\n" +#~ " (length '(a b c d e))\n" +#~ " (lambda (&rest rest)\n" +#~ " (apply #'+ rest))))\n" +#~ msgstr "" + +#~ msgid "" +#~ "(defun curry-n (n fn)\n" +#~ " (if (= 0 n)\n" +#~ " (funcall fn)\n" +#~ " (lambda (&rest rest)\n" +#~ " (curry-n (something n) fn))))\n" +#~ "\n" +#~ "(defun add (a b c d e)\n" +#~ " (curry-n\n" +#~ " (length '(a b c d e))\n" +#~ " (lambda (&rest rest)\n" +#~ " (apply #'+ rest))))\n" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_tils/2021-04-24-common-lisp-argument-precedence-order-parameterization-of-a-generic-function.po b/po/fr/LC_MESSAGES/_tils/2021-04-24-common-lisp-argument-precedence-order-parameterization-of-a-generic-function.po new file mode 100644 index 0000000..6aa66a8 --- /dev/null +++ b/po/fr/LC_MESSAGES/_tils/2021-04-24-common-lisp-argument-precedence-order-parameterization-of-a-generic-function.po @@ -0,0 +1,210 @@ +# +msgid "" +msgstr "" + +msgid "" +"title: Common Lisp argument precedence order parameterization of a generic " +"function" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "" +"ref: common-lisp-argument-precedence-order-parameterization-of-a-generic-" +"function" +msgstr "" + +msgid "" +"When CLOS dispatches a method, it picks the most specific method definition " +"to the argument list:" +msgstr "" + +msgid "" +"\n" +"* (defgeneric a-fn (x))\n" +"#<STANDARD-GENERIC-FUNCTION A-FN (0) {5815ACB9}>\n" +"\n" +"* (defmethod a-fn (x) :default-method)\n" +"#<STANDARD-METHOD A-FN (T) {581DB535}>\n" +"\n" +"* (defmethod a-fn ((x number)) :a-number)\n" +"#<STANDARD-METHOD A-FN (NUMBER) {58241645}>\n" +"\n" +"* (defmethod a-fn ((x (eql 1))) :number-1)\n" +"#<STANDARD-METHOD A-FN ((EQL 1)) {582A7D75}>\n" +"\n" +"* (a-fn nil)\n" +":DEFAULT-METHOD\n" +"\n" +"* (a-fn \"1\")\n" +":DEFAULT-METHOD\n" +"\n" +"* (a-fn 0)\n" +":A-NUMBER\n" +"\n" +"* (a-fn 1)\n" +":NUMBER-1\n" +msgstr "" + +msgid "" +"CLOS uses a similar logic when choosing the method from parent classes, when" +" multiple ones are available:" +msgstr "" + +msgid "" +"* (defclass class-a () ())\n" +"\n" +"#<STANDARD-CLASS CLASS-A {583E0B25}>\n" +"* (defclass class-b () ())\n" +"\n" +"#<STANDARD-CLASS CLASS-B {583E7F6D}>\n" +"* (defgeneric another-fn (obj))\n" +"\n" +"#<STANDARD-GENERIC-FUNCTION ANOTHER-FN (0) {583DA749}>\n" +"* (defmethod another-fn ((obj class-a)) :class-a)\n" +"; Compiling LAMBDA (.PV-CELL. .NEXT-METHOD-CALL. OBJ):\n" +"; Compiling Top-Level Form:\n" +"\n" +"#<STANDARD-METHOD ANOTHER-FN (CLASS-A) {584523C5}>\n" +"* (defmethod another-fn ((obj class-b)) :class-b)\n" +"; Compiling LAMBDA (.PV-CELL. .NEXT-METHOD-CALL. OBJ):\n" +"; Compiling Top-Level Form:\n" +"\n" +"#<STANDARD-METHOD ANOTHER-FN (CLASS-B) {584B8895}>\n" +msgstr "" + +msgid "" +"Given the above definitions, when inheriting from `class-a` and `class-b`, " +"the order of inheritance matters:" +msgstr "" + +msgid "" +"* (defclass class-a-coming-first (class-a class-b) ())\n" +"#<STANDARD-CLASS CLASS-A-COMING-FIRST {584BE6AD}>\n" +"\n" +"* (defclass class-b-coming-first (class-b class-a) ())\n" +"#<STANDARD-CLASS CLASS-B-COMING-FIRST {584C744D}>\n" +"\n" +"* (another-fn (make-instance 'class-a-coming-first))\n" +":CLASS-A\n" +"\n" +"* (another-fn (make-instance 'class-b-coming-first))\n" +":CLASS-B\n" +msgstr "" + +msgid "" +"Combining the order of inheritance with generic functions with multiple " +"arguments, CLOS has to make a choice of how to pick a method given two " +"competing definitions, and its default strategy is prioritizing from left to" +" right:" +msgstr "" + +msgid "" +"* (defgeneric yet-another-fn (obj1 obj2))\n" +"#<STANDARD-GENERIC-FUNCTION YET-ANOTHER-FN (0) {584D9EC9}>\n" +"\n" +"* (defmethod yet-another-fn ((obj1 class-a) obj2) :first-arg-specialized)\n" +"#<STANDARD-METHOD YET-ANOTHER-FN (CLASS-A T) {5854269D}>\n" +"\n" +"* (defmethod yet-another-fn (obj1 (obj2 class-b)) :second-arg-specialized)\n" +"#<STANDARD-METHOD YET-ANOTHER-FN (T CLASS-B) {585AAAAD}>\n" +"\n" +"* (yet-another-fn (make-instance 'class-a) (make-instance 'class-b))\n" +":FIRST-ARG-SPECIALIZED\n" +msgstr "" + +msgid "" +"For that, we use the `:argument-precedence-order` option when declaring a " +"generic function:" +msgstr "" + +msgid "" +"* (defgeneric yet-another-fn (obj1 obj2) (:argument-precedence-order obj2 obj1))\n" +"#<STANDARD-GENERIC-FUNCTION YET-ANOTHER-FN (2) {584D9EC9}>\n" +"\n" +"* (yet-another-fn (make-instance 'class-a) (make-instance 'class-b))\n" +":SECOND-ARG-SPECIALIZED\n" +msgstr "" + +msgid "" +"I liked that the `:argument-precedence-order` option exists. We shouldn't " +"have to change the arguments from `(obj1 obj2)` to `(obj2 obj1)` just to " +"make CLOS pick the method that we want. We can configure its default " +"behaviour if desired, and keep the order of arguments however it best fits " +"the generic function." +msgstr "" + +msgid "Comparison with Clojure" +msgstr "" + +msgid "Clojure has an equivalent, when using `defmulti`." +msgstr "" + +msgid "" +"Since when declaring a multi-method with `defmulti` we must define the " +"dispatch function, Clojure uses it to pick the method definition. Since the " +"dispatch function is required, there is no need for a default behaviour, " +"such as left-to-right." +msgstr "" + +msgid "Conclusion" +msgstr "" + +msgid "" +"Making the argument precedence order configurable for generic functions but " +"not for class definitions makes a lot of sense." +msgstr "" + +msgid "" +"One shouldn't change the order of arguments of a generic function for the " +"sake of tailoring it to the CLOS priority ranking algorithm, but doing it " +"for a class definition is just fine." +msgstr "" + +msgid "TIL." +msgstr "" + +msgid "" +"CLOS has to make a choice between the first and the second definition of " +"`yet-another-fn`, but its choice is just a heuristic. What if we want the " +"choice to be based on the second argument, instead of the first?" +msgstr "" + +msgid "" +"When declaring a class, we can choose the precedence order, and that is " +"about it. But when defining a generic function, the order of arguments is " +"more important to the function semantics, and the argument precedence being " +"left-to-right is just the default behaviour." +msgstr "" + +msgid "References" +msgstr "" + +msgid "" +"[Object-Oriented Programming in Common Lisp: A Programmer's Guide to " +"CLOS](https://en.wikipedia.org/wiki/Object-" +"Oriented_Programming_in_Common_Lisp), by Sonja E. Keene" +msgstr "" + +msgid "date: 2021-04-24 2" +msgstr "" + +#~ msgid "date: 2021-04-24" +#~ msgstr "" + +#~ msgid "" +#~ "CLOS has to make a choice between the first and the second definition of " +#~ "`yet-another-fn`, but its choice is just a heuristic. What if we want to the" +#~ " choice to be based on the second argument first?" +#~ msgstr "" + +#~ msgid "" +#~ "When declaring a class, we can choose the precedence order, and that is " +#~ "about it. But when defining a generic function, the order of argumentws is " +#~ "more important to the function semantics, and the argument precedence being " +#~ "left-to-right is just the default behaviour." +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/_tils/2021-04-24-three-way-conditional-for-number-signs.po b/po/fr/LC_MESSAGES/_tils/2021-04-24-three-way-conditional-for-number-signs.po new file mode 100644 index 0000000..925a00b --- /dev/null +++ b/po/fr/LC_MESSAGES/_tils/2021-04-24-three-way-conditional-for-number-signs.po @@ -0,0 +1,95 @@ +# +msgid "" +msgstr "" + +msgid "title: Three-way conditional for number signs" +msgstr "" + +msgid "date: 2021-04-24 3" +msgstr "" + +msgid "layout: post" +msgstr "" + +msgid "lang: en" +msgstr "" + +msgid "ref: three-way-conditional-for-number-signs" +msgstr "" + +msgid "" +"A useful macro from Paul Graham's [On " +"Lisp](http://www.paulgraham.com/onlisptext.html) book:" +msgstr "" + +msgid "" +"(defmacro nif (expr pos zero neg)\n" +" (let ((g (gensym)))\n" +" `(let ((,g ,expr))\n" +" (cond ((plusp ,g) ,pos)\n" +" ((zerop ,g) ,zero)\n" +" (t ,neg)))))\n" +msgstr "" + +msgid "" +"The latest example I can think of is section 1.3.3 of [Structure and " +"Interpretation of Computer " +"Programs](https://mitpress.mit.edu/sites/default/files/sicp/index.html), " +"which I was reading recently:" +msgstr "" + +msgid "" +"(define (search f neg-point pos-point)\n" +" (let ((midpoint (average neg-point pos-point)))\n" +" (if (close-enough? neg-point post-point)\n" +" midpoint\n" +" (let ((test-value (f midpoint)))\n" +" (cond ((positive? test-value)\n" +" (search f neg-point midpoint))\n" +" ((negative? test-value)\n" +" (search f midpoint pos-point))\n" +" (else midpoint))))))\n" +msgstr "" + +msgid "" +"(define (search f neg-point pos-point)\n" +" (let ((midpoint (average neg-point pos-point)))\n" +" (if (close-enough? neg-point post-point)\n" +" midpoint\n" +" (nif (f midpoint)\n" +" (search f neg-point midpoint)\n" +" (midpoint)\n" +" (search f midpoint pos-point)))))\n" +msgstr "" + +msgid "" +"It also avoids `cond`'s extra clunky parentheses for grouping, which is " +"unnecessary but built-in." +msgstr "" + +msgid "" +"As a macro, I personally feel it tilts the balance towards expressivenes " +"despite its extra cognitive load toll." +msgstr "" + +msgid "" +"After I looked at this macro, I started seeing opportunities to using it in " +"many places, and yet I didn't see anyone else using it." +msgstr "" + +msgid "" +"Not that the book should introduce such macro this early, but I couldn't " +"avoid feeling bothered by not using the `nif` macro, which could even remove" +" the need for the intermediate `test-value` variable:" +msgstr "" + +#~ msgid "" +#~ "After I looked at this macro, I started seeing opportunities to using it in " +#~ "many places, and yet I didn't see anyonelse using it." +#~ msgstr "" + +#~ msgid "" +#~ "Not that the book should introduce such macro this early, but I couldn't " +#~ "avoid feeling bothered by not using a `nif` macro, which could even remove " +#~ "the need for the intermediate `test-value` variable:" +#~ msgstr "" diff --git a/po/fr/LC_MESSAGES/a-propos.po b/po/fr/LC_MESSAGES/a-propos.po new file mode 100644 index 0000000..15a2579 --- /dev/null +++ b/po/fr/LC_MESSAGES/a-propos.po @@ -0,0 +1,30 @@ +# +msgid "" +msgstr "" + +msgid "layout: page" +msgstr "" + +msgid "title: About lang: en ref: about" +msgstr "" + +msgid "" +"Hi, I'm EuAndreh. I write software and occasionally music. You can find my " +"contact information in the footer of this page, or mail my [public " +"inbox](mailto:~euandreh/public-inbox@lists.sr.ht) " +"([archive](https://lists.sr.ht/~euandreh/public-inbox))." +msgstr "" + +msgid "" +"This is my personal website where I write articles, publish software and " +"more related work." +msgstr "" + +msgid "Other things" +msgstr "" + +msgid "[Pastebins listing]({% link pastebins.en.md %})." +msgstr "" + +msgid "[Articles by category]({% link categories.en.md %})." +msgstr "" diff --git a/po/fr/LC_MESSAGES/about.po b/po/fr/LC_MESSAGES/about.po new file mode 100644 index 0000000..53789ad --- /dev/null +++ b/po/fr/LC_MESSAGES/about.po @@ -0,0 +1,56 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: \n" +"POT-Creation-Date: \n" +"PO-Revision-Date: \n" +"Last-Translator: \n" +"Language-Team: \n" +"Language: fr\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: Poedit 2.4.2\n" + +msgid "" +"Hi, I'm EuAndreh. I write software and occasionally music. You can find my " +"contact information in the footer of this page, or mail my [public " +"inbox](mailto:~euandreh/public-inbox@lists.sr.ht) " +"([archive](https://lists.sr.ht/~euandreh/public-inbox))." +msgstr "" +"Salut, je suis EuAndreh. J'écris logiciel et parfois musique. Vous pouvez " +"rencontrer de donnés pour me contacter au bas cette de page, ou vous pouvez " +"également envoyer une message dans ma [boîte de réception " +"publique](mailto:~euandreh/public-inbox@lists.sr.ht) " +"([archive](https://lists.sr.ht/~euandreh/public-inbox))." + +msgid "" +"This is my personal website where I write articles, publish software and " +"more related work." +msgstr "" +"Ceci est mon site personnel où j'écris des articles, publie des logicielles " +"et d'autres travaux connexes." + +msgid "title: About" +msgstr "title: À propos" + +msgid "lang: en" +msgstr "lang: fr" + +msgid "ref: about" +msgstr "ref: about" + +msgid "layout: default" +msgstr "layout: default" + +#~ msgid "layout: page" +#~ msgstr "layout: page" + +#~ msgid "Other things" +#~ msgstr "Autres" + +#~ msgid "[Articles by category]({% link categories.en.md %})." +#~ msgstr "[Articles par catégorie]({% link categories.fr.md %})." + +#~ msgid "[Pastebins listing]({% link pastebins.en.md %})." +#~ msgstr "[Liste de pastebins]({% link pastebins.fr.md %})." diff --git a/po/fr/LC_MESSAGES/articles-by-category.po b/po/fr/LC_MESSAGES/articles-by-category.po new file mode 100644 index 0000000..7bad5b0 --- /dev/null +++ b/po/fr/LC_MESSAGES/articles-by-category.po @@ -0,0 +1,34 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: \n" +"POT-Creation-Date: \n" +"PO-Revision-Date: \n" +"Last-Translator: \n" +"Language-Team: \n" +"Language: fr\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: Poedit 2.4.2\n" + +msgid "title: Articles by category" +msgstr "title: Articles par catégorie" + +msgid "lang: en" +msgstr "lang: fr" + +msgid "{% include categories.html kind=\"articles\" %}" +msgstr "{% include categories.html kind=\"articles\" %}" + +msgid "ref: articles-by-category" +msgstr "ref: articles-by-category" + +msgid "layout: default" +msgstr "layout: default" + +#~ msgid "layout: page" +#~ msgstr "layout: page" + +#~ msgid "ref: articles-by-categories" +#~ msgstr "ref: articles-by-categories" diff --git a/po/fr/LC_MESSAGES/categorias.po b/po/fr/LC_MESSAGES/categorias.po new file mode 100644 index 0000000..c4da368 --- /dev/null +++ b/po/fr/LC_MESSAGES/categorias.po @@ -0,0 +1,12 @@ +# +msgid "" +msgstr "" + +msgid "title: Articles by category" +msgstr "" + +msgid "layout: page lang: en ref: categories" +msgstr "" + +msgid "{% include categories.html %}" +msgstr "" diff --git a/po/fr/LC_MESSAGES/categories.en.po b/po/fr/LC_MESSAGES/categories.en.po new file mode 100644 index 0000000..b5afcca --- /dev/null +++ b/po/fr/LC_MESSAGES/categories.en.po @@ -0,0 +1,31 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: \n" +"POT-Creation-Date: \n" +"PO-Revision-Date: \n" +"Last-Translator: \n" +"Language-Team: \n" +"Language: en\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: Poedit 2.4.1\n" + +msgid "title: Articles by category" +msgstr "title: Articles par catégorie" + +msgid "layout: page" +msgstr "layout: page" + +msgid "lang: en" +msgstr "lang: fr" + +msgid "ref: categories" +msgstr "ref: categories" + +msgid "{% include categories.html kind=\"articles\" %}" +msgstr "{% include categories.html kind=\"articles\" %}" + +#~ msgid "{% include categories.html %}" +#~ msgstr "{% include categories.html %}" diff --git a/po/fr/LC_MESSAGES/diapositives.po b/po/fr/LC_MESSAGES/diapositives.po new file mode 100644 index 0000000..c32f5d4 --- /dev/null +++ b/po/fr/LC_MESSAGES/diapositives.po @@ -0,0 +1,12 @@ +# +msgid "" +msgstr "" + +msgid "title: Slides" +msgstr "" + +msgid "layout: page lang: en ref: slides" +msgstr "" + +msgid "{% include link-listing.html kind=\"slides\" %}" +msgstr "" diff --git a/po/fr/LC_MESSAGES/en/index.po b/po/fr/LC_MESSAGES/en/index.po new file mode 100644 index 0000000..706c515 --- /dev/null +++ b/po/fr/LC_MESSAGES/en/index.po @@ -0,0 +1,32 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: \n" +"POT-Creation-Date: \n" +"PO-Revision-Date: \n" +"Last-Translator: \n" +"Language-Team: \n" +"Language: fr\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n > 1);\n" +"X-Generator: Poedit 2.4.2\n" + +msgid "{% include link-listing.html kind=\"articles\" %}" +msgstr "{% include link-listing.html kind=\"articles\" %}" + +msgid "title: Blog" +msgstr "title: Blogue" + +msgid "lang: en" +msgstr "lang: fr" + +msgid "ref: index" +msgstr "ref: index" + +msgid "layout: default" +msgstr "layout: default" + +#~ msgid "layout: page" +#~ msgstr "layout: page" diff --git a/po/fr/LC_MESSAGES/hml.po b/po/fr/LC_MESSAGES/hml.po new file mode 100644 index 0000000..3ab80bc --- /dev/null +++ b/po/fr/LC_MESSAGES/hml.po @@ -0,0 +1,18 @@ +# +msgid "" +msgstr "" + +msgid "title: Today I Learned" +msgstr "" + +msgid "layout: page lang: en ref: tils" +msgstr "" + +msgid "**T**oday **I** **L**earned: small entries of useful knowledge." +msgstr "" + +msgid "Shameless rip-off of [Anna e só](https://til.flourishing.stream/)." +msgstr "" + +msgid "{% include link-listing.html kind=\"tils\" %}" +msgstr "" diff --git a/po/fr/LC_MESSAGES/index.po b/po/fr/LC_MESSAGES/index.po new file mode 100644 index 0000000..c361c55 --- /dev/null +++ b/po/fr/LC_MESSAGES/index.po @@ -0,0 +1,28 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: \n" +"POT-Creation-Date: \n" +"PO-Revision-Date: \n" +"Last-Translator: \n" +"Language-Team: \n" +"Language: fr\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: Poedit 2.4.2\n" + +msgid "{% include link-listing.html kind=\"articles\" %}" +msgstr "{% include link-listing.html kind=\"articles\" %}" + +msgid "title: Blog" +msgstr "title: Blogue" + +msgid "layout: default" +msgstr "layout: default" + +msgid "lang: en" +msgstr "lang: fr" + +msgid "ref: root" +msgstr "ref: root" diff --git a/po/fr/LC_MESSAGES/music.po b/po/fr/LC_MESSAGES/music.po new file mode 100644 index 0000000..61f9148 --- /dev/null +++ b/po/fr/LC_MESSAGES/music.po @@ -0,0 +1,28 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: \n" +"POT-Creation-Date: \n" +"PO-Revision-Date: \n" +"Last-Translator: \n" +"Language-Team: \n" +"Language: fr\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: Poedit 2.4.2\n" + +msgid "title: Music" +msgstr "title: Musique" + +msgid "layout: default" +msgstr "layout: default" + +msgid "lang: en" +msgstr "lang: fr" + +msgid "ref: music" +msgstr "ref: music" + +msgid "{% include music-listing.html %}" +msgstr "{% include music-listing.html %}" diff --git a/po/fr/LC_MESSAGES/pastebins-by-category.po b/po/fr/LC_MESSAGES/pastebins-by-category.po new file mode 100644 index 0000000..c6ffaa1 --- /dev/null +++ b/po/fr/LC_MESSAGES/pastebins-by-category.po @@ -0,0 +1,31 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: \n" +"POT-Creation-Date: \n" +"PO-Revision-Date: \n" +"Last-Translator: \n" +"Language-Team: \n" +"Language: fr\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: Poedit 2.4.2\n" + +msgid "lang: en" +msgstr "lang: fr" + +msgid "ref: pastebins-by-category" +msgstr "ref: pastebins-by-category" + +msgid "{% include categories.html kind=\"pastebins\" %}" +msgstr "{% include categories.html kind=\"pastebins\" %}" + +msgid "title: Pastebins by category" +msgstr "title: Pastebins par catégorie" + +msgid "layout: default" +msgstr "layout: default" + +#~ msgid "layout: page" +#~ msgstr "layout: page" diff --git a/po/fr/LC_MESSAGES/pastebins.en.po b/po/fr/LC_MESSAGES/pastebins.en.po new file mode 100644 index 0000000..0ec4577 --- /dev/null +++ b/po/fr/LC_MESSAGES/pastebins.en.po @@ -0,0 +1,32 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: \n" +"POT-Creation-Date: \n" +"PO-Revision-Date: \n" +"Last-Translator: \n" +"Language-Team: \n" +"Language: fr\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n > 1);\n" +"X-Generator: Poedit 2.4.2\n" + +msgid "{% include link-listing.html kind=\"pastebins\" %}" +msgstr "{% include link-listing.html kind=\"pastebins\" %}" + +msgid "title: Pastebins" +msgstr "title: Pastebins" + +msgid "lang: en" +msgstr "lang: fr" + +msgid "ref: pastebins" +msgstr "ref: pastebins" + +msgid "layout: default" +msgstr "layout: default" + +#~ msgid "layout: page" +#~ msgstr "layout: page" diff --git a/po/fr/LC_MESSAGES/pastebins.pt.po b/po/fr/LC_MESSAGES/pastebins.pt.po new file mode 100644 index 0000000..6fe90f3 --- /dev/null +++ b/po/fr/LC_MESSAGES/pastebins.pt.po @@ -0,0 +1,12 @@ +# +msgid "" +msgstr "" + +msgid "title: Pastebins" +msgstr "" + +msgid "layout: page lang: en ref: pastebins" +msgstr "" + +msgid "{% include link-listing.html kind=\"pastebins\" %}" +msgstr "" diff --git a/po/fr/LC_MESSAGES/podcast-episodes-by-category.po b/po/fr/LC_MESSAGES/podcast-episodes-by-category.po new file mode 100644 index 0000000..fde540b --- /dev/null +++ b/po/fr/LC_MESSAGES/podcast-episodes-by-category.po @@ -0,0 +1,34 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: \n" +"POT-Creation-Date: \n" +"PO-Revision-Date: \n" +"Last-Translator: \n" +"Language-Team: \n" +"Language: fr\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: Poedit 2.4.2\n" + +msgid "title: Podcast episodes by category" +msgstr "title: Épisodes de podcast par catégorie" + +msgid "lang: en" +msgstr "lang: fr" + +msgid "ref: podcast-episodes-by-category" +msgstr "ref: podcast-episodes-by-category" + +msgid "{% include categories.html kind=\"podcasts\" %}" +msgstr "{% include categories.html kind=\"podcasts\" %}" + +msgid "layout: default" +msgstr "layout: default" + +#~ msgid "layout: page" +#~ msgstr "layout: page" + +#~ msgid "{% include categories.html kind=\"pastebins\" %}" +#~ msgstr "{% include categories.html kind=\"pastebins\" %}" diff --git a/po/fr/LC_MESSAGES/podcast.en.po b/po/fr/LC_MESSAGES/podcast.en.po new file mode 100644 index 0000000..7c99597 --- /dev/null +++ b/po/fr/LC_MESSAGES/podcast.en.po @@ -0,0 +1,32 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: \n" +"POT-Creation-Date: \n" +"PO-Revision-Date: \n" +"Last-Translator: \n" +"Language-Team: \n" +"Language: fr\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n > 1);\n" +"X-Generator: Poedit 2.4.2\n" + +msgid "title: Podcast" +msgstr "title: Podcast" + +msgid "lang: en" +msgstr "lang: fr" + +msgid "ref: podcast" +msgstr "ref: podcast" + +msgid "{% include link-listing.html kind=\"podcasts\" %}" +msgstr "{% include link-listing.html kind=\"podcasts\" %}" + +msgid "layout: default" +msgstr "layout: default" + +#~ msgid "layout: page" +#~ msgstr "layout: page" diff --git a/po/fr/LC_MESSAGES/pt/index.po b/po/fr/LC_MESSAGES/pt/index.po new file mode 100644 index 0000000..94b9903 --- /dev/null +++ b/po/fr/LC_MESSAGES/pt/index.po @@ -0,0 +1,12 @@ +# +msgid "" +msgstr "" + +msgid "title: Blog" +msgstr "" + +msgid "layout: page lang: en ref: index" +msgstr "" + +msgid "{% include link-listing.html kind=\"articles\" %}" +msgstr "" diff --git a/po/fr/LC_MESSAGES/screencasts-by-category.po b/po/fr/LC_MESSAGES/screencasts-by-category.po new file mode 100644 index 0000000..26d2a75 --- /dev/null +++ b/po/fr/LC_MESSAGES/screencasts-by-category.po @@ -0,0 +1,31 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: \n" +"POT-Creation-Date: \n" +"PO-Revision-Date: \n" +"Last-Translator: \n" +"Language-Team: \n" +"Language: fr\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: Poedit 2.4.2\n" + +msgid "title: Screencasts by category" +msgstr "title: Screencasts par catégorie" + +msgid "lang: en" +msgstr "lang: fr" + +msgid "ref: screencasts-by-category" +msgstr "ref: screencasts-by-category" + +msgid "{% include categories.html kind=\"screencasts\" %}" +msgstr "{% include categories.html kind=\"screencasts\" %}" + +msgid "layout: default" +msgstr "layout: default" + +#~ msgid "layout: page" +#~ msgstr "layout: page" diff --git a/po/fr/LC_MESSAGES/screencasts.en.po b/po/fr/LC_MESSAGES/screencasts.en.po new file mode 100644 index 0000000..c15c590 --- /dev/null +++ b/po/fr/LC_MESSAGES/screencasts.en.po @@ -0,0 +1,32 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: \n" +"POT-Creation-Date: \n" +"PO-Revision-Date: \n" +"Last-Translator: \n" +"Language-Team: \n" +"Language: fr\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n > 1);\n" +"X-Generator: Poedit 2.4.2\n" + +msgid "title: Screencasts" +msgstr "title: Screencasts" + +msgid "lang: en" +msgstr "lang: fr" + +msgid "ref: screencasts" +msgstr "ref: screencasts" + +msgid "{% include link-listing.html kind=\"screencasts\" %}" +msgstr "{% include link-listing.html kind=\"screencasts\" %}" + +msgid "layout: default" +msgstr "layout: default" + +#~ msgid "layout: page" +#~ msgstr "layout: page" diff --git a/po/fr/LC_MESSAGES/slides-by-category.po b/po/fr/LC_MESSAGES/slides-by-category.po new file mode 100644 index 0000000..b0727b6 --- /dev/null +++ b/po/fr/LC_MESSAGES/slides-by-category.po @@ -0,0 +1,31 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: \n" +"POT-Creation-Date: \n" +"PO-Revision-Date: \n" +"Last-Translator: \n" +"Language-Team: \n" +"Language: fr\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: Poedit 2.4.2\n" + +msgid "lang: en" +msgstr "lang: fr" + +msgid "ref: slides-by-category" +msgstr "ref: slides-by-category" + +msgid "{% include categories.html kind=\"slides\" %}" +msgstr "{% include categories.html kind=\"slides\" %}" + +msgid "title: Slides by category" +msgstr "title: Diapositives par catégorie" + +msgid "layout: default" +msgstr "layout: default" + +#~ msgid "layout: page" +#~ msgstr "layout: page" diff --git a/po/fr/LC_MESSAGES/slides.po b/po/fr/LC_MESSAGES/slides.po new file mode 100644 index 0000000..c0137ed --- /dev/null +++ b/po/fr/LC_MESSAGES/slides.po @@ -0,0 +1,31 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: \n" +"POT-Creation-Date: \n" +"PO-Revision-Date: \n" +"Last-Translator: \n" +"Language-Team: \n" +"Language: fr\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: Poedit 2.4.2\n" + +msgid "{% include link-listing.html kind=\"slides\" %}" +msgstr "{% include link-listing.html kind=\"slides\" %}" + +msgid "title: Slides" +msgstr "title: Diapositives" + +msgid "lang: en" +msgstr "lang: fr" + +msgid "ref: slides" +msgstr "ref: slides" + +msgid "layout: default" +msgstr "layout: default" + +#~ msgid "layout: page" +#~ msgstr "layout: page" diff --git a/po/fr/LC_MESSAGES/til-by-category.po b/po/fr/LC_MESSAGES/til-by-category.po new file mode 100644 index 0000000..ab3a481 --- /dev/null +++ b/po/fr/LC_MESSAGES/til-by-category.po @@ -0,0 +1,34 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: \n" +"POT-Creation-Date: \n" +"PO-Revision-Date: \n" +"Last-Translator: \n" +"Language-Team: \n" +"Language: fr\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: Poedit 2.4.2\n" + +msgid "lang: en" +msgstr "lang: fr" + +msgid "ref: til-by-category" +msgstr "ref: til-by-category" + +msgid "title: TIL by category" +msgstr "title: AJA par catégorie" + +msgid "{% include categories.html kind=\"tils\" %}" +msgstr "{% include categories.html kind=\"tils\" %}" + +msgid "layout: default" +msgstr "layout: default" + +#~ msgid "layout: page" +#~ msgstr "layout: page" + +#~ msgid "{% include categories.html kind=\"til\" %}" +#~ msgstr "{% include categories.html kind=\"til\" %}" diff --git a/po/fr/LC_MESSAGES/til.po b/po/fr/LC_MESSAGES/til.po new file mode 100644 index 0000000..1053643 --- /dev/null +++ b/po/fr/LC_MESSAGES/til.po @@ -0,0 +1,39 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: \n" +"POT-Creation-Date: \n" +"PO-Revision-Date: \n" +"Last-Translator: \n" +"Language-Team: \n" +"Language: fr\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: Poedit 2.4.2\n" + +msgid "**T**oday **I** **L**earned: small entries of useful knowledge." +msgstr "" +"**A**ujourd'hui **J**'ai **A**ppris (de l'anglais, _**T**oday **I** " +"**L**earned_): petites postes de connaissances utiles." + +msgid "Shameless rip-off of [Anna e só](https://til.flourishing.stream/)." +msgstr "Copie éhontée de [Anna e só](https://til.flourishing.stream/)." + +msgid "{% include link-listing.html kind=\"tils\" %}" +msgstr "{% include link-listing.html kind=\"tils\" %}" + +msgid "title: Today I Learned" +msgstr "title: Aujourd'hui J'ai Appris" + +msgid "lang: en" +msgstr "lang: fr" + +msgid "ref: tils" +msgstr "ref: tils" + +msgid "layout: default" +msgstr "layout: default" + +#~ msgid "layout: page" +#~ msgstr "layout: page" |