Skip to content

Pub Publish hangs #23362

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

Closed
DartBot opened this issue May 3, 2015 · 8 comments
Closed

Pub Publish hangs #23362

DartBot opened this issue May 3, 2015 · 8 comments
Labels
closed-cannot-reproduce Closed as we were unable to reproduce the reported issue

Comments

@DartBot
Copy link

DartBot commented May 3, 2015

This issue was originally filed by [email protected]


What steps will reproduce the problem?
1.cmd> pub -v publish
2.
3.

What is the expected output? What do you see instead?

find: > bin [: No such file or directory
FINE: Pub 1.10.0-dev.1.10
IO : Spawning "cmd /c ver" in C:\Dart\directory.
IO : Finished ver. Exit code 0.
    | stdout:
    | |
    | | Microsoft Windows [Versi-ón 6.3.9600]
    | Nothing output on stderr.
IO : Spawning "cmd /c git --version" in C:\Dart\directory.

And nothing more happens for ever. (directory is changed from the package directory).

What version of the product are you using? 1.10.0-dev.1.10

On what operating system? Windows 8.1

What browser (if applicable)?

Please provide any additional information below.

Previous publish were ok, in april 2015.

@floitschG
Copy link
Contributor

Added Area-Pub, Triaged labels.

@nex3
Copy link
Member

nex3 commented May 4, 2015

CC-ing Peter Ahe, who knows more than I do about Windows batch scripting.

I can see two things going wrong here. First, the "find" command in the batch script that starts pub is failing. I have no idea what this command is for or what the failure might do, but hopefully Peter can shed some light on it.

The other thing is that it looks like the "git" executable that we try to spawn never exits. I'm not sure why this would be, and I'm curious what happens if you run "git --version" manually in a terminal. It may be that your Git installation is corrupted somehow; try reinstalling it and see if that helps.


cc @peter-ahe-google.
Added NeedsInfo label.

@DartBot
Copy link
Author

DartBot commented May 4, 2015

This comment was originally written by [email protected]


Manually running git from the command line:

cmd> cmd /c git --version
git version 1.9.5.github.0

But, in previous pub publish, git was not defined in my path and publish worked. Now don't work in both cases.

@nex3
Copy link
Member

nex3 commented May 4, 2015

Have you tried reinstalling git?

@DartBot
Copy link
Author

DartBot commented May 5, 2015

This comment was originally written by [email protected]


git reinstalled, and nothing new.

I see, while publish is hanged, the process eat 12% CPU for ever.

@nex3
Copy link
Member

nex3 commented May 5, 2015

I'm sorry, but I have no idea why this would be happening :(. I can't imagine why the same git command would never terminate when run from within pub but work fine elsewhere. It'll probably work if you completely uninstall git, but short of that I don't know of a way for you to work around this.


Added CannotReproduce label.

@DartBot
Copy link
Author

DartBot commented May 5, 2015

This comment was originally written by [email protected]


I have removed git from the system and reinstalled it. Same result.
I removed git from the path (as was when it worked a month ago). So

CMD> git --version
'git' command don't exist

and the "cmd> pub -v publish" result is the same. Frozen.

I think the problem is not git related.
Also, a pub repair cache does not resolve the problem.

@DartBot DartBot added Type-Defect closed-cannot-reproduce Closed as we were unable to reproduce the reported issue labels May 5, 2015
@DartBot
Copy link
Author

DartBot commented Jun 4, 2015

This issue has been moved to dart-lang/pub#15.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-cannot-reproduce Closed as we were unable to reproduce the reported issue
Projects
None yet
Development

No branches or pull requests

4 participants