1. 15 Dec, 2017 1 commit
  2. 14 Dec, 2017 1 commit
  3. 13 Dec, 2017 2 commits
  4. 11 Dec, 2017 3 commits
  5. 10 Dec, 2017 1 commit
  6. 08 Dec, 2017 1 commit
  7. 07 Dec, 2017 2 commits
  8. 06 Dec, 2017 3 commits
  9. 05 Dec, 2017 2 commits
  10. 01 Dec, 2017 1 commit
  11. 23 Nov, 2017 4 commits
  12. 22 Nov, 2017 3 commits
  13. 21 Nov, 2017 1 commit
    • Sebastien Robin's avatar
      erp5: fixed mysql data import when we have stored routines · efe3524c
      Sebastien Robin authored
      Issue was:
      - user project_user was created
      - project_user create stored routines
      - mysql data is dumped (including list of users)
      - mysql data is restored, but stored routines have the information
        DEFINER that must match an existing user. This does not
        work if there is no flush privileges instructions
      
      So make sure to insert flush privileges while dumping
      efe3524c
  14. 20 Nov, 2017 1 commit
  15. 17 Nov, 2017 2 commits
  16. 15 Nov, 2017 2 commits
    • Julien Muchembled's avatar
      typo · 325af127
      Julien Muchembled authored
      325af127
    • Julien Muchembled's avatar
      Use inotify-simple instead of inotifyx · 31142ddf
      Julien Muchembled authored
      There's little hope that it gets maintained because it contains a C extension whereas alternatives often use ctypes. In particular, it has no support for Python 3, and this is a blocker for us. At the beginning, [I though we were switching to pyinotify](0bb405fc): it is quite popular, and even used by fail2ban, but the code is ugly (big, crazy API, limited, and probably slow).
      
      I didn't really know inotify and it's disappointing to see that created files (CREATE+WRITE+CLOSE_WRITE) can't be distinguished from hard links (CREATE). Acting upon new inodes is a common scenario and in the first case, you want to wait CLOSE_WRITE or you would read a partially written file. What I mean is that inotify is often unreliable, unless you detect changes done by your own software (e.g. you can make sure that files aren't hard-linked) but then some other IPC is probably simpler.
      
      In any case, I open this MR because I haven't tested it. I only checked with pylint (hence the second commit).
      
      /cc @alain.takoudjou @gabriel @luke (from Git history)
      
      /reviewed-on nexedi/slapos!257
      31142ddf
  17. 14 Nov, 2017 9 commits
  18. 13 Nov, 2017 1 commit