"official/vision/serving/export_tfhub.py" did not exist on "10ee28ddf7666881057f36d596b7a515237ba8c4"
  1. 19 Jan, 2024 1 commit
  2. 18 Jan, 2024 7 commits
  3. 16 Jan, 2024 2 commits
  4. 15 Jan, 2024 7 commits
  5. 12 Jan, 2024 3 commits
  6. 11 Jan, 2024 3 commits
  7. 10 Jan, 2024 3 commits
  8. 08 Jan, 2024 2 commits
  9. 05 Jan, 2024 2 commits
  10. 04 Jan, 2024 2 commits
  11. 02 Jan, 2024 3 commits
  12. 30 Dec, 2023 1 commit
  13. 29 Dec, 2023 1 commit
    • Paul McCann's avatar
      Don't silence errors when loading tasks (#1148) · 34b563b1
      Paul McCann authored
      
      
      * Add example failing task
      
      This task includes an invalid import. This will cause an exception and
      the task will not be loaded. But this just results in a DEBUG level log
      message, so in normal usage you'll see no error, and will be told the
      task doesn't exist.
      
      Here's an example command line to run the task:
      
          python -m lm_eval --model hf --model_args pretrained=rinna/japanese-gpt-1b --tasks fail
      
      This task is based on a Japanese Winograd task, but that's not
      important, and was just used due to familiarity.
      
      * Do not ignore errors when loading tasks
      
      * Change how task errors are logged
      
      This makes the proposed changes from PR discussion.
      
      1. Exceptions not related to missing modules/imports are logged as
         warnings.
      
      2. module/import related exceptions are still logged at debug level, but
         if any of them happen there is a warning about it with instructions
         on how to show logs.
      
      * Remove intentionally failing task
      
      ---------
      Co-authored-by: default avatarPaul O'Leary McCann <polm@dampfkraft.com>
      34b563b1
  14. 28 Dec, 2023 1 commit
  15. 27 Dec, 2023 2 commits