Login
You're viewing the mastodonapp.uk public feed.
  • Sep 18, 2026, 5:12 PM

    Since #prusa3d decided to automatically close all their old issue reports (most of which were never given any visible activity from the prusa side) in the lead up to #prusaslicer 3.0.0 being released, I actually re-tested one I'd reported .. and of course it reproduces.

    so I commented on that one, and then had to file 3 fresh bugs for new terrible UI behavior in their 3.0.0 alpha release.

    Wanna take any bets how responsive Prusa will be to these reports? There are a LOT of recent comments with varying levels of politeness in the bugs they had set to auto-close with zero Prusa follow-up, I can tell you that.

    In the bug of interest to me, there actually HAD been a comment that I think came from a prusaslicer contributor -- to the effect that the bug was probably upstream, so no action was possible by them. But, my sibling in git, YOU are the one with a relationship with your upstream, so why don't YOU go ahead and report this to them so it can maybe get fixed someday? I do NOT have a relationship with your upstream!

    Anyway this is getting angrier than intended so I'll stop typing now.

    💬 1🔄 2⭐ 2

Replies