text:
line coloring after running CoverageFunc seems broken

Not sure since when, but when I run the coverage functions, the tests run, output gives the total coverage percentage but all lines are colored as "GocUncovered"

Turns out this is fixed by #5


text:
Scrolling backwards in Circular List Adapter

This works great for going down in the list but backwards it's just like a normal list and hits the start. Is there a way to make it work similar the other way around as when scrolling down? Or I have to scroll down far enough when opening the fragment so I'm sure the user wont scroll whole way back to the start? Thanks

Closing because of this.

source: gharchive/issue

authors: nilsi ragunathjawahar

repo: ragunathjawahar/adapter-kit

license_type: permissive

license_source: bigquery


text:
Define text for error messages and implement

Description
Define text for error messages and implement
Acceptance criteria

Error messages are gathered at one place
Errors are reviewed
Messages fit the space we have (it depends)
Messages avoid tech jargon

Tasks

[x] Start searching for a known way for internationalization for Vue apps
[x] "Translate" the errors
[x] Proof check that error messages fit within the layout

Supporting
See https://uxplanet.org/how-to-write-good-error-messages-858e4551cd4

Closed via #241

repo: raiden-network/light-client

license: MIT

license_source: github-api


text:
between broken with decimal columns

If you try to supply a range made from BigDecimal values (e.g. provided by columns of type decimal), the code breaks.
https://github.com/rails/arel/blob/63ea665c8083f8069a0d05d4f15cf19e08e470a6/lib/arel/predications.rb#L27-L45
It's because you can't compare BigDecimal with INFINITY
> BigDecimal.new(10) == Float::INFINITY
FloatDomainError: Infinity
from (pry):10:in `to_r'

The solution is not to use comparison but to use Float#infinite? and BigDecimal#infinite?
[13] pry(main)> Float::INFINITY.infinite?
=> 1
[14] pry(main)> -Float::INFINITY.infinite?
=> -1
[15] pry(main)> BigDecimal::INFINITY.infinite?
=> 1
[16] pry(main)> -BigDecimal::INFINITY.infinite?
=> -1

The problem this introduces is that it no longer works for Numeric values, e.g. Fixnum and Bignum. However, these can never be infinite.

I have filed a bug report because it might make sense for Numeric to provide #infinite?
https://bugs.ruby-lang.org/issues/12039
Not sure what the best outcome is here, but I don't think this should fail.

Currently, the rough plan is to remove the infinite handling from Arel, and move it into Active Record as a result of https://github.com/rails/rails/commit/6efb39456a8ee3569f3787cc2f26c041365a0e27. Your proposed fix in Ruby would solve this, and is probably the best place to handle it.

Thanks for the quick reply.
What is the reasoning behind moving it to the ActiveRecord code base?

Arel is an AST, not a query builder. We need information that only exists at the AR level for this to be useful.

@sgrif Just thought I'd let you know, that this is now fixed in Ruby.

Thank you for following up.

@sgrif Thanks so much for all your hard work dude, you're awesome!

authors: ioquatix sgrif

repo: rails/arel

license: mit


text:
pre 5.0 gone?

One of the things I love railsdiff the most for is when upgrading an app across a Rails major version boundary.
But today I went to railsdiff.org, and it seems to only know about rails 5.0 and later?
I miss the earlier ones!  It was great to see how a default rails app had changed going way back.
I am not sure if this is intentional or a bug?

I see everything going way back still seems avail at https://github.com/railsdiff/api/tree/master/generated
So maybe this is a bug?

Ah wait, and now the old ones are back for me on railsdiff.org. Temporary bug?

The UI forces you to compare older source version to newer target version. So, if you set the source version as 5.0.0, then the target version options will be 5.0.1+. Perhaps you were just looking at the target options?

I swear I wasn't, I didn't have options before 5.0.0.beta1 available in 'source'....
Aha. Because I was uncharacteristically using Firefox.
In Firefox, no options for source are given earlier than 5.0.0.beta1.
In Chrome no problem.
No idea how this would possibly be browser-dependent, but that's what I'm seeing!

Oh, I see what you're saying. Firefox doesn't give much height to how it displays the <select>'s options dropdown, that said, all the options are there but you need to scroll that small dropdown.

Oh wow, mine cut off RIGHT below 5.0.0.beta1, with no half-line next, and what with that seeming like a reasonable boundary (5.x only), I got confused!

But okay, see what's going on now -- indeed it is scrollable. The bad UX is on Firefox's part I guess. Closing! Thanks!

Thanks for alerting me to your concern.

authors: jrochkind jswanner

repo: railsdiff/railsdiff


text:
adding in mobile support for zeal

We have released our mobile apps now. Adding in mobile support in the Zeal connector

@graadient Thank you for raising this PR 👍
I'll take a look at it shortly, but in the meantime IIRC zeal should support EIP-6963. Can you find the rdns field that they're using and add it to the zealWallet ?

thanks - added the rnds

@graadient Legend!

source: gharchive/pull-request

authors: graadient magiziz

repo: rainbow-me/rainbowkit