-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
good first issue lists #49927
Comments
@Ligoml 您好,想问下是要在 Python 端加输入检查,还是要在C++端用 |
根据情况而定。能够在C++端加的,一定要在C++端加。如果C++端不具备条件的,则在Python端加。 |
感谢所有参与的13位小伙伴,这个任务已经全部做完了:
欢迎大家继续关注飞桨快乐开源活动,我们近期已发布新的任务,谢谢大家! |
大家好,我们通过代码扫描工具,在 Paddle 框架中检测出若干适合入门框架开发的 issue,这些 issue 可以通过简单的 case 复现。欢迎大家一起提 PR 解决,你可以通过下表认领感兴趣的任务。为表感谢,我们为你准备了新春礼品🎁
对每个 case,我们都提供了详细的错误调用堆栈,能够看到代码在 Paddle 的哪个源码文件中出现这种错误(所以很容易锁定错误代码位置)。这些问题大概率是对输入参数检查不全面导致的,可以通过添加 PADDLE_ENFORCE_相关的参数检查和报错来解决。当然,也有可能是 Paddle 框架/算子内有更深层次的问题。我们希望你做的是:
a. PR 描述中请介绍你发现的原因及你的解决办法。
b. 请同时将复现 case 添加为1个单测。不要新建单测文件,将单测放到框架(模块)/算子已有的单测文件中。
注:
Hello, we have detected several good first issues in the PaddlePaddle framework by code scanning tools. These issues can be reproduced through simple cases. Welcome to solve together, and you can claim the tasks of interest through the following table. To express our gratitude, we have prepared a Chinese New Year gift for you 🎁
For each case, we provide a detailed stack trace message. In the stack trace message, you can see which source code file contains this error (so it is easy to lock the error code location). This problem is probably caused by incomplete inspection of input parameters. You can add PADDLE_ ENFORCE_* parameter checking and error reporting. Of course, these problems may also be caused by deeper bugs in the framework or operators. We hope contributors to do the followings:
a. Please introduce the reasons you found and your solution in the PR description.
b. Please also add the reproduced case as a unit test into the existing test file of the framework (module)/operator. Do not create a new single test file.
NOTE:
The text was updated successfully, but these errors were encountered: