podio / podio-rb Goto Github PK

Hello. I have written integration with podio, chef and consul-templates. The consul integration is using the diplomat rubygem, which is written with a faraday 0.9.0 dependency.

Do you have plans to upgrade to faraday 0.9.0? Is that on your roadmap?

The current faraday gem is v2.9.x, and for a newer application using common gems that depend on faraday require >2 now. This dependency <= 1.3.0 makes is infeasible to use podio-rb.

s.add_dependency('faraday', ['>= 0.8.0', '<= 1.3.0'])

Please consider updating the gem to work with faraday v2+.

Podio is great, having an API is even greater, and opensourcing the client connector... ok, you understood my point.

However, this would be nice to have tags in your Github repo matching the versions on Rubygems. I would feel a lot more confident with that...

I am trying to play around with podio gem. When I call Podio.setup and pass my api keys it does not give me any error but after that when I try to authenticate Podio.client and pass my username and password I get the following error

OpenSSL::SSL::SSLError: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed

all API calls fail with

OpenSSL::SSL::SSLError - SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed

on Heroku using Ruby 1.8.7

Is there a wiki to add this to?

If you get this error:

init() got an unexpected keyword argument 'disable_ssl_certificate_validation'

then probably caused by old httplib2 library, to fix:

easy_install -U httplib2

Hi!

