yes. im sharing the client tho

was just wondering, if interceptors can be shared, idk the intrinsics of the library. it may broke the procceed chain if i use the same interceptor in two independent clients

im building two instances. thanks tho 😛

if you're sharing the client then the interceptors are shared

i use the same okhttp client, with two newBuilder. and add the interceptors not on the base

ah, i see. it's safe to share them if you want.

ok thanks!

the interceptors are stateless right, so it is safe to share i am guessing

yep that's right. even if they're stateful, they can be called concurrently from multiple threads even in a single client so adding them to additional ones doesn't change anything.

^ That being said, since a

PagedList

only takes a

DataSource

as a parameter, is there any way to propagate new data when the datasource becomes invalidated? That seems like it's handled automatically with livedata, but I feel like there's a better way to handle it without LiveData for SQLDelight

Or maybe there's a flow extension for that?

Willing to wait. If there's an opportunity for a PR here, I'm happy to help 🙂

example URL that gets hit is:

<https://www.someapi.com/posts?request=SearchQuery(> <serialized content>)

Also, I've annotated my SearchQuery class with

@JsonAdapter(SearchQueryAdapter::class)

Sometimes I get reported exceptions like this:

Fatal Exception: java.io.EOFException
       at okio.Buffer.skip + 881(Buffer.java:881)
       at okio.Buffer.clear + 874(Buffer.java:874)
       at okio.RealBufferedSource.close + 462(RealBufferedSource.java:462)
       at okio.RealBufferedSource$inputStream$1.close + 450(RealBufferedSource.java:450)
       at kotlinx.coroutines.io.jvm.javaio.ReadingKt$toByteReadChannel$2.invokeSuspend + 96(ReadingKt.java:96)
       at kotlinx.coroutines.io.jvm.javaio.ReadingKt$toByteReadChannel$2.create(ReadingKt.java:10)
       at kotlinx.coroutines.io.CoroutinesKt$launchChannel$job$1.invokeSuspend + 123(CoroutinesKt.java:123)
       at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith + 33(BaseContinuationImpl.java:33)
       at kotlinx.coroutines.DispatchedTask.run + 241(DispatchedTask.java:241)
       at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely + 594(CoroutineScheduler.java:594)
       at kotlinx.coroutines.scheduling.CoroutineScheduler.access$runSafely + 60(CoroutineScheduler.java:60)
       at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run + 740(CoroutineScheduler.java:740)

It contains no references to my own code. This makes it very difficult to fix these exceptions. I already have debug mode enabled for Coroutines. Does anyone here have any suggestions how I could fix something like this? Thread in Slack Conversation

My SQL is rusty and I have no experience with SQLDelight. I’m trying to create an insert function which returns the inserted row id. I tried this:

insert:
INSERT INTO myTable VALUES (NULL, ?, ?, ?);
SELECT LAST_INSERT_ROWID();

But it still generates a function returning

Unit

you need another named query for the select

but you only need to define it once and then you can re-use it

it is admittedly a bit tedious

I've started to read more about SQLDelight but it seems there's no way to generate runtime Queries and the related issue https://github.com/square/sqldelight/issues/626 is really old. Is this completely off the table for now or is there some kind of undocumented / experimental stuff for that?

Using retrofit 2.6.1 with kotlinx serialization (via

com.jakewharton.retrofit:retrofit2-kotlinx-serialization-converter:0.4.0

) gives me this stacktrace that I'm struggling to work through. Does anyone have any ideas?

i have the following

Team.sq

file:

Team.sq

Kotlin Coroutine Adapter from Jake deprecated?

Yes

When is this feature going to be implemented, if ever? https://github.com/square/moshi/pull/746 Are you sitting on it to implement it with new mpp Okio straight away?

@gpeal Thanks for the tip! https://github.com/square/workflow/pull/576

is it intended functionality for the retrofit declaration with a non-nullable response body (eg.

Response<PaginatedResponse>

) to be nullable from the response?

I have a content provider that essentially triggers the creation of my appComponent. Which in case include Timber logging. The issue is that the tree has not been planted yet (Application.onCreate not called yet). Are there any issues with doing this statically? I.e.:

static {
     if (BuildConfig.DEBUG) {
            Timber.plant(new DebugTree());
        } else {
            Timber.plant(new CrashTree());
        }
}

i have a question about SqlDelight