[{"data":1,"prerenderedAt":192},["ShallowReactive",2],{"project-24363326":3},{"id":4,"name":5,"line":6,"line_source":7,"title":8,"url":9,"domain":10,"maker":11,"posted_at":12,"year":13,"points":14,"comments":15,"rank_in_year":16,"shown_in_year":17,"top":14,"tier":18,"category":19,"subcategory":20,"format":21,"keywords":22,"reception":28,"sentiment":29,"stance_mix":30,"scored_comments":35,"aspects":36,"strip":40,"post_text":41,"what":42,"said":62,"maker_in_thread":123,"shape":132,"grid":134,"attempts":153,"same_week":154,"maker_shows":32,"maker_hidden":184,"reader_version":185,"card":186},"24363326","FixCache","keep track of bug-prone files from Git commit history","title","Show HN: FixCache – keep track of bug-prone files from Git commit history","https:\u002F\u002Fgithub.com\u002Faavshr\u002FfixCache","github.com","aavshr",1599136190,2020,40,11,1205,3028,"shown","dev_tools","code review bot","api",[23,24,25,26,27],"bug-prone files","git commit history","pull request review","bug cache","github app","curious",-0.133,{"positive":31,"neutral":32,"mixed":33,"critical":34},0,3,1,2,6,{"docs":37,"idea":38,"execution":39},{"positive":31,"critical":31},{"positive":31,"critical":34},{"positive":31,"critical":31},[32,31,31,33,31,33,32,31,32,32,31],null,{"problem":43,"audience":50,"pricing":41,"motivation":56,"time_to_build":41,"stack":60,"openness":61,"stage":61,"team_size":61},{"value":44,"source":45,"evidence":46},"Prioritizing verification and testing of files likely to contain bugs","maker",[47],{"id":48,"by":11,"text":49},"24387772","The core assumptions of the algorithm: - if a file introduced introduced a bug recently, it will tend to introduce bugs again - new files added with the bug introducing file will…",{"value":51,"source":45,"evidence":52},"Pull request reviewers",[53],{"id":54,"by":11,"text":55},"24363368","Hello HN, this is a github app implementation of FixCache(https:\u002F\u002Fpeople.csail.mit.edu\u002Fhunkim\u002Fimages\u002F3\u002F37\u002FPapers_kim_2007_bugcache.pdf) I wanted to do as a side project that…",{"value":57,"source":45,"evidence":58},"Side project useful to pull request reviewers, implementing a 2007 MIT bugcache paper",[59],{"id":54,"by":11,"text":55},[],"unknown",{"praise":63,"objections":72,"requests":94,"questions":110,"alternatives":122},[64],{"value":65,"source":66,"evidence":67},"Interesting idea based on a published paper","commenter",[68],{"id":69,"by":70,"text":71},"24378599","nmstoker","Looks really cool, although it's a shame the description isn't a bit more \"plain language\" - a simple summary of what it is intended for, before going into jargon would help…",[73,81,87],{"value":74,"source":66,"evidence":75},"Description is jargon-heavy and unclear about purpose",[76,77],{"id":69,"by":70,"text":71},{"id":78,"by":79,"text":80},"24387054","remram","I read the whole README but have no idea what this does. Is it letting you know when you change files that have had a large number of bug fixes recently? With the assumption that…",{"value":82,"source":66,"evidence":83},"Bug-fix locations may be biased by reporting and management attention",[84],{"id":85,"by":79,"text":86},"24408597","Are you sure it's not discovering bad developers? Maybe critical areas, e.g. that have the same amount of bugs as the rest but are complained about more? (since the algorithm can…",{"value":88,"source":66,"evidence":89},"Keyword matching may miss bugs that GitHub issue or PR metadata would catch",[90],{"id":91,"by":92,"text":93},"24374037","rcthompson","Based on the existence of the config option \"FIX_KEY_WORDS\", it seems like this detects bugs just using keyword matching? Github also tracks when issues are fixed by commits (and…",[95,99,106],{"value":96,"source":66,"evidence":97},"Plain-language README describing intended use and value",[98],{"id":69,"by":70,"text":71},{"value":100,"source":66,"evidence":101},"Pluggable hook to define what counts as a bug fix",[102],{"id":103,"by":104,"text":105},"24382316","shoo","One way to support this would be to make FixCache support an optional hook that would be responsible for deciding if a given commit was a bug fix or not. Naively, it could have…",{"value":107,"source":66,"evidence":108},"Use GitHub issue or PR metadata to detect fixes",[109],{"id":91,"by":92,"text":93},[111,118],{"value":112,"source":66,"evidence":113},"How is spatial locality defined",[114],{"id":115,"by":116,"text":117},"24366629","bjackman","Neato. How is \"spatial locality\" defined? Just distance in the filesystem tree?",{"value":119,"source":66,"evidence":120},"Why recently fixed files would be more bug-prone",[121],{"id":78,"by":79,"text":80},[],{"comments":124,"answered":125,"key":126},5,4,[127,130,131],{"id":128,"text":129},"24379142","I agree, I will update the README to showcase it's intended use and value more. Thanks for the input!",{"id":54,"text":55},{"id":48,"text":49},{"commenters":35,"max_depth":32,"maker_replies":124,"first_comment_mins":124,"lifespan_hours":133},122,[135,137,139,141,143,144,145,147,149,150,151],[69,31,32,136,70,31],"project\u002Fmixed\u002Fdocs",[128,31,31,138,11,33],"maker\u002Fpositive\u002Fdocs",[54,33,31,140,11,33],"project\u002Fneutral\u002Fidea",[78,34,33,142,79,31],"project\u002Fcritical\u002Fidea",[48,34,31,140,11,33],[85,34,33,142,79,31],[91,32,32,146,92,31],"project\u002Fneutral\u002Fexecution",[148,32,31,146,11,33],"24374264",[103,32,32,146,104,31],[115,125,32,146,116,31],[152,125,31,146,11,33],"24368494",[],[155,160,165,170,174,179],{"id":156,"name":157,"points":158,"category":159},"24380969","Linux Upskill Challenge",780,"learning_science",{"id":161,"name":162,"points":163,"category":164},"24422432","Mimestream",403,"productivity",{"id":166,"name":167,"points":168,"category":169},"24381700","Talk",310,"consumer_social",{"id":171,"name":172,"points":173,"category":19},"24407706","Titanoboa",279,{"id":175,"name":176,"points":177,"category":178},"24370296","typing",237,"creative",{"id":180,"name":181,"points":182,"category":183},"24363493","kiss-orm",220,"languages",false,"v2",{"id":187,"name":5,"line":6,"ai":184,"cat":19,"year":13,"points":14,"comments":15,"rec":28,"s":188,"top":14,"kw":189,"maker":11,"domain":10,"tier":18,"attempts":31,"strip":190,"url":9,"mix":191,"praise":65,"objection":74,"sub":20},24363326,-0.13,[23,24,25,26,27],"30010130330",[31,32,33,34],1794036595525]