From 714a92a163645bb436b1e8f4c56a818656c35f8a Mon Sep 17 00:00:00 2001 From: Adrian Kummerlaender Date: Sat, 13 Apr 2019 17:37:10 +0200 Subject: Remove newly extracted features i.e. Overview is now a mostly pure aggregator again. The new commit / blip feature is now maintained in `blip.kummerlaender.eu`. --- ...0_38_23f6297c212525d71692eb7ee8e6e096ad4711a3.md | 13 ------------- ...1_12_c08fbb73a960bd19ab1ca553da5bb8111622baba.md | 13 ------------- ...0_52_1ffaf37388cd691e88196b6e00455eda0e652cf0.md | 20 -------------------- ...5_02_af756d78ac042a2eed2417c5250d4b675d43bf93.md | 11 ----------- ...2_30_b3ef0fc8daa41e433f1919a4933a1cc047f59341.md | 9 --------- ...2_08_84666523e9a278ac95ca43dbaa534e8aaaf3ebd2.md | 9 --------- ...8_26_55daf8a35f4f1761f5f4c4ebe4a6dcb4b0ace514.md | 18 ------------------ ...1_51_d2126fe52fd3c002631e66fa7d6e2d5cd8862bea.md | 21 --------------------- source/00_content/meta.xml | 8 ++------ 9 files changed, 2 insertions(+), 120 deletions(-) delete mode 100644 source/00_content/commits/blog.kummerlaender.eu/2017_01_17_20_38_23f6297c212525d71692eb7ee8e6e096ad4711a3.md delete mode 100644 source/00_content/commits/blog.kummerlaender.eu/2018_06_04_21_12_c08fbb73a960bd19ab1ca553da5bb8111622baba.md delete mode 100644 source/00_content/commits/change/2016_02_14_20_52_1ffaf37388cd691e88196b6e00455eda0e652cf0.md delete mode 100644 source/00_content/commits/change/2016_02_17_15_02_af756d78ac042a2eed2417c5250d4b675d43bf93.md delete mode 100644 source/00_content/commits/change/2016_02_20_22_30_b3ef0fc8daa41e433f1919a4933a1cc047f59341.md delete mode 100644 source/00_content/commits/compustream/2019_02_25_22_08_84666523e9a278ac95ca43dbaa534e8aaaf3ebd2.md delete mode 100644 source/00_content/commits/nixos_system/2018_10_01_08_26_55daf8a35f4f1761f5f4c4ebe4a6dcb4b0ace514.md delete mode 100644 source/00_content/commits/slang/2017_04_13_21_51_d2126fe52fd3c002631e66fa7d6e2d5cd8862bea.md (limited to 'source/00_content') diff --git a/source/00_content/commits/blog.kummerlaender.eu/2017_01_17_20_38_23f6297c212525d71692eb7ee8e6e096ad4711a3.md b/source/00_content/commits/blog.kummerlaender.eu/2017_01_17_20_38_23f6297c212525d71692eb7ee8e6e096ad4711a3.md deleted file mode 100644 index 9145e13..0000000 --- a/source/00_content/commits/blog.kummerlaender.eu/2017_01_17_20_38_23f6297c212525d71692eb7ee8e6e096ad4711a3.md +++ /dev/null @@ -1,13 +0,0 @@ -# Use `pandoc` as markdown processor - -The trigger but not the actual reason for this replacement of `kramdown` with `pandoc` was a strange generation issue with `kramdown`'s latest release. - -All recent articles failed to generate anything more than an empty page. A quick check of the resulting HTML for those articles offered nothing out of the ordinary. After taking a close look at the articles in question I narrowed the set of failing articles down to those containing footnotes - tangentially I only started using footnotes a couple of articles ago i.e. this explained this part of the issue. - -Some debugging of `InputXSLT` offered the following problem: `Xerces-C` generated an error message and stopped processing XML inputs containing `nbsp` non-blocking space characters in the implementation of the `external-command` function. This change in `kramdown`'s output can be traced back to enhancement issue [399](https://github.com/gettalong/kramdown/pull/399). Obviously this is not a problem in `kramdown` but an issue in the way this static site generator is wrapping HTML inputs. - -This problem should be solvable by adding appropriate namespace and doctype declarations to the markdown-generated HTML output. Instead I opted to perform the change to `pandoc` I had already planned for quite some time. - -The choice fell on `pandoc` as it offers some additional markdown features as well as allowing for conversion to a rich set of document formats. i.e. features like printing articles as PDF using LaTeX are trivial to implement if `pandoc` is the markdown processor of choice. Furthermore page compilation is noticeably faster using `pandoc`. - -One might note that this switch only solved the original issue by coincidence: Should `pandoc` start to generate non-blocking space characters the same problem will occur. But I have hopes that such a change would be configurable via `pandoc`'s plethora of configuration options. As this static site generator assumes everything to be XHTML I see no reason why I should not continue to treat HTML inputs as XML. diff --git a/source/00_content/commits/blog.kummerlaender.eu/2018_06_04_21_12_c08fbb73a960bd19ab1ca553da5bb8111622baba.md b/source/00_content/commits/blog.kummerlaender.eu/2018_06_04_21_12_c08fbb73a960bd19ab1ca553da5bb8111622baba.md deleted file mode 100644 index 616ee83..0000000 --- a/source/00_content/commits/blog.kummerlaender.eu/2018_06_04_21_12_c08fbb73a960bd19ab1ca553da5bb8111622baba.md +++ /dev/null @@ -1,13 +0,0 @@ -# Nixify build process - -Building the website in the presence of the Nix package manager is now -as simple as: - -- cloning this repo -- entering the nix-shell environment declared by `shell.nix` -- calling `generate` -- optionally call `preview` to spawn a webserver in `target/99_result` - -All dependencies such as the internal InputXSLT, StaticXSLT and -BuildXSLT modules as well as external ones such as KaTeX and pandoc are -built declaratively by Nix. diff --git a/source/00_content/commits/change/2016_02_14_20_52_1ffaf37388cd691e88196b6e00455eda0e652cf0.md b/source/00_content/commits/change/2016_02_14_20_52_1ffaf37388cd691e88196b6e00455eda0e652cf0.md deleted file mode 100644 index e7ee30b..0000000 --- a/source/00_content/commits/change/2016_02_14_20_52_1ffaf37388cd691e88196b6e00455eda0e652cf0.md +++ /dev/null @@ -1,20 +0,0 @@ -# Implement support for excluding arbitrary paths from tracking - -The library may be provided with a new-line separated list of regular expressions via the newly introduced `CHANGE_LOG_IGNORE_PATTERN_PATH`. - -Any proposed tracking path that is matched by any of the provided patterns is excluded from change reporting. This functionality uses the Standard's regular expression parsing functionality and as such doesn't introduce any new dependencies. If no file path is provided or the provided file path is unreadable all paths will be tracked. - -`change` was adapted to set `CHANGE_LOG_IGNORE_PATTERN_PATH` to `.change_log_ignore` which means that it will by default exclude any patterns provided via this file in the current working directory. - -An example for such a file customized for hiding _vim_'s internal write -logic may look as follows: - - [0-9]+ - [^~]*~ - [.*\.viminfo - .*\.swp - -Note that this is implemented in a fashion where it is not guaranteed that the full _canonical_ path is checked against the patterns. It remains to be decided if this is enough for all common use cases of this new functionality. - -`tracking::PathMatcher` lacks any explicit thread synchronization - according to my current knowledge this should not be necessary as we are only ever reading the private `std::vector` instance. -If invalid regular expressions are provided they are silently ignored. diff --git a/source/00_content/commits/change/2016_02_17_15_02_af756d78ac042a2eed2417c5250d4b675d43bf93.md b/source/00_content/commits/change/2016_02_17_15_02_af756d78ac042a2eed2417c5250d4b675d43bf93.md deleted file mode 100644 index 8c81150..0000000 --- a/source/00_content/commits/change/2016_02_17_15_02_af756d78ac042a2eed2417c5250d4b675d43bf93.md +++ /dev/null @@ -1,11 +0,0 @@ -# Implement static allocator for initialization - -The previous interposition logic based on plain usage of `dlsym` analogously to various online examples led to a deadlock during _neovim_ startup. This deadlock was caused by _neovim_'s custom memory allocation library _jemalloc_ because it calls `mmap` during its initialization phase. The problem with calling `mmap` during initialization is that this already leads to executing `libChangeLog`'s `mmap` version whoes static `actual_mmap` function pointer is not initialized at this point in time. This is detected and leads to a call to `dlsym` to remedy this situation. Sadly `dlsym` in turn requires memory allocation using `calloc` which leads us back to initializing _jemalloc_ and as such to a deadlock. - -I first saw this as a bug in _jemalloc_ which seemed to be confirmed by a short search in my search engine of choice. This prompted me to create an appropriate [bug report](https://github.com/jemalloc/jemalloc/issues/329) which was dismissed as a problem in the way `mmap` was interposed and not as a bug in the library. Thus it seems to be accepted practice that it is not the responsibility of a custom memory allocator to cater to the initialization needs of other libraries relying on function interposition. This is of course a valid position as the whole issue is a kind of _chicken and egg_ problem where both sides can be argued. - -To cut to the chase I was left with the only option of working around this deadlock by adapting `libChangeLog` to call `dlsym` without relying on the wrapped application's memory allocator of choice. The most straight forward way to do this is to provide another custom memory allocator alongside the _payload_ function interpositions of `mmap` and friends. - -`init/alloc.cc` implements such a selectively transparent memory allocator that offers a small static buffer for usage in the context of executing `dlsym`.The choice between forwarding memory allocation requests to the wrapped application's allocator and using the static buffer is governed by `init::dlsymContext`. This tiny helper class maintains an `dlsym_level` counter by posing as a scope guard. - -The end result of this extension to `libChangeLog` is that it now also works with applications using _jemalloc_ such as _neovim_ and should overall be much more robust during its initialization phase. diff --git a/source/00_content/commits/change/2016_02_20_22_30_b3ef0fc8daa41e433f1919a4933a1cc047f59341.md b/source/00_content/commits/change/2016_02_20_22_30_b3ef0fc8daa41e433f1919a4933a1cc047f59341.md deleted file mode 100644 index e724abc..0000000 --- a/source/00_content/commits/change/2016_02_20_22_30_b3ef0fc8daa41e433f1919a4933a1cc047f59341.md +++ /dev/null @@ -1,9 +0,0 @@ -# Interpose `open` library function - -`open` is not as side effect free as I had imagined - i.e. if the flag `O_TRUNC` is passed it truncates the file contents alongside opening the file descriptor. In practice this is done by _emacs_ prior to writing the new file content and as such needs to be intercepted so we can start tracking the file before it is changed. - -Interposing `open` required some changes to make the library work without including `fcntl.h`. This header not only defines some of the flags we require to check if a library call actually is able to change files but also defines the `open` library function. - -While implementing this change I noticed that the function interpositions implemented in C++ actually need to be declared as `external "C"` so their names do not get wrangled during compilation. I suspect that this was previously implicitly done for e.g. `mmap` and `write` by the included C standard library headers. However this did not work for `open` which is why all function interpositions are now explicitly declared external. - -End result: _emacs_ file changes are now tracked correctly. diff --git a/source/00_content/commits/compustream/2019_02_25_22_08_84666523e9a278ac95ca43dbaa534e8aaaf3ebd2.md b/source/00_content/commits/compustream/2019_02_25_22_08_84666523e9a278ac95ca43dbaa534e8aaaf3ebd2.md deleted file mode 100644 index 2ab7c03..0000000 --- a/source/00_content/commits/compustream/2019_02_25_22_08_84666523e9a278ac95ca43dbaa534e8aaaf3ebd2.md +++ /dev/null @@ -1,9 +0,0 @@ -# Compustream performance improvements and interactive wall drawing - -I found some time to further develop my GLSL compute shader based interactive LBM fluid simulation previously described in [_Fun with compute shaders and fluid dynamics_](https://blog.kummerlaender.eu/article/fun_with_compute_shaders_and_fluid_dynamics). Not only is it now possible to interactively draw bounce back walls into the running simulation but performance was greatly improved by one tiny line: - - glfwSwapInterval(0); - -If this function is not called during GLFW window initialization the whole rendering loop is capped to 60 FPS -- including compute shader dispatching. This embarrassing oversight on my part caused the simulation to run way slower than possible. - - diff --git a/source/00_content/commits/nixos_system/2018_10_01_08_26_55daf8a35f4f1761f5f4c4ebe4a6dcb4b0ace514.md b/source/00_content/commits/nixos_system/2018_10_01_08_26_55daf8a35f4f1761f5f4c4ebe4a6dcb4b0ace514.md deleted file mode 100644 index 28820ef..0000000 --- a/source/00_content/commits/nixos_system/2018_10_01_08_26_55daf8a35f4f1761f5f4c4ebe4a6dcb4b0ace514.md +++ /dev/null @@ -1,18 +0,0 @@ -# Describe custom gitolite and cgit setup - -Replaces short-term Gitea instance on `code.kummerlaender.eu`. - -The main reason for implementing this more complex setup is that Gitea -both lacks in features in areas that I care about and provides distracting -features in other areas that I do not use. - -e.g. Gitea provides multi-user, discussion and organization support but doesn't provide -Atom feeds which are required for [Overview](https://tree.kummerlaender.eu/projects/xslt/overview/). - -This is why exposing [gitolite](http://gitolite.com)-managed repositories -via [cgit](https://git.zx2c4.com/cgit/about/) is a better fit for my usecases. - -Note that gitolite is further configured outside of Nix through its own admin repository. - -As a side benefit `pkgs.kummerlaender.eu` now provides further archive -formats of its Nix expressions which simplifies Nix channel usage. diff --git a/source/00_content/commits/slang/2017_04_13_21_51_d2126fe52fd3c002631e66fa7d6e2d5cd8862bea.md b/source/00_content/commits/slang/2017_04_13_21_51_d2126fe52fd3c002631e66fa7d6e2d5cd8862bea.md deleted file mode 100644 index ad39eee..0000000 --- a/source/00_content/commits/slang/2017_04_13_21_51_d2126fe52fd3c002631e66fa7d6e2d5cd8862bea.md +++ /dev/null @@ -1,21 +0,0 @@ -# Implement deferred word, conditional resolution - -Due to the non-trivial way tokens were previously processed the compiler could not safely perform tail-call elimination. Thus the _slang_ evaluation depth was restricted by the maximum call stack size. - -This issue is mitigated by introducing deferred word resolution - i.e. pushing expanded tokens onto a buffer stack and processing them in an explicit loop. - -This change ties into the implementation of the language's conditional primitive. The previous implementation did implicitly not support direct nesting of conditional expressions such as: - - truthA if - mainBranch - truthB if - secondaryMainBranch - then else - then - alternativeBranch - else - -This issue is now made explicit by disallowing direct nesting of conditionals as depicted above. Appropriate exceptions are generated when required and the conditional primitive is reimplemented in a more robust fashion under the assumption that this rule holds. Note that nesting is still fully supported iff. the nested conditional is contained in a deferredly evaluated word. As a positive side effect this will make it slightly harder to generate unreadable code by forcing developers to write simpler words. - -The main change of the conditional primitive lies in deferring branch token processing until the conditional expression is concluded by `else`. This is achieved by capturing non-dropped tokens in an internal buffer akin to how the word definition operator `§` is implemented. -The branch buffer is discharged after `else` is evaluated. Discharging is triggered via the newly introduced `result` method of the primitive evaluation module. This avenue for injecting tokens into the processing stream may be used by further primitives in the future. diff --git a/source/00_content/meta.xml b/source/00_content/meta.xml index 9897e1e..755c505 100644 --- a/source/00_content/meta.xml +++ b/source/00_content/meta.xml @@ -3,13 +3,9 @@ kummerlaender.eu https://kummerlaender.eu Adrian Kummerländer - Overview of kummerlaender.eu; blog and commit timeline aggregator - - 32 - + Overview of *.kummerlaender.eu 3 - 16 + 6 - https://code.kummerlaender.eu -- cgit v1.2.3