Synchronise files not working in 2017.2 EAP 172.2465.7
When synchronising the files to the remote host, the diff window is shown correctly but trying to synchronise files from this window does not work and results in the following message:
Synchronization completed in less than a minute: 8 files are skipped by user
PhpStorm 2017.2 EAP
Build #PS-172.2465.7, built on May 24, 2017
PhpStorm EAP User
Expiration date: June 23, 2017
JRE: 1.8.0_152-release-855-b1 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0
Reverting to the last non EAP version works fine.
Please sign in to leave a comment.
Hello,
Is there anything in File | Settings | Build, Execution, Deployment | Deployment > your server > Excluded paths?
Most of my projects have excluded paths but they do not apply to the files that are being skipped. Also excluded files are not listed in the Diff window. However, as test, I have removed all excluded paths from one of the projects but the problem persists.
I have noticed that the problem only seems to apply to files being transferred TO the remote server not files transferred from the remote server.
Could you please attach 2 screenshots of Tools > Deployment > Options taken from 2017.1 and from 2017.2 EAP?
As requested:
Same problem.
PhpStorm 2017.2 EAP
Build #PS-172.2465.7, built on May 24, 2017
PhpStorm EAP User
Expiration date: June 23, 2017
JRE: 1.8.0_152-release-855-b1 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 4.1.39-56-default
Can you reproduce this in another (preferably new) project?
Reproducible with new (empty) project and new deployment configuration (SFTP and FTP).
Same problem here, synchronization says "completed successfully", but nothing is synchronized with my remote server. Can't use this app in these conditions.
Same problem here !!
PhpStorm 2017.2 EAP
Build #PS-172.2465.7, built on May 24, 2017
PhpStorm EAP User
Expiration date: June 23, 2017
JRE: 1.8.0_152-release-855-b1 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0
Thank you for reporting, here's the bug: https://youtrack.jetbrains.com/issue/WI-36686