Forum » Support and Bug Reports »

Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

martin

Please attach a full log file showing the problem (using the latest version of WinSCP).

To generate log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you may email it to me. You will find my address (if you log in) in my forum profile. Please include link back to this topic in your email. Also note in this topic that you have emailed the log.
mikestreety

Ah you genius!

Seems when I upload, the timestamp is that of my computer, but compiling it uses the server time.

Interesting - thanks!
martin

Ok. It can be a problem with timestamps. Check that, after your upload files with WinsCP, the timestamps are not in the past (earlier then previous build).
mikestreety

Ah sorry - realised there are some crossed wires.

sass --watch is run in a separate terminal application (putty) connected to the same server.
martin

Re: Sass Compiling with --watch

An environment when command is run from WinSCP is different than your regular terminal environment. Particularly, some environment variable are removed. Also the session does not have TTY, what among other means that different startup scripts are called. All this can have impact on your build scripts.
mikestreety

Sass Compiling with --watch

Hello,

This is a bit of a random one, and i'm not sure which side this lies - because of that i'm making both parties aware in the hope we can get somewhere.

WinSCP version 5.2.5 (but also happens on older ones)

I am using WinSCP to transfer files to a local server running CentOS via SFTP (also happens over SCP).

In a terminal window, I am running 

sass --watch


- this compiles sass files into css when they are updated. If you don't know about sass, its a CSS Prepocessor.

After uploading the file the first time, the watch script detects that there is a change and compiles the sass, however, every time after that it simply detects and change and doesn't compile.

The reason I am posting this here is because it only happens with WinSCP. Using the same protocol on the same sever with the same files but with a different SFTP/SCP program, the files compile correctly on every upload.

I apologise for the vagueness of the post - being quite bespoke, I struggled to fulfill all the criteria in the link.

There is my Sass bug report on Github.

Documentation

Support

Associations

Follow Us