3 ms·

If your software has a bug, it’s your bug. If the root cause of the bug in your software comes from a direct call into some dependency, that’s immaterial to the

by nkrisc 1y ago

If your software has a bug, it’s your bug. If the root cause of the bug in your software comes from a direct call into some dependency, that’s immaterial to the users of your software. Your software is incorrect, so your software has a bug. How you choose to resolve it is up to you. You might implement a fix in your code to handle the bug case until the dependency is fixed.

coldpie 1y ago
Of course. They chose to resolve it by saying the underlying software should be fixed. That seems perfectly fine to me.
- Symbiote 1y ago
  That's not a resolution, that's ignoring the bug.
  - coldpie 1y ago
    No, it isn't. It's directing the bug to the people who are able to fix it.
    - aydyn 1y ago
      No its not, stop being obtuse on purpose.
    - croon 1y ago
      You can fix it by handling the erroneous output from your dependency, or switching out your dependency, or submit a fix to the dependency, or asking them to fix it.
- fasterik 1y ago
  The responsible thing to do would be to report the bug to the upstream project and keep the issue open pending the underlying issue's resolution. This is a broader cultural thing. In large organizations there is a tendency toward deflecting as much responsibility as possible onto other teams. In part it's a lack of resources, but it's also a result of individual contributors not being willing to take ownership of the product they work on.