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

Error trying to add github project #162

Open
hernanat opened this issue Sep 16, 2021 · 6 comments
Open

Error trying to add github project #162

hernanat opened this issue Sep 16, 2021 · 6 comments

Comments

@hernanat
Copy link

I've been trying to add my project And get this error:

Screen Shot 2021-09-15 at 7 32 22 PM

Response:

Screen Shot 2021-09-15 at 7 33 25 PM

Using git scheme:

Screen Shot 2021-09-15 at 7 36 55 PM

Response:

Screen Shot 2021-09-15 at 7 37 29 PM

After my last attempt, trying to visit https://rubydoc.info/github/hernanat/extended_range showed a 503 error, but usually it just shows this:

Screen Shot 2021-09-15 at 7 38 39 PM

I've also encountered some SQL Lite disk corruption errors.

@lsegal
Copy link
Collaborator

lsegal commented Sep 16, 2021

Have you tried running yard on the project locally? I'm seeing errors, which leads me to believe this is a legitimate error coming from rubydoc.info, and if it's a bug it would be in YARD itself.

@hernanat
Copy link
Author

Have you tried running yard on the project locally? I'm seeing errors, which leads me to believe this is a legitimate error coming from rubydoc.info, and if it's a bug it would be in YARD itself.

not yet, but funnily enough if I use this link https://rubydoc.info/gems/extended_range

The docs load. Not sure what the issue is, I can get the project running and have a look tomorrow if you don't have any ideas.

@hernanat
Copy link
Author

oh sorry, I misinterpreted what you asked. Yes, I have ran yard locally.

@hernanat
Copy link
Author

hernanat commented Sep 16, 2021

here is the output from YARD:

[warn]: Load Order / Name Resolution Problem on Range:
-
Something is trying to call mixins on object Range before it has been recognized.
This error usually means that you need to modify the order in which you parse files
so that Range is parsed before methods or other objects attempt to access it.
-
YARD will recover from this error and continue to parse but you *may* have problems
with your generated documentation. You should probably fix this.
-

[error]: Unhandled exception in YARD::Handlers::Ruby::MixinHandler:
  in `lib/extended_range.rb`:7:

	7: Range.include CoreExtensions::Range::Operations

[warn]: Load Order / Name Resolution Problem on Range:
-
Something is trying to call mixins on object Range before it has been recognized.
This error usually means that you need to modify the order in which you parse files
so that Range is parsed before methods or other objects attempt to access it.
-
YARD will recover from this error and continue to parse but you *may* have problems
with your generated documentation. You should probably fix this.
-

[error]: Unhandled exception in YARD::Handlers::Ruby::MixinHandler:
  in `lib/extended_range.rb`:8:

	8: Range.include CoreExtensions::Range::Checks

Files:           3
Modules:         6 (    6 undocumented)
Classes:         0 (    0 undocumented)
Constants:       1 (    1 undocumented)
Attributes:      0 (    0 undocumented)
Methods:         9 (    1 undocumented)
 50.00% documented

It does say that there is an error, but it also says that it would continue on so I'm not sure if that would be the problem.

The docs load fine locally (and on the link above)

@hernanat
Copy link
Author

hernanat commented Sep 16, 2021

I added the following .yardopts file:

--exclude lib/extended_range.rb

which silenced the errors but had no impact on the issue above. All this file does is take care of the monkey patching of Range so it is fine to exclude, but doesn't seem to be the issue :(

@lsegal
Copy link
Collaborator

lsegal commented Sep 17, 2021

Seems like there was an issue with the recent Ruby 3.0 upgrade that was temporarily causing GitHub metadata fetches to fail. That's been resolved and adding the repo is working again.

Thanks for reporting!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants