@g_bonfiglio Whatever you do, donโt buy Aquafina, it tastes absolutely horrible. Turns out in the US they bottle tap water ๐คฎ, make sure when you buy that it says โspring waterโ on the bottle
Midjourney finally released their consistent character features!
You can now generate images w/ consistent faces, hair styles, & even clothing across styles & scenes
This has been the top requested feature from the community for a while now
Some examples & how it works:
The hardest part of Engineering Management for me is context switching.
Not the jumping from meeting to meeting but understanding the current status of 50 different projects, their blockers, dependencies, etc. Still trying to figure out how to get a good handle on this ๐ณ๐
- 3 AM page ๐จ
- Kafka broker is running out of disk (11.8TB out of 12TB used) ๐จ
- You check everything: throughput, connections network. Nothing seems out of the ordinary ๐ฅ
- Retention settings are set to 1 day. It's one topic that hasn't been cleaned in weeks ๐คทโโ๏ธ
- You frantically Google, page, and ping team-mates ๐
... until you figure out ...
the `log.message.timestamp.type` setting
This setting defines what the timestamp on a Kafka record is for storage purposes on the broker.
This timestamp is used, among other things, in the calculation of log retention.
That is, when you have `log.retention.hours=24`, Kafka will delete a log file only when the LARGEST (latest) timestamp of any record in that log file is older than 24 hours.
Back to the `timestamp.type`. There are two supported values:
๐ธ LogAppendTime - the time at which the record was appended to the log (disk)
๐ธCreateTime - the time that was provided by the Producer when constructing its message
The DEFAULT is CreateTime.
This means that if you have just one Producer client produce a message with a timestamp in the future -- e.g "01-01-2120" - your log file will never get deleted!
This is a common gotcha and can cost you a night's (or a few) sleep.
Ways to circumvent this:
๐ก- changing `log.message.timestamp.type` to AppendTime
๐ก- setting size-based retention limits too - `log.retention.bytes`
This will ensure you have a maximum upper bound per topic that you'll never breach ๐
The TL;DR of how you can search:
โข from:twittername
โข keyword1 OR keyword2
โข min_faves:2000
โข min_retweets:2000
โข filter:links
โข filter:images
โข until:YYYY-MM-DD
โข since:YYYY-MM-DD
โข near:location within:15mi
Today Iโm going to do something Iโve been putting off for months, moving Plex off the NAS and using docker NFS volume mounts from on the new host. This should be fun..