You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order for the dropdown to be useful, datasets must be expressed in terms of strings. When providing a selected value at the start (given that the user provides their own dataset), it can only compare hashable values i.e. strings.
However, when working with the pipeline, the datasets must be expressed as lists of strings (in order to accommodate input sequences). How should we address this conflict?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In order for the dropdown to be useful, datasets must be expressed in terms of strings. When providing a selected value at the start (given that the user provides their own dataset), it can only compare hashable values i.e. strings.
However, when working with the pipeline, the datasets must be expressed as lists of strings (in order to accommodate input sequences). How should we address this conflict?
Beta Was this translation helpful? Give feedback.
All reactions