Skip to content
This repository has been archived by the owner on Dec 16, 2022. It is now read-only.

Add a text_to_instance method on DatasetReader #190

Closed
matt-gardner opened this issue Aug 25, 2017 · 2 comments
Closed

Add a text_to_instance method on DatasetReader #190

matt-gardner opened this issue Aug 25, 2017 · 2 comments
Assignees

Comments

@matt-gardner
Copy link
Contributor

The Predictors currently have to pull out the tokenizer and the token indexers from the DatasetReader and recreate what the DatasetReader does internally for every instance. This means that if we want to change (or add parameters to) what the DatasetReader does, we have to change the Predictors to match. Instead, we should just add a text_to_instance method on the DatasetReader itself, so that the Predictor can just keep around the DatasetReader, and pass off all processing to it.

@joelgrus
Copy link
Contributor

I'll do this, should be quick

@joelgrus
Copy link
Contributor

actually, I take this back, it's not quick, I'll leave it for later

@matt-gardner matt-gardner self-assigned this Sep 1, 2017
schmmd pushed a commit that referenced this issue Feb 26, 2020
* skiff files

* move models to json

* more stuff

* fix cloudbuild.yaml

* fix command

* change healthcheck

* add one model

* two services

* ingress

* only 1replica

* change ingress

* explicit root path

* Set more specific labels on the MC resources. (#189)

* parameterize entries

* oops

* loop over model names

* use all the models

* add back catchall

* try catchall a different way

* add more paths

* rename ingress

* add db info

* add cloudsql proxy container

* another try

* add volumes

* fix emptydir

* init container

* undo init containers

* Add an extra bit of information to use as part of the selector. (#190)

As it stands the base service includes *all* pods, as they all
have the labels it selects against.

This adds the `ui_server` label to that pod, so that we won't
send traffic to all 13 of them.

* match all

* Try send_static_file

* Moar logs; service labels

* Try a catch all route instead.

* redirect even when no-models

* add back default routes

* rename machine-comprehension -> reading-comprehension

* allow memory and cpu overrides

* handle extra fields correctly

* try very few resources

* move health check to /health route

* better stackdriver logging

* maybe this will make logging work correctly

* do not propagate

* add python-json-logger to Dockerfile

* increase time to first healthcheck

* address pr comments part 1
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants