This is the ninth day of my participation in the First Challenge 2022. For details: First Challenge 2022.

preface

At present, our Intranet code is managed by TortoiseSVN, which is usually used quite well without any major problems.

However, today encountered a more intractable problem, here to make a record, in order to facilitate their own and need a friend in the future encountered this kind of problem when a reference.

The phenomenon of

The specific error symptoms are shown in the figure below:

why

The steps leading to the above phenomenon are as follows:

  1. Updates clicked from the outermost directory are kept in check for a long time due to the large number of files;
  2. Click the Unupdate button;
  3. The TortoiseSVN process can be disabled from the TortoiseSVN task manager.

After the above steps, this phenomenon occurs when the directory is updated again, and the error is the same regardless of which level of directory it is updated from.

Try a

Manually clear the fault according to the information displayed in the error symptom. The error shown in the following figure is displayed:

No matter from which level of directory start, are the same error, it seems that this way is blocked, can only find another way.

Failed to run the WC DB work queue associate with XXX Failed to start the WC DB work queue associated with XXX.

try

Sqlite3 is recommended to be used for database cleaning. The database is located in the.svn folder of the local directory selected at the time, named as Wc.db, as shown in the following figure:

. I forgot to take the screenshot of the content in SVN at that time, and borrowed the one I found on the Internet:

Jokingly, this database file name WC has made me have a bad association.

Note:. SVN folder is usually hidden folder, need to set display.

Therefore, I downloaded the sqlite3 installation package from the Internet and applied for importing it into the Intranet according to the online tutorial.

While waiting for the import, it occurred to me that not only sqlite3 can modify database files (.db), but Navicat Premium can also parse database files installed on my Intranet machine, so why not give it a try? Because before only use it to connect to the database, did not react.

The final solution

Try Navicat Premium to open the wc.db file and it will parse normally.

The next steps are as follows:

  1. findWORK_QUEUETable;
  2. Right-click the table and choose Clear.
  3. savewc.db

Replace the file with the same name under.svn with the modified wc.db, and then execute the cleanup command again. After waiting for more than 10 seconds, the following information is displayed:

The final solution is as follows:

You can see that the SVN is cleared successfully.

conclusion

From today’s event, I can conclude as follows:

  1. During SVN update, do not click to cancel the update.
  2. If you do click cancel, wait for the SVN to cancel and do not forcibly shut down the SVN process.
  3. Information on the Internet is generally only suitable for reference and is too homogenized;
  4. I’m sure there are more ways to fix today’s error than the one I wrote.

~

Thanks for reading!

~

Learn interesting knowledge, meet interesting friends, shape interesting soul!

Hello everyone, I am the author of “programming Samadhi”, I am king Yi, my public account is “programming Samadhi”, welcome to pay attention, I hope you can give me more advice!