I’ve used freezetime (Python) a decent amount and have experienced some very very very funny flakes due to it.
- Sometimes your test code expects time to be moving forward
- sometimes your code might store classes into a hashmap for caching, and the cache might be built before the freeze time class override kicks in
- sometimes it happens after you have patched the classes and now your cache is weirdly poisoned
- sometimes some serialization code really cares about the exact class used
- sometimes test code acts really weird if time stops moving forward (when people use freezetime frozen=true). Selenium timeouts never clearing was funny
- sometimes your code gets a hold of the unpatched date clsss through silliness but only in one spot
Fun times.
The nicest thing is being able to just pass in a “now” parameter in things that care about time.
there is something bitterly ironic about iPods (and their "sync" system to basically disallow arbitrary loading and sharing of music and "just" dropping music onto it) being now considered an example of an open device.
I don't believe there are residency requirements to ownership so the people doing that do not need to go through this flow at all. Just an entirely separate issue, though it might be tackled.
I do have the impression Tokyo is getting similar dynamics to the rest of the world on this front: builders don't care where the money is coming from and so if money from outside the country can get buildings built they're happy.
A friend of mine moved into a sold-out Yokohama tower mansion recently... and despite the bike and car parking being fully booked even more than 6 months in it was _quite_ empty. I have a feeling a lot of people are buying into the market expecting to get easy rental money and not really seeing it.
I don't know how verifiable it is, but the general narrative has been a lot is Chinese parking their money outside the reach of the CCP. I've never quite understood the mechanics of this though.
this has been my sort of big tent alignment with AI people. If I'm getting good CLI tooling that _actually works_ (or fixes to existing ones that have been busted forever) then I'm pretty happy.
Things that make systems more understandable to the LLMs ... usually make things more understandable for humans as well. Usually.
The biggest issue I've found is that vibed up tooling tends to be pretty bad at having the right kind of "sense" for what makes good CLI UX. So you still have awkward argument structures or naming. Better than nothing though
It never made sense to me why cars and pedestrians need to share the same spaces. Why can't we have more efficient walking routes that are away from cars?
if you have roads shared with pedestrians and cars (and bikes!) you can build denser cities.
I lived real downtown in Tokyo and my street was like "1.5" lanes wide (if cars were coming in both directions one basically needs to pull over and stop). I could just walk in the middle of the street. There was no sidewalk. No street parking of course. Cars would drive down at 15km/h or whatever, and slow to a crawl if people were in the street.
Straight lines are efficient walking routes, and ... well... that might involve just crossing the street directly! Every layer of grade separation gets in the way of that.
End result of all of this is less pavement to maintain, slower drivers (-> safer!), good walking and cycling conditions, etc etc etc.
Was kinda curious about the pricing and honestly the pricing[0] seems like one digit less than I expected. 10k JPY for the number, then 1k JPY per some of the various options (stuff like routing seems to be literally "we set up a phone tree and at the end of the phone tree we just dial a number you give us")
So it sounds like in the end you need to pay 10k JPY per queue + an extra bit of money to wire it all together. Maybe with Twilio you can set up something similarly fire-and-forget but "I explain to Docomo once how to set up my phone tree" sounds nicer than "I set up a twilio... thingy".
I'm sure somebody out there has at least considered being the layer over Twilio that just offers some of these straightforward services... but... toll-free numbers on Twilio cost 27 cents a minute in Japan. Sounds real close to that 33 yen.[1]
"jj new" is like "I'm going to make some changes", then you do "jj squash" to say "OK these look good enough to commit".
If you work this way you're "always" in a WIP state. And if you switch to another spot you won't lose your work, cuz it's persisted.
The end result if you work like this is you don't need stashing, since you get "free" stashing in your commit tree, which is more likely what people want (and if it's not... rebasing is easy so just move the node/`jj duplicate` it!)
`jj edit` exists but I think it's just not what people want in the default case at all. In exchange: rebasing "just works", stashing is not a thing to think about, and you don't lose your work
Is the problem here that everyone wants a different like 45% of the S3 API? Or is it that minio sucked all the oxygen out of the air in this space by being good at this, and now we need something else to show up?
For me it went into the multi-node direction, where I'd use Ceph anyway (or build on-top of an existing solid distributed database) if I needed it.
Also think there is an abstraction mismatch with the object stores that store the objects with a 1:1 mapping into the file system. Obvious issues are that you only get good listing performance with '/' as delimiter and things like "keys with length up to 1024 bytes" break.
The jellyfin DB itself is unfortunately sqlite instead of being DB agnostic. Maybe you could hack together something such that only one node handles writes and everyone else handles reads... if getting multiple cheap nodes gets your more bandwidth. I have to imagine that jellyfin fairly quickly stops being in charge of the media stream directly.
But yeah I think the transcoding and the size of your data pipe is the only "hard" part. The DB read/writes themselves are going to not be an issue (I think)
If Jellyfin ever fixes the mountain of bugs from the "upgrade". They aren't even acknowledging major bugs that make Jellyfin unusable for like 20% of users.
Do not upgrade Jellyfin if you have a sizeable library. Backup first if you do.
- Sometimes your test code expects time to be moving forward
- sometimes your code might store classes into a hashmap for caching, and the cache might be built before the freeze time class override kicks in
- sometimes it happens after you have patched the classes and now your cache is weirdly poisoned
- sometimes some serialization code really cares about the exact class used
- sometimes test code acts really weird if time stops moving forward (when people use freezetime frozen=true). Selenium timeouts never clearing was funny
- sometimes your code gets a hold of the unpatched date clsss through silliness but only in one spot
Fun times.
The nicest thing is being able to just pass in a “now” parameter in things that care about time.
reply