Hi I don''t get any changes coming in for the repo for the last 3 days, are those changes that make up RC1 in? Then on a side note I''m still unable to run xmpp4r with IronRuby. it should work but gets stuck in waiting for a thread that never returns. --- Met vriendelijke groeten - Best regards - Salutations Ivan Porto Carrero Blog: http://flanders.co.nz Google Wave: portocarrero.ivan at googlewave.com Twitter: http://twitter.com/casualjim Author of IronRuby in Action (http://manning.com/carrero) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20091121/25b96516/attachment.html>
The RC1 bits will be in GIT shortly ? looks like the pushes to GIT haven?t been happening/working. Also, the RC1 ?announcement? and other things from my RubyConf talk will make their way online over the next couple of days, but in short this release is ?RC1? because we want more people to start using it and find blocking bugs. WRT xmpp4r, it?d be great if you could investigate what the actual bug is; a small repro will drastically increase the chances of it being fixes in the near future, especially when it?s a library failing for some strange reasons. ~js From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Ivan Porto Carrero Sent: Saturday, November 21, 2009 12:06 AM To: ironruby-core Subject: [Ironruby-core] ironruby RC1 Hi I don''t get any changes coming in for the repo for the last 3 days, are those changes that make up RC1 in? Then on a side note I''m still unable to run xmpp4r with IronRuby. it should work but gets stuck in waiting for a thread that never returns. --- Met vriendelijke groeten - Best regards - Salutations Ivan Porto Carrero Blog: http://flanders.co.nz Google Wave: portocarrero.ivan at googlewave.com<mailto:portocarrero.ivan at googlewave.com> Twitter: http://twitter.com/casualjim Author of IronRuby in Action (http://manning.com/carrero) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20091121/4aeedfca/attachment-0001.html>
I know it has something to do with Threading and the value of @tickets in
this class.
I''ve just managed to connect with xmpp4r to my jabber server :=D but
then
the stream is closed so you can''t actually send messages etc.
They have this class:
##
# This class implements semaphore for threads synchronization.
class Semaphore
##
# Initialize new semaphore
#
# val:: [Integer] number of threads, that can enter to section
def initialize(val=0)
@tickets = val
@lock = Mutex.new
@cond = ConditionVariable.new
end
##
# Waits until are available some free tickets
def wait
@lock.synchronize {
@cond.wait(@lock) while !(@tickets > 0)
@tickets -= 1
}
end
##
# Unlocks guarded section, increments number of free tickets
def run
@lock.synchronize {
@tickets += 1
@cond.signal
}
end
end
---
Met vriendelijke groeten - Best regards - Salutations
Ivan Porto Carrero
Blog: http://flanders.co.nz
Google Wave: portocarrero.ivan at googlewave.com
Twitter: http://twitter.com/casualjim
Author of IronRuby in Action (http://manning.com/carrero)
On Sat, Nov 21, 2009 at 2:28 PM, Jimmy Schementi <
Jimmy.Schementi at microsoft.com> wrote:
> The RC1 bits will be in GIT shortly ? looks like the pushes to GIT haven?t
> been happening/working. Also, the RC1 ?announcement? and other things from
> my RubyConf talk will make their way online over the next couple of days,
> but in short this release is ?RC1? because we want more people to start
> using it and find blocking bugs. WRT xmpp4r, it?d be great if you could
> investigate what the actual bug is; a small repro will drastically increase
> the chances of it being fixes in the near future, especially when it?s a
> library failing for some strange reasons.
>
>
>
> ~js
>
>
>
> *From:* ironruby-core-bounces at rubyforge.org [mailto:
> ironruby-core-bounces at rubyforge.org] *On Behalf Of *Ivan Porto Carrero
> *Sent:* Saturday, November 21, 2009 12:06 AM
> *To:* ironruby-core
> *Subject:* [Ironruby-core] ironruby RC1
>
>
>
> Hi
>
>
>
> I don''t get any changes coming in for the repo for the last 3
days, are
> those changes that make up RC1 in?
>
>
>
> Then on a side note I''m still unable to run xmpp4r with IronRuby.
it should
> work but gets stuck in waiting for a thread that never returns.
>
>
>
>
>
>
> ---
> Met vriendelijke groeten - Best regards - Salutations
> Ivan Porto Carrero
> Blog: http://flanders.co.nz
> Google Wave: portocarrero.ivan at googlewave.com
> Twitter: http://twitter.com/casualjim
> Author of IronRuby in Action (http://manning.com/carrero)
>
> _______________________________________________
> Ironruby-core mailing list
> Ironruby-core at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ironruby-core
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20091121/6abefb4d/attachment.html>
I needed to add I managed to connect by initializing the tickets with another value than 0. I set it to 1 --- Met vriendelijke groeten - Best regards - Salutations Ivan Porto Carrero Blog: http://flanders.co.nz Google Wave: portocarrero.ivan at googlewave.com Twitter: http://twitter.com/casualjim Author of IronRuby in Action (http://manning.com/carrero) On Sat, Nov 21, 2009 at 4:37 PM, Ivan Porto Carrero <ivan at flanders.co.nz>wrote:> I know it has something to do with Threading and the value of @tickets in > this class. > I''ve just managed to connect with xmpp4r to my jabber server :=D but then > the stream is closed so you can''t actually send messages etc. > > They have this class: > > ## > # This class implements semaphore for threads synchronization. > class Semaphore > > ## > # Initialize new semaphore > # > # val:: [Integer] number of threads, that can enter to section > def initialize(val=0) > @tickets = val > @lock = Mutex.new > @cond = ConditionVariable.new > end > > ## > # Waits until are available some free tickets > def wait > @lock.synchronize { > @cond.wait(@lock) while !(@tickets > 0) > @tickets -= 1 > } > end > > ## > # Unlocks guarded section, increments number of free tickets > def run > @lock.synchronize { > @tickets += 1 > @cond.signal > } > end > end > --- > Met vriendelijke groeten - Best regards - Salutations > Ivan Porto Carrero > Blog: http://flanders.co.nz > Google Wave: portocarrero.ivan at googlewave.com > Twitter: http://twitter.com/casualjim > Author of IronRuby in Action (http://manning.com/carrero) > > > > On Sat, Nov 21, 2009 at 2:28 PM, Jimmy Schementi < > Jimmy.Schementi at microsoft.com> wrote: > >> The RC1 bits will be in GIT shortly ? looks like the pushes to GIT haven?t >> been happening/working. Also, the RC1 ?announcement? and other things from >> my RubyConf talk will make their way online over the next couple of days, >> but in short this release is ?RC1? because we want more people to start >> using it and find blocking bugs. WRT xmpp4r, it?d be great if you could >> investigate what the actual bug is; a small repro will drastically increase >> the chances of it being fixes in the near future, especially when it?s a >> library failing for some strange reasons. >> >> >> >> ~js >> >> >> >> *From:* ironruby-core-bounces at rubyforge.org [mailto: >> ironruby-core-bounces at rubyforge.org] *On Behalf Of *Ivan Porto Carrero >> *Sent:* Saturday, November 21, 2009 12:06 AM >> *To:* ironruby-core >> *Subject:* [Ironruby-core] ironruby RC1 >> >> >> >> Hi >> >> >> >> I don''t get any changes coming in for the repo for the last 3 days, are >> those changes that make up RC1 in? >> >> >> >> Then on a side note I''m still unable to run xmpp4r with IronRuby. it >> should work but gets stuck in waiting for a thread that never returns. >> >> >> >> >> >> >> --- >> Met vriendelijke groeten - Best regards - Salutations >> Ivan Porto Carrero >> Blog: http://flanders.co.nz >> Google Wave: portocarrero.ivan at googlewave.com >> Twitter: http://twitter.com/casualjim >> Author of IronRuby in Action (http://manning.com/carrero) >> >> _______________________________________________ >> Ironruby-core mailing list >> Ironruby-core at rubyforge.org >> http://rubyforge.org/mailman/listinfo/ironruby-core >> >> >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20091121/bbc06570/attachment.html>
I?m working on automating the pushes, but they aren?t done yet, and I haven?t
had good enough internet while at RubyConf to push. Releasing was hard enough ;)
I?ll do a push tonight when I get home.
JD
From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Ivan Porto Carrero
Sent: Saturday, November 21, 2009 7:38 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] ironruby RC1
I know it has something to do with Threading and the value of @tickets in this
class.
I''ve just managed to connect with xmpp4r to my jabber server :=D but
then the stream is closed so you can''t actually send messages etc.
They have this class:
##
# This class implements semaphore for threads synchronization.
class Semaphore
##
# Initialize new semaphore
#
# val:: [Integer] number of threads, that can enter to section
def initialize(val=0)
@tickets = val
@lock = Mutex.new
@cond = ConditionVariable.new
end
##
# Waits until are available some free tickets
def wait
@lock.synchronize {
@cond.wait(@lock) while !(@tickets > 0)
@tickets -= 1
}
end
##
# Unlocks guarded section, increments number of free tickets
def run
@lock.synchronize {
@tickets += 1
@cond.signal
}
end
end
---
Met vriendelijke groeten - Best regards - Salutations
Ivan Porto Carrero
Blog: http://flanders.co.nz
Google Wave: portocarrero.ivan at googlewave.com<mailto:portocarrero.ivan at
googlewave.com>
Twitter: http://twitter.com/casualjim
Author of IronRuby in Action (http://manning.com/carrero)
On Sat, Nov 21, 2009 at 2:28 PM, Jimmy Schementi <Jimmy.Schementi at
microsoft.com<mailto:Jimmy.Schementi at microsoft.com>> wrote:
The RC1 bits will be in GIT shortly ? looks like the pushes to GIT haven?t been
happening/working. Also, the RC1 ?announcement? and other things from my
RubyConf talk will make their way online over the next couple of days, but in
short this release is ?RC1? because we want more people to start using it and
find blocking bugs. WRT xmpp4r, it?d be great if you could investigate what the
actual bug is; a small repro will drastically increase the chances of it being
fixes in the near future, especially when it?s a library failing for some
strange reasons.
~js
From: ironruby-core-bounces at rubyforge.org<mailto:ironruby-core-bounces at
rubyforge.org> [mailto:ironruby-core-bounces at
rubyforge.org<mailto:ironruby-core-bounces at rubyforge.org>] On Behalf Of
Ivan Porto Carrero
Sent: Saturday, November 21, 2009 12:06 AM
To: ironruby-core
Subject: [Ironruby-core] ironruby RC1
Hi
I don''t get any changes coming in for the repo for the last 3 days, are
those changes that make up RC1 in?
Then on a side note I''m still unable to run xmpp4r with IronRuby. it
should work but gets stuck in waiting for a thread that never returns.
---
Met vriendelijke groeten - Best regards - Salutations
Ivan Porto Carrero
Blog: http://flanders.co.nz
Google Wave: portocarrero.ivan at googlewave.com<mailto:portocarrero.ivan at
googlewave.com>
Twitter: http://twitter.com/casualjim
Author of IronRuby in Action (http://manning.com/carrero)
_______________________________________________
Ironruby-core mailing list
Ironruby-core at rubyforge.org<mailto:Ironruby-core at rubyforge.org>
http://rubyforge.org/mailman/listinfo/ironruby-core
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20091121/474f89b7/attachment.html>
Yeah I saw that on twitter but you did make it in the end :) Much appreciated thanks --- Met vriendelijke groeten - Best regards - Salutations Ivan Porto Carrero Blog: http://flanders.co.nz Google Wave: portocarrero.ivan at googlewave.com Twitter: http://twitter.com/casualjim Author of IronRuby in Action (http://manning.com/carrero) On Sat, Nov 21, 2009 at 8:50 PM, Jim Deville <jdeville at microsoft.com> wrote:> I?m working on automating the pushes, but they aren?t done yet, and I > haven?t had good enough internet while at RubyConf to push. Releasing was > hard enough ;) > > > > I?ll do a push tonight when I get home. > > > > JD > > > > *From:* ironruby-core-bounces at rubyforge.org [mailto: > ironruby-core-bounces at rubyforge.org] *On Behalf Of *Ivan Porto Carrero > *Sent:* Saturday, November 21, 2009 7:38 AM > *To:* ironruby-core at rubyforge.org > *Subject:* Re: [Ironruby-core] ironruby RC1 > > > > I know it has something to do with Threading and the value of @tickets in > this class. > > I''ve just managed to connect with xmpp4r to my jabber server :=D but then > the stream is closed so you can''t actually send messages etc. > > > > They have this class: > > > > ## > > # This class implements semaphore for threads synchronization. > > class Semaphore > > > > ## > > # Initialize new semaphore > > # > > # val:: [Integer] number of threads, that can enter to section > > def initialize(val=0) > > @tickets = val > > @lock = Mutex.new > > @cond = ConditionVariable.new > > end > > > > ## > > # Waits until are available some free tickets > > def wait > > @lock.synchronize { > > @cond.wait(@lock) while !(@tickets > 0) > > @tickets -= 1 > > } > > end > > > > ## > > # Unlocks guarded section, increments number of free tickets > > def run > > @lock.synchronize { > > @tickets += 1 > > @cond.signal > > } > > end > > end > > --- > Met vriendelijke groeten - Best regards - Salutations > Ivan Porto Carrero > Blog: http://flanders.co.nz > Google Wave: portocarrero.ivan at googlewave.com > Twitter: http://twitter.com/casualjim > Author of IronRuby in Action (http://manning.com/carrero) > > > On Sat, Nov 21, 2009 at 2:28 PM, Jimmy Schementi < > Jimmy.Schementi at microsoft.com> wrote: > > The RC1 bits will be in GIT shortly ? looks like the pushes to GIT haven?t > been happening/working. Also, the RC1 ?announcement? and other things from > my RubyConf talk will make their way online over the next couple of days, > but in short this release is ?RC1? because we want more people to start > using it and find blocking bugs. WRT xmpp4r, it?d be great if you could > investigate what the actual bug is; a small repro will drastically increase > the chances of it being fixes in the near future, especially when it?s a > library failing for some strange reasons. > > > > ~js > > > > *From:* ironruby-core-bounces at rubyforge.org [mailto: > ironruby-core-bounces at rubyforge.org] *On Behalf Of *Ivan Porto Carrero > *Sent:* Saturday, November 21, 2009 12:06 AM > *To:* ironruby-core > *Subject:* [Ironruby-core] ironruby RC1 > > > > Hi > > > > I don''t get any changes coming in for the repo for the last 3 days, are > those changes that make up RC1 in? > > > > Then on a side note I''m still unable to run xmpp4r with IronRuby. it should > work but gets stuck in waiting for a thread that never returns. > > > > > > > --- > Met vriendelijke groeten - Best regards - Salutations > Ivan Porto Carrero > Blog: http://flanders.co.nz > Google Wave: portocarrero.ivan at googlewave.com > Twitter: http://twitter.com/casualjim > Author of IronRuby in Action (http://manning.com/carrero) > > > _______________________________________________ > Ironruby-core mailing list > Ironruby-core at rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core > > > > _______________________________________________ > Ironruby-core mailing list > Ironruby-core at rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20091122/a03866d4/attachment-0001.html>
The comment for the ?val? parameter says ?number of threads, that can enter to
section?, and so it seems reasonable that it should be atleast 1. I wonder if
this just happens to work in MRI because ?run? gets called before ?wait?. This
could happen predictably with MRI?s green threads because the scheduler has
fixed rules of which thread gets scheduled, and so the chances of races is low
even on a multiproc machine. Could you check if this theory is true by adding
logging to the methods and running with MRI? If it is correct, then we will have
to figure out if/why xmpp4r expects to call ?run? first, and how to get this to
happen with IronRuby.
From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Ivan Porto Carrero
Sent: Saturday, November 21, 2009 7:39 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] ironruby RC1
I needed to add I managed to connect by initializing the tickets with another
value than 0. I set it to 1
---
Met vriendelijke groeten - Best regards - Salutations
Ivan Porto Carrero
Blog: http://flanders.co.nz
Google Wave: portocarrero.ivan at googlewave.com<mailto:portocarrero.ivan at
googlewave.com>
Twitter: http://twitter.com/casualjim
Author of IronRuby in Action (http://manning.com/carrero)
On Sat, Nov 21, 2009 at 4:37 PM, Ivan Porto Carrero <ivan at
flanders.co.nz<mailto:ivan at flanders.co.nz>> wrote:
I know it has something to do with Threading and the value of @tickets in this
class.
I''ve just managed to connect with xmpp4r to my jabber server :=D but
then the stream is closed so you can''t actually send messages etc.
They have this class:
##
# This class implements semaphore for threads synchronization.
class Semaphore
##
# Initialize new semaphore
#
# val:: [Integer] number of threads, that can enter to section
def initialize(val=0)
@tickets = val
@lock = Mutex.new
@cond = ConditionVariable.new
end
##
# Waits until are available some free tickets
def wait
@lock.synchronize {
@cond.wait(@lock) while !(@tickets > 0)
@tickets -= 1
}
end
##
# Unlocks guarded section, increments number of free tickets
def run
@lock.synchronize {
@tickets += 1
@cond.signal
}
end
end
---
Met vriendelijke groeten - Best regards - Salutations
Ivan Porto Carrero
Blog: http://flanders.co.nz
Google Wave: portocarrero.ivan at googlewave.com<mailto:portocarrero.ivan at
googlewave.com>
Twitter: http://twitter.com/casualjim
Author of IronRuby in Action (http://manning.com/carrero)
On Sat, Nov 21, 2009 at 2:28 PM, Jimmy Schementi <Jimmy.Schementi at
microsoft.com<mailto:Jimmy.Schementi at microsoft.com>> wrote:
The RC1 bits will be in GIT shortly ? looks like the pushes to GIT haven?t been
happening/working. Also, the RC1 ?announcement? and other things from my
RubyConf talk will make their way online over the next couple of days, but in
short this release is ?RC1? because we want more people to start using it and
find blocking bugs. WRT xmpp4r, it?d be great if you could investigate what the
actual bug is; a small repro will drastically increase the chances of it being
fixes in the near future, especially when it?s a library failing for some
strange reasons.
~js
From: ironruby-core-bounces at rubyforge.org<mailto:ironruby-core-bounces at
rubyforge.org> [mailto:ironruby-core-bounces at
rubyforge.org<mailto:ironruby-core-bounces at rubyforge.org>] On Behalf Of
Ivan Porto Carrero
Sent: Saturday, November 21, 2009 12:06 AM
To: ironruby-core
Subject: [Ironruby-core] ironruby RC1
Hi
I don''t get any changes coming in for the repo for the last 3 days, are
those changes that make up RC1 in?
Then on a side note I''m still unable to run xmpp4r with IronRuby. it
should work but gets stuck in waiting for a thread that never returns.
---
Met vriendelijke groeten - Best regards - Salutations
Ivan Porto Carrero
Blog: http://flanders.co.nz
Google Wave: portocarrero.ivan at googlewave.com<mailto:portocarrero.ivan at
googlewave.com>
Twitter: http://twitter.com/casualjim
Author of IronRuby in Action (http://manning.com/carrero)
_______________________________________________
Ironruby-core mailing list
Ironruby-core at rubyforge.org<mailto:Ironruby-core at rubyforge.org>
http://rubyforge.org/mailman/listinfo/ironruby-core
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20091122/c3cd1323/attachment.html>
Actually, this is a bug in ConditionVariable, and we have RubySpec tags for the
ConditionVariable to disable some failing specs. ConditionVariable used
Monitor.Pulse to implement ConditionVariable#wait which will yield control only
if there is a waiting thread; otherwise the pulse is ignored. So we need to use
AutoResetEvent.
I have opened bug
http://ironruby.codeplex.com/WorkItem/View.aspx?WorkItemId=3151 and attached a
fix to it. I am gone on vacation, so someone will have to get it checked in.
From: Shri Borde
Sent: Saturday, November 21, 2009 4:31 PM
To: ironruby-core at rubyforge.org
Subject: RE: [Ironruby-core] ironruby RC1
The comment for the ?val? parameter says ?number of threads, that can enter to
section?, and so it seems reasonable that it should be atleast 1. I wonder if
this just happens to work in MRI because ?run? gets called before ?wait?. This
could happen predictably with MRI?s green threads because the scheduler has
fixed rules of which thread gets scheduled, and so the chances of races is low
even on a multiproc machine. Could you check if this theory is true by adding
logging to the methods and running with MRI? If it is correct, then we will have
to figure out if/why xmpp4r expects to call ?run? first, and how to get this to
happen with IronRuby.
From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Ivan Porto Carrero
Sent: Saturday, November 21, 2009 7:39 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] ironruby RC1
I needed to add I managed to connect by initializing the tickets with another
value than 0. I set it to 1
---
Met vriendelijke groeten - Best regards - Salutations
Ivan Porto Carrero
Blog: http://flanders.co.nz
Google Wave: portocarrero.ivan at googlewave.com<mailto:portocarrero.ivan at
googlewave.com>
Twitter: http://twitter.com/casualjim
Author of IronRuby in Action (http://manning.com/carrero)
On Sat, Nov 21, 2009 at 4:37 PM, Ivan Porto Carrero <ivan at
flanders.co.nz<mailto:ivan at flanders.co.nz>> wrote:
I know it has something to do with Threading and the value of @tickets in this
class.
I''ve just managed to connect with xmpp4r to my jabber server :=D but
then the stream is closed so you can''t actually send messages etc.
They have this class:
##
# This class implements semaphore for threads synchronization.
class Semaphore
##
# Initialize new semaphore
#
# val:: [Integer] number of threads, that can enter to section
def initialize(val=0)
@tickets = val
@lock = Mutex.new
@cond = ConditionVariable.new
end
##
# Waits until are available some free tickets
def wait
@lock.synchronize {
@cond.wait(@lock) while !(@tickets > 0)
@tickets -= 1
}
end
##
# Unlocks guarded section, increments number of free tickets
def run
@lock.synchronize {
@tickets += 1
@cond.signal
}
end
end
---
Met vriendelijke groeten - Best regards - Salutations
Ivan Porto Carrero
Blog: http://flanders.co.nz
Google Wave: portocarrero.ivan at googlewave.com<mailto:portocarrero.ivan at
googlewave.com>
Twitter: http://twitter.com/casualjim
Author of IronRuby in Action (http://manning.com/carrero)
On Sat, Nov 21, 2009 at 2:28 PM, Jimmy Schementi <Jimmy.Schementi at
microsoft.com<mailto:Jimmy.Schementi at microsoft.com>> wrote:
The RC1 bits will be in GIT shortly ? looks like the pushes to GIT haven?t been
happening/working. Also, the RC1 ?announcement? and other things from my
RubyConf talk will make their way online over the next couple of days, but in
short this release is ?RC1? because we want more people to start using it and
find blocking bugs. WRT xmpp4r, it?d be great if you could investigate what the
actual bug is; a small repro will drastically increase the chances of it being
fixes in the near future, especially when it?s a library failing for some
strange reasons.
~js
From: ironruby-core-bounces at rubyforge.org<mailto:ironruby-core-bounces at
rubyforge.org> [mailto:ironruby-core-bounces at
rubyforge.org<mailto:ironruby-core-bounces at rubyforge.org>] On Behalf Of
Ivan Porto Carrero
Sent: Saturday, November 21, 2009 12:06 AM
To: ironruby-core
Subject: [Ironruby-core] ironruby RC1
Hi
I don''t get any changes coming in for the repo for the last 3 days, are
those changes that make up RC1 in?
Then on a side note I''m still unable to run xmpp4r with IronRuby. it
should work but gets stuck in waiting for a thread that never returns.
---
Met vriendelijke groeten - Best regards - Salutations
Ivan Porto Carrero
Blog: http://flanders.co.nz
Google Wave: portocarrero.ivan at googlewave.com<mailto:portocarrero.ivan at
googlewave.com>
Twitter: http://twitter.com/casualjim
Author of IronRuby in Action (http://manning.com/carrero)
_______________________________________________
Ironruby-core mailing list
Ironruby-core at rubyforge.org<mailto:Ironruby-core at rubyforge.org>
http://rubyforge.org/mailman/listinfo/ironruby-core
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20091122/5fa15839/attachment-0001.html>
Push has been done. I?ve tagged it both v0.9.3 and v1.0RC1
From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Ivan Porto Carrero
Sent: Saturday, November 21, 2009 4:00 PM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] ironruby RC1
Yeah I saw that on twitter but you did make it in the end :)
Much appreciated thanks
---
Met vriendelijke groeten - Best regards - Salutations
Ivan Porto Carrero
Blog: http://flanders.co.nz
Google Wave: portocarrero.ivan at googlewave.com<mailto:portocarrero.ivan at
googlewave.com>
Twitter: http://twitter.com/casualjim
Author of IronRuby in Action (http://manning.com/carrero)
On Sat, Nov 21, 2009 at 8:50 PM, Jim Deville <jdeville at
microsoft.com<mailto:jdeville at microsoft.com>> wrote:
I?m working on automating the pushes, but they aren?t done yet, and I haven?t
had good enough internet while at RubyConf to push. Releasing was hard enough ;)
I?ll do a push tonight when I get home.
JD
From: ironruby-core-bounces at rubyforge.org<mailto:ironruby-core-bounces at
rubyforge.org> [mailto:ironruby-core-bounces at
rubyforge.org<mailto:ironruby-core-bounces at rubyforge.org>] On Behalf Of
Ivan Porto Carrero
Sent: Saturday, November 21, 2009 7:38 AM
To: ironruby-core at rubyforge.org<mailto:ironruby-core at rubyforge.org>
Subject: Re: [Ironruby-core] ironruby RC1
I know it has something to do with Threading and the value of @tickets in this
class.
I''ve just managed to connect with xmpp4r to my jabber server :=D but
then the stream is closed so you can''t actually send messages etc.
They have this class:
##
# This class implements semaphore for threads synchronization.
class Semaphore
##
# Initialize new semaphore
#
# val:: [Integer] number of threads, that can enter to section
def initialize(val=0)
@tickets = val
@lock = Mutex.new
@cond = ConditionVariable.new
end
##
# Waits until are available some free tickets
def wait
@lock.synchronize {
@cond.wait(@lock) while !(@tickets > 0)
@tickets -= 1
}
end
##
# Unlocks guarded section, increments number of free tickets
def run
@lock.synchronize {
@tickets += 1
@cond.signal
}
end
end
---
Met vriendelijke groeten - Best regards - Salutations
Ivan Porto Carrero
Blog: http://flanders.co.nz
Google Wave: portocarrero.ivan at googlewave.com<mailto:portocarrero.ivan at
googlewave.com>
Twitter: http://twitter.com/casualjim
Author of IronRuby in Action (http://manning.com/carrero)
On Sat, Nov 21, 2009 at 2:28 PM, Jimmy Schementi <Jimmy.Schementi at
microsoft.com<mailto:Jimmy.Schementi at microsoft.com>> wrote:
The RC1 bits will be in GIT shortly ? looks like the pushes to GIT haven?t been
happening/working. Also, the RC1 ?announcement? and other things from my
RubyConf talk will make their way online over the next couple of days, but in
short this release is ?RC1? because we want more people to start using it and
find blocking bugs. WRT xmpp4r, it?d be great if you could investigate what the
actual bug is; a small repro will drastically increase the chances of it being
fixes in the near future, especially when it?s a library failing for some
strange reasons.
~js
From: ironruby-core-bounces at rubyforge.org<mailto:ironruby-core-bounces at
rubyforge.org> [mailto:ironruby-core-bounces at
rubyforge.org<mailto:ironruby-core-bounces at rubyforge.org>] On Behalf Of
Ivan Porto Carrero
Sent: Saturday, November 21, 2009 12:06 AM
To: ironruby-core
Subject: [Ironruby-core] ironruby RC1
Hi
I don''t get any changes coming in for the repo for the last 3 days, are
those changes that make up RC1 in?
Then on a side note I''m still unable to run xmpp4r with IronRuby. it
should work but gets stuck in waiting for a thread that never returns.
---
Met vriendelijke groeten - Best regards - Salutations
Ivan Porto Carrero
Blog: http://flanders.co.nz
Google Wave: portocarrero.ivan at googlewave.com<mailto:portocarrero.ivan at
googlewave.com>
Twitter: http://twitter.com/casualjim
Author of IronRuby in Action (http://manning.com/carrero)
_______________________________________________
Ironruby-core mailing list
Ironruby-core at rubyforge.org<mailto:Ironruby-core at rubyforge.org>
http://rubyforge.org/mailman/listinfo/ironruby-core
_______________________________________________
Ironruby-core mailing list
Ironruby-core at rubyforge.org<mailto:Ironruby-core at rubyforge.org>
http://rubyforge.org/mailman/listinfo/ironruby-core
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20091122/fa17707b/attachment-0001.html>
The mono build is up from that one too. http://dlrci.colliertech.org/ironruby --- Met vriendelijke groeten - Best regards - Salutations Ivan Porto Carrero Blog: http://flanders.co.nz Google Wave: portocarrero.ivan at googlewave.com Twitter: http://twitter.com/casualjim Author of IronRuby in Action (http://manning.com/carrero) On Sun, Nov 22, 2009 at 10:45 AM, Jim Deville <jdeville at microsoft.com>wrote:> Push has been done. I?ve tagged it both v0.9.3 and v1.0RC1 > > > > *From:* ironruby-core-bounces at rubyforge.org [mailto: > ironruby-core-bounces at rubyforge.org] *On Behalf Of *Ivan Porto Carrero > *Sent:* Saturday, November 21, 2009 4:00 PM > > *To:* ironruby-core at rubyforge.org > *Subject:* Re: [Ironruby-core] ironruby RC1 > > > > Yeah I saw that on twitter but you did make it in the end :) > > > > Much appreciated thanks > --- > Met vriendelijke groeten - Best regards - Salutations > Ivan Porto Carrero > Blog: http://flanders.co.nz > Google Wave: portocarrero.ivan at googlewave.com > Twitter: http://twitter.com/casualjim > Author of IronRuby in Action (http://manning.com/carrero) > > > On Sat, Nov 21, 2009 at 8:50 PM, Jim Deville <jdeville at microsoft.com> > wrote: > > I?m working on automating the pushes, but they aren?t done yet, and I > haven?t had good enough internet while at RubyConf to push. Releasing was > hard enough ;) > > > > I?ll do a push tonight when I get home. > > > > JD > > > > *From:* ironruby-core-bounces at rubyforge.org [mailto: > ironruby-core-bounces at rubyforge.org] *On Behalf Of *Ivan Porto Carrero > *Sent:* Saturday, November 21, 2009 7:38 AM > *To:* ironruby-core at rubyforge.org > *Subject:* Re: [Ironruby-core] ironruby RC1 > > > > I know it has something to do with Threading and the value of @tickets in > this class. > > I''ve just managed to connect with xmpp4r to my jabber server :=D but then > the stream is closed so you can''t actually send messages etc. > > > > They have this class: > > > > ## > > # This class implements semaphore for threads synchronization. > > class Semaphore > > > > ## > > # Initialize new semaphore > > # > > # val:: [Integer] number of threads, that can enter to section > > def initialize(val=0) > > @tickets = val > > @lock = Mutex.new > > @cond = ConditionVariable.new > > end > > > > ## > > # Waits until are available some free tickets > > def wait > > @lock.synchronize { > > @cond.wait(@lock) while !(@tickets > 0) > > @tickets -= 1 > > } > > end > > > > ## > > # Unlocks guarded section, increments number of free tickets > > def run > > @lock.synchronize { > > @tickets += 1 > > @cond.signal > > } > > end > > end > > --- > Met vriendelijke groeten - Best regards - Salutations > Ivan Porto Carrero > Blog: http://flanders.co.nz > Google Wave: portocarrero.ivan at googlewave.com > Twitter: http://twitter.com/casualjim > Author of IronRuby in Action (http://manning.com/carrero) > > On Sat, Nov 21, 2009 at 2:28 PM, Jimmy Schementi < > Jimmy.Schementi at microsoft.com> wrote: > > The RC1 bits will be in GIT shortly ? looks like the pushes to GIT haven?t > been happening/working. Also, the RC1 ?announcement? and other things from > my RubyConf talk will make their way online over the next couple of days, > but in short this release is ?RC1? because we want more people to start > using it and find blocking bugs. WRT xmpp4r, it?d be great if you could > investigate what the actual bug is; a small repro will drastically increase > the chances of it being fixes in the near future, especially when it?s a > library failing for some strange reasons. > > > > ~js > > > > *From:* ironruby-core-bounces at rubyforge.org [mailto: > ironruby-core-bounces at rubyforge.org] *On Behalf Of *Ivan Porto Carrero > *Sent:* Saturday, November 21, 2009 12:06 AM > *To:* ironruby-core > *Subject:* [Ironruby-core] ironruby RC1 > > > > Hi > > > > I don''t get any changes coming in for the repo for the last 3 days, are > those changes that make up RC1 in? > > > > Then on a side note I''m still unable to run xmpp4r with IronRuby. it should > work but gets stuck in waiting for a thread that never returns. > > > > > > > --- > Met vriendelijke groeten - Best regards - Salutations > Ivan Porto Carrero > Blog: http://flanders.co.nz > Google Wave: portocarrero.ivan at googlewave.com > Twitter: http://twitter.com/casualjim > Author of IronRuby in Action (http://manning.com/carrero) > > > _______________________________________________ > Ironruby-core mailing list > Ironruby-core at rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core > > > > > _______________________________________________ > Ironruby-core mailing list > Ironruby-core at rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core > > > > _______________________________________________ > Ironruby-core mailing list > Ironruby-core at rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20091122/d4178fc8/attachment.html>