Bit export fails due to auth issue #2211
Comments
|
hello, If the description above doesn't describe your situation / solve your issue, please re-open. @Tallyb I think it's worth writing a few words about what happens when running |
|
Thanks for the info @GiladShoham Question though, what happens when I have updated multiple components from different scopes, what argument do I need to add to export all to their collections? |
|
Also, why is trying to export to the Bootstrap collection when I have not tagged changes in it because it is not my component. |
The implicit bit export (without any args) are designed for this exactly. so you can run bit export and everything goes back to where it belongs.
If you didn't tag them, it's really odd. it might be a bug. |
|
Yes, I did not tag them, it's a bug. I will run it again tomorrow and re-open this issue with all the details. |
|
@AlexanderKaran |
|
Hi @GiladShoham So I had a who load of updates and I ran:
I did not tag the third-party component from Bootstrap at all I then run:
And I get the auth error even though I did not change the Bootstrap component: Here is my terminal print out: Here is my bit status: `alexanderkaran@AlexandersMBP2 cc_school_web % bit status ` |
|
I have managed to export most by exporting each component one by one. However, now I am left with a few that won't export because apparently the ID is wrong even though I am copying what comes from bit status. Also bit export still has the auth issue. |
|
@AleksandarSavic95 Thanks for reporting this. |
|
Any update on this? It really slowing dev down having to export components one by one? |
|
@AlexanderKaran , Can you think of a way for me to reproduce the issue? Until this is fixed, you can use wildcards to avoid exporting them one by one. |
|
@davidfirst Thanks for the wild card update, maybe we can update the docs so they are a little clearer with these things. react-bootstrap comes from here: https://bit.dev/react-bootstrap/react-bootstrap/container We never update it, change it or anything else. It's installed via NPM and used in a few of our Bit components. Will run those commands when I get to the office. |
|
Also, I ran:
And it states: zsh: no matches found: ui-components/* When there are this many components to export like this: (use "bit export <remote_scope> to push these components to a remote scope") Everyone starting with cc- is ui-components/* |
|
@AlexanderKaran add quotes: This is because zsh is trying to interpret the asterisk. |
|
Thank you @Tallyb |
|
@AlexanderKaran Did what @Tallyb suggested worked as expected? |
|
@GiladShoham Yes it did, export each collection one by one causes no errors, only on export all do I get the error |
|
@AlexanderKaran , if you're still experiencing this issue, please run the following |
|
Sure, will do this today @davidfirst |
|
Email sent, sorry for the slow reply some other priorities took over |
|
Good news! I'm able to reproduce the issue. Working on a fix now. |
|
The issue has been fixed by the PR above. |
* 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>
* 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>
When tag multiple components and then running
bit exportI get an error if any of my components being exported include a bit package from the bit library itself.
error: permission to scope hub.bit.dev:react-bootstrap.react-bootstrap was denied see troubleshooting at https://docs.bit.dev/docs/setup-authentication#authentication-issuesA few of the components that are causing issues include a component or two from this library
https://bit.dev/react-bootstrap/react-bootstrap
When exporting and tagging components one by one I do not get the issue, only when doing multiple exports, which really slows things down.
Specifications
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: