aroundabout opened a new issue, #520:
URL: https://github.com/apache/incubator-hugegraph-toolchain/issues/520

   ### Bug Type (问题类型)
   
   exception / error (异常报错)
   
   ### Before submit
   
   - [X] I had searched in the 
[issues](https://github.com/apache/hugegraph-toolchain/issues) and found no 
similar issues.
   
   ### Environment (环境信息)
   
   - Toolchain Version: latest
   - platform: github action (linux/arm64)
   
   
   ### Expected & Actual behavior (期望与实际表现)
   
   
https://github.com/hugegraph/actions/actions/runs/6194003062/job/16817665758#step:5:11833
   In repo [hugegraph/actions](https://github.com/hugegraph/actions), build 
docker images and push:
   
![image](https://github.com/apache/incubator-hugegraph-toolchain/assets/49650772/dac77992-78c5-459e-aa80-8fa9c10943fc)
   The reason is that `yarn install` will timeout in arm64 platform
   
![image](https://github.com/apache/incubator-hugegraph-toolchain/assets/49650772/8ca1bf0b-5ecd-47a7-88e7-8a9f1be8571f)
   
   The problem is still not solved until 2023.7 as the issue 
https://github.com/nodejs/docker-node/issues/1335#issuecomment-1652973487
   
   The way to solve the problem is to set the timeout like 
https://github.com/pomerium/pomerium/pull/3019/files
   
   In toolchain, we can change the line: 
   
https://github.com/apache/incubator-hugegraph-toolchain/blob/master/hugegraph-hubble/hubble-dist/pom.xml#L84
 
   to 
   ```
   timeout 120000 yarn install && yarn build || exit 1
   ```
   
   ### Vertex/Edge example (问题点 / 边数据举例)
   
   _No response_
   
   ### Schema [VertexLabel, EdgeLabel, IndexLabel] (元数据结构)
   
   _No response_


-- 
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