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

Failing when trying to run the: Example 1: Valuing Oracle's Common Equity, Based on 4 Quarters of History and 2 Quarters of Forecasts #12

Open
mbkupfer opened this issue Jan 28, 2016 · 2 comments

Comments

@mbkupfer
Copy link

This is the message I get.

Warning: failed to load entity
        wrong number of arguments (2 for 1)
        ["/myhomedirectory/.rvm/gems/ruby-2.1.1/gems/sec_query-1.1.0/lib/sec_query/entity.rb:37:in `find'"
         "/myhomedirectory/.rvm/gems/ruby-2.1.1/gems/finmodeling-0.2.1/lib/finmodeling/company.rb:44:in `find'"
         "./examples/show_reports.rb:119:in `<main>'"]
@jimlindstrom
Copy link
Owner

Hi @mbkupfer. I'm not actively supporting this project any more. If you are interested in taking it over, I'd be happy to help ramp you up. Or if you dig into this issue and have any suggestions, I would welcome a pull request.

@mbkupfer
Copy link
Author

HI @jimlindstrom, while I'd like to take over such a project, I'm still
just starting out with writing programs and don't think I'd have the
experience yet to take it over.
Especially since I'm still having issues just trying to understand how it
is all pieced together.

Maybe what would be great is if you could ramp me up with just the part
that pulls filing information into workable formats. Then I could take over
something more manageable. I did try looking into the gems you use in
Finmodeling but don't quite understand yet how you are connecting the xblr,
sec_query and the Edgar gem. To make matters more difficult, all the gems
seem to have little to no documentation.

On Thu, Jan 28, 2016, 6:14 AM Jim Lindstrom notifications@github.com
wrote:

Hi @mbkupfer https://github.com/mbkupfer. I'm not actively supporting
this project any more. If you are interested in taking it over, I'd be
happy to help ramp you up. Or if you dig into this issue and have any
suggestions, I would welcome a pull request.


Reply to this email directly or view it on GitHub
#12 (comment)
.

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