-
Notifications
You must be signed in to change notification settings - Fork 176
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
mbed import and mbed add broken on cygwin #578
Comments
@bmcdonnell-ionx It looks like you hit an odd corner case there. Did you try the workarounds mentioned in #299 after it was closed? |
Oh, I hadn't realized that #299 is a "won't fix (for now)". The workarounds didn't work for this issue, though. I just tried the work-around by @mukymuk:
But it made no difference. [EDIT: If it matters, the line in
...but I do have |
Thanks for looking at that. You can find the executable for Mbed CLI with |
Why do you ask? |
I did not ask. I was just trying to help you find your |
Oh. The path to I just upgraded to mbed-cli v1.2.2, and I see that I do have |
@bmcdonnell-ionx They seemed to indicate that adding |
As you mentoined, cygwin is not supported at this time. You could use |
There is no |
@bmcdonnell-ionx That's why I'm doubtful. |
Is there a place where a list of things broken on cygwin is kept? |
The very bottom of |
I discovered that mention between when I opened this issue and now. Is there a list somewhere else? On #299, @screamerbg said
"PR" means, "problem report", right? Is that the same or different from these issue reports here on GitHub?
|
@bmcdonnell-ionx Nope, PR means Pull Request. Issues are different, though the numbers are unique between Issues and PRs. |
Thanks for clarifying. Is there a good place to maintain the list of things broken on cygwin? |
They are closed when the original authors problem is resolved, which in the case of #299, was a documentation addition.
You can fork mbed-cli, checkout a feature branch |
@bmcdonnell-ionx We could maintain a list in that section in the readme I mentioned. |
I'm not sure how much sense forking makes, since I don't currently have the intent to fix this issue myself. |
@bmcdonnell-ionx If you're contributing at all, forking makes sense. |
Thus far, I'm only filing issue reports, not making any direct code contributions. I'm concerned about visibility. I don't want to maintain a list of cygwin-related issues for me. It should be something that others can find relatively easily, and contribute to. |
@bmcdonnell-ionx Then please make edits to the Readme. I think that's the best place for such a list. |
Or did you mean that this issue can stay open? Having this here and open is good enough, IMO. I just thought you were going to close it like the other one... |
@bmcdonnell-ionx I just installed the latest Cygwin 64bit v2.10 from https://cygwin.com/install.html. Importing with Mbed CLI works just fine. From within Cygwin64 Terminal
Everything works fine except for the output buffering coming from Python itself. It can be disabled by running Windows Command Prompt:
Again, everything works as expected and there are no output buffering issues. Note that I'm using Mbed CLI 1.5.1 |
And here's Mbed CLI import to a non-home dir inside the Cygwin environment (using Windows Prompt)
Everything worked just fine, including progress bars (the Python buffered issue is present only in the standard Cygwin Terminal app) |
I just did the same, and updated Mbed CLI to v1.5.1, but the problem persists for me.
|
I recently encountered an issue regarding git and cygwin on a Windows machine due to permissions. It eventually boiled down to cygwin's version of Might be worth checking which instance of git is being used in your environments. Could you both run the following and post the output? On the Windows Command prompt: |
Looks like Cygwin is using its own Windows Command prompt:
Cygwin:
|
Are you sure you have the latest verison of mbed-cli installed from pip? In your log I found this print:
I can't find that log line anywhere in the source, so not sure where that's coming from. Assuming that's all ok, I can also see its trying to run the following:
If you run that in your current terminal, does that command fail? If it is then it may be an issue of not using Cygwin formatted paths. I admit I don't use Cygwin so this is pretty much the limit of my debugging tips. |
Ah, looks like you might be using this branch? #642 (log line is here: https://github.com/ARMmbed/mbed-cli/pull/642/files#diff-dad37ed6e3ea3a963df6ff7090c2562fR1184) Try uninstalling that branch first and reinstalling from pip to see if the issue is resolved. |
That should do the trick |
It hangs, and does not uninstall.
Should pip still be able to uninstall what was installed from source (i.e. not via pip)? |
Yeah it definitely should be able to uninstall. I'm afraid I don't know how to help on this one, this problem seems pretty specific to your environment. You may try uninstalling it from outside of cygwin, but that may cause more issues. But I think its probably safe to say the uninstall issue is not a problem with mbed-cli specifically. |
I uninstalled Mbed CLI by deleting its files from I also uninstalled Cygwin, and reinstalled by running The problem persists. I included Python 2 & 3 in my Cygwin install.
What does Know anyone who might have any ideas? |
@bmcdonnell-ionx Apologies for the late reply. I've somehow missed this.
This is on Windows 10, where Python has been installed as a native application. I'm not sure how your python is under |
How did you set up your cygwin box so python appears as a native cygwin app?
I installed python from the Cygwin setup-x86_64.exe, like any other package.
I do also have python installed natively on Windows, though my Cygwin apparently isn't using that.
|
Internal Jira reference: https://jira.arm.com/browse/MBOCUSTRIA-70 |
@here - I am observing the same problem too. Has there been any more updates on this? |
Hi all, I'm sorry but cygwin is not a supported platform for the mbed CLI tools; although it seems that some users have managed to achieve some level of success here. We'd welcome PRs from the community that help support this platform in future. |
In my experience so far, most mbed-cli commands work as well in Cygwin as they do from the Windows command line. The import and add commands don't work, though, as shown below. (I tried a few different ways, to see if there was a workaround.)
Looks like it's just an issue with the way the output directory path is generated.
Issue #299 also relates to paths on cygwin, so be careful not to introduce a regression there when fixing this.
Originally posted on mbed forum: mbed-cli on cygwin.
The text was updated successfully, but these errors were encountered: