#158 inappropriate making in background directories

[Lee Worden]

I browse a background session directory. Let's be specific:
http://yushan.mcmaster.ca/wonder_development/index.php/Special:GetProjectFile?jobid=178981131&project=Gut&filename=.
I am trying to track down a problem so I change the final argument to filename=..

Turns out WW/PE doesn't allow me to use .. to escape from the project directory, but what does happen is "Make succeeded but did not create ..". Which (a) seems wrong, since it's not like .. doesn't exist, and (b) shouldn't happen, because we shouldn't be trying to make additional things in background sessions.

Worse, what I was trying to do was look at the 'script' file in the parent directory, which documents what make command was used in the background job; and when I get there, browsing from a command line, I find:
nice --adjustment=10 [various stuff omitted] make [various stuff omitted] '..' >'[path]/...make.log' 2>&1

It's overwritten the script file! What's going on?

[Lee Worden]

see also:
slow and unintelligible background jobs
https://sourceforge.net/tracker/index.php?func=detail&aid=3476800&group_id=366300&atid=1527385

it might make sense to look at both of these at once, since they're in
somewhat the same parts of the code.

[Lee Worden]

This doesn't happen any more. I just retested it and it gives a more sensible error: "invalid filename: ..".

I don't know whether it messes up the .script file (though I'll be surprised if it does), because unfortunately there's another bug there, which I'll file separately.

There's also a problem that there's no user-friendly way to browse the base directory of the background job, the one that contains the project directories. They don't have a '..' link and if you try to use '..' manually you get shot down. The way to browse the base directory is to remove the project name from the URL and leave only the job number and the filename '.'.