pimguilherme commented on issue #7099:
URL: 
https://github.com/apache/incubator-devlake/issues/7099#issuecomment-1998522356

   Cool, thanks for confirming @klesh!
   
   I have put together a small script to trigger the deadlock on an empty local 
devlake instance running 0.18.0 (it would probably work on newer instances with 
probably some small adjustments to the script)
   
   Here are the steps:
   - copy env.example to .env and set PIPELINE_MAX_PARALLEL=5 and 
ENCRYPTION_SECRET=secret
   - online devlake with `docker-compose -f docker-compose-dev.yml up`
   - once devlake is up, run the attached bash script: 
[deadlock-setup.txt](https://github.com/apache/incubator-devlake/files/14607955/deadlock-setup.txt)
     `bash deadlock-setup.txt` **(NOTE: you need jq, curl, gunzip and grep 
installed to run this script)**
     ( it will just do a series of calls to the API to set up 3 apache 
repositories/projects, druid, arrow-datafusion and incubator-devlake, set a 
smaller sync window and trigger the pipelines continuously until deadlock is 
met.. I have included a test user github token for public repos)
   - wait until deadlock is hit (it took about 7 minutes in my tests, according 
to attached logs)
   - 
[deadlock-example.txt](https://github.com/apache/incubator-devlake/files/14607972/deadlock-example.txt)
   - 
[deadlock-example2.txt](https://github.com/apache/incubator-devlake/files/14608116/deadlock-example2.txt)
   
   
   please let me know how it goes
   
   PS I also met this error somewhat consistently in the first pipelines, but i 
think we can focus on the deadlocks:
   
![image](https://github.com/apache/incubator-devlake/assets/1406885/8f6744fc-b4e6-4974-b4ca-695df3e842db)
   
   
   cheers!


-- 
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: dev-unsubscr...@devlake.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to