wouldd commented on issue #7826: URL: https://github.com/apache/incubator-devlake/issues/7826#issuecomment-2331967737
@klesh we do have a test environment for devlake, but we're already hitting jira api ratelimits, I'm not sure about duplicating a large project, what would this achieve that we can't do in our main system? I'm still not able to get useful logs out which I think is the helm chart does not define any persistent volume claims so those logs do not last through a restart. that's going to be the same in our dev environment. I will say that we're now on day 4 of me forcing only full refreshes ignoring the build in scheduler. and so far the only ongoing problem is that if you look at the graphs when a refresh kicks off the information vanishes until it gets far enough to have repopulated - I feel like that could be solved with some kind of transaction or temp table switching. I guess you don't normally run this in kubernetes despite the helm chart? -- 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
