[Ironruby-core] Any coming IronRuby releases fixing igem this year?

Shay Friedman shay.friedman at gmail.com
Sat Dec 18 09:18:02 EST 2010


My repo is synced with the recent changes and I still get the same error
(which originates from a different one as I stated above)...

Shay.



On Sat, Dec 18, 2010 at 12:09 PM, Mohamed Meligy <eng.meligy at gmail.com>wrote:

> @Tomas,
> Thanks a lot. I'm checking that now.
>
> @Shay
> Can you please confirm your repo is in sync and see if the problem is still
> the same for you?
> I'll be checking too, but if I get issues, will not be sure it's code issue
> not me missing an instruction or so.
>
> Thanks a lot everyone.
>
> Regards,
>
>
>
> *Mohamed Meligy
> *Readify | Senior Developer
>
> M:+61 451 835006 | W: www.readify.net
> [image: Description: Description: Description: Description: rss_16]  [image:
> Description: Description: Description: Description:
> cid:image003.png at 01CAF81D.6A076510] <http://www.linkedin.com/in/meligy>  [image:
> Description: Description: Description: Description:
> cid:image005.png at 01CAF81D.6A076510] <http://twitter.com/meligy>
>  <http://www.greatplacetowork.com.au/best/best-companies-australia.php><http://www.readify.net/AboutUs/NewsItem.aspx?id=10>
>
>
>
> On Sat, Dec 18, 2010 at 4:32 AM, Tomas Matousek <
> Tomas.Matousek at microsoft.com> wrote:
>
>>  The fix is already checked into the main. So if there is still any
>> problem it's another bug.
>>
>>
>>
>> Build instructions are here:
>>
>>
>>
>> http://github.com/IronLanguages/main/wiki/Building
>>
>>
>>
>> let me know if anything there is not clear or doesn't work.
>>
>>
>>
>> Tomas
>>
>>
>>  ------------------------------
>> *From:* ironruby-core-bounces at rubyforge.org [
>> ironruby-core-bounces at rubyforge.org] on behalf of Mohamed Meligy [
>> eng.meligy at gmail.com]
>> *Sent:* Friday, December 17, 2010 6:05 AM
>>
>> *To:* ironruby-core at rubyforge.org
>> *Subject:* Re: [Ironruby-core] Any coming IronRuby releases fixing igem
>> this year?
>>
>>   @Tomas, if it works on your local machine, maybe it's worth checking it
>> out and having a 1.1.2 release.
>> If your local repository is in sync already, then maybe there is some
>> other issues that needs to be fixed.
>>
>>  If this is easy as repositories sync issue of existing working fix or
>> so, would really appreciate a 1.1.2 update. I'm new to Ruby and Rails and
>> would love to try the IronRuby Rails integration even better with Visual
>> Studio.
>>
>>  I'm kind of lost in the source too. Not sure which VS solutions I should
>> build and where the output Ruby\bin kind-of-directory would then be, neither
>> how to get the MSI file for VS tools.
>> Will be great if there is some explanation to this (forgive me if it's
>> some readme already in the source), or else, then another release will be
>> much easier to deal with.
>>
>>
>>  Thanks a lot.
>>
>>
>>  Regards,
>>
>>
>>
>> *Mohamed Meligy
>> *Readify | Senior Developer
>>
>> M:+61 451 835006 | W: www.readify.net
>> [image: Description: Description: Description: Description: rss_16]  [image:
>> Description: Description: Description: Description:
>> cid:image003.png at 01CAF81D.6A076510] <http://www.linkedin.com/in/meligy>  [image:
>> Description: Description: Description: Description:
>> cid:image005.png at 01CAF81D.6A076510] <http://twitter.com/meligy>
>>  <http://www.greatplacetowork.com.au/best/best-companies-australia.php><http://www.readify.net/AboutUs/NewsItem.aspx?id=10>
>>
>>
>>
>> On Fri, Dec 17, 2010 at 8:46 PM, Albert-Jan Pieter Nijburg <
>> albertjan at curit.com> wrote:
>>
>>>  Hey,
>>>
>>>
>>>
>>> I looked into this also and read_nonblock will still return 0 bytes
>>> sometimes. I made a small hack in SocketStream.cs that forces the socket to
>>> return more than 0 bytes.
>>>
>>>
>>>
>>>             *if* (bytesToRead > 0) {
>>>
>>>                 while(oldPos == _pos) {
>>>
>>>                     _pos += _socket.Receive(readBuffer, bytesToRead,
>>> SocketFlags.None);
>>>
>>>                 }
>>>
>>>             }
>>>
>>>
>>>
>>> I know this is absolutely not the way to fix it but it does specify the
>>> source of the exception maybe a bit better.
>>>
>>>
>>>
>>> Regards,
>>>
>>>
>>>
>>> Albert-Jan
>>>
>>>
>>>
>>> *Van:* ironruby-core-bounces at rubyforge.org [mailto:
>>> ironruby-core-bounces at rubyforge.org] *Namens *Tomas Matousek
>>> *Verzonden:* vrijdag 17 december 2010 9:14
>>> *Aan:* ironruby-core at rubyforge.org
>>> *Onderwerp:* Re: [Ironruby-core] Any coming IronRuby releases fixing
>>> igem this year?
>>>
>>>
>>>
>>> I believe I fixed this in main. So if you download the sources and build
>>> it should work.
>>>
>>> Let me know if it works for you. Maybe we should do a 1.1.2 release
>>> soon - it should be pretty easy - it might ease adoption of 1.1.
>>>
>>>
>>>
>>> Tomas
>>>
>>>
>>>   ------------------------------
>>>
>>> *From:* ironruby-core-bounces at rubyforge.org [
>>> ironruby-core-bounces at rubyforge.org] on behalf of Mohamed Meligy [
>>> eng.meligy at gmail.com]
>>> *Sent:* Thursday, December 16, 2010 4:29 PM
>>> *To:* ironruby-core at rubyforge.org
>>> *Subject:* [Ironruby-core] Any coming IronRuby releases fixing igem this
>>> year?
>>>
>>> Hello all,
>>>
>>> I noticed IronRuby 1.1.1 has problems in igem where it fails to installs
>>> gems due to some conversion issue from nil to string. IronRuby 1.0 is
>>> compatible with Ruby 1.8.x which can run Rails 2.x not Rails 3.0.
>>>
>>>
>>>
>>> I'm interested in learning Rails 3.0 on IronRuby and see how I can
>>> integrate .NET stuff with that.
>>>
>>>
>>>
>>>
>>>
>>> So, is there any coming patch release or even git code push that solves
>>> the igem issues?
>>>
>>>
>>>
>>>
>>>
>>> Will be great if I get something to play with in Christmas holidays, but
>>> this might be very unrealistic anyway.
>>>
>>>
>>>
>>>
>>>
>>> Thanks a lot.
>>>
>>>
>>>
>>> Regards,
>>>
>>>
>>>
>>> *Mohamed Meligy
>>> *Readify | Senior Developer
>>>
>>> M:+61 451 835006 | W: www.readify.net
>>>
>>> [image: Beschrijving: Description: Description: Description: Description:
>>> rss_16]  [image: Beschrijving: Description: Description: Description:
>>> Description: cid:image003.png at 01CAF81D.6A076510]<http://www.linkedin.com/in/meligy>
>>>   [image: Beschrijving: Description: Description: Description:
>>> Description: cid:image005.png at 01CAF81D.6A076510]<http://twitter.com/meligy>
>>> [image: Beschrijving:
>>> http://gurustop.net/mail/signature/readify-50best.jpg]<http://www.greatplacetowork.com.au/best/best-companies-australia.php>[image:
>>> Beschrijving: http://gurustop.net/mail/signature/readify-partner2010.png]<http://www.readify.net/AboutUs/NewsItem.aspx?id=10>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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/20101218/f5686354/attachment.html>


More information about the Ironruby-core mailing list