Skip to content

Use CAFFE_ENFORCE instead of CHECK in caffe2 rnn executor#13144

Closed
ilia-cher wants to merge 1 commit intopytorch:masterfrom
ilia-cher:export-D10857963
Closed

Use CAFFE_ENFORCE instead of CHECK in caffe2 rnn executor#13144
ilia-cher wants to merge 1 commit intopytorch:masterfrom
ilia-cher:export-D10857963

Conversation

@ilia-cher
Copy link
Copy Markdown
Contributor

@ilia-cher ilia-cher commented Oct 25, 2018

Use CAFFE_ENFORCE instead of CHECK when validating inputs in RNN executor

Summary: The intention of this diff is to prevent prevent predictor service from crashing by the "Check failed: timestep >= 0 && timestep < _T" error, as a bandage, before D10848803 can be landed (assuming D10848803 replaces the CHECKs into CAFFE_ENFORCEs, too).

Differential Revision: D10857963

fbshipit-source-id: 896db804a89960e8d49f0434723515035062e0cc
@ezyang ezyang added the merged label Jun 25, 2019
laurentdupin pushed a commit to laurentdupin/pytorch that referenced this pull request Apr 24, 2026
)

Summary:
Pull Request resolved: pytorch#13144

The intention of this diff is to prevent prevent predictor service from crashing by the "Check failed: timestep >= 0 && timestep < _T" error, as a bandage, before D10848803 can be landed (assuming D10848803 replaces the CHECKs into CAFFE_ENFORCEs, too).

Reviewed By: ilia-cher

Differential Revision: D10857963

fbshipit-source-id: bb56ad83aa867a2d25953aa7ffd84b078f8bf84a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants