Menu

#1 Error during cleanup

R0.5
open
nobody
Startup (1)
4
2007-03-29
2007-03-19
ltsllc
No

Occasionally, you will get a dialog that says that there was an error during repository cleanup, with the options to continue anyway or stop the program.

Discussion

  • ltsllc

    ltsllc - 2007-03-19
     
  • ltsllc

    ltsllc - 2007-03-19
    • milestone: --> R0.5
     
  • ltsllc

    ltsllc - 2007-03-19
    • priority: 5 --> 6
     
  • ltsllc

    ltsllc - 2007-03-19
    • labels: --> Startup
    • summary: Startup: error during cleanup --> Error during cleanup
     
  • ltsllc

    ltsllc - 2007-03-20

    Logged In: YES
    user_id=1621042
    Originator: YES

    Having trouble getting this to happen again >.< Modified the message so you can print out a stack trace.

    It may not be fixed, but if it happens again, it should be easier to figure out what is going on.

     
  • ltsllc

    ltsllc - 2007-03-21

    Logged In: YES
    user_id=1621042
    Originator: YES

    A further development: after a bit of time, this bug appeared again. I have a feeling it has to do with incompatible repository files.

    At any rate, here is a stack trace from the problem:

    com.lts.application.ApplicationException: The file, C:\Documents and Settings\user\Timelord\repos\Timelord29641.bak, is neither a directory nor a regular file.
    at com.lts.application.Application.cleanupRepositories(Application.java:3013)
    at com.lts.application.Application.initializeApplication(Application.java:2371)
    at com.lts.pest.Pest.initializeApplication(Pest.java:264)
    at com.lts.application.Application.startApplication(Application.java:1049)
    at com.lts.timelord.Timelord.main(Timelord.java:208)

     
  • ltsllc

    ltsllc - 2007-03-21

    Logged In: YES
    user_id=1621042
    Originator: YES

    The file mentioned in the stack trace, C:\Documents and
    Settings\user\Timelord\repos\Timelord29641.bak, does not appear to exist.

     
  • ltsllc

    ltsllc - 2007-03-29

    Logged In: YES
    user_id=1621042
    Originator: YES

    For no good reason, I'm pretty sure this problem is about repository version conflicts --- trying to use a newer version of Timelord with files from an older version. This is because I have not seen the error in a while.

    At any rate, decreasing the priority until it becomes an issue again.

     
  • ltsllc

    ltsllc - 2007-03-29
    • priority: 6 --> 4
     

Log in to post a comment.

MongoDB Logo MongoDB