300 karma · joined March 7, 2018
"api.github.com/repos/{owner}/{repo}/actions/runs?status=in_progress" -> outputs 3 workflow runs
5 seconds later -> outputs 2 workflow runs
5 seconds later -> outputs same 3 workflow runs again
Apparently they make no guarantees of any type of consistency or continuity in output, which has the side effect of also making it completely useless.
Most people are quite capable of understanding higher-order ideas without fully grasping the underlying details too.
What makes a/your TM special that this is the case?
I don’t mean to take too much of your time though, maybe I’m too dumb for this.
Edit: I can sort of see how O(log n) is impossible or at least O(n) in a TM, but to reduce it to O(1) makes no sense to me
I’m not trying to dunk on you, but I can’t help to note that the denseness of math is too much for an idiot like me.
I personally can’t think of anything software related that Ubuntu provides over Debian for normal desktop users. Only the Ubuntu 6-month release schedule can be a bit nicer.
https://wiki.debian.org/DebianTesting
It is a good idea to install security updates from unstable since they take extra time to reach testing and the security team only releases updates to unstable
https://github.com/apache/logging-log4j2/blob/04637dd9102175...
-Dlog4j.formatMsgNoLookups=true
or
-Dlog4j2.formatMsgNoLookups=true
? Every project seems to list one or the other, even this cheat-sheet seems to list both in a random way...
This goes for loads of stuff. I would wager a $30 meal to be fresher than a $5 meal on average. I'm not saying there aren't any $5 meals that are fresher than some $30 meals, but just that the $30 has a lot lower chance to make me sick.
When I run 'winget list' It says I have Firefox 88.0 installed and there's an update for 88.0.1. But then I run 'winget upgrade Mozilla.Firefox' and it says 'No applicable update found'. Very similar stuff happens even for very popular Microsoft apps like VS2019 and VSCode, there it runs the installer but either doesn't update at all (VS2019) or winget thinks it's perpetually out of date (VSCode). For most other packages it cannot even link the listed application-id to the corresponding winget package, even if it definitely exists.
I understand it's all very variable and nonstandard in the Windows ecosystem, but I think it should be possible to get the versioning mostly right and build a much better database of application-ids and corresponding package names.
I'll just say that the emphasis should be on clean branches and PR's much more than clean individual commits. And on good code much more than clean git branches.
If there's too much ceremony around branches and pull requests I tend to avoid small fixes because it's just much work and that definitely doesn't improve the quality of the code.
_However_ some calories keep you hungry so it's probably _much_ easier to limit your calories on low-sugar than a high-sugar diet.
An overly clean git history for me is a sign of too much perfectionism and greatly reduced productivity.
When I code I usually have a general idea of the stuff I want to include in my branch, but then I stumble upon bugs or code couplings which I need to fix for my feature to work. And then I include the fix into my feature branch, because it's just tedious to switch all the time and create 5 interdependent branches that need to be merged together anyway. Also as long as the feature branch itself is fairly clean then I don't give a rats ass about atomic commits.
And commits having to pass tests is just ludicrous. That's what the tests are for, so you can fix it before merging the branch. Don't go crazy on the commit level..
It depends a bit on the project, and how public it is. But in the end your git history never provides any benefit to customers and doesn't make your code better by itself. I hardly ever rewrite or rebase commits unless there's a good reason for it.