Hi Patrick, Not to discourage you from pressing for fixes, but 9 times out of 10 I have to just end up forking open source projects to fix bugs and then just use my own fork. This is the fast path. Perhaps you've already intuited this. Just to let you know you aren't alone in the experience.
Often the best you can do is to post a link (say, in an Issue on the original) to your fork with fixes so others can find it, and maintainers can pull from it if/when they get to it, and move on to more interesting work... This is the beauty of open source at work. Best wishes. Jason On Thursday, March 20, 2025 at 4:44:57 PM UTC Andy Balholm wrote: > On both of them, someone did a mention of @mpvl (Marcel van Lohuizen), so > I assume he is the primary maintainer of the package, and everyone else is > waiting for him to do something. > > Andy > > On Thursday, March 20, 2025 at 6:23:09 AM UTC-7 Patrick wrote: > >> Hello all, >> >> I have opened two issues for the bidi package in the text repository that >> are clearly bugs. I have provided an analysis for both bugs and a pull >> request for one. Except for some housekeeping, these issues seem to get no >> attention. >> >> How is it possible to draw attention to the reports? Both fixes are not >> nice-to-have feature requests but pointing out (and fixing) incorrect >> behaviour of the implemented algorithm. >> >> https://github.com/golang/go/issues/71809 >> https://github.com/golang/go/issues/72089 >> >> I know that these are not in the core, so they are of lower priority, but >> perhaps I can offer more insight on what is going wrong? >> >> I hope it is not silly to ask here... >> >> Patrick >> >> -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/golang-nuts/d1eece13-3195-4cf0-b139-614ab86bbdben%40googlegroups.com.
