hingu-8103 opened a new issue, #795:
URL: https://github.com/apache/hugegraph-toolchain/issues/795

   ### Bug Type (问题类型)
   
   others (please comment below)
   
   ### Before submit
   
   - [x] I had searched in the 
[issues](https://github.com/apache/hugegraph-toolchain/issues) and found no 
similar issues.
   
   ### Environment (环境信息)
   
   - Server Version: v1.x.x
   - Toolchain Version: v1.x.x
   - Data Size:  xx vertices, xx edges <!-- (like 1000W 点, 9000W 边) -->
   
   
   ### Expected & Actual behavior (期望与实际表现)
   
   ## Expected behaviour 
   When calling `HugeClientBuilder.configTimeout(0)`, the timeout should be 
reset to the default timeout value of 20 seconds, which is stored internally as 
20000 milliseconds.
   
   ## Actual behaviour 
   `configTimeout(0)` incorrectly applies the `SECOND` conversion again to 
`DEFAULT_TIMEOUT`, even though `DEFAULT_TIMEOUT` is already defined in 
milliseconds.
   
   As a result, the timeout becomes:
   20000 * 1000 = 20000000 ms
   which equals 20000 seconds, instead of the intended 20 seconds.
   
   ## Repro 
   Add the below unit test in `HugeClientBuilderTest.java` to reproduce the bug 
   ```
   @Test
   public void testReproDefaultTimeoutBug() {
       HugeClientBuilder builder =
               new HugeClientBuilder("http://127.0.0.1:8080";, "DEFAULT", 
"hugegraph");
   
       builder.configTimeout(0);
   
       System.out.println("timeout=" + builder.timeout());
   }
   ```
   
   ### Vertex/Edge example (问题点 / 边数据举例)
   
   ```javascript
   
   ```
   
   ### Schema [VertexLabel, EdgeLabel, IndexLabel] (元数据结构)
   
   ```javascript
   
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to