google-code-export / ruby-activeldap

Automatically exported from code.google.com/p/ruby-activeldap
Other
1 stars 1 forks source link

[Ruby 1.9 Support] :: Running Tests #20

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. svn checkout http://ruby-activeldap.googlecode.com/svn/trunk/
ruby-activeldap-read-only
2. cd ruby-activeldap-read-only
3. generate test/config.yaml
----
test:
  host: 127.0.0.1
  port: 389
  base: dc=127.0.0.1,dc=com
  bind_dn: ""
  try_sasl: true
  method: :tls
  sasl_mechanisms: ["GSSAPI"]
  allow_anonymous: false
----
4. run ruby test/run-test.rb

What is the expected output? What do you see instead?

Please see attached log.

Original issue reported on code.google.com by Alexey.Chebotar@gmail.com on 10 Mar 2009 at 12:45

Attachments:

GoogleCodeExporter commented 9 years ago
It's a Ruby/LDAP problem not ActiveLdap. Ruby/LDAP doesn't support Ruby 1.9.1 
at all.
e.g. We need to use RSTRING_PTR, RSTRING_LEN, RARRAY_PTR and RARRAY_LEN macros 
to
access String and Array value.

Original comment by kou...@gmail.com on 12 Mar 2009 at 12:16

GoogleCodeExporter commented 9 years ago
I trying to run tests with compiled Ruby/LDAP with RSTRING_PTR, RSTRING_LEN,
RARRAY_PTR and RARRAY_LEN with small (maybe wrong :) ) fix in C code.

Please see attached log.

Original comment by Alexey.Chebotar@gmail.com on 13 Mar 2009 at 11:57

Attachments:

GoogleCodeExporter commented 9 years ago
BTW. Look at output warnings. :)
[root ruby-activeldap-read-only]# ruby test/run-test.rb > 
ruby19_run-test_r878.log
/usr/lib/ruby/gems/1.9.1/gems/activerecord-2.3.1/lib/active_record/validations.r
b:312: warning:
`*' interpreted as argument prefix
/usr/lib/ruby/gems/1.9.1/gems/activerecord-2.3.1/lib/active_record/dirty.rb:40:
warning: `*' interpreted as argument prefix
/usr/lib/ruby/gems/1.9.1/gems/activerecord-2.3.1/lib/active_record/callbacks.rb:
228:
warning: `*' interpreted as argument prefix
/usr/lib/ruby/gems/1.9.1/gems/activerecord-2.3.1/lib/active_record/callbacks.rb:
344:
warning: shadowing outer local variable - result
/usr/lib/ruby/gems/1.9.1/gems/activerecord-2.3.1/lib/active_record/association_p
reload.rb:114:
warning: shadowing outer local variable - records
/usr/lib/ruby/site_ruby/1.9.1/i686-linux/ldap.so: warning: defining
LDAP::Conn.allocate is deprecated; use rb_define_alloc_func()
/usr/lib/ruby/site_ruby/1.9.1/i686-linux/ldap.so: warning: defining
LDAP::Mod.allocate is deprecated; use rb_define_alloc_func()
/usr/lib/ruby/site_ruby/1.9.1/ldap/ldif.rb:381: warning: shadowing outer local
variable - attr
/usr/lib/ruby/site_ruby/1.9.1/ldap/ldif.rb:401: warning: shadowing outer local
variable - mod_type
/usr/lib/ruby/site_ruby/1.9.1/ldap/ldif.rb:402: warning: shadowing outer local
variable - attr

Original comment by Alexey.Chebotar@gmail.com on 13 Mar 2009 at 2:22

GoogleCodeExporter commented 9 years ago
Results of tests on revision 880.

Original comment by Alexey.Chebotar@gmail.com on 13 Mar 2009 at 3:22

Attachments:

GoogleCodeExporter commented 9 years ago
All tests are passed with both Ruby 1.8.7 and 1.9.1 on r891 on my environment. 
:)

Ruby/LDAP: Do you have a plan to feed back your change to the upstream?

Warnings: Did you notice that there are no warnings from ActiveLdap? ;-) They 
are for
ActiveRecord and Ruby/LDAP.

Original comment by kou...@gmail.com on 14 Mar 2009 at 7:38

GoogleCodeExporter commented 9 years ago
Hello koutou.
Thanks for fixes :)
First of all I want to try remove warnings from Ruby/LDAP. And then submit 
patch for
developers... but Ruby/LDAP does not have updates from 2006 year :(
Maybe we can include Ruby/LDAP in ActiveLdap ?

Original comment by danger1...@gmail.com on 14 Mar 2009 at 10:32

GoogleCodeExporter commented 9 years ago
BTW. Maybe you can help me with warnings:
/usr/lib/ruby/site_ruby/1.9.1/ldap/ldif.rb:381: warning: shadowing outer local
variable - attr
/usr/lib/ruby/site_ruby/1.9.1/ldap/ldif.rb:401: warning: shadowing outer local
variable - mod_type
/usr/lib/ruby/site_ruby/1.9.1/ldap/ldif.rb:402: warning: shadowing outer local
variable - attr

? :)

Original comment by Alexey.Chebotar@gmail.com on 14 Mar 2009 at 10:43

GoogleCodeExporter commented 9 years ago
Two warnings now removed :)
{{{
# ruby test/run-test.rb > ruby191_run-test_r893.log
/usr/lib/ruby/gems/1.9.1/gems/activerecord-2.3.1/lib/active_record/validations.r
b:312: warning:
`*' interpreted as argument prefix
/usr/lib/ruby/gems/1.9.1/gems/activerecord-2.3.1/lib/active_record/dirty.rb:40:
warning: `*' interpreted as argument prefix
/usr/lib/ruby/gems/1.9.1/gems/activerecord-2.3.1/lib/active_record/callbacks.rb:
228:
warning: `*' interpreted as argument prefix
/usr/lib/ruby/gems/1.9.1/gems/activerecord-2.3.1/lib/active_record/callbacks.rb:
344:
warning: shadowing outer local variable - result
/usr/lib/ruby/gems/1.9.1/gems/activerecord-2.3.1/lib/active_record/association_p
reload.rb:114:
warning: shadowing outer local variable - records
/usr/lib/ruby/site_ruby/1.9.1/ldap/ldif.rb:381: warning: shadowing outer local
variable - attr
/usr/lib/ruby/site_ruby/1.9.1/ldap/ldif.rb:401: warning: shadowing outer local
variable - mod_type
/usr/lib/ruby/site_ruby/1.9.1/ldap/ldif.rb:402: warning: shadowing outer local
variable - attr
}}}

P.S. ruby18_run-test_r880.log it's result of test on ruby 1.8.6 (2008-08-11
patchlevel 287) [i686-linux] (I will submit new results soon)

Original comment by Alexey.Chebotar@gmail.com on 14 Mar 2009 at 12:10

Attachments:

GoogleCodeExporter commented 9 years ago
warning: shadowing outer local variable: The following code is reported:
variable = nil
some_method do |variable|
  # use existing variable name in the scope as block variable name.
end

The "1) Error" test requires user search by anonymous. So, the error is not 
critical.

The "2) Failure" is also not critical. The test will pass if you run the test a 
few
times or you run the test on veeeeeeeeery fast machine. :)

Original comment by kou...@gmail.com on 15 Mar 2009 at 10:46

GoogleCodeExporter commented 9 years ago
Ruby/LDAP: If you maintain it, we can use the same repository. e.g.
http://ruby-activeldap.googlecode.com/svn/ldap/

Original comment by kou...@gmail.com on 15 Mar 2009 at 10:54

GoogleCodeExporter commented 9 years ago
How I know, I can't create folder 'ldap' in your svn repository :)
P.S. Developer of Ruby/LDAP does not gives answer about patch...
P.S.S. I found submitted patch to developer before me
http://sourceforge.net/tracker/index.php?func=detail&aid=2622809&group_id=66444&
atid=514521
:) (But this patch not removes  warnings :) )

Original comment by Alexey.Chebotar@gmail.com on 16 Mar 2009 at 6:21

GoogleCodeExporter commented 9 years ago
Attached Ruby/LDAP without warnings.
All tests are passed with Ruby 1.9.1 on r894 :)
I will try to make support for Ruby 1.8.7 and 1.9.1 by Ruby/LDAP

Original comment by Alexey.Chebotar@gmail.com on 16 Mar 2009 at 9:24

Attachments:

GoogleCodeExporter commented 9 years ago
We will add you to ActiveLdap project members on Google Code and RubyForge if 
you say
"all yes" against the questions:
* Do you maintain Ruby/LDAP?
** Do you apply or reject received patches?
** Do you release new Ruby/LDAP?
** Do you announce on new Ruby/LDAP release?
* Do you create Ruby/LDAP pages that will say "Ruby/LDAP maintainer is changed"?

I hope you say "all yes". :-)

Original comment by kou...@gmail.com on 16 Mar 2009 at 2:37

GoogleCodeExporter commented 9 years ago
Ok. I will do this all :)

Original comment by Alexey.Chebotar@gmail.com on 17 Mar 2009 at 9:32

GoogleCodeExporter commented 9 years ago
OK. I'll add you to the ActiveLdap project members on Google Code after Google's
maintanance is finished.

Could you tell me your RubyForge account? I'll add you to the ActiveLdap project
members on RubyForge.
You will use RubyForge for Ruby/LDAP project site.

Original comment by kou...@gmail.com on 17 Mar 2009 at 2:06

GoogleCodeExporter commented 9 years ago
I've created account on RubyForge: alexey_chebotar
Thank you for adding me to your project.

Original comment by Alexey.Chebotar@gmail.com on 17 Mar 2009 at 2:49

GoogleCodeExporter commented 9 years ago
I've add you to the ActiveLdap project members on RubyForge.

On Google Code:
1. You can import Ruby/LDAP into 
https://ruby-activeldap.googlecode.com/svn/ldap/:

  % cd ruby-ldap/
  % make distclean
  % svn import . https://ruby-activeldap.googlecode.com/svn/ldap/trunk/

2. You can use Wiki pages on Google Code for Ruby/LDAP.

On RubyForge:
1. You can put Ruby/LDAP related documents (e.g. project home page, RDoc and so 
on)
into http://ruby-activeldap.rubyforge.org/ldap/.
I'll add link to Ruby/LDAP page to http://ruby-activeldap.rubyforge.org/ after 
you
put a page.

2. You can announce about 'Ruby/LDAP reloaded' on
ruby-activeldap-discuss@rubyforge.org. :)
We will create a new ML for Ruby/LDAP but it'll not be needed for now.

If you have any problems about this, could you submit a new ticket or use
ruby-activeldap-discuss ML?

Original comment by kou...@gmail.com on 17 Mar 2009 at 3:05

GoogleCodeExporter commented 9 years ago
I can't put Ruby/LDAP into svn on Google Code:

[root ruby-ldap-0.9.7]# svn import .
https://ruby-activeldap.googlecode.com/svn/ldap/trunk/ -m "Ruby/LDAP 0.9.7 (Last
Update: Aug 09 2006)"

Authentication realm: <https://ruby-activeldap.googlecode.com:443> Google Code
Subversion Repository
Username: alexey.chebotar
Password for 'alexey.chebotar': [password from google account]
svn: OPTIONS of 'https://ruby-activeldap.googlecode.com/svn/ldap/trunk':
authorization failed (https://ruby-activeldap.googlecode.com)

Original comment by Alexey.Chebotar@gmail.com on 17 Mar 2009 at 7:46

GoogleCodeExporter commented 9 years ago
See http://code.google.com/p/ruby-activeldap/source/checkout

Original comment by kou...@gmail.com on 17 Mar 2009 at 10:09

GoogleCodeExporter commented 9 years ago
Hello kotou. I've send email with announce to ML. But nothing happens :( I 
don't see
my thread in
http://rubyforge.org/pipermail/ruby-activeldap-discuss/2009-March/thread.html

Original comment by Alexey.Chebotar@gmail.com on 26 Mar 2009 at 6:29

GoogleCodeExporter commented 9 years ago
Did you confirm ML subscription? I think Gmail treated the confirmation message 
as spam.

I've confirmed your address in administration page. Please resend your message.

Original comment by kou...@gmail.com on 26 Mar 2009 at 2:21