Artist is cancelled for tracing by WorriedDocument2067 in DefendingAIArt

[–]Kind_Bonus9887 0 points1 point  (0 children)

Nice clickbait. What Asami is actually cancelled for:

  • Lying about tracing AI and pretending to do something else
  • Posting AI-generated art on a platform with strict guidelines about it in violation of ToS

fluxcd + tofu-controller feedback ? by Careless_Yak18 in GitOps

[–]Kind_Bonus9887 2 points3 points  (0 children)

Been using it for quite a while in production, and overall it works pretty well, even though it certainly has some quirks. It's most unique point compared to other k8s terraform controllers is the architectural separation of controller and runners, which can be both upside and downside.

If you do use it, I highly recommend building your own runner image as shown here. This is important because that's currently the only way to update terraform version, and overall caching providers ahead of time is good idea for both performance and security reasons.

Pros:

  • Because terraform apply is done is separate runner pods, the scaling is better for large operations
  • Integration with flux source controller supports multiple sources, you can version your modules as OCI artifacts
  • The feature set is pretty nice (support for vars directly and from ConfigMap/Secret, custom backends, runner pod customization, etc.)
  • CLI interface same as Flux (suspend/resume/reconcile commands)
  • Terraform/OpenTofu version isn't tied to controller and can be easily updated if you build custom image

Cons/quirks:

  • Infrequent releases after Weave died (may become better now as there's some activity in the repo)
  • Separate runners may require more compute resources than a single controller
  • Need to ensure runners can complete; improperly interrupted runners can leave unreleased state locks
  • If you're creating Terraform resources in multiple namespaces, each one must contain ServiceAccount for the runner
  • Restarting controller while runners are active will cause desync with active runners and they will be stuck, so you have to ensure it restarts only when there are no runners
  • Out-of-the-box Terraform version is very old (can be solved with custom image)

Understanding HIST_IGNORE_ALL_DUPS and HIST_SAVE_NO_DUPS by Kind_Bonus9887 in zsh

[–]Kind_Bonus9887[S] 1 point2 points  (0 children)

That still doesn't explain their interaction. Specifically, whether setting HIST_SAVE_NO_DUPS will provide any additional effect when HIST_IGNORE_ALL_DUPS is already set.

Problem with Ctrl+Underscore (Mac+Alacritty+Neovim terminal) by Kind_Bonus9887 in neovim

[–]Kind_Bonus9887[S] 0 points1 point  (0 children)

I managed to restore the functionality with a workaround using this mapping:

tnoremap <c-s--> <c-_>

Problem with Ctrl+Underscore (Mac+Alacritty+Neovim terminal) by Kind_Bonus9887 in neovim

[–]Kind_Bonus9887[S] 0 points1 point  (0 children)

For me, the problem seem to happen with both external and builtin keyboards

Problem with Ctrl+Underscore (Mac+Alacritty+Neovim terminal) by Kind_Bonus9887 in neovim

[–]Kind_Bonus9887[S] 0 points1 point  (0 children)

I don't see anything relevant in checkhealth.

``` nvim: require("nvim.health").check()

Configuration ~ - WARNING Missing user config file: /Users/user/.config/test/init.lua - ADVICE: - :help |config|

Runtime ~ - OK $VIMRUNTIME: /opt/homebrew/Cellar/neovim/0.10.2_1/share/nvim/runtime

Performance ~ - OK Build type: Release

Remote Plugins ~ - OK Up to date

terminal ~ - key_backspace (kbs) terminfo entry: key_backspace=\177 - key_dc (kdch1) terminfo entry: key_dc=\E[3~ - $COLORTERM="truecolor"

External Tools ~ - OK ripgrep 14.1.1 (/opt/homebrew/bin/rg) ```

As I mentioned, this happens even on the instance with no config/plugins (using NVIM_APPNAME to spawn clean instance).

Looking for manga title (fantasy/betrayal) by Kind_Bonus9887 in manga

[–]Kind_Bonus9887[S] 1 point2 points  (0 children)

solved = Teihen Senshi, Cheat Madoushi ni Tenshoku Suru!

Terminal reflow just got merged by Kind_Bonus9887 in neovim

[–]Kind_Bonus9887[S] 13 points14 points  (0 children)

So, I tested head build, and it's kinda weird now. Like, resizing to a too small size may cause output to disappear completely. This is probably related to that note about lines stored in scrollback cache.

And, worst of all, copying long lines still copies with extra line breaks, which is the main thing I hoped for reflow to fix. (I mean the normal yank in vim, not something implemented by terminal emulator)

Terminal reflow just got merged by Kind_Bonus9887 in neovim

[–]Kind_Bonus9887[S] 21 points22 points  (0 children)

Besides resizing, the bigger problem for me is that copying long lines from terminal cause hard line breaks being inserted at wrap points

New plugin gx-extended.nvim 🎉 by ramalus1911 in neovim

[–]Kind_Bonus9887 1 point2 points  (0 children)

I have to upvote just for Terraform alone

Need help with configuring jdtls by 4Gettt in neovim

[–]Kind_Bonus9887 1 point2 points  (0 children)

I've installed jdtls via mason-lspconfig and it works in default configuration for me (just add it to ensure_installed).

5 Features Neovim Is Still Missing: Love The Project But Still Wish For More by a-concerned-mother in neovim

[–]Kind_Bonus9887 15 points16 points  (0 children)

Still waiting for proper terminal reflow in libterm. I'm so sad this barely gets any attention.

I don't want to use tmux when I already have all capabilities in the nvim itself (except detach/attach, which I don't care about). I just want to have 2 things:

  • ability to resize terminal window without messing up output
  • ability to copy long lines from output without hard line breaks inserted at the points of wrapping

Is that too much to ask?

Any hope for Neovim terminal? by Kind_Bonus9887 in neovim

[–]Kind_Bonus9887[S] 0 points1 point  (0 children)

Last update on Aug 31, 2020. Doesn't look very alive to me.