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

Bug on windows #117

Closed
PrajwalM2212 opened this issue Nov 6, 2018 · 11 comments
Closed

Bug on windows #117

PrajwalM2212 opened this issue Nov 6, 2018 · 11 comments
Milestone

Comments

@PrajwalM2212
Copy link
Collaborator

PrajwalM2212 commented Nov 6, 2018

moban is reported to be giving incorrect outputs in netlify.toml file on windows. https://github.com/coala/coala/pull/5881/files#diff-5db06fd2327543bbb72119cd1e5761cf
It would be great if the problem is identified and fixed.

It is replacing

[build]
  publish = "docs/_build/html"
  command = "pip install -r docs-requirements.txt && export PYTHONPATH=$(pwd) && python setup.py docs"  


../../templates/docs/netlify.toml.jj2
@chfw
Copy link
Member

chfw commented Nov 6, 2018

Cannot see the change. I need to be able to reproduce it before looking at it.

@jayvdb
Copy link
Member

jayvdb commented Nov 13, 2018

The file mentioned in coala/coala .moban.yaml refers to a symlink, and windows replaces the file contents with garbage from the symlink during the sync

@chfw
Copy link
Member

chfw commented Dec 10, 2018

with windows unit tests running, a number of issues were found:

#142 , #141

@jayvdb jayvdb added this to the 0.4.0 milestone Jan 24, 2019
@jayvdb jayvdb pinned this issue Jan 24, 2019
@chfw
Copy link
Member

chfw commented Feb 16, 2019

@PrajwalM2212 , what is this problem again?

did you create a symlink file on windows? docs/netlify.toml link to ../../templates/docs/netlify.toml.jj2

and moban replace the target with junk.

@chfw
Copy link
Member

chfw commented Feb 16, 2019

blocked because no way to reproduce it.

@jayvdb
Copy link
Member

jayvdb commented Feb 18, 2019

Probably already fixed, if we have a test case which uses a symlink created on Unix, and that symlink test is active on Windows.

@chfw
Copy link
Member

chfw commented Feb 28, 2019

According to this post: https://unix.stackexchange.com/questions/63172/does-windows-recognize-linuxs-symbolic-links, it seems Windows itself could distinguish linux symbolic link.

Hence, I am not sure if os.path.islink would be able to find out this is linux symbolic link.

chfw added a commit that referenced this issue Feb 28, 2019
@chfw
Copy link
Member

chfw commented Mar 7, 2019

please reference #251 , linux symbolic link is seen as a text file with the actual linked file inside it. hence, we would need some special utility so that moban can detect it as linux symlink on windows.

screenshot 2019-03-07 at 21 46 17

chfw added a commit that referenced this issue Mar 8, 2019
* 🔬 let's start the test first. #117

* 🐛 fix import error

* 🔬 show true failures on windows

* 🐛fix samefile not available on windows. python-rope/ropevim#66

* 🐛 fix windows os path problem

* 💚 make windows ci work

* 💚 final touch on the windows ci failure

* 💄 beautify the code using black and isort

* 📰 show sub folder on windows

* 🐛 jinja2 does not windows style file path

* 💚 fix last failure...sigh..

* 📚 update change log
@ayan-b
Copy link
Member

ayan-b commented Mar 11, 2019

@chfw isn't this issue solved by #251 & #254?

@chfw
Copy link
Member

chfw commented Mar 11, 2019

Nope, they are not resolve it. Both issues were found when I was looking at this issue.

I do not think a unit test is possible for this issue either.

@chfw
Copy link
Member

chfw commented Mar 11, 2019

What I can do is to insert a warning note in our doc: saying: Never put a symblic link in your templates if you want to use it in windows.

@chfw chfw closed this as completed in 5781e3f Mar 17, 2019
@chfw chfw unpinned this issue Mar 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants