tree 0f0db024a0531af60b9ec74c416cb3b5b4d7b8ee
parent dd67774e106c902110b17fc1d6f23937f70a8fe7
author RickyMa <rickyma@tencent.com> 1710992120 +0800
committer GitHub <noreply@github.com> 1710992120 +0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsFcBAABCAAQBQJl+6r4CRC1aQ7uu5UhlAAAmFoQAEEEZchVQkPIxpC8BwACXd1a
 syjqgKxkRU/ClOl85EI5Y3SQq2Bs6005XslRsN7QKn/UTfM4jUHrGlOVe9z82L6B
 ClW25PiSzfRDRljaCVXBwiYzSMDtkpII0LJDBRlbtAwL+hrZ+ewRSpoqVN8wqk6Q
 RDcAIVGjFpgD5ZKPkKYBOCevB7fZhf7NGpC5xlwf+Y6+196fghNZx3B8cprN4RNS
 Tt4LrVwnnByT2ySRKJNF4IUe0gFm49X1DAY966EWTn28ZOTWbnX+Vvs5tEkQpvjw
 9hWx2uF0oTRNgNI/DLk7oY65NrbVoy7w4x4fGHaMhkCMn0/DOpPC2f6W4ztNsPR7
 x5d3sSynPpO/A+5TcN9WuHWR1YHiyQz3HAsCPiAXTsw0Zx3n8ar0QB/OVd5Q3rwj
 0ADtrVaDce7t6PeAYfvwm6/BxvjmLc6xA6XkNYKrqvmnaaKB/0zUCHWbC6naG4N+
 HnEo25xWhvMDVyFMyHjTybH8r+72ovMG+/wXADeN2UfKfK+ZGvXqgD6l4fVjFouY
 NV5WMG983/SJhIj0wgyJM2puD2AMtNToy08NgaTM+aqYgXA12id35P9UIQok7Zf1
 qFnOi5rMnOCm58M68gDo89Yz6gIrHKeFbl2bbwMX/2cIG6Q0RSyGXJ61zYsVrFdt
 9DQIjiB6o+xziAcabcIJ
 =Zug5
 -----END PGP SIGNATURE-----
 

[MINOR] refactor: Calling lock() method outside try block to avoid unnecessary errors (#1590)

### What changes were proposed in this pull request?

Calling `lock()` method outside try block to avoid unnecessary errors

### Why are the changes needed?

In general, the `lock()` method should be placed outside the try block. The reason is that if the `lock()` method throws an exception, it indicates that the lock was not acquired, so there is no need to attempt to release it in the finally block. If the `lock()` method is placed within the try block and it throws an exception, the finally block will still be executed and attempt to release a lock that was never acquired, leading to errors.

### Does this PR introduce _any_ user-facing change?

No.

### How was this patch tested?

Existing UTs.