-
Notifications
You must be signed in to change notification settings - Fork 38
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
Removes vocabs and propogates fixes for breaks #79
Conversation
Conflicts: src/translator/response.cpp -> Bringing to sync with ByteArray updates src/translator/response.h -> Bringing to sync with ByteArray updates
We however have Histories in constructor, which we will remove out of the way soon.
There is a potential bug in main. If a sentence is attempted to be inserted corresponding to an empty For now, I have pushed the eos corresponding This is handling invalid user-input - not something strictly wrong with the container (Annotation). |
…entence is happening
Focused PRs please. This appears to be both fixing annotations and removing vocabs. Separate them. |
By ordering these you've make it much harder to get in. You can simplify the diff here now. |
I have decoupled changes to simplify diff, this source breaks marian-decoder-new and the speed tests bound to it. |
@jerinphilip Does it make sense to merge |
@abhi-agg I hit the magic merge button, please review |
Well, there are no more bugs in main than what exists already with this in, so... Just breaks marian-decoder-new on invalid inputs thanks to sentencepiece that's all. Fix is in #85 which after hours of struggle I believe cannot improve much beyond. |
I'll take advantage of this situation and work the other way. I pull this source into annotation-bugfix branch through main. |
This PR removes
sourceVocab()
andtargetVocab()
exposed byService
as requested by Mozilla for interface towards a cleaner API.sourceVocab()
is unused and harmless to remove. RemovingtargetVocab()
breaks existingmarian-decoder-new
and consequently regression-tests. Further changes in the PR propogates the vocab change to provide aResponse
based output printing in the regression-test-app. We have lost capabilities to completely benchmark withmarian-decoder
for time being as the newOutputCollector
equivalent is a dumbed down version which only couts lines.Keeping the changes minimal for reducing review-load (edit: oops, sorry, accidentally removed a bit of
marian::Histories
in the process). Marking as ready for review.Regression tests (2/4) are failing for bytearray loads for bergamot-translator-app and service, which is already known and will fix with submodule update.
Regression-tests for service-cli which now tests the preliminary alignment and annotations are succeeding if PR merges.
bergamot-translator-app
stays intact, so no harm done.Checklist