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

Dependencies.io troubleshooting #1921

Closed
dependencies bot opened this issue Sep 30, 2017 · 142 comments
Closed

Dependencies.io troubleshooting #1921

dependencies bot opened this issue Sep 30, 2017 · 142 comments

Comments

@dependencies
Copy link

dependencies bot commented Sep 30, 2017

We're opening this issue to inform you about problems with your dependencies.io configuration or build failures.

We'll add a comment here when we see problems. You can close this issue when
you have things resolved -- we'll open it back up if we detect new problems.

Helpful links:

Note: To help keep your repo as clean as possible, this is the only issue
that we're going to open and comment on. Feel free to delete the comments
that are made as you resolve them, if you want to keep this issue short and tidy.

@Hypnosphi Hypnosphi self-assigned this Sep 30, 2017
@storybookjs storybookjs deleted a comment from dependencies bot Sep 30, 2017
@Hypnosphi
Copy link
Member

@davegaeddert is there a chance that lerna collector is bound to a specific lerna version?

https://app.dependencies.io/projects/github/storybooks/storybook

lerna info version 2.2.0
lerna ERR! EMISMATCH Lerna major version mismatch: The current version of lerna is 2.2.0, but the Lerna version in `lerna.json` is 2.3.1. You can either run `lerna init` again or install `lerna@2.3.1`.

@Hypnosphi Hypnosphi reopened this Oct 4, 2017
@Hypnosphi
Copy link
Member

I believe it should use local lerna version with yarn lerna <command> instead of global one

@davegaeddert
Copy link
Contributor

