Skip to content
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

FileEntity 'path' property has wrong separator in Windows. #678

Closed
pcstout opened this issue Apr 23, 2019 · 4 comments
Closed

FileEntity 'path' property has wrong separator in Windows. #678

pcstout opened this issue Apr 23, 2019 · 4 comments
Labels

Comments

@pcstout
Copy link

pcstout commented Apr 23, 2019

Bug Report

Operating system

Windows 10 Pro

Client version

1.9.2

Description of the problem

On Windows (win32) the path separator in the FileEntity is wrong.

Repro. Steps:

  • Upload a file and look at the returned object's path property.

Expected behavior

  • Path separator is \ and the character casing is correct.
    Correct path: C:\\Users\\John\\AppData\\Local\\Temp\\tmpi7kpbq0s\\data\\core\\core_file_ace2.csv

Actual behavior

  • Path separator is / and character casing is incorrect.
    Incorrect path: c:/users/john/appdata/local/temp/tmpi7kpbq0s/data/core/core_file_ace2.csv
@kimyen
Copy link
Contributor

kimyen commented Apr 24, 2019

Hello @pcstout ,

Thank you for reporting this issue. I notice that you put down Ubuntu Linux 18.04 for Operating System. How do you run into problems with the Windows file path in a Linux environment?
Can you tell us more about how this problem impact your work? so that we can better prioritize this issue?

@pcstout
Copy link
Author

pcstout commented Apr 24, 2019

@kimyen Sorry about that, it was on Windows 10 Pro. I updated the description.

@kimyen
Copy link
Contributor

kimyen commented Apr 24, 2019

Thank you! I created https://sagebionetworks.jira.com/browse/SYNPY-959 to track the engineering progress. If this issue impact your downstream work (e.g., using the path to access the file), please let us know.

@pcstout
Copy link
Author

pcstout commented Apr 24, 2019

Thanks @kimyen.
This is impacting one of our projects but we have some workarounds. Would be nice to get this fixed sooner than later though.

@kimyen kimyen added the bug label May 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants