Following error occurred on attempt to save files phpstorm

Почему я не могу сохранять данные в PhpStorm

Почему я не могу сохранять данные в PhpStorm?

«Unable to save settings : Failed to save settings . Please restart PhpStorm».

может быть вызвано множеством причин — блокировка файлов, неправильные конфигурации, сторонние плагины, . Пожалуйста, предоставьте свой idea.log (intellij-support.jetbrains.com/hc/en-us/articles/…)

У меня была такая же ошибка, и я решил ее следующим образом:

Ошибка возникает из-за того, что PHPStorm не имеет доступа к созданию файлов журнала в каталоге / var / www. Надеюсь, это тоже кому-то поможет

Примечательно, что файлы журнала PHPStorm сохраняются в папке .idea, которая по умолчанию может быть скрыта и в моем случае работает:

не применил запрошенные разрешения к скрытым папкам в моем текущем каталоге. Мне удалось решить проблему, только запустив chmod в папку .idea:

Источник

«Unable to save settings. Please restart PhpStorm» #1543

Machine

PhpStorm 2020.3 EAP
Build #PS-203.4203.36, built on October 1, 2020
PhpStorm EAP User
Expiration date: October 31, 2020
Runtime version: 11.0.8+10-b1098.1 x86_x64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.

Symfony plugin version: 0.21.202

macOS Catalina 10.15.7

Screen

The text was updated successfully, but these errors were encountered:

Eugene Morozov commented 2 hours ago
Yep, it seems to be caused by the plugin.

It seems that sometimes (sometimes: not all machines, not all PHPStorm versions) the plugin trys to create a file on c:/symfony2.xml (

But it is not allowed to create a file in the root of drive c (system-drive)

Maybe the Problem in my case is, that my Name is «Jörg» — with an german ö

And so the hole path is lost => it will create a file on root c:/

Maybe the Problem in my case is, that my Name is «Jörg» — with an german ö

I don’t think so, Linux user here and it tries to create /symfony2.xml which is not working.
My path is plain simple /home/user/development/customers/customername/projectname without any special characters.
Therefore I think we can rule UTF-8 problems out.

yes well. same here 🙁

Here is documentation part about Storage annotation

I assume that fix is simply removing slash.

i’ve compiled it and your patch seems to work. 👍

Can confirm the issue’s gone with @jensschulze ‘s patch in the latest PhpStorm 2020.3 EAP Build #PS-203.4818.52

Источник

Pycharm не может сохранять файлы

У меня Samsung T5 (внешний жесткий диск), и я использую Pycharm версии 2020.3.5 (сообщество). Моя проблема в том, что я не могу сохранить существующий файл. Я могу сохранить с помощью другой программы, например «Блокнот» и т. д.

Это первый раз, когда у проекта возникает эта проблема.

Мой журнал PyCharm:

попробуйте открыть pycham как администратор

Я пробовал, но то же самое

Отредактируйте вопрос, включив соответствующие части файла журнала. В вопросе недостаточно информации, чтобы понять, что вызывает ошибку.

Я предполагаю, что ваши каталоги перепутались.

Проверьте, в каком каталоге находится ваш файл, а затем выясните, в каком каталоге Python вы сейчас находитесь, используя метод getcwd ().

Cwd — это текущий рабочий каталог в Python. Это возвращает путь к текущему каталогу файлов python в виде строки.

Сравните два и внесите соответствующие изменения. Каталоги должны быть точно такими же.

Иногда незначительное изменение в каталоге может вывести из строя.

Другие вопросы по теме

Похожие вопросы

Находите ответы на сложные технические вопросы по программированию, с которыми сталкиваются инженеры по всему миру в своей ежедневной практике на сайте RedDeveloper.

Источник

Following error occurred on attempt to save files phpstorm

This forum is closed. Thank you for your contributions.

Asked by:

Question

So I was trying to modify my user properties under Computer Management > Local Users and Groups > Users > UserName > Properties > «Member Of» Tab. I am currently assigned to the «Administrators» group. However, if i attempt to change, add, or remove any other groups, this error pops up:

«One or more errors occurred while recording the group membership changes for user [User Name]»

Followed immediately by:

«The following error occurred while attempting to save the properties for user [USER NAME]

More data is available.»

I can’t do anything to get around this. I can’t remove groups, add groups (ANY of them), it just throws these two errors as soon as I try to apply the changes (or press OK). I generally don’t post in forums but I did my research and couldn’t find anything on this specific error or problem.

This problem is persistent when trying to modify ANY of the users listed under the «Users» folder in Computer Management .

Источник

Troubleshooting common deployment issues

This section provides the list of solutions and workarounds for common problems with deployments in PhpStorm.

Collecting PhpStorm deployment logs

If your issue is not addressed in this section, contact our support engineers. If asked to provide deployment logs, follow the instructions to collect them.

Collect deployment logs

Select Help | Configure Debug Log in the main menu.

In the Custom Debug Log Configuration dialog that opens, add the following lines depending on the issues you are experiencing:

Issues with deployment/synchronization: #com.jetbrains.plugins.webDeployment

Issues with issues with SSH/SFTP: #com.intellij.ssh

Click OK and reproduce the issue.

Locate the log file by selecting Help | Show Log in Explorer (for Windows and Linux) or Help | Show Log in Finder (for macOS).

If necessary, you can locate the log manually:

The most recent log file is named idea.log ; older files names end with a number, that is idea.log.1 , idea.log.2 , and so on. In most cases you need only the most recent one.

Attach the log file(s) to the issue or forum thread.

General troubleshooting

Deployment is slow or fails

Deployment can be a resource-intensive operation, especially if a project or a deployment server contains lots of directories and files. In the Settings dialog ( Ctrl+Alt+S ), navigate to Build, Execution, Deployment and explore the following configuration options, which can speed up deployment:

Exclude directories that are not needed from deployment (for example, images). This can be done from the Deployment: Excluded Paths Tab page.

On the Options page, clear the Overwrite up-to-date files to skip uploading files that don’t need to be uploaded.

Depending on the server, switching between active and passive transfer mode in the advanced FTP settings may help. This can be done by toggling Passive mode in the Deployment: Connection Tab for the server.

File transfer becomes unresponsive

This can happen in case PhpStorm tries to resolve an IPv4 host via IPv6. By default, PhpStorm only listens for incoming IPv4 connections. To make sure IPv6 is disabled, check the PhpStorm JVM options:

Select Help | Edit Custom VM Options from the main menu.

In the .vmoptions file that opens, make sure the -Djava.net.preferIPv4Stack=true line is present.

Otherwise, to enable IPv6 support, delete the -Djava.net.preferIPv4Stack=true line. In this case, make sure to add the IPv6 entry for your host to the /etc/hosts file.

Download/upload actions are not available

Download/upload actions may not be available because of a missing mapping. If a file or folder that you want to download is not configured in any mapping, PhpStorm will not download it. Mappings can be configured as described in the Map project folders to folders on the server and the URL addresses to access them.

For some actions, a default deployment server needs to be selected on the Deployment page of the Settings dialog.

Some folders are not deployed

A common cause for folders not being deployed is when they are explicitly excluded. To solve this, in the Remote host tool window right-click the given folder and select Remove Path From Excluded from the context menu. Once this is done, the folder will be deployed.

This can also be configured from the Deployment page of the Settings dialog ( Ctrl+Alt+S ). Open the Excluded Paths tab for the server and remove the excluded path. Note that both the source and the target folders should be checked. Folders can also be excluded by name on the Options page under Exclude items by name .

Sharing deployment configurations between projects

Deployment Servers are configured at the IDE level: they are available for all projects and can be shared between them.

Note that only the name and connection details (specified on the Deployment: Connection Tab tab) are shared between projects: mappings and excluded paths are project-specific and have to be configured separately. Using this approach, connection details have to be entered just once, while mappings and excluded paths can be configured per-project, sharing the connection details. This can be useful when projects share the same deployment server and use the same connection settings. If connection settings are different between projects, they have to be configured for every project separately.

If necessary, you can set a server to be visible in a single project by selecting the Visible only for this project checkbox on the Deployment: Connection Tab.

IDE settings do not allow me to configure mappings

The default new project settings are used to configure the default settings for new projects and do not affect the currently opened projects. To configure settings for the current project, use the Settings dialog Ctrl+Alt+S .

Can subfolders within the same folder have different deployment settings? Can a local folder be deployed to multiple locations?

When uploading folders and configuring mappings, note the following:

You can specify mappings for specific folders to different paths on the deployment server. This can be configured on the Deployment: Mappings Tab for the server.

You can exclude specific folders and files from being uploaded/downloaded. This can be configured on the Deployment: Excluded Paths Tab for the server.

You cannot upload the same folder (or subfolders) to different sites at once. A separate deployment configuration needs to be created for each of them and uploaded to each site one by one.

If this is what you want to do, we recommend automating the process with a capable tool. For example, Phing has an FTP task which can be used from PhpStorm. Within PhpStorm, you can use the Sync with Deployed. command and select from available deployment servers for every upload.

I cannot assign a keyboard shortcut to the Sync With Deployed to My Server menu item

It is not possible to assign a keyboard shortcut directly to the Sync With Deployed to command, only to the generic Sync with Deployed to. command, which will then display a popup menu with the list of servers. Refer to Configure keyboard shortcuts for details.

If you do wish to assign a keyboard shortcut to a specific deployment server, it is possible to record a Macro and assign a shortcut to it instead:

Select Edit | Macros | Start Macro Recording and start recording a Macro.

Select Tools | Deployment | Sync With Deployed to and close the sync window.

Stop recording the Macro by selecting Edit | Macros | Stop Macro Recording from the main menu.

Set the Macro name, for example Sync with .

Open in the Settings dialog ( Ctrl+Alt+S ), select Keymap and find the Macros node. From the context menu of the new sync Macro that was just recorded, select Add Keyboard Shortcut and provide the desired shortcut .

How do I deploy a database using PhpStorm?

There are a couple of ways to deploy a database using PhpStorm:

Make use of the integrated database tools and run the required DDL and SQL statements manually.

Can I run a script or executable on my files before the upload occurs?

Things like minifying CSS, optimizing images, encoding PHP files using IonCube, and so on are actions that you may want to execute before an upload happens. The best approach to do this is run them not when the upload is started, but when the files are changed, by using File Watchers in PhpStorm. When the time comes to upload them to a deployment server, upload the processed files instead.

Note that the Skip external changes checkbox must be cleared on the Options page for this to work.

Sometimes files are not uploaded automatically

By default, PhpStorm uploads the files if they are changed by some external processes (VCS, transpilers, and so on). If the files are not uploaded, make sure that the Upload changed files automatically to the default server on the Options page is set to Always and the Skip external changes checkbox is cleared.

Can I run pre- and post-deployment actions?

It’s possible using Run/Debug configurations. You can create a fake Run/Debug Configuration, or a Run/Debug configuration that should be the last step, and add the required steps under Before launch .

As an alternative, we recommend using Phing or any other build system to execute complex sequences of steps.

FTP troubleshooting

FTP issue: Invalid descendent file name «http:»

When a deployment server has been configured or when using the Test Connection button in the project settings, the Invalid descendent file name «http:» error is displayed. Note that all file names with a colon : in the name will be considered invalid.

This can happen if a file containing http: in its name exists in the project. The library that PhpStorm uses to connect to FTP (Apache Commons VFS) cannot read the contents of a folder containing such a file, which causes the operation to fail. The only solution is to remove the file containing http: in its name from the project.

PhpStorm seems to connect to the server but can’t list files or perform upload

This may be because the deployment server requires a so-called passive FTP connection. To set this mode, select the Passive mode checkbox in the Deployment: Connection Tab for the selected server.

Deploying files when changing branches using Git checkout

There are a couple of ways to go about deploying files when switching between branches using Git checkout:

One way is to configure deployments to always upload files and external changes. To do this, on the Options page, set Upload changed files automatically to the default server to Always and clear the Skip external changes checkbox. Note that this will upload all files to the server when switching branches.

Use git-ftp. It performs minimal uploads and is also able to mirror file and directory removals.

FTPS troubleshooting

PhpStorm cannot establish connection with an FTPS server

If an FTPS server is configured to use TLS 1.0 / TLS 1.1, PhpStorm cannot connect to it and the following error message is displayed:

This happens because PhpStorm supports connecting to servers via TLS 1.2 and later. Using TLS 1.0 and TLS 1.1 is not supported, since these protocols are deprecated and considered insecure.

As a workaround, you can enable TLS 1.0 / TLS 1.1 support by adjusting the PhpStorm JVM options. Note that using outdated protocols can and will introduce security risks to your environment and consider it to be a last resort option.

Create a file custom.java.security with the following contents:

In the .vmoptions file that opens, add the following line:

Источник

Почему я не могу сохранять данные в PhpStorm

Почему я не могу сохранять данные в PhpStorm?

«Unable to save settings : Failed to save settings . Please restart PhpStorm».

может быть вызвано множеством причин — блокировка файлов, неправильные конфигурации, сторонние плагины, . Пожалуйста, предоставьте свой idea.log (intellij-support.jetbrains.com/hc/en-us/articles/…)

У меня была такая же ошибка, и я решил ее следующим образом:

Ошибка возникает из-за того, что PHPStorm не имеет доступа к созданию файлов журнала в каталоге / var / www. Надеюсь, это тоже кому-то поможет

Примечательно, что файлы журнала PHPStorm сохраняются в папке .idea, которая по умолчанию может быть скрыта и в моем случае работает:

не применил запрошенные разрешения к скрытым папкам в моем текущем каталоге. Мне удалось решить проблему, только запустив chmod в папку .idea:

Источник

«Unable to save settings. Please restart PhpStorm» #1543

Comments

prgTW commented Oct 3, 2020 •

Machine

PhpStorm 2020.3 EAP
Build #PS-203.4203.36, built on October 1, 2020
PhpStorm EAP User
Expiration date: October 31, 2020
Runtime version: 11.0.8+10-b1098.1 x86_x64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.

Symfony plugin version: 0.21.202

macOS Catalina 10.15.7

Screen

The text was updated successfully, but these errors were encountered:

dbalabka commented Oct 4, 2020

prgTW commented Oct 5, 2020

Eugene Morozov commented 2 hours ago
Yep, it seems to be caused by the plugin.

computerundsound commented Oct 13, 2020

It seems that sometimes (sometimes: not all machines, not all PHPStorm versions) the plugin trys to create a file on c:/symfony2.xml (

But it is not allowed to create a file in the root of drive c (system-drive)

Maybe the Problem in my case is, that my Name is «Jörg» — with an german ö

And so the hole path is lost => it will create a file on root c:/

discordier commented Oct 13, 2020

Maybe the Problem in my case is, that my Name is «Jörg» — with an german ö

I don’t think so, Linux user here and it tries to create /symfony2.xml which is not working.
My path is plain simple /home/user/development/customers/customername/projectname without any special characters.
Therefore I think we can rule UTF-8 problems out.

elkuku commented Oct 14, 2020

yes well. same here 🙁

jensschulze commented Oct 15, 2020

dbalabka commented Oct 15, 2020

Here is documentation part about Storage annotation

dbalabka commented Oct 15, 2020

I assume that fix is simply removing slash.

Blog404DE commented Oct 15, 2020

i’ve compiled it and your patch seems to work. 👍

mattsches commented Oct 16, 2020

Can confirm the issue’s gone with @jensschulze ‘s patch in the latest PhpStorm 2020.3 EAP Build #PS-203.4818.52

Источник

Pycharm не может сохранять файлы

У меня Samsung T5 (внешний жесткий диск), и я использую Pycharm версии 2020.3.5 (сообщество). Моя проблема в том, что я не могу сохранить существующий файл. Я могу сохранить с помощью другой программы, например «Блокнот» и т. д.

Это первый раз, когда у проекта возникает эта проблема.

Мой журнал PyCharm:

попробуйте открыть pycham как администратор

Я пробовал, но то же самое

Отредактируйте вопрос, включив соответствующие части файла журнала. В вопросе недостаточно информации, чтобы понять, что вызывает ошибку.

Я предполагаю, что ваши каталоги перепутались.

Проверьте, в каком каталоге находится ваш файл, а затем выясните, в каком каталоге Python вы сейчас находитесь, используя метод getcwd ().

Cwd — это текущий рабочий каталог в Python. Это возвращает путь к текущему каталогу файлов python в виде строки.

Сравните два и внесите соответствующие изменения. Каталоги должны быть точно такими же.

Иногда незначительное изменение в каталоге может вывести из строя.

Другие вопросы по теме

Похожие вопросы

Находите ответы на сложные технические вопросы по программированию, с которыми сталкиваются инженеры по всему миру в своей ежедневной практике на сайте RedDeveloper.

Источник

System Settings

Configure the general behavior of PhpStorm.

Confirm before exiting the IDE

Show a dialog with a confirmation when you attempt to close PhpStorm.

When closing a tool window with a running process

Select what to do with the running process:

Terminate process : stop the process entirely.

Disconnect : leave the process running but disconnect from it.

Ask : show a dialog with actions to choose from.

Project

Reopen projects on startup

Open all projects that were open when you closed PhpStorm last time.

Open project in

Select where you want to open projects:

New window : open every projects in a separate window.

Current window : close the current projects and open the new one in the same window.

Ask : show a dialog with actions to choose from.

Default project directory

Specify the default location for projects. PhpStorm suggests this directory when you create a new project or want to open an existing project.

Autosave

Save files if the IDE is idle for

Save all modified files at regular time intervals.

Save files when switching to a different application or a built-in terminal

Save all modified files when you switch from PhpStorm to a different application.

You cannot disable autosave completely by disabling these options.

Back up files before saving

Before saving the file, create a backup. If the save operation is successful, PhpStorm deletes the backup. If not, it restores the contents of the original file from backup. This behavior is known as «safe write», and it prevents losing your file in case of a faulty save operation.

Synchronize external changes when switching to the IDE window or opening an editor tab

Reload externally changed files when you switch to PhpStorm from a different application, or when you switch to the corresponding editor tabs.

Источник

Options

Use this page to specify additional configuration settings for uploading and downloading project files to and from local and remote servers. For more details about various server access configurations, see Deploy your application.

The options specified in this dialog apply to all defined server configurations regardless of the server type (local, remote) and the data transfer protocol used. Protocol-specific options for server configurations of the type FTP/SFTP/FTPS/WebDAV are defined on the Connection tab of the Deployment page of the Settings/Preferences dialog.

Exclude items by name

In this field, specify patterns for the names of files and folders that you do not need to be deployed.

Use semicolons ; as delimiters, asterisks * to match zero or more characters, and question marks ? to match a single character.

For example, if you have a folder stylesheets with three files style.css , style1.css , and style2.scss , then style* excludes the entire folder, style?.css excludes style.css , and style?.* excludes style1.css and style2.scss .

The exclusion is applied recursively. This means that if a matching folder has subfolders, the contents of these subfolders are not deployed either.

Use this list to specify how much detailed logging you need to have. The available options are:

Errors only : select this option to have the log show only errors occurred during upload.

Brief : select this option to have all events reflected in the log but without details.

Details : select this option to have more details on the upload shown in the log, for example, full file paths.

Overwrite up-to-date files

If this checkbox is selected, all files will be uploaded no matter whether they have been changed since the previous upload or not.

Otherwise, if this checkbox is not selected, only the files that have been changed since the previous upload will be uploaded.

Preserve files timestamps

Select this checkbox to prevent resetting timestamps of files on upload.

Delete target items when source ones do not exist (when transferring from Project view or Remote Host view)

If this checkbox is selected, any file in the destination directory will be removed if the file with this name is not involved in the current upload.

This option is applicable when synchronization if performed from the Project tool window or from the Remote Host tool window.

Create empty directories

Select this checkbox to have an empty directory on the server created automatically if a new local directory has been created in your project since the last upload in the source folder.

Prompt when overwriting or deleting local items

Select this checkbox to have PhpStorm prompt for confirmation before overwriting or deleting local items for synchronization during download.

Confirm uploading files

Select this checkbox to have PhpStorm prompt for confirmation before uploading local items to a remote host.

Upload changed files automatically to the default server

From this list, choose when you want PhpStorm to automatically upload a file to the default server or server group. The available options are:

Always : choose this option to have a file uploaded upon each save, no matter automatic or explicitly invoked.

On explicit save action : choose this option to have a file uploaded after save only if this save was invoked manually by choosing File | Save All or pressing Ctrl+S .

Never : choose this option to suppress automatic upload.

The default server configuration or a server group is appointed on the Deployment page by selecting the desired item in the list and clicking the Use as Default toolbar button .

Skip external changes

Select this checkbox to exclude local changes that were made using a third-party tool (a VCS, a script, and so on) from automatic upload.

The checkbox is available only when the Always or On explicit save action option is selected in the Upload changed files automatically to the default server list.

Delete remote files when local are deleted

Select this checkbox to have PhpStorm automatically delete remote files during automatic uploads in case the local ones are deleted. The checkbox is available only when the Always or On explicit save action option is selected in the Upload changed files automatically to the default server list.

Note that this option serves as an extra safety measure and may result in unwanted files remaining on the remote server. As an example, consider a local file Foo.php , which is renamed to Bar.php . Since renaming a file is technically indistinguishable from deleting the file and creating a new one, the following will happen after automatic upload:

If the option is enabled, the remote server will only contain Bar.php .

If the option is disabled, the remote server will contain both Foo.php and Bar.php after automatic upload. You will probably need to delete Foo.php manually afterwards.

Preserve original file permissions

If enabled, PhpStorm will preserve the original local files’ permissions when uploading files on remote hosts over FTP/FTPS.

The option is only available for macOS and Linux.

Override default permissions on files

Select this checkbox to change the default permissions assigned to uploaded files on remote hosts. Click Browse to open the Files Default Permissions dialog, where you can manage access to uploaded files on remote hosts by assigning permissions.

Override default permissions on folders

Select this checkbox to change the default permissions assigned to uploaded folders on remote hosts. Click Browse to open the Folders Default Permissions dialog, where you can manage access to uploaded folders on remote hosts by assigning permissions.

Warn when uploading over newer file

Use this list to define the version-control policy to apply when uploading files to remote hosts. Depending on this choice, PhpStorm either checks whether any changes have been made to the corresponding files on the remote host since you downloaded them or just overwrites the remote files.

No choose this option to have the file on the remote host overwritten with its local copy silently. All the changes made to the remote file since your last synchronization will be abandoned.

Compare timestamp & size if you choose this option, PhpStorm performs two checks:

Compares the sizes of the local and remote files.

Compares the remote file timestamp set at the moment of the last synchronization with the current remote file timestamp.

If the files differ in their size or the remote file timestamps differ, PhpStorm opens a Difference Viewer for Files, where you can explore and integrate the differences.

This type of check depends on the timezone setting. If the timezone setting on your local machine is different from that on the remote host, the check may be successful even though the file versions actually differ.

Compare content when this option is chosen, PhpStorm compares the content of the local and remote files. If any diversions are detected, PhpStorm opens a Difference Viewer for Files, where you can explore and integrate the differences.

Notify of remote changes

Select this checkbox to receive notifications about changes on the remote host. The checkbox is available only when the Compare timestamp and size or Compare content option is selected in the Warn when uploading over newer file list.

Источник

2020-10-03 21:13:56,373 [2030320]   WARN - mponents.impl.stores.StoreUtil - Save settings failed
java.io.IOException: Cannot create file '/symfony2.xml'
	at com.intellij.openapi.vfs.impl.local.LocalFileSystemBase.createChildFile(LocalFileSystemBase.java:337)
	at com.intellij.openapi.vfs.newvfs.persistent.PersistentFSImpl.createChildFile(PersistentFSImpl.java:498)
	at com.intellij.openapi.vfs.newvfs.impl.VirtualFileSystemEntry.createChildData(VirtualFileSystemEntry.java:275)
	at com.intellij.configurationStore.StorageUtilKt.getOrCreateVirtualFile(storageUtil.kt:147)
	at com.intellij.configurationStore.FileBasedStorageKt.writeFile(FileBasedStorage.kt:269)
	at com.intellij.configurationStore.FileBasedStorage$FileSaveSession.saveLocally(FileBasedStorage.kt:115)
	at com.intellij.configurationStore.XmlElementStorage$XmlElementStorageSaveSession$SaveExecutor.save(XmlElementStorage.kt:164)
	at com.intellij.configurationStore.SaveExecutorKt.executeSave(SaveExecutor.kt:92)
	at com.intellij.configurationStore.SaveExecutorKt.saveSessions(SaveExecutor.kt:86)
	at com.intellij.configurationStore.ProjectSaveSessionProducerManager$saveWithAdditionalSaveSessions$$inlined$withEdtContext$1$lambda$1.compute(actions.kt:61)
	at com.intellij.openapi.application.impl.ApplicationImpl.lambda$runWriteAction$16(ApplicationImpl.java:1009)
	at com.intellij.openapi.application.impl.ApplicationImpl.runWriteActionWithClass(ApplicationImpl.java:988)
	at com.intellij.openapi.application.impl.ApplicationImpl.runWriteAction(ApplicationImpl.java:1009)
	at com.intellij.configurationStore.ProjectSaveSessionProducerManager$saveWithAdditionalSaveSessions$$inlined$withEdtContext$1.invokeSuspend(ComponentStoreImpl.kt:709)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:56)
	at com.intellij.openapi.application.constraints.BaseConstrainedExecution$Companion$scheduleWithinConstraints$1.invoke(BaseConstrainedExecution.kt:68)
	at com.intellij.openapi.application.constraints.BaseConstrainedExecution$Companion.scheduleWithinConstraints(BaseConstrainedExecution.kt:71)
	at com.intellij.openapi.application.constraints.BaseConstrainedExecution.scheduleWithinConstraints(BaseConstrainedExecution.kt:38)
	at com.intellij.openapi.application.impl.BaseExpirableExecutorMixinImpl.access$scheduleWithinConstraints$s1153900543(BaseExpirableExecutorMixinImpl.kt:12)
	at com.intellij.openapi.application.impl.BaseExpirableExecutorMixinImpl$scheduleWithinConstraints$$inlined$Runnable$1.run(Runnable.kt:19)
	at com.intellij.openapi.application.TransactionGuardImpl.runWithWritingAllowed(TransactionGuardImpl.java:216)
	at com.intellij.openapi.application.TransactionGuardImpl.access$200(TransactionGuardImpl.java:24)
	at com.intellij.openapi.application.TransactionGuardImpl$2.run(TransactionGuardImpl.java:199)
	at com.intellij.openapi.application.impl.ApplicationImpl.runIntendedWriteActionOnCurrentThread(ApplicationImpl.java:822)
	at com.intellij.openapi.application.impl.ApplicationImpl.lambda$invokeLater$4(ApplicationImpl.java:323)
	at com.intellij.openapi.application.impl.FlushQueue.doRun(FlushQueue.java:85)
	at com.intellij.openapi.application.impl.FlushQueue.runNextEvent(FlushQueue.java:134)
	at com.intellij.openapi.application.impl.FlushQueue.flushNow(FlushQueue.java:47)
	at com.intellij.openapi.application.impl.FlushQueue$FlushNow.run(FlushQueue.java:190)
	at java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:313)
	at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:776)
	at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:727)
	at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
	at java.base/java.security.AccessController.doPrivileged(Native Method)
	at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
	at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:746)
	at com.intellij.ide.IdeEventQueue.defaultDispatchEvent(IdeEventQueue.java:973)
	at com.intellij.ide.IdeEventQueue._dispatchEvent(IdeEventQueue.java:840)
	at com.intellij.ide.IdeEventQueue.lambda$dispatchEvent$8(IdeEventQueue.java:451)
	at com.intellij.openapi.progress.impl.CoreProgressManager.computePrioritized(CoreProgressManager.java:773)
	at com.intellij.ide.IdeEventQueue.lambda$dispatchEvent$9(IdeEventQueue.java:450)
	at com.intellij.openapi.application.impl.ApplicationImpl.runIntendedWriteActionOnCurrentThread(ApplicationImpl.java:822)
	at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:498)
	at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
	at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
	at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
	at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
	at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
	at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)