1. 20 Mar, 2011 1 commit
  2. 19 Mar, 2011 4 commits
  3. 18 Mar, 2011 1 commit
  4. 17 Mar, 2011 2 commits
  5. 16 Mar, 2011 1 commit
  6. 10 Mar, 2011 3 commits
  7. 09 Mar, 2011 1 commit
  8. 17 Feb, 2011 2 commits
  9. 06 Feb, 2011 1 commit
  10. 05 Feb, 2011 1 commit
  11. 24 Jan, 2011 1 commit
  12. 20 Jan, 2011 1 commit
  13. 03 Jan, 2011 3 commits
  14. 24 Dec, 2010 2 commits
  15. 23 Dec, 2010 1 commit
  16. 21 Dec, 2010 5 commits
  17. 16 Dec, 2010 1 commit
  18. 15 Dec, 2010 3 commits
  19. 10 Dec, 2010 2 commits
  20. 07 Dec, 2010 1 commit
  21. 04 Dec, 2010 2 commits
    • Francois-Rene Rideau's avatar
    • Francois-Rene Rideau's avatar
      2.011.3: fix infinite loop when a .asd file has a timestamp in the future. · 5db8c252
      Francois-Rene Rideau authored
      The issue was reported by Sid H <shortsightedsid@gmail.com> on asdf-devel.
      Problem is, when the filesystem server clock is in the future of
      the system clock (either because the NFS server has a clock in the future,
      or because the lisp host has a clock in the past),
      defsystem would call find-system (via find-component via parse-component-form)
      to make sure it modifies any previously registered object if any,
      rather than create a new object with "interesting" consequences if anyone
      held to the previous object.
      find-system would see the file has been modified
      since last registered with register-system,
      and proceed to load again, in an infinite loop that stop
      either when the Lisp process runs out of stack, or
      the date and time specified in the timestamp is reached.
      Now, ASDF doesn't bother reloading if the timestamp is in the future.
      5db8c252
  22. 03 Dec, 2010 1 commit