-
Notifications
You must be signed in to change notification settings - Fork 924
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
bit export command gets stuck in terminal window #2268
Labels
Comments
@odedre Thanks. |
I was able to reproduce it, started fixing it, will complete the fix tomorrow. |
davidfirst
added a commit
that referenced
this issue
Feb 6, 2020
…d is completed by adding an error handler. Also, changed some "logger.debug" to "logger.silly". Also, support configuring the logger level by running "bit config set log_level <level>". Also, limit the number of concurrent files write to 100
davidfirst
added a commit
that referenced
this issue
Feb 7, 2020
…d is completed by adding an error handler. Also, changed some "logger.debug" to "logger.silly". Also, support configuring the logger level by running "bit config set log_level <level>". Also, limit the number of concurrent files write to 100 (#2310)
GiladShoham
added a commit
that referenced
this issue
Feb 9, 2020
* fix #2211 and #2308, when exporting to multiple scopes, make sure to not export their dependencies when these dependencies themselves are not export pending (#2309) * resolve #2268, prevent logger from holding the terminal once a command is completed by adding an error handler. Also, changed some "logger.debug" to "logger.silly". Also, support configuring the logger level by running "bit config set log_level <level>". Also, limit the number of concurrent files write to 100 (#2310) * fix typo in the BitId README * fix "bit status" and "bit tag" when new components require each other by module paths (#2313) Co-authored-by: David First <david@bit.dev>
davidfirst
added a commit
that referenced
this issue
Feb 17, 2020
* fix #2211 and #2308, when exporting to multiple scopes, make sure to not export their dependencies when these dependencies themselves are not export pending (#2309) * bump dev version * resolve #2268, prevent logger from holding the terminal once a command is completed by adding an error handler. Also, changed some "logger.debug" to "logger.silly". Also, support configuring the logger level by running "bit config set log_level <level>". Also, limit the number of concurrent files write to 100 (#2310) * fix typo in the BitId README * fix "bit status" and "bit tag" when new components require each other by module paths (#2313) * Fix e2e-tests to avoid code execution inside "describe" blocks (#2329) * move all Helper instantiation from describe to before. * fix defaultScope tests, remove code that was entered by mistake in the describe block to before block. * delete javascript-hook.e2e file, the tests there were written long ago, marked as "skip" and not relevant anymore. * support import/require statements of module paths when it has no scope-name (e.g. "@bit/button") (#2331) * resolve part of #2341, enable "--all" flag when "--all-versions" is used and vice versa, to enable re-exporting a component after deleting it (#2345) * Fixed broken link leading to quick start guide (#2338) * fix dynamic dist reference from package.json (#1808) when isolating via capsule (#2348) * remove .only from extension tests Co-authored-by: Erik <arebokert@hotmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I exported 95 components at the same time. I see a list of the exported components but it seems that even though the process finished(I ran bit status on a separate tab), bit doesn't return and I have to
cmd + c
to be able to continue in this tab.Expected Behavior
bit should finish running.
Specifications
The text was updated successfully, but these errors were encountered: