Jiri Daněk created PROTON-1814:
----------------------------------

             Summary: core/terminus.rb:239:in `block in apply': undefined 
method[s ...] for #<Qpid::Proton::Terminus: ...> (NoMethodError)
                 Key: PROTON-1814
                 URL: https://issues.apache.org/jira/browse/PROTON-1814
             Project: Qpid Proton
          Issue Type: Bug
          Components: ruby-binding
    Affects Versions: proton-j-0.22.0
         Environment: commit b6436ff34ecd091ffd49c091405c8a543479eb30 
(upstream/master)
Author: Andrew Stitcher <[email protected]>
Date:   Fri Mar 23 16:40:04 2018 -0400

    PROTON-1810: Disable fuzz regression testing on MacOSX differently
    - Feedback from release manager
            Reporter: Jiri Daněk
            Assignee: Alan Conway


bin/cli-proton-ruby-receiver -c 1 --log-msgs dict --broker 
amqp://127.0.0.1:5672/lala --log-msgs dict
/home/jdanek/.gem/ruby/2.5.0/gems/qpid_proton-0.22.0/lib/core/terminus.rb:239:in
 `block in apply': undefined method `filter=' for #<Qpid::Proton::Terminus: 
address="lala" dynamic?=false> (NoMethodError)
        from 
/home/jdanek/.gem/ruby/2.5.0/gems/qpid_proton-0.22.0/lib/core/terminus.rb:231:in
 `each_pair'
        from 
/home/jdanek/.gem/ruby/2.5.0/gems/qpid_proton-0.22.0/lib/core/terminus.rb:231:in
 `apply'
        from 
/home/jdanek/.gem/ruby/2.5.0/gems/qpid_proton-0.22.0/lib/core/receiver.rb:51:in 
`open'
        from 
/home/jdanek/.gem/ruby/2.5.0/gems/qpid_proton-0.22.0/lib/core/session.rb:117:in 
`open_receiver'
        from 
/home/jdanek/.gem/ruby/2.5.0/gems/qpid_proton-0.22.0/lib/core/connection.rb:217:in
 `open_receiver'
        from 
/home/jdanek/Work/repos/cli-proton-ruby/lib/handlers/receiver_handler.rb:102:in 
`on_container_start'
        from 
/home/jdanek/.gem/ruby/2.5.0/gems/qpid_proton-0.22.0/lib/handler/adapter.rb:74:in
 `forward'
        from 
/home/jdanek/.gem/ruby/2.5.0/gems/qpid_proton-0.22.0/lib/handler/messaging_adapter.rb:27:in
 `delegate'
        from 
/home/jdanek/.gem/ruby/2.5.0/gems/qpid_proton-0.22.0/lib/handler/messaging_adapter.rb:38:in
 `on_container_start'
        from 
/home/jdanek/.gem/ruby/2.5.0/gems/qpid_proton-0.22.0/lib/core/container.rb:144:in
 `run_one'
        from 
/home/jdanek/.gem/ruby/2.5.0/gems/qpid_proton-0.22.0/lib/core/container.rb:347:in
 `run'
        from 
/home/jdanek/Work/repos/cli-proton-ruby/lib/receiver_client.rb:48:in 
`initialize'
        from 
/home/jdanek/Work/repos/cli-proton-ruby/bin/cli-proton-ruby-receiver:21:in `new'
        from 
/home/jdanek/Work/repos/cli-proton-ruby/bin/cli-proton-ruby-receiver:21:in 
`<top (required)>'
        from -e:1:in `load'
        from -e:1:in `<main>'

Process finished with exit code 1

After investigation of the method Qpid::Proton::Terminus#apply at 
qpid_proton-0.22.0/lib/core/terminus.rb:226

{noformat}
    def apply(opts=nil)
      return unless opts
      if opts.is_a? String      # Shorthand for address
        self.address = opts
      else
        opts.each_pair do |k,v|
          case k
          when :address then self.address = v
          when :dynamic then self.dynamic = !!v
          when :distribution_mode then self.distribution_mode = v
          when :durability_mode then self.durability_mode = v
          when :timeout then self.timeout = v
          when :expiry_policy then self.expiry_policy = v
          when :filter then self.filter = v
          when :capabilities then self.capabilities = v
          end
        end
      end
    end
{noformat}

I figure there are these three accessors missing

Getter:
{noformat}
undefined method `dynamic' for #<Qpid::Proton::Terminus: address="lala" 
dynamic?=false>
{noformat}

Setters:
{noformat}
undefined method `filter=' for #<Qpid::Proton::Terminus: address="lala" 
dynamic?=false>
undefined method `capabilities=' for #<Qpid::Proton::Terminus: address="lala" 
dynamic?=false>
{noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to