The forgotten case of the dependency bugs

• DOI: 10.1145/3377813.3381364
• Publication Date: 2020-09-19T00:21:21Z
• Authors: Anders Fischer-Ni...; Zhoulai Fu; Ting Su; Andrzej Wąsowski
• Keywords: Mixed methods; Bug reports; Software development practices; Dependency bugs; Software faults; 02 engineering and technology; 004; Robot Operating System (ROS); Taxonomy of bugs; 0202 electrical engineering, electronic engineering, information engineering; Software linters; Quantitative analysis; Qualitative analysis

A dependency bug is a software fault that manifests itself when accessing an unavailable asset. Dependency bugs are pervasive and we all hate them. This paper presents a case study of dependency bugs in the Robot Operating System (ROS), applying mixed methods: a qualitative investigation of 78 dependency bug reports, a quantitative analysis of 1354 ROS bug reports against 19553 reports in the top 30 GitHub projects, and a design of three dependency linters evaluated on 406 ROS packages. The paper presents a definition and a taxonomy of dependency bugs extracted from data. It describes multiple facets of these bugs and estimates that as many as 15% (!) of all reported bugs are dependency bugs. We show that lightweight tools can find dependency bugs efficiently, although it is challenging to decide which tools to build and difficult to build general tools. We present the research problem to the community, and posit that it should be feasible to eradicate it from software development practice.