alsuren
I think that this could all be done using real branches, plus an integration branch with post-commit hooks to backport each commit onto the "default" branch and recreate the octopus merge "integration" commit each time. Would that work, or am I missing something?
We ended up doing it all in typescript, or with some postgraphile shenanigans.
One of the things we missed when requirements gathering was the ability to view a table of records each at their "latest published" version.
I think this can probably be done by including a pair of tztsrange columns in the history table (one for "when was this the latest valid draft?" and one for "when was this the latest valid published version", and do a bunch of date shuffling whenever you publish a version.
We've not actually done this yet, because there are some edge cases around dependency graphs and computed columns, but for a simpler app I reckon it would work just fine.
Recently I have been using SD 1.5 checkpoints with the LCM lora for all of my image generation (generally weighted down to 0.8 strength, with 6 step inference). It's not as fast as sdxl turbo, but at least it does a good job of people's faces.
It would be good to make more efficient use of people's donated resources by making it possible to use LCM lora.
I tried to extend the idea to cargo build (see http://alsuren.github.io/2022/07/30/why-cargo-quickbuild.htm...) but I never got it to work with proc macro packages so I gave up. If anyone wants to have a go at getting it working, I'm happy to mentor.
I feel like this should be made opt in somehow. If you are a noninteractive process and stdin is a tty then you probably shouldn't be swallowing input. I frequently blind-type the next command while a long running command is active, because well behaved noninteractive programs don't swallow input from stdin.
You would hope that the 350kg is from a point load in the middle of the bed. If anyone finds out, I would also be interested to know.
This post has prompted me to give fish another go, so I looked into it again.
It looks like the abbreviation system can now (since March this year) help you with !! (https://fishshell.com/docs/current/cmds/abbr.html even gives it as an example)
I also use `!$` (`vim script.py` and then `python !$` or `git commit !$`) but the parser rejects `!$` before it can be rewritten by the abbreviation system. [edit: https://superuser.com/a/1762626 points out that if you add a space before hitting enter then it works fine, so I'm guessing it's just a bug, and I should go with d below]
Options seem to include:
a) make a !$ replacement that is not illegal and change your muscle memory `\$` or `!\$` or `!@` or `!%`
b) use a keybinding for !$ as suggested in https://github.com/fish-shell/fish-shell/issues/288
c) some combination of a and b (e.g. make a `!\$` abbreviation and then make a binding so that if you type !$ it replaces it with `!\$` so that it gets past the parser without expliding)
d) patch the parser to allow !$ as a special case if there is an abbr for it.
I just tried b but it's pretty jarring. I think I might go with c instead.
I'm actually feeling quite positive about this now.
There is something I've been wanting to add to bash since forever, which is something to help me cd into a repo that I just cloned (e.g. `git clone https://github.com/fish-shell/fish-shell` then `cd !/` could expand to `cd fish-shell`).
Exciting times.
Cycle to work schemes let you buy a bike before income tax. I'm not sure how that compares to e-car tax breaks though.
All your employer if they have such a scheme.
https://github.com/bytedance/monolith exists, but is an empty repo. A Web Search for "github bytedance monolith" finds a bunch of files in that repo that are 404s when you click on them.
I will have to tell my housemate about your setup - we have a bunch of 433mhz light switches hooked up to our system, but they're currently connected via an esp32 in a slightly ugly way. That usb dongle sounds like a much better solution to that problem.
As an aside, we are also currently using OpenHAB to make the bridge to Google Assistant when we want to trigger actions. My housemate is currently in the process of ripping it out, and replacing it with something that he's working on in rust, using axum. I would give you a link, but I can't remember what is called, and GitHub is down.