Fix w2l@anywhere inference build #930
Conversation
vineelpratap
commented
Jan 5, 2021
vineelpratap
commented
- Fix build for inference pipeline
There was a problem hiding this comment.
@vineelpratap has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.
vineelpratap
force-pushed
the
inf_build
branch
from
2399848
to
5032269
Compare
|
@vineelpratap has updated the pull request. You must reimport the pull request before landing. |
vineelpratap
force-pushed
the
inf_build
branch
from
5032269
to
e51df81
Compare
|
@vineelpratap has updated the pull request. You must reimport the pull request before landing. |
vineelpratap
force-pushed
the
inf_build
branch
from
e51df81
to
12013d9
Compare
|
@vineelpratap has updated the pull request. You must reimport the pull request before landing. |
There was a problem hiding this comment.
@vineelpratap has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.
Summary: - Fix build for inference pipeline Pull Request resolved: #930 Differential Revision: D25783104 Pulled By: vineelpratap fbshipit-source-id: a0024f46ffb335d7cdc83ce0700a889491bc7228
|
This pull request was exported from Phabricator. Differential Revision: D25783104 |
vineelpratap
force-pushed
the
inf_build
branch
from
12013d9
to
5888ee8
Compare
|
Is there anything stopping this PR? |
|
Hi @vineelpratap! Thank you for your pull request. We require contributors to sign our Contributor License Agreement, and yours needs attention. You currently have a record in our system, but the CLA is no longer valid, and will need to be resubmitted. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at [email protected]. Thanks! |
