1. 09 Aug, 2024 1 commit
  2. 08 Aug, 2024 1 commit
  3. 06 Aug, 2024 1 commit
  4. 05 Aug, 2024 1 commit
  5. 01 Aug, 2024 1 commit
  6. 31 Jul, 2024 1 commit
  7. 24 Jul, 2024 1 commit
  8. 23 Jul, 2024 4 commits
  9. 17 Jul, 2024 1 commit
  10. 16 Jul, 2024 2 commits
  11. 15 Jul, 2024 1 commit
  12. 14 Jul, 2024 1 commit
  13. 03 Jul, 2024 2 commits
  14. 02 Jul, 2024 1 commit
  15. 01 Jul, 2024 1 commit
  16. 28 Jun, 2024 1 commit
  17. 27 Jun, 2024 1 commit
  18. 20 Jun, 2024 1 commit
  19. 15 Jun, 2024 1 commit
  20. 12 Jun, 2024 2 commits
  21. 10 Jun, 2024 1 commit
  22. 01 Jun, 2024 2 commits
  23. 24 May, 2024 1 commit
  24. 23 May, 2024 1 commit
  25. 20 May, 2024 2 commits
  26. 19 May, 2024 1 commit
  27. 16 May, 2024 1 commit
  28. 13 May, 2024 2 commits
  29. 10 May, 2024 1 commit
    • SangBin Cho's avatar
      [Core] Fix circular reference which leaked llm instance in local dev env (#4737) · 6a0f6172
      SangBin Cho authored
      Storing exception frame is extremely prone to circular refernece because it contains the reference to objects.
      
      When tensorizer is not installed, it leaks llm instance because error frame has references to various modules which cause circular reference problem.
      
      I also found spec decoding has a circular reference issue, and I solved it using weakref.proxy.
      6a0f6172
  30. 02 May, 2024 1 commit
  31. 30 Apr, 2024 1 commit