he initial definition, and then "gbd buildpackage
--git-pbuilder" to actually build it)
Cheers
--
Ola Bini
definition repository to match this. I
couldn't find any documentation that describes what needs to be done -
is it available somewhere?
Cheers
--
Ola Bini
by the Go team
immediately?
Thanks
--
Ola Bini
signature.asc
Description: PGP signature
work very soon. We are of course using
these experiences in our thinking around the design of the API for libotr-ng.
Cheers
--
Ola Bini (https://olabini.se)
"Yields falsehood when quined" yields falsehood when quined.
signature.asc
Description: PGP signature
___
nd
specualtive. Something to discuss over a beer sometime instead,
maybe. =)
Cheers
--
Ola Bini (https://olabini.se)
"Yields falsehood when quined" yields falsehood when quined.
signature.asc
Description: PGP signature
___
OTR-dev mailing list
OTR-dev@lists.cypherpunks.ca
http://lists.cypherpunks.ca/mailman/listinfo/otr-dev
ies.
> That means I do trust them to bundle only stuff they care about and
> understand.
I strongly disagree. No matter how skilled a developer is, a larger
library means more internal complexity, something that has been shown
increases the likelihood of bugs. I don't trust any developer, no
ma
t; surprising and abrupt to me, but that's all I know.
Yeah, I've heard similar things from other users of Conversations. I
do know that the main developer have been quite unhappy with OTR for a
long time, and have mentioned it in presentations and so on. But there
seems to be very little evid
and
OMEMO at several times. I would characterize those interactions as not
being super constructive.
Cheers
--
Ola Bini (https://olabini.se)
"Yields falsehood when quined" yields falsehood when quined.
signature.asc
Description: PGP signature
__
and v4 have
significant differences, so there wouldn't be that much shared code
paths.
For us, #3 struck the right balance between user functionality and
maintenance ease for the developers.
Hope that helps!
Cheers
--
Ola Bini (https://olabini.se)
"Yields falsehood when quined&qu
milar API to libotr is incredibly important for adoption.
You can find it here https://github.com/otrv4/libotrv4
It's currently not anywhere near complete - we are planning on pushing
forward on that work now that I have a fairly stable version of the
specification.
Cheers
--
Ola Bini (https://o
Tor meeting in Amsterdam, so perhaps Ola, he,
> and any other interested parties could set aside some time to go over
> the document (or an iterated version of it) in person there?
Me, Iv=E1n and Yakira will all be attending the Tor meeting, so we
should be able to have a discussion there - b
l achieve broad consensus on this specification -
and once that happens it will be published on the OTR web page as the
official specification for version 4. If you think it would help
understanding to have a temporary code name we could absolutely do
that - but at the moment I don't exactly see the p
Hi Paul,
My name is Ola Bini - I am part of the STRIKE team that has done this
work.
> So I am very confused about this specification. This is your version of
> what you would like to be otrv4, but you are not the OTR team, so this
> is not anything "official" ?
> Can the content be committed to the github repo?
Did you even look in the repo?
https://github.com/agl/pond/tree/master/doc
Cheers
--
Ola Bini (https://olabini.se)
"Yields falsehood when quined" yields falsehood when quined.
signature.asc
Description: PGP signature
ill we hit a guard that satisfies us, or should we sample
> directly from the correct set (e.g. only from the set of IPv6 guards). I'm
> still not sure about this.
I'm much more in favor of sampling in general, rather than trying to
hit the specific thing. If we sample in general, we will not skew the
ear more frequently than we would like.
I'm not sure we can do this - a lot of the filters will be based on
backwards compatibility with the existing Tor configuration options,
things such as ReachableAddresses - I'm not sure how to reasonably
enumerate all possibilities in a useful way.
Cheers
--
ems you don't like that idea - there seems
to be some dissent among the Tor devs which approach is best for this situation.
Cheers
--
Ola Bini (https://olabini.se)
"Yields falsehood when quined" yields falsehood when quined.
signature.asc
Description: PGP signature
_
dcode
> their guard. It's used a lot by people currently.
Yeah. Is the guard picked randomly from this list, or using something
more complicated?
> > - UseEntryGuardsAsDirGuards
> > I don't understand exactly what this settings does.
>
> I'm not sure either. I'd just let it keep t
--
Ola Bini (https://olabini.se)
"Yields falsehood when quined" yields falsehood when quined.
signature.asc
Description: PGP signature
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
Hi,
Just keep in mind cultural connotations of colors - and also the high
rate of red-green color blindness in men.
Cheers
--
Ola Bini (https://olabini.se)
"Yields falsehood when quined" yields falsehood when quined.
signature.asc
Description: PGP
too many guards or too many of them disappear.
>
> I don't have a strong opinion here.
Me neither. I think a percentage is a good starting point - it feels
easier to tweak in different ways.
> It seems to me that the value 20 here could get reduced to something like 5 or
> even less. Of course 5 is also an arbitrary value and to actually find out the
> "best" number here we should test the algorithm ourselves in various network
> types.
Arbitrarily changed to 5. =)
Cheers
--
Ola Bini (https://olabini.se)
"Yields falsehood when quined" yields falsehood when quined.
signature.asc
Description: PGP signature
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
Great, lots of good comments. I'll respond in depth once the fever has
left my brain! =D
On Thu, Mar 03, 2016 at 03:15:26PM +0100, George Kadianakis wrote:
> Ola Bini <ob...@thoughtworks.com> writes:
>
> > Hi,
>
> Here are some more comments to the latest version
e in STATE_RETRY_ONLY and
> we manage to connect to a non-primary guard, we hang up the connection, and go
> back into STATE_PRIMARY_GUARDS.
Maybe. Should we do this only in STATE_RETRY_ONLY or for the UTOPIC
and DYSTOPIC states as well?
Cheers
--
Ola Bini (https://olabini.se)
"Yield
.
- We might be able to start implementing this in tor proper tomorrow
- or wednesday hopefully.
From now, the team will take over most communication.
Cheers
--
Ola Bini (https://olabini.se)
"Yields falsehood when quined" yields falsehood when quined.
signature.asc
Description: PGP
dystopic conditions, then this heuristic will
make it more likely we will faster find a guard to connect to.
> > ALGO_CHOOSE_ENTRY_GUARD_END:
> > If circuit is set up correctly, let algorithm know
> > Algorithm marks the guard chosen as used and makes sure i
Hi again,
Here is the newest version of the algorithm:
https://gist.github.com/olabini/343da01de8e01491bf5c
The biggest change is the addition of the state
STATE_TRY_ONLY_TRIED. Once it enters this state, it will never exit it
again.
Cheers
--
Ola Bini (https://olabini.se)
"Yields fals
Ah, good point. So, it seems N_PRIMARY_GUARDS is an argument to the algorithm.
Cheers
--
Ola Bini (https://olabini.se)
"Yields falsehood when quined" yields falsehood when quined.
signature.asc
Description: PGP signature
___
tor-dev ma
Hi,
Here is the next version of the algorithm - put it in a gist to make
it easier to look at:
https://gist.github.com/olabini/343da01de8e01491bf5c
Cheers
--
Ola Bini (https://olabini.se)
"Yields falsehood when quined" yields falsehood when quined.
signature.asc
Descri
me till we manage to recover from flaky network
>
> and I can also think of security related stats like:
>
> * Number of guards we tried before succeeding first circuit
> * Number of guards we exposed ourselves to after time t
Haven't thought abou that yet - we currently only
/protocol-otr-extension-j.md
I would appreciate thoughts and comments.
We have a more or less complete implementation of this for our OTR
Golang implementation (barring some updates) - and it seems to work
really well.
Cheers
--
Ola Bini (https://olabini.se)
"Yields falsehood when quined&qu
cond value is vaguely specified on purpose,
since it will be always be subjective to the local peers situation.
So - is this proposal completely stupid, or something others think would be=
valuable as well?
Thoughts?
--
Ola Bini (https://olabini.se)
"Yields falsehood when quined" y
Hi,
I'm finally about to get back to hacking on Seph, specifically looking
at performance - I would really like to be able to run the latest
changes (things for u2 related to invoke dynamic) in MacOS X - what is
the current status of this, and is it even possible at the moment?
Cheers
--
Ola
On 2011-07-28 10.11, Christian Thalinger wrote:
On Jul 28, 2011, at 6:10 PM, Ola Bini wrote:
The bad performance sounds like something is not inlined at all.
How are you invoking valueMH? Via invokedynamic or a direct MH
call?
valueMH is combined with an exactInvoker and then chained
performance change at all.
So now I'm a bit lost - I have no idea why this is so much slower than
the explicit bytecode. Any thoughts? My next attack will be to go and
compare the assembler.
Cheers
--
Ola Bini (http://olabini.com)
Ioke - JRuby - ThoughtWorks
Yields falsehood when quined
Please try out the patch. I've also updated the mlvm patches to the
latest bsd-port which (quite awesomely) is b146.
It runs fine for me.
Cheers
--
Ola Bini (http://olabini.com)
Ioke - JRuby - ThoughtWorks
Yields falsehood when quined yields falsehood when quined
): This is not a formal review request yet,
but please make a pre-review.
John, good stuff! This runs nicely for me without putting things on the
BCP. As far as I can tell, the class-not-found error is gone.
Cheers
--
Ola Bini (http://olabini.com)
Ioke - JRuby - ThoughtWorks
Yields falsehood when quined
in the JUnit run that it's not on the bootclasspath.
Cheers
On 2011-06-14 01.22, John Rose wrote:
On Jun 13, 2011, at 8:37 AM, Ola Bini wrote:
On 2011-06-13 10.14, Ola Bini wrote:
I did a rebuild of MLVM+bsdport today, and I now see the missing
class crash again on my Mac too (to clarify
a new instance of the compiled
implementation of the inner abstraction.
Hope this helps.
Cheers
On 2011-06-14 01.22, John Rose wrote:
On Jun 13, 2011, at 8:37 AM, Ola Bini wrote:
On 2011-06-13 10.14, Ola Bini wrote:
I did a rebuild of MLVM+bsdport today, and I now see the missing
class crash
On 2011-06-13 03.44, John Rose wrote:
On Jun 11, 2011, at 1:31 PM, Ola Bini wrote:
Asking here too: is that still happening? -- Christian
I haven't seen any commits that is likely to fix it, but I will rebuild
and take a look today.
The commits for 7047697 and 7052202 both fix crashes
On 2011-06-13 10.14, Ola Bini wrote:
On 2011-06-13 03.44, John Rose wrote:
On Jun 11, 2011, at 1:31 PM, Ola Bini wrote:
Asking here too: is that still happening? -- Christian
I haven't seen any commits that is likely to fix it, but I will rebuild
and take a look today.
The commits
On 2011-06-04 01.47, John Rose wrote:
On Jun 3, 2011, at 7:07 AM, Ola Bini wrote:
Is there anything I can do to help out with finding this problem?
I can't reproduce the VM crash yet. Like Christian, I got through
problems 1 and 2, on bsd (both 32-bit and 64-bit).
Problem 3 generates
On 2011-06-02 12.53, Ola Bini wrote:
On 2011-06-02 11.59, John Rose wrote:
I was hoping your crash would go away with today's patches. I'll look into
it.
I did a build after today's patches. Still same problem:
java.lang.NoClassDefFoundError: seph/lang/SephObject
[junit
direction at least. Is there
anything I can do to help diagnose this crash?
Cheers
--
Ola Bini (http://olabini.com)
Ioke - JRuby - ThoughtWorks
Yields falsehood when quined yields falsehood when quined.
#
# A fatal error has been detected by the Java Runtime Environment:
#
# Internal Error
I ran the compile against what's in b144, but directly from the JDK7 repo
On 2011-05-27 12.26, John Rose wrote:
On May 26, 2011, at 11:38 PM, Ola Bini wrote:
It seems there is still a difference in how asType MHs work between what
is in current JDK7 repo, and what you get from building
On 2011-05-27 12.53, John Rose wrote:
On May 27, 2011, at 12:11 AM, Ola Bini wrote:
I ran the compile against what's in b144, but directly from the
JDK7 repo
On 2011-05-27 12.26, John Rose wrote:
On May 26, 2011, at 11:38 PM, Ola Bini wrote:
Caused
On 2011-05-27 12.59, John Rose wrote:
On May 27, 2011, at 12:26 AM, Ola Bini wrote:
type() is just a call site type, so that will be the
SephObject,SThread etc.
Good. So what's the code that creates the target (not the fallback)?
It looks like it has its types denatured to Object
by default.
If you want to build without coro set uyur guards like this:
export davinci=$(pwd) guards=buildable testable /coro
Thanks Stephen,
I didn't know it was included by default. =)
Cheers
- --
Ola Bini (http://olabini.com)
Ioke - JRuby - ThoughtWorks
Yields falsehood when quined
Hi,
I just updated to the latest version of bsdport+mlvm-coro. It seems that
the latest merge has removed all the breakages I was experiencing. Thanks!
Cheers
--
Ola Bini (http://olabini.com)
Ioke - JRuby - ThoughtWorks
Yields falsehood when quined yields falsehood when quined
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-05-28 10.39, Ola Bini wrote:
Hi,
I just updated to the latest version of bsdport+mlvm-coro. It seems that
the latest merge has removed all the breakages I was experiencing. Thanks!
Cheers
Terribly sorry - I spoke to soon. It is gone
, Ola Bini ola.b...@gmail.com wrote:
On 2011-05-28 10.39, Ola Bini wrote:
Hi,
I just updated to the latest version of bsdport+mlvm-coro. It seems that
the latest merge has removed all the breakages I was experiencing. Thanks!
Cheers
Terribly sorry - I spoke to soon. It is gone from bsdport
-a)
Cheers
--
Ola Bini (http://olabini.com)
Ioke - JRuby - ThoughtWorks
Yields falsehood when quined yields falsehood when quined.
___
mlvm-dev mailing list
mlvm-dev@openjdk.java.net
http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
Hi,
Just to clarify, my builds are against the current patchset in the MLVM
repository, so that might explain why you're not seeing these problems.
Cheers
On 2011-05-25 14.29, Christian Thalinger wrote:
On May 25, 2011, at 5:58 AM, Ola Bini wrote:
Hi,
There are at least three problems
drop, but it's not bsdport with mlvm either.
Cheers
On 2011-05-25 14.29, Christian Thalinger wrote:
On May 25, 2011, at 5:58 AM, Ola Bini wrote:
Hi,
There are at least three problems that are still there. They might be
connected, or not.
(I will tell you how to reproduce these at the end)
I
the information is available anyway,
it'd make sense to make it easily accessible.
I'm not against it. =)
Cheers
- --
Ola Bini (http://olabini.com)
Ioke - JRuby - ThoughtWorks
Yields falsehood when quined yields falsehood when quined.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (Darwin
, insertArguments(findVirtual(SephObject.class,
invocationFor, SephObject.class, int.class), 1, arity()));
}
Obviously this is a bit simplified, but the key insight is that you can
use findVirtual to lookup a method handle to MethodHandle.invoke of any
arity you want.
Cheers
--
Ola Bini (http
on the receiver
and not on the receiver class (or prototype).
Because I'm building a prototype based language and the behavior is
decided by the result of the invocationFor method.
Cheers
--
Ola Bini (http://olabini.com)
Ioke - JRuby - ThoughtWorks
Yields falsehood when quined yields falsehood when
On 2011-05-25 10.50, John Rose wrote:
On May 23, 2011, at 7:33 PM, Ola Bini wrote:
Have you seen any reason why that happens?
There are some known problems (crashers even) with method handle
compilation.
The permuteArguments transform has a bug when you mix long/doubles
and other
://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
--
Ola Bini (http://olabini.com)
Ioke - JRuby - ThoughtWorks
Yields falsehood when quined yields falsehood when quined.
___
mlvm-dev mailing list
mlvm-dev@openjdk.java.net
http://mail.openjdk.java.net
.activateWith(Unknown Source)
at seph.lang.ast.NamedMessage.go(NamedMessage.java:162)
at seph.lang.ast.NamedMessage.sendTo(NamedMessage.java:143)
at
seph.lang.interpreter.MessageInterpreter.evaluateFully(MessageInterpreter.java:92)
=(
Cheers
--
Ola Bini (http://olabini.com)
Ioke
:1692)
at seph.lang.compiler.Bootstrap.tailCallFallback(Bootstrap.java:949)
at seph$gen$abstraction$0.activateWith(Unknown Source)
at seph$gen$abstraction$0.activateWith(Unknown Source)
Is this an actual limit, and will it be lifted at some point?
Cheers
--
Ola Bini (http
On 2011-05-19 23.23, Charles Oliver Nutter wrote:
On Thu, May 19, 2011 at 12:51 PM, Ola Bini ola.b...@gmail.com wrote:
I'm currently getting this error:
Caused by: java.lang.IllegalArgumentException: too many values to insert
:
Confirmed here too. And since it wiped out my previous copy I'm dead
in the water at the moment :(
- Charlie
On Tue, May 17, 2011 at 8:24 AM, Ola Bini ola.b...@gmail.com wrote:
Hi,
It seems something has introduced a failure. Updating from the bsdport
and patches repo with default settings
' is dangerous,
better use `mkstemp'
/usr/bin/ld: BFD 2.17.50.0.6-14.el5 20061020 internal error, aborting at
../../bfd/elflink.c line 6841 in elf_link_check_versioned_symbol
/usr/bin/ld: Please report this bug.
This used to build fine a month or so ago.
Cheers
--
Ola Bini (http://olabini.com)
Ioke
is saved as:
# [thread -1339240448 also had an error]
#
# If you would like to submit a bug report, please visit:
# http://bugreport.sun.com/bugreport/crash.jsp
Cheers
--
Ola Bini (http://olabini.com)
Ioke - JRuby - ThoughtWorks
Yields falsehood when quined yields falsehood when quined
--
Ola Bini (http://olabini.com)
Ioke - JRuby - ThoughtWorks
Yields falsehood when quined yields falsehood when quined.
___
mlvm-dev mailing list
mlvm-dev@openjdk.java.net
http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
:
return identity(type).bindTo(w.convert(value, type));
has to become
return insertArguments(identity(type), 0, w.convert(value,
type));
Correct?
Rémi
On 04/05/2011 02:55 PM, Ola Bini wrote:
Stephen et al,
I did a new build with the indy patch sets yesterday. Just
for JSR 292
! netbeans/meth/nbproject/project.properties
___
mlvm-dev mailing list
mlvm-dev@openjdk.java.net
http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
- --
Ola Bini (http://olabini.com)
Ioke - JRuby - ThoughtWorks
Yields
that is so a class won't be loaded twice.
Cheers
- --
Ola Bini (http://olabini.com)
Ioke - JRuby - ThoughtWorks
Yields falsehood when quined yields falsehood when quined.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Mozilla - http
://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
___
mlvm-dev mailing list
mlvm-dev@openjdk.java.net
http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
- --
Ola Bini (http://olabini.com)
Ioke - JRuby - ThoughtWorks
Yields falsehood when quined yields
() { } unless
args.first.is_a? Symbol
That is, I just add an empty tap call...
Has anyone seen this? Any guesses on what causes it? I'll post a JIRA
unless someone has an obvious solution to this.
Cheers
- --
Ola Bini (http://olabini.com)
Ioke - JRuby - ThoughtWorks
Yields falsehood when quined yields
Bini
Assignee: Ola Bini
Priority: Minor
If doing a File.expand_path on a path beginning with classpath: it won't do
the right thing.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http
Oh, and the 1.5.2 tag seems to have the same problem.
On 2010-09-13 16.53, Ola Bini wrote:
Haven't built JRuby in a while, and now suddenly I have problems running
the test suite. Specifically, it hangs for Java 6 during the Testsuite:
org.jruby.test.JRubyTestSuite step. Is anyone else seeing
Components: Core Classes/Modules
Affects Versions: JRuby 1.5.2
Reporter: Ola Bini
Assignee: Ola Bini
On Windows, a call to openSelector() on SelectorProvider can sometimes (very
seldom - depending on resources on the machine) throw an IOException that says
Unable to establish
just stopped doing it period, without
the enable_object_features call. I think that would make the transition
easier.
Cheers
--
Ola Bini (http://olabini.com)
Ioke - JRuby - ThoughtWorks
Yields falsehood when quined yields falsehood when quined
removed the gem while sorting out this issue?
Cheers
--
Ola Bini (http://olabini.com)
Ioke - JRuby - ThoughtWorks
Yields falsehood when quined yields falsehood when quined.
-
To unsubscribe from this list, please visit:
http
We should have tags for 1.9 specs
-
Key: JRUBY-4426
URL: http://jira.codehaus.org/browse/JRUBY-4426
Project: JRuby
Issue Type: Task
Components: Ruby 1.9, RubySpec
Reporter: Ola Bini
in the repository. That might also
make it easier to handle them.
Cheers
--
Ola Bini (http://olabini.com)
Ioke creator (http://ioke.org)
JRuby Core Developer (http://jruby.org)
Developer, ThoughtWorks Studios (http://studios.thoughtworks.com)
Practical JRuby on Rails (http://apress.com/book/view
to Object, Class,
Module, etc. It keeps Ruby from returning singleton methods for these
classes, as an example.
Is there a similar concept in JRuby, or does it need to be built? Or is
there another (better) way?
What flag exactly is it you're trying to mimic?
--
Ola Bini (http://olabini.com)
Ioke
something new.
Hey,
I didn't get very far - but there's at least a start at something like
it, with Ribs - which can be found in my github:
http://github.com/olabini/ribs
Cheers
--
Ola Bini (http://olabini.com)
Ioke creator (http://ioke.org)
JRuby Core Developer (http://jruby.org)
Developer
Ola Bini wrote:
I replaced our method tables with tries a few years back. The
performance ended up being quite bad since the trie implementation
need to handle more than just alphabetic characters, so each trie node
needs to have an internal array that is a bit too large. Array lookup
is also
is the size and array lookup.
And since my experiences trying this, as I mentioned earlier, it ended
up significantly worse.
Cheers
--
Ola Bini (http://olabini.com)
Ioke creator (http://ioke.org)
JRuby Core Developer (http://jruby.org)
Developer, ThoughtWorks Studios (http
done it. =)
Cheers
--
Ola Bini (http://olabini.com)
Ioke creator (http://ioke.org)
JRuby Core Developer (http://jruby.org)
Developer, ThoughtWorks Studios (http://studios.thoughtworks.com)
Practical JRuby on Rails (http://apress.com/book/view/9781590598818)
Yields falsehood when quined yields
that are there for 1.8.7 compatibility.
Cheers
--
Ola Bini (http://olabini.com)
Ioke creator (http://ioke.org)
JRuby Core Developer (http://jruby.org)
Developer, ThoughtWorks Studios (http://studios.thoughtworks.com)
Practical JRuby on Rails (http://apress.com/book/view/9781590598818)
Yields
want to make the
choice without the debate!
--
Ola Bini (http://olabini.com)
Ioke creator (http://ioke.org)
JRuby Core Developer (http://jruby.org)
Developer, ThoughtWorks Studios (http://studios.thoughtworks.com)
Practical JRuby on Rails (http://apress.com/book/view/9781590598818)
Yields
1.8.7
Reporter: Ola Bini
Fix For: JRuby 1.4
Two failures in Enumerable:
{noformat}
1)
Enumerable#cycle loops indefinitely if no argument or nil argument FAILED
Expected nil
to equal 42
/Users/olabini/workspace/mspec/lib/mspec/expectations/expectations.rb:15:in
`fail_with
Reporter: Ola Bini
Fix For: JRuby 1.4
{noformat}
1)
ConditionVariable#broadcast should return self if nothing to broadcast to FAILED
Expected []
to equal #ConditionVariable:0x10 @waiters=[]
/Users/olabini/workspace/mspec/lib/mspec/expectations/expectations.rb:15:in
`fail_with
New RubySpec failure in Rational
Key: JRUBY-3855
URL: http://jira.codehaus.org/browse/JRUBY-3855
Project: JRuby
Issue Type: Bug
Components: Ruby 1.8.7
Reporter: Ola Bini
Just for those who are interested in looking at 1.8.7 - I will tackle
the Enumerable failures today. They stand for the bulk of all the failures.
I'll be doing that for most of the work day European time.
I'll be on IRC if there are any questions.
Cheers
--
Ola Bini (http://olabini.com)
Ioke
should just
aim to fix all the buggy behavior.
So. Votes: bug compatibility or not?
Cheers
--
Ola Bini (http://olabini.com)
Ioke creator (http://ioke.org)
JRuby Core Developer (http://jruby.org)
Developer, ThoughtWorks Studios (http://studios.thoughtworks.com)
Practical JRuby on Rails (http
Ola Bini wrote:
Hi,
In the process of porting to 1.8.7 it has become obvious that most of
our remaining tags for specs are based on pieces that are marked as
ruby_bug in the specs.
I would like to open up the discussion of whether JRuby should be
bug-by-bug compliant with a specific
--
Ola Bini (http://olabini.com)
Ioke creator (http://ioke.org)
JRuby Core Developer (http://jruby.org)
Developer, ThoughtWorks Studios (http://studios.thoughtworks.com)
Practical JRuby on Rails (http://apress.com/book/view/9781590598818)
Yields falsehood when quined yields falsehood when quined
if that
will propagate automatically to github - but otherwise people will just
have to work against kenai.
I decided to do a branch, since the breakage will be quite substantial.
Cheers
--
Ola Bini (http://olabini.com)
Ioke creator (http://ioke.org)
JRuby Core Developer (http://jruby.org)
Developer
report it to Matz co.
Make sure you're comparing with the most current 1.8.7 patchlevel, btw.
- Charlie
I'm already doing it on a branch since there are so many failures. Would
like to stabilize that before merging. See my earlier email.
I'm using the latest release.
Cheers
--
Ola Bini (http
Rubyspec: ARGF specs make loads of other tests fail
---
Key: JRUBY-3841
URL: http://jira.codehaus.org/browse/JRUBY-3841
Project: JRuby
Issue Type: Bug
Reporter: Ola Bini
jruby.properties to be 1.8.7 instead, we end up at:
2806 files, 4955 examples, 12400 expectations, 85 failures, 303 errors
Which is actually not bad at all.
Cheers
--
Ola Bini (http://olabini.com)
Ioke creator (http://ioke.org)
JRuby Core Developer (http://jruby.org)
Developer, ThoughtWorks Studios
,
--Vladimir
Nice, then we should just get started.
Merging the stdlib is one part of it, of course.
Cheers
--
Ola Bini (http://olabini.com)
Ioke creator (http://ioke.org)
JRuby Core Developer (http://jruby.org)
Developer, ThoughtWorks Studios (http://studios.thoughtworks.com)
Practical JRuby
Hi,
Not sure if we ever reached a consensus on 1.8.7.
A typical problem point is that the new Hpricot is using some 1.8.7
features (such as String#lines).
Should we start making things 1.8.7 compatible or not? If not, how
should we handle libraries like these?
Cheers
--
Ola Bini (http
heard about Matz asking people
to report any remaining incompatibilities between 1.8.6 and 1.8.7,
nobody has been able to point out a single thing.
I vote we go straight-up 1.8.7.
+1
--
Ola Bini (http://olabini.com)
Ioke creator (http://ioke.org)
JRuby Core Developer (http://jruby.org
this list, please visit:
http://xircles.codehaus.org/manage_email
--
Yehuda Katz
Developer | Engine Yard
(ph) 718.877.1325
--
Ola Bini (http://olabini.com)
Ioke creator (http://ioke.org)
JRuby Core Developer (http://jruby.org)
Developer, ThoughtWorks Studios (http
are not? (:
I think he was referring to all lucky people with 64bit machines... =)
Cheers
--
Ola Bini (http://olabini.com)
Ioke creator (http://ioke.org)
JRuby Core Developer (http://jruby.org)
Developer, ThoughtWorks Studios (http://studios.thoughtworks.com)
Practical JRuby on Rails (http://apress.com
1 - 100 of 373 matches
Mail list logo
