![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png){kind=small}
Entry tags:
Question thread #149
It's time for another question thread!
The rules:
- You may ask any dev-related question you have in a comment. (It doesn't even need to be about Dreamwidth, although if it involves a language/library/framework/database Dreamwidth doesn't use, you will probably get answers pointing that out and suggesting a better place to ask.)
- You may also answer any question, using the guidelines given in To Answer, Or Not To Answer and in this comment thread.
The rules:
- You may ask any dev-related question you have in a comment. (It doesn't even need to be about Dreamwidth, although if it involves a language/library/framework/database Dreamwidth doesn't use, you will probably get answers pointing that out and suggesting a better place to ask.)
- You may also answer any question, using the guidelines given in To Answer, Or Not To Answer and in this comment thread.
It's dev related I swear....
The issue: Since I have been mostly-off MacOS for *cough* years, I am very out-of-the-loop for good tools. And I know there are at least 3 MacOS people who've done dev here.
To that end: Any recommendations for apps for person-who-pokes-at-code?
Things I'm specifically thinkin of:
A suitable analogue to Notepad++ for plain-text-editing with syntax highlighting
Good terminal emulators (For both local and ssh/telent [yes I know telnet is ancient and insecure; I still have cases where I need to use it]) to replace putty
SFTP client to replace WinSCP.
And, to be honest, I'm open to hearing recs about anything I should look at. But the above is why I thought it to be tangentially related. (Mods, feel free to smite/screen if not-sufficiently-related-enough.)
Re: It's dev related I swear....
BBEdit is the best text editor in the universe, and the paid version also is a scp client that lets you edit on-server so you don't have to mess with transferring files
The built-in Terminal works for just about anything you'd use PuTTY for! At least I've never found a reason to need something additional.
Re: It's dev related I swear....
Re: It's dev related I swear....
I've always found
sftpto work well enough for me, but if you want a graphical client I'm pretty sure Cyberduck is as good as it ever was.I think
sshandtelnetstill come preinstalled on macs? The default terminal is fairly decent, but if you want something fancier there are options. Ghostty and kitty are what all the cool kids are using right now, but Wezterm and Alacritty are also quite solid. iTerm2 is also still around, but I don't think there's any compelling reason to use it over wezterm or really any of the others here.Re: It's dev related I swear....
journal style question
no subject
no subject
no subject
Nearly a year later, circling back re: the above thread. My little corner of the web trucked along just fine for awhile, everything functioning as intended, until a system reboot a couple months ago ate a bunch of the comments and posts we've been playing around with.
Initially, I thought it was something to do with memcached and I've been poking at that, but I finally went elbows-deep into the database tables to cross-reference what's still there versus what's been eaten to actually be able to watch comments posting 'live' and I'm finding a bunch are being written into the database tables as " " (no quotes LOL) rather than the actual text. There doesn't seem to be any rhyme or reason as to which ones are going into the database versus which ones are giving the blank text (varying lengths, emojis or not, etc) but a test reboot of the server confirmed that those comments encoded as disappear from live view on the front end while hard-coded comments remain and I'm totally out of ideas for where I can start troubleshooting this.
Any ideas would be greatly appreciated. ðŸ˜
no subject
no subject
no subject
The problem was, in fact, with the database, specifically within the character_set and collation parameters and a mismatch with the character_set_system being utf8mb3 where everything else was utf8mb4/utf8mb4_0900_ai_ci.
Essentially what was happening is the utf8mb3 was causing the garbage/blank character spaces to actually write to the database in lieu of some posted comments/posts - I was able to track that down with watching the database table populate between comments to spot the pattern (it was specifically related to some emojis and iOS "special" characters like curly quotes). All seemed fine on the front end with Memcached masking the issue - they'd post correctly to Memcached but fail in the database, so with restarts - bye bye data.
Thank you again!
no subject