1. 09 Mar, 2023 1 commit
  2. 07 Mar, 2023 1 commit
  3. 06 Mar, 2023 1 commit
  4. 03 Mar, 2023 1 commit
  5. 02 Mar, 2023 2 commits
  6. 28 Feb, 2023 1 commit
  7. 27 Feb, 2023 1 commit
  8. 24 Feb, 2023 2 commits
  9. 17 Feb, 2023 1 commit
  10. 16 Feb, 2023 2 commits
  11. 15 Feb, 2023 1 commit
  12. 13 Feb, 2023 1 commit
  13. 08 Feb, 2023 1 commit
  14. 07 Feb, 2023 1 commit
  15. 03 Feb, 2023 1 commit
  16. 02 Feb, 2023 2 commits
  17. 01 Feb, 2023 1 commit
  18. 31 Jan, 2023 4 commits
  19. 30 Jan, 2023 1 commit
  20. 26 Jan, 2023 1 commit
  21. 23 Jan, 2023 2 commits
  22. 20 Jan, 2023 1 commit
  23. 17 Jan, 2023 2 commits
  24. 03 Jan, 2023 1 commit
  25. 30 Dec, 2022 1 commit
    • Nick Hill's avatar
      fix(router): Include special tokens when tokenizing (#14) · 3efa5bbb
      Nick Hill authored
      There's currently a discrepancy in the tokenization between the router
      and python server code. The latter includes special tokens but former
      does not.
      
      This results in a token count mismatch for seq2seq models such as mt0
      where the tokenizer emits an EOS token at the end.
      
      This in turn results in some unexpected/incorrect output, in particular
      when batch concatenation is involved, because the python code uses the
      input length passed from the router for each row.
      
      As far as I can tell, it is better to include this token in the encoder
      `input_ids`, so I guess it's best to just adjust on the router side.
      3efa5bbb
  26. 15 Dec, 2022 1 commit
  27. 12 Dec, 2022 1 commit
  28. 08 Dec, 2022 1 commit
  29. 05 Dec, 2022 1 commit
  30. 14 Nov, 2022 2 commits