男孩儿救了那只虫子。
虫子很小。
The bug was caused by an error in the script.
这个故障是由脚本程序出错造成的。
我不喜欢虫子。
我能看到小虫。
So I know the bug is not above.
因此我知道bug不在上面了。
The bug sleeps in a peanut shell.
虫子睡在一个花生壳里。
Click the bug or the arrow to read on.
点击小虫子或者箭头来继续阅读。
The next step is obvious: Fix the bug.
下一步显而易见：修复bug。
By the way, do you know how to fix the bug?
顺便问一下，您知道如何修复bug吗？
Do you understand the code where the bug appears?
您是否理bug出现的那段代码？
Does the bug seem simple, obvious, and local?
bug是不是看起来简单、明显并且是局部的？
The first thing to do is tag the bug-fixed code.
首先要做的是给修复 bug 之后的代码加上版本标记。
Oh, and don't sweat the bug legs; they grow back!
哦，不要担心虫子腿；它们会长回来的！
See the Resources section for a link to the bug page.
见参考资料一节中错误页的链接。
When do they get paid for the work of fixing the bug?
他们什么时候开始通过修复自己的bug来获得报酬了？
The bug should go through the life cycle to be closed.
缺陷在走完其生命周期最终会关闭。
Then you can enter the description of the bug you've found.
然后输入您发现的bug的描述。
Fix the bug: lifetime managers with open generic types.
修复bug：在生命周期管理器中使用泛型类型。
You may be able to spot the bug in Listing 2 very easily.
您可能会非常容易地发现清单2中的bug ！
The bug is found in saliva and normally causes no problems.
这种病毒存在于唾液中，一般是不会有什么问题的。
How can you find out what's wrong if the bug isn't obvious?
如果错误不明显，那么您怎样找到错误原因？
I made a sweeping change, and the test cases caught the bug.
我进行了较大的更改，测试就发现了bug。
I would think that future releases of the class will fix the bug.
我想将来发布的这个类会修复这个bug。
Nothing new was added, but the bug fixes are sure to be welcome.
虽然没有添加任何新的内容，但一些bug的修补应该很受欢迎。
Figure 1 shows the description for the bug Naked notify in method.
图1显示了缺陷Nakednotify in method的说明。
When the customer sends the bug list I send the bugs to developers.
客户把bug列表发给我，我再把这些bug发给开发人员。
See if you can spot the bug faster than I did (about five minutes).
看看您能不能比我更快发现bug(我用了大约5分钟)。
The bug had been there for at least two weeks, and I hadn't noticed.
这个bug存在至少有两周了，而我没有注意到它。
The difference between expectation and reality is where the bug lies.
期望和现实之间的差别就是问题所在。
应用推荐