-
Couldn't load subscription status.
- Fork 79
BUG: Fix problem with default basedir #1439
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
Conversation
If the base data directory was not set, a default one would be selected, by using '..' to refer to a directory below, which in turn would inconsistently flag users as lacking permissions: ``` QiitaPetAuthorizationError: User demo@microbio.me is not authorized to access /Users/yoshikivazquezbaeza/.virtualenvs/qiita-0.2.0-rc1/lib/python2.7/site-packages/qiita_db/support_files/test_data/job/1_summarize_taxa_through_plots.py_output_dir/taxa_summary_plots/bar_charts.html ``` Although the paths were the same, this is verified through string matching thus 'lol/foo/../jk' and 'lol/jk' would not match (see example structure below) even though they refer to the same folder: lol/ ├── foo │ └── file.txt ├── jk └── plel
|
👍 once test pass |
|
After chatting offline with @antgonza, it seems like we will also need a DB patch. The reason is that the settings table might already have a path of this form The only way to look for this would be to query for the |
|
We will not need to modify anything in the DB besides the settings table... and given that if we change the path in the DB it will point to the same folder, it will not hurt. |
|
@ElDeveloper, I think this is touching on the broader issue of path On Mon, Aug 24, 2015 at 8:35 PM, Jose Navas notifications@github.com
|
|
@wasade, yeah that's what I meant. |
|
For some reason it works in an IPython session but when I call |
|
Ok, this should be ready for review, thanks for the help @josenavas! |
|
👍 |
BUG: Fix problem with default basedir
If the base data directory was not set, a default one would be selected,
by using '..' to refer to a directory below, which in turn would
inconsistently flag users as lacking permissions:
Although the paths were the same, this is verified through string
matching thus 'lol/foo/../jk' and 'lol/jk' would not match (see example
structure below) even though they refer to the same folder:
lol/
├── foo
│ └── file.txt
├── jk
└── plel