Any chance to make Podio run on Rails 4? It seems completely incompatible for now :(

I'm currently running into API rate limits during testing of my app. It would be really cool to be able to interrogate the Podio object for information about how many calls are left for a given API endpoint.

I believe this information could be gathered from the response headers as explained here: https://developers.podio.com/index/limits

You've stated that you follow semantic versioning, but it seems like it's been a long while since a tag has been added to this repo. We use this gem in our app and need to pin a specific version. We'd prefer to use a tag rather than a SHA.

Hi. Hope you're doing great!

In the project you have a dependency:

s.add_dependency('faraday', ['>= 0.8.0', '< 0.10.0'])

And I want to use podio-rb along with another gem that requires Faraday >= 0.12.0.

Do you have any plans on upgrading Faraday dependency?

Why am I only encountering this issue when clicking 'create new lead' or when clicking the edit button on a lead?? 'Show tasks', 'detail' & 'delete' all work fine.

In item_diff.rb a property called external_id is defined.

This property is never populated by the underlying API

I believe this property is useful and should be populated. Can the underlying API be enhanced to include this property?

I can connect by setting up an SSL Connection directly just fine, and the node client is working. I think the problem is that the cert store needs to have set_default_paths() executed. Ruby's openssl support does verification, but does not load the default cert stores. No idea why. But to replicate, all I'm doing is, in irb:

require 'podio'
Podio.setup()
Podio.client.authenticate_with_credentials("MY EMAIL", "MY PASSWORD")

Yielding:
Faraday::SSLError: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed

I can connect via ssl though, so long as I call set_default_paths on the cert store.

I'm trying to write code using the Podio API and this gem, but I'm finding it difficult to get a response from Podio/Cisco developers.

Questions on StackOverflow are answered by inexperienced staff if at all.

Issues raised here are ignored.

I don't think my questions or suggestions are unreasonable and it's difficult to contemplate continuing to use Podio if the API is a stale project unsupported by Cisco.

@theflow @RSpace: Sorry to bug you but do you know of anybody I can contact to find out whether the API is still supported by Cisco?

Hello,

"NoMethodError (undefined method `post' for nil:NilClass)" shows only in production when the app executes Podio::Item.create, Podio::Search.in_app, etc. I tried to execute the same thing in the production console but it works. Same goes under development environment - the app works fine. My current setup below:

config/initializers/podio.rb
require 'rubygems'
require 'podio'
Podio.setup(:api_key => 'YOUR_API_KEY', :api_secret => 'YOUR_API_SECRET')
Podio.client.authenticate_with_credentials('YOUR_PODIO_ACCOUNT', 'YOUR_PODIO_PASSWORD')

Thanks,

Henry

When a user updates a field on an item in Podio, an update hook is triggered in my app. Thing is, there are a couple fields that I don't want changed at all. Since there's no read-only option per field, I'm trying to use the revert function, but it constantly throws an infinite loop. Is there any way to prevent this?
I'm using Ruby.

ex:
when 'item.update'
(setup code)
if label == 'Project'
Podio::ItemDiff.revert(@item_id, @curr_rev)
end
end

From the README: "... all find methods return model instances with attributes cast to the expected type (string, integer, boolean, datetime, etc.)"

I have a Podio::Item instance, and am trying to get at custom attributes (for example location), but I get NoMethodError: undefined method 'location' for #<Podio::Item:0x007f03db573010>. Using a default attribute such as title seems to work.

What can the problem be?

The podio documentation here: https://developers.podio.com/authentication/app_auth outlines the POST:

HTTP METHOD: POST URL: https://api.podio.com/oauth/token/v2 HEADER: "Content-Type: application/json" BODY: { "grant_type": "app", "app_id": YOUR_PODIO_APP_ID, "app_token": YOUR_PODIO_APP_TOKEN, "client_id": YOUR_CLIENT_ID, "redirect_uri": YOUR_URL, "client_secret": YOUR_CLIENT_SECRET }

However the the podio ruby client found here: https://github.com/podio/podio-rb/blob/master/lib/podio/client.rb#L96 uses req.headers['Content-Type'] = 'application/x-www-form-urlencoded'.

Podio uses thread locals to store the client. Is there a reason for doing that instead of standard instance variables? I ask because it causes problems on certain servers.

Hi. Please see:
rails/rails#14664

Your gem is impacted. When I add require 'active_support' to ./lib/podio.rb it works well:

require 'faraday'
require 'active_support'
require 'active_support/core_ext'

Otherwise, I receive random errors on some of my machines, just as others have reported.

Error: Values cannot be set directly for field with id <calc field id>

(I'm not actually changing this field)

My app has many users. Each of them has their own Podio credentials, which I allow them to define using the podio-ominauth strategy.

I am a bit alarmed that the models in this gem all use the singleton method Podio.connection to issue API calls to Podio. This appears to use whichever user's credentials were last passed to Podio.setup.

I may be misunderstanding the architecture of this gem. Please reassure me that I am wrong about this and my many users will not be seeing each others' data in my app.

When I try to run the sample-app with my app id and secret, after clicking the try to authorize link, I get the following error:

undefined method `authorize_url' for nil:NilClass

The line causing the error:

 redirect Podio.client.authorize_url(:redirect_uri => redirect_uri)

When inspecting the app with RubyMine, the error seems to happen in

Faraday::Connection.new(:url => api_url, :headers => configured_headers, :request => {:client => self}) do |builder| 

Can you give me any hint?

Using OS X 10.9, ruby-2.0.0p247 and the latest podia-gem.

/Users/robertshippey/.rvm/gems/ruby-2.2.2/gems/activesupport-4.2.1/lib/active_support/core_ext/module/deprecation.rb:21:in `deprecate': uninitialized constant ActiveSupport::Deprecation (NameError)
    from /Users/robertshippey/.rvm/gems/ruby-2.2.2/gems/activesupport-4.2.1/lib/active_support/core_ext/class/delegating_attributes.rb:26:in `<class:Class>'
    from /Users/robertshippey/.rvm/gems/ruby-2.2.2/gems/activesupport-4.2.1/lib/active_support/core_ext/class/delegating_attributes.rb:6:in `<top (required)>'
    from /Users/robertshippey/.rvm/gems/ruby-2.2.2/gems/backports-3.6.4/lib/backports/std_lib.rb:9:in `require'
    from /Users/robertshippey/.rvm/gems/ruby-2.2.2/gems/backports-3.6.4/lib/backports/std_lib.rb:9:in `require_with_backports'
    from /Users/robertshippey/.rvm/gems/ruby-2.2.2/gems/activesupport-4.2.1/lib/active_support/core_ext/class.rb:2:in `<top (required)>'
    from /Users/robertshippey/.rvm/gems/ruby-2.2.2/gems/backports-3.6.4/lib/backports/std_lib.rb:9:in `require'
    from /Users/robertshippey/.rvm/gems/ruby-2.2.2/gems/backports-3.6.4/lib/backports/std_lib.rb:9:in `require_with_backports'
    from /Users/robertshippey/.rvm/gems/ruby-2.2.2/gems/activesupport-4.2.1/lib/active_support/core_ext.rb:2:in `block in <top (required)>'
    from /Users/robertshippey/.rvm/gems/ruby-2.2.2/gems/activesupport-4.2.1/lib/active_support/core_ext.rb:1:in `each'
    from /Users/robertshippey/.rvm/gems/ruby-2.2.2/gems/activesupport-4.2.1/lib/active_support/core_ext.rb:1:in `<top (required)>'
    from /Users/robertshippey/.rvm/gems/ruby-2.2.2/gems/backports-3.6.4/lib/backports/std_lib.rb:9:in `require'
    from /Users/robertshippey/.rvm/gems/ruby-2.2.2/gems/backports-3.6.4/lib/backports/std_lib.rb:9:in `require_with_backports'
    from /Users/robertshippey/.rvm/gems/ruby-2.2.2/gems/podio-1.0.0/lib/podio.rb:2:in `<top (required)>'
    from /Users/robertshippey/.rvm/gems/ruby-2.2.2/gems/backports-3.6.4/lib/backports/std_lib.rb:9:in `require'
    from /Users/robertshippey/.rvm/gems/ruby-2.2.2/gems/backports-3.6.4/lib/backports/std_lib.rb:9:in `require_with_backports'
    from /Users/robertshippey/Desktop/status/jobs/podio.rb:2:in `<top (required)>'
...

I'm new to Ruby and I don't really know what this means. I'm using ruby-2.2.2 and my only other dependancies are dashing and httparty. I had a look and there was an issue already on here, #16, which looked relevant but apparently fixed so I'm unsure.