xoudini

7 ms·

1.
by xoudini 4y ago
> without any external dependencies (i.e. no Redis/RabbitMQ) You still depend on a database with the `Task` model. This would be a no-go for that reason, since there's no reasonable way to have an impact on its behaviour, outsi
2.
by xoudini 5y ago
I won't comment on whether it's a solved problem in general, as I don't actively follow the area very closely, but that particular QRNG has been shown to be more biased than /dev/urandom [0], and other QRNGs have ex
3.
by xoudini 5y ago
Link to anchor: https://www.spacex.com/updates/index.html#sl-geostrom (sic)
4.
by xoudini 5y ago
Well, just letting it expire would certainly halt local development at <dayjob> until renewing. The primary reason for this is that some integrations require TLS for callbacks, so we have a local reverse proxy serving everything with
5.
by xoudini 5y ago
That would be my exact use-case for a service like this: monitoring a domain I have pointing at localhost (and not only for expiry, but also for revocation). At least currently the demo check fails on trying on trying to establish a connect
6.
by xoudini 5y ago
Well, to be fair, the `len` operation on lists in Python is a constant time operation. What makes the example particularly bad is using a cast on the result of a floating-point division, rather than just using Python 3 integer division (i.e
7.
by xoudini 5y ago
I'm not familiar with the software in question, but I'm quite sure it'd still be possible to have someone else to sit your exam. For instance, you could have an external webcam pointed at yourself, and have someone else in fr
8.
by xoudini 5y ago
Here's a (perhaps "unnecessarily clever") Python 3 version I wrote a while back, for some reason: import functools def fizzbuzz(n): if not n % 3: yield (r := "fizz") if not n % 5: yiel
9.
by xoudini 5y ago
I can see this happening, but with a reasonable bug-tracking solution in place and enforcing `fix/...` branches for fixes, these situations could mostly be avoided.
10.
by xoudini 5y ago
Hm, you're right. The simplest example I could think of right now is the upstream having renamed/deleted something that the dev branch depends on, but didn't directly touch. That would definitely cause a "broken" hi
11.
by xoudini 5y ago
In some cases I agree, but squashes can end up so large that doing a `git bisect` (which is quite useful in finding the comparatively small commit which introduced a bug) becomes unfeasible.
12.
by xoudini 5y ago
When you rebase, you basically replay the history of your branch since it diverged from the branch you're rebasing onto. Thus, the branch is always in a consistent state (or equally consistent to when you originally authored the commit
13.
by xoudini 5y ago
There shouldn't be an issue in doing so. During a rebase you'll either have no conflicts — in which case there isn't an issue — or you'll have to stop to resolve conflicts, and you might as well run tests before continui
14.
by xoudini 6y ago
In Swift 3 (and probably previous versions as well), `String.count` defaulted to the count of the Unicode scalar representation. In this version, iterating over a string would operate on each Unicode scalar, which often doesn't make se
15.
by xoudini 6y ago
I had a similar thought: git init -q && git commit -q --allow-empty -m "Hello, World\!" && git show --format=%B | head -1