@Hypnosphi good point. We pushed an update to both the collector and actor (decided to add the repo's node_modules/.bin to the path instead). I tested it on a fork and it ran fine, but let me know if you have any more trouble. Thanks!

@storybookjs storybookjs deleted a comment from dependencies bot Oct 4, 2017
@storybookjs storybookjs deleted a comment from dependencies bot Oct 4, 2017
@storybookjs storybookjs deleted a comment from dependencies bot Oct 4, 2017
@dependencies
Copy link
Author

dependencies bot commented Oct 5, 2017

Build # 11 on master (f355399) failed!

Errors

  • One or more collectors failed

@dependencies
Copy link
Author

dependencies bot commented Oct 7, 2017

Build # 15 on master (81152d5) failed!

Errors

  • One or more actors failed

@Hypnosphi
Copy link
Member

@dependencies
Copy link
Author

dependencies bot commented Oct 8, 2017

Build # 16 on master (3036b2c) failed!

Errors

  • One or more actors failed

@davegaeddert
Copy link
Contributor

@Hypnosphi I'll take a look.

@dependencies
Copy link
Author

dependencies bot commented Oct 9, 2017

Build # 17 on master (3036b2c) failed!

Errors

  • One or more actors failed

@dependencies
Copy link
Author

dependencies bot commented Oct 9, 2017

Build # 18 on master (1730834) failed!

Errors

  • One or more collectors failed

@davegaeddert
Copy link
Contributor

davegaeddert commented Oct 9, 2017

@Hypnosphi I think the actor should be working now. The collector failed because it looks like somewhere in the last couple commits some babel/vue dependencies were introduced but not added to yarn.lock? Our collector quits if it notices uncommited yarn.lock changes so that you don't get a bunch of pull requests that all include those (unrelated) changes with them.

The issue with the actor might need a little more thought, but should work for how you're using it right now since your bootstrap command is just yarn. The problem is that you have to install the local lerna before you can use it...otherwise you get that version mismatch between what the local repo asks for and what our current global version is. Is that why your bootstrap command no longer uses lerna bootstrap? Did I see that you (or someone on storybook) is also involved in lerna development? I was reading some issues about global vs local questions -- what is the general way that you use lerna in development? Do you have a version of lerna installed globally on your machine? Or local? Or both?

Sorry for all the questions -- if anybody has an expertise on this, comments are welcome! We just want to make sure that anything we build around lerna works the way that people expect. From what I can tell, these questions on the collector/actor are probably similar to what you've had to deal with in development.

@Hypnosphi
Copy link
Member

Hypnosphi commented Oct 9, 2017

some babel/vue dependencies were introduced but not added to yarn.lock

Will fix that.
@ndelangen btw such cases can be prevented with #1980

Is that why your bootstrap command no longer uses lerna bootstrap

The reason is that we find it convenient to use a single command to install both root and package s dependencies

what is the general way that you use lerna in development

I just always use yarn lerna <command>

@dependencies
Copy link
Author

dependencies bot commented Oct 17, 2017

Build # 27 on master (c2f605c) failed!

Errors

  • One or more actors failed

@Hypnosphi
Copy link
Member

@davegaeddert I failed to find out what's the error here: https://app.dependencies.io/projects/github/storybooks/storybook/builds/27

@davegaeddert
Copy link
Contributor

@Hypnosphi looks like it just timed out (20 min. limit). Still need to get that error messaging to reflect that so it's more obvious.

@nickbalestra
Copy link

Hello! Not sure if of any help, but I'm having similar issues with dependencies.io (not withlerna actor that I still need to try).
I found that omitting the settings kinda solved a similar error.

@dependencies
Copy link
Author

dependencies bot commented Nov 6, 2017

Build # 51 on master (725ac4b) failed!

Errors

  • One or more actors failed

@dependencies
Copy link
Author

dependencies bot commented Nov 9, 2017

Build # 57 on master (f48fbd3) failed!

Errors

  • One or more actors failed

@Hypnosphi
Copy link
Member

@davegaeddert is it React release that breaks the build? https://app.dependencies.io/projects/github/storybooks/storybook/builds/57

Btw, what does this "actions" column mean, exactly?

@dependencies
Copy link
Author

dependencies bot commented Nov 10, 2017

Build # 58 on master (16cb94d) failed!

Errors

  • One or more actors failed

@dependencies
Copy link
Author

dependencies bot commented Nov 10, 2017

Build # 59 on master (50dc2f1) failed!

Errors

  • One or more actors failed

@davegaeddert
Copy link
Contributor

@Hypnosphi I'll take a look. The actions column is just saying how many actors ran (on that build) for that particular dependency. Admittedly, the UI needs some updating now that we have a better feel for how things work and how people use it.

@dependencies
Copy link
Author

dependencies bot commented Jun 9, 2018

Build # 351 on master (4a250fb) failed!

Errors

  • One or more actors failed

@stale
Copy link

stale bot commented Jun 30, 2018

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks!

@stale stale bot added the inactive label Jun 30, 2018
@dependencies
Copy link
Author

dependencies bot commented Jul 4, 2018

Build # 357 on master (5f279c1) failed!

Errors

  • One or more actors failed

@dependencies
Copy link
Author

dependencies bot commented Jul 9, 2018

Build # 358 on master (f49c444) failed!

Errors

  • One or more actors failed

@dependencies
Copy link
Author

dependencies bot commented Aug 6, 2018

Build # 362 on master (b2b275b) failed!

Errors

  • One or more collectors failed

@ndelangen ndelangen reopened this Aug 8, 2018
@stale stale bot removed the inactive label Aug 8, 2018
@ndelangen
Copy link
Member

ndelangen commented Aug 8, 2018

@Hypnosphi How do I find the problem? I do not know how to fix it..

@Hypnosphi
Copy link
Member

@davegaeddert Hi! Looks like it tries to upgrade all the babel packages (and maybe others too, like eslint) from stable to beta: https://v1.dependencies.io/projects/github/Hypnosphi/storybook

Is there a chance that L.Y.Y started mistakenly matching 7.0.0-tag for 6.0.0 as current version?

@davegaeddert
Copy link
Contributor

Hi! @Hypnosphi did you mean to link to Hypnosphi/storybook instead of storybooks/storybook? Looks like they have different configs, just want to make sure we're on the same page first.

@dependencies
Copy link
Author

dependencies bot commented Aug 13, 2018

Build # 363 on master (4121d26) failed!

Errors

  • One or more collectors failed

@dependencies
Copy link
Author

dependencies bot commented Aug 20, 2018

Build # 364 on master (b7054f3) failed!

Errors

  • One or more collectors failed

@Hypnosphi
Copy link
Member

Hypnosphi commented Aug 20, 2018

@davegaeddert sorry, my bad. Looks like some bad node version is used then:
https://v1.dependencies.io/projects/github/storybooks/storybook

The engine "node" is incompatible with this module. Expected version "^6.14.0 || ^8.10.0 || >=9.10.0"

@davegaeddert
Copy link
Contributor

@Hypnosphi ok thanks. I'll see if we can get that fixed, but we're no longer actively maintaining the v1 components. I know we talked about this a bit before, but do you know what would be holding you back from switching to v2 at this point? What's the biggest outstanding question there?

@Hypnosphi
Copy link
Member

@dependencies
Copy link
Author

dependencies bot commented Aug 27, 2018

Build # 365 on master (9d2756c) failed!

Errors

  • One or more collectors failed

@dependencies
Copy link
Author

dependencies bot commented Sep 3, 2018

Build # 366 on master (a2a2a91) failed!

Errors

  • One or more collectors failed

@dependencies
Copy link
Author

dependencies bot commented Sep 10, 2018

Build # 367 on master (bd9c701) failed!

Errors

  • One or more collectors failed

@dependencies
Copy link
Author

dependencies bot commented Sep 17, 2018

Build # 368 on master (c14b250) failed!

Errors

  • One or more collectors failed

@dependencies
Copy link
Author

dependencies bot commented Sep 24, 2018

Build # 369 on master (dd1953c) failed!

Errors

  • One or more collectors failed

@dependencies
Copy link
Author

dependencies bot commented Oct 1, 2018

Build # 370 on master (621a4ed) failed!

Errors

  • One or more collectors failed

@dependencies
Copy link
Author

dependencies bot commented Oct 8, 2018

Build # 371 on master (f7ccb82) failed!

Errors

  • One or more collectors failed

@dependencies
Copy link
Author

dependencies bot commented Oct 8, 2018

Build # 372 on master (f7ccb82) failed!

Errors

  • One or more collectors failed

@dependencies
Copy link
Author

dependencies bot commented Oct 8, 2018

Build # 373 on master (be3ab29) failed!

Errors

  • One or more collectors failed

@dependencies
Copy link
Author

dependencies bot commented Oct 10, 2018

Build # 374 on master (80d6b99) failed!

Errors

  • One or more collectors failed

@stale
Copy link

stale bot commented Oct 31, 2018

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks!

@stale stale bot added the inactive label Oct 31, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants