Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Need to report uninitialized error when paddle.init() is not called #2031

Closed
emailweixu opened this issue May 5, 2017 · 3 comments
Closed

Need to report uninitialized error when paddle.init() is not called #2031

emailweixu opened this issue May 5, 2017 · 3 comments
Assignees
@kuke
Labels
Bug

Comments

@emailweixu
Copy link
Collaborator

emailweixu commented May 5, 2017 •
edited
Loading

Currently if paddle.init() is not called in the beginning, there can be some strange errors not understandable by the user (e.g. #1971 ). We should explicitly check whether paddle.init() is called and report a sensible error message.
@lcy-seso lcy-seso added the Bug label May 9, 2017
@xinghai-sun
Copy link
Contributor

Yes. I also encountered the same problem and it wasted me a lot of time.

@hedaoyuan
Copy link
Contributor

I think we can add a global flag that is paddle initialized. And increase the judgment that has been initialized before some operation.

@kuke kuke self-assigned this May 22, 2017
@typhoonzero
Copy link
Contributor

Close due to low activity, please feel free to reopen it.

heavengate pushed a commit to heavengate/Paddle that referenced this issue Aug 16, 2021
@yghstill
fix save_model bug and remove inputs[mode] in rcnn (PaddlePaddle#2031)
7042801
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kuke kuke

Labels
Bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@kuke @lcy-seso @xinghai-sun @emailweixu @typhoonzero @hedaoyuan