Port to RxJava 2.

[JakeWharton]

• Maven groupId is now com.squareup.sqlbrite2.
• Package name is now com.squareup.sqlbrite2.
• Query.mapTo* methods now return ObserverOperator instead of Function for use with lift instead of to.
• Backpressure is no longer supported and must be applied with operators.

Closes #136

[JakeWharton]

Lint just spins on the sample. Not sure why...

[iNoles]

You could have put checkReleaseBuilds false or abortOnError false under lintOptions block.

[JakeWharton]

checkReleaseBuilds has no effect, this is the lint task that's running. abortOnError also has no effect as the lint task never completes.

[JakeWharton]

Besides, adding either of those is not correct here.

[albodelu]

As a quick fix, you can try to increase travis_wait (10 minutes by default) to 20 minutes.

This bash function is discussed here and documented here.

You need to add the default script section to .travis.yml like this:

script:
  - travis_wait 20 ./gradlew build connectedCheck

travis_wait is not the better solution because it shows a green build result when a test fails, due to the travis_wait command finishes successfully.

It's only to see what does under the hood.

A better solution would be to try to decrease the requited time or to print something every 8 minutes like this.

# Print delayed 8 minutes
# Print and return the text of this script delayed
function print-delayed {
    sleep 480
    print-mytext "`echo "\n"`"
}

I use it like this:

script:
  - ./execute print-delayed & # Print script text delayed 8 minutes to avoid travis timeout
  - ./gradlew build connectedCheck

A Gradle task would be better in your case, this is only a dirty workaround.

[JakeWharton]

I let it run for 30m locally. It's not a problem with Travis as it should complete in a few seconds. Reverting the Android Gradle plugin update fixed it until we can jump to 3.0.

[arazabishov]

@JakeWharton Is there any particular reason not to use Flowable as a main building block for SqlBrite?

[JakeWharton]

Because the system doesn't support backpressure.

…

On Mon, Jun 5, 2017 at 5:37 AM Araz Abishov ***@***.***> wrote: @JakeWharton <https://github.com/jakewharton> Is there any particular reason not to use Flowable as main building block for SqlBrite? Thanks. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#183 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAEEEVM65fhgaHOoNJoQyha54tvDGIgvks5sA8xcgaJpZM4Nvb3m> .

[arazabishov]

Thanks, good to know.

…

On Mon, Jun 5, 2017, 15:28 Jake Wharton ***@***.***> wrote: Because the system doesn't support backpressure. On Mon, Jun 5, 2017 at 5:37 AM Araz Abishov ***@***.***> wrote: > @JakeWharton <https://github.com/jakewharton> Is there any particular > reason not to use Flowable as main building block for SqlBrite? Thanks. > > — > You are receiving this because you were mentioned. > > > Reply to this email directly, view it on GitHub > <#183 (comment)>, or mute > the thread > < https://github.com/notifications/unsubscribe-auth/AAEEEVM65fhgaHOoNJoQyha54tvDGIgvks5sA8xcgaJpZM4Nvb3m > > . > — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#183 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AD8TPSiXVHH4Duv4qHT9QIO4EGga8nQ2ks5sBAJ9gaJpZM4Nvb3m> .