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

Connection.past_scans() fails #220

Closed
nbirnel opened this issue Apr 27, 2016 · 4 comments
Closed

Connection.past_scans() fails #220

nbirnel opened this issue Apr 27, 2016 · 4 comments
Labels

Comments

@nbirnel
Copy link
Contributor

nbirnel commented Apr 27, 2016

/usr/local/lib/ruby/gems/2.2.0/gems/nexpose-3.3.1/lib/nexpose/ajax.rb:166:in `request': NexposeAPI: GET request to /ajax/user_pref_set.txml?name=global-completed-scans.rows&value= failed. request body:  (Nexpose::APIError)
        from /usr/local/lib/ruby/gems/2.2.0/gems/nexpose-3.3.1/lib/nexpose/ajax.rb:34:in `get'
        from /usr/local/lib/ruby/gems/2.2.0/gems/nexpose-3.3.1/lib/nexpose/ajax.rb:263:in `set_rows'
        from /usr/local/lib/ruby/gems/2.2.0/gems/nexpose-3.3.1/lib/nexpose/ajax.rb:221:in `ensure in preserving_preference'
        from /usr/local/lib/ruby/gems/2.2.0/gems/nexpose-3.3.1/lib/nexpose/ajax.rb:221:in `preserving_preference'
        from /usr/local/lib/ruby/gems/2.2.0/gems/nexpose-3.3.1/lib/nexpose/scan.rb:374:in `past_scans'

Using ruby 2.2, nepose-client 3.3.1, nexpose console 6.2.3

@sgreen-r7
Copy link
Contributor

Yep, looks broken - and also breaks when limiting the past scans as well.

[5] pry(main)> nsc.past_scans 1 Nexpose::APIError: NexposeAPI: GET request to /ajax/user_pref_set.txml?name=global-completed-scans.rows&value= failed. request body: from /Users/sgreen/.rvm/gems/ruby-2.2.2@nexpose-cucumber/gems/nexpose-3.3.1/lib/nexpose/ajax.rb:166:inrequest'`

thanks for the heads up @nbirnel -- we'll look into this and see if we can get a fixed pushed out.

@sgreen-r7
Copy link
Contributor

Looks like that endpoint was removed. Go ahead and let us know if you can verify that the PR #221 fixes your issue. We can merge into master and release a new gem version once you let us know. Thanks again @nbirnel

@sgreen-r7
Copy link
Contributor

We merged the fix into master, and we'll be releasing a new version of the gem today. Just need to talk to @gschneider-r7 if we're going to merge some of stuff in before we release.

@sgreen-r7
Copy link
Contributor

@nbirnel version 3.3.2 of the gem has been released and your issue should be fixed.

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

No branches or pull requests

2 participants