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

Mutagen enabled globally: "Could not write settings file: Mutagen sync session 'junk' does not exist" #4162

Closed
1 task done
rfay opened this issue Sep 1, 2022 · 3 comments

Comments

@rfay
Copy link
Member

rfay commented Sep 1, 2022

Is there an existing issue for this?

  • I have searched the existing issues

Run a Diagnostic and Paste Link Here

No response

Current Behavior

If you create an empty directory named junk, and then ddev config --auto there with mutagen enabled globally, you get

Could not write settings file: Mutagen sync session 'junk' does not exist

Of course...

  • With an empty directory (detected project type'php') it shouldn't be creating a settings file anyway
  • During ddev config it doesn't care about mutagen... and it's never started yet.

Expected Behavior

Shouldn't see that.

Steps To Reproduce

No response

Anything else?

No response

@rpkoller
Copy link
Collaborator

rpkoller commented Sep 1, 2022

i can confirm with ddev config --auto i also get the same mutagen sync session does not exist message. but in the line before there is another detail to note: Found a php codebase at /Users/rkoller/Sites/junk but the directory is empty so how it was able to find an actually php codebase? that was odd. i've then tried the same with manual installations:

TEST1

  1. used default name.
  2. used web as doctroot and confirmed its creation3.
  3. chose project type drupal9.
  4. output:
Project Type [backdrop, drupal10, drupal6, drupal7, drupal8, drupal9, laravel, magento, magento2, php, shopware6, typo3, wordpress] (php): drupal9
Ensuring write permissions for testingers 
No settings.php file exists, creating one 
Existing settings.php file includes settings.ddev.php 
Configuration complete. You may now run 'ddev start'. 

TEST2

  1. used default name.
  2. used web as doctroot and confirmed its creation3.
  3. chose project type php.
  4. output:
Project Type [backdrop, drupal10, drupal6, drupal7, drupal8, drupal9, laravel, magento, magento2, php, shopware6, typo3, wordpress] (php): 
Could not write settings file: Mutagen sync session 'lala' does not exist 
Configuration complete. You may now run 'ddev start'. 

but the general question is why is mutagen required or a thing at all without the project being started yet? because i suppose in your test as well as in my three rounds the project was not started yet with ddev start?

p.s. forgot to add yes i have mutagen enabled globally.

@rfay
Copy link
Member Author

rfay commented Sep 1, 2022

Any un-recognized codebase is reported as a "php" codebase, which is the default type. Doesn't have to be any code. This is the same report that's always been there for an unrecognized codebase.

@rpkoller
Copy link
Collaborator

rpkoller commented Sep 1, 2022

ahhhh ok. that just looked odd for an empty directory getting a message that a php codebase was found ^^ but that explains that detail. thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants