For #1 I've been keeping a keen eye on pgcat [1], in particular the https://github.com/postgresml/pgcat/issues/303 which
implies that it should be possible to add support for transaction mode LISTEN/NOTIFY support.
Coming up to 37 and for the last few weeks I’ve had the same sort of realisation - reading novels seems to take more concentration than it should, and I’ve become lazy with maths.
I’ve had an eye check, a few months back a general medical. Both were fine/no significant changes. I rarely drink, no drugs. I feared a series of migraines might been response but I’ve been assured otherwise.
I so far figured it’s too much skim reading, a lot of very poor sleep, being on the edge of burn out and maybe a touch of post COVID brain fog.
Your post is encouraging me to start doing something about it.
I don’t have much to add but it’s reassuring to know that I’m not alone
At my org, if I use teleport, I have to MFA in via a UI, and they offer zero other alternatives.
The teleport daemon falls over due to memory stress and other issues that sshd doesn't fall over during, and when do you often need CLI access to a node? When it's under stress....
Goodbye automation.
It's a good idea, but it's made ssh and the problems I solve with ssh worse for me.
Just to echo this, I’m currently using a crate called deku (for a toy project to learn rust). Deku is a wrapper on top of bitvec which lets you annotate structs and enums for decoding and encoding. The speed I was able to implement a binary TCPStream encoder/decoder was great. Both have been rock solid for me.
If you’re selling dashboarding, you need to show that dashboarding really quickly. I looked at the site, skipped through the video and saw nothing. I did see something on the docs site, but I was lost at that point.
I would go further and say, in a crowded space like that with some excellent free options (i'd also add https://redash.io/ to the list which is very pleasant to work with), you need to show what actually differentiates you from those free and mature solutions.
> I hear this all the time, but I question how true it is. I've been running my own mail servers for decades, and I've never had any problems with sending or receiving mail. I suspect anyone who properly configures their server will be fine.
At work I ran email servers professionally and with good deliverability for years. My own email server was arguably longer lived than those at work, just much lower volumes. IP block was clean, DKIM, SPF, rDNS, etc. all setup correctly.
I thought I had no deliverability issues. I interacted with mailing lists regularly, the odd email to friends and family and I was firmly in your camp until I had to deal with a death in the family.
I think this was shortly after Microsoft BPOS became Office365. It became very very clear very very rapidly that to certain orgs I just wasn't hitting the inbox. And there was jack shit I could do about it. That was the end of my mail server, and it's certainly got worse over time.
In development mode with inotify you get python hot code reloading. In development mode the XML (with a handful of exceptions regarding menus, and ir.actions) will be read from disk on refresh.
I do wish there was hot code reloading for the views (xml), but realistically if you’re making an app of any complexity the views in the backend are the small part and likely not where you are spending the majority of your time.
Website stuff is absolutely 100% stuck in the past at the moment, imho.
If it helps, as far as I'm aware Ganesha [1] is still widely used, supported, in some cases faster than the kernel implementation, and can be pointed at an arbitrary config file.
[1] https://github.com/postgresml/pgcat