Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: Add Debugging long mutagen startup time #6213

Merged
merged 1 commit into from
May 20, 2024

Conversation

rfay
Copy link
Member

@rfay rfay commented May 18, 2024

The Issue

At Drupalcon Portland 2024 someone was explaining how much they liked mutagen on their macOS amd64 machine, but their project could take 30 minutes to do the syncing.

I wasn't able to figure out working with them what the problem was. I eventually determined that we used to show the files syncing as they happened, but now we've replace it with dots, which makes debugging much harder.

How This PR Solves The Issue

Provide a technique for debugging.

Manual Testing Instructions

Follow the instructions. To create a dummy file if you need one, use dd if=/dev/zero of=dummyfile bs=1M count=5000

Release/Deployment Notes

@rfay rfay marked this pull request as ready for review May 18, 2024 19:40
@rfay rfay requested a review from a team as a code owner May 18, 2024 19:40
@rfay rfay requested a review from stasadev May 20, 2024 20:06
@rfay
Copy link
Member Author

rfay commented May 20, 2024

When mutagen is enabled we still say For details on sync status 'ddev mutagen st wind10 -l' as if that were useful. It shows errors if there are any, but it doesn't repeat., so you can't see the kind of issues considered in this PR.

It's possible we should give the full command here instead of showing that.

@rfay rfay merged commit 8bfad1c into ddev:master May 20, 2024
12 of 14 checks passed
@rfay rfay deleted the 20240518_improve_mutagen_debugging branch May 20, 2024 20:